FREELANCE SOFTWARE DEVELOPER / SANTO DOMINGO, RD

FRANCISCO
CASTRO — Software Engineer, Santo Domingo, DR

I build software that survives contact with real operations.

Full-stack systems, enterprise integrations, and the architecture connecting them.

LIVE ARCHITECTUREFLOW / ACTIVE
ENGINEERINGIN MOTION2026 / DR

01 / SELECTED SYSTEMS

Built for the complexity
behind real operations.

IN PRODUCTION / 2026

FieldReport

An offline-first mobile workflow for field technicians, synchronizing completed service work when connectivity returns.

OFFLINESYNCERP
  • Flutter
  • .NET
  • SQL Server

IN PRODUCTION / 2026

MyFleet

A customer portal centralizing vehicle status, service history, orders, and maintenance appointments across companies.

CLIENTPORTALBC
  • Angular
  • .NET
  • Business Central

IN PRODUCTION / 2026

Deployment Infrastructure

One reusable delivery workflow coordinates multiple projects, environments, and self-hosted Linux and Windows runners.

  • GitHub Actions
  • YAML
  • Linux
  • Windows Server

02 / SERVICES

Software built for how your business actually operates.

01

Custom Web & Backend Systems

APIs, admin dashboards, and internal tools built on .NET and Angular for real business rules, not templates.

  • .NET
  • ASP.NET Core
  • Angular
02

Offline-First Mobile Apps

Flutter apps for field work and point of sale that keep running without connectivity and sync automatically.

  • Flutter
  • SQLite
  • Sync
03

ERP & Business Central Integrations

Connect existing systems to Microsoft Dynamics 365 Business Central without disrupting daily operations.

  • AL
  • SOAP
  • REST
04

Architecture & Technical Consulting

System design, code review, and technical decisions for teams building software meant to survive production.

  • Design
  • Review
  • Advisory
Discuss a project

HOW WE'D WORK TOGETHER

  1. 01Free discovery call

    We talk about what your business needs. No cost, no commitment.

  2. 02Scoped proposal

    Clear deliverables, timeline, and price before anything starts.

  3. 03Build in phases

    You see progress along the way, not just at the end.

  4. 04Delivery & support

    Handoff with documentation and a support window after launch.

Currently taking on select projects alongside full-time work. Response within 24 hours.

03 / HOW I BUILD

Screens are surfaces.
I build the system beneath them.

01

DOMAIN BEFORE ENDPOINTS

Understand the business rules first. Then decide what the API, data, and interface need to become.

02

FAILURE IS PART OF THE DESIGN

Connectivity drops. Existing systems constrain. Good architecture accounts for reality, not just the happy path.

03

INTEGRATE WITH WHAT EXISTS

Real companies already have workflows and systems. Useful software must coexist with both.

04

SHIP → OBSERVE → IMPROVE

Architecture earns its value in production, where feedback turns design decisions into better systems.

04 / EXPERIENCE

Software inside
the operation.

JAN 2026
PRESENT

MINECON S.A.

Full Stack Developer

Building web and mobile applications integrated with Business Central for multiple companies. The work covers operational automation, multi-company architecture, REST and SOAP integrations, offline synchronization, and deployment infrastructure.

  • Enterprise applications
  • ERP integrations
  • CI/CD infrastructure
BACKEND

C# / .NET / ASP.NET Core / EF Core

FRONTEND

Angular / TypeScript

MOBILE

Flutter / Offline sync

ENTERPRISE

Business Central / AL / SOAP

DATA

SQL Server / PostgreSQL / SQLite

DELIVERY

Linux / Docker / GitHub Actions

CREDENTIALS

  • AWS Cloud FundamentalsAWS
  • Cloud — Advanced LevelTalento Digital.do
  • Angular: Zero to ExpertUdemy
  • SQL AssociateDataCamp
  • Python Data AssociateDataCamp
  • Software Architect Mindset WorkshopDev Senior Code

05 / ABOUT

I am a full-stack developer from the Dominican Republic. I study Software Development at ITLA while building software used in day-to-day business operations.

I like tracing a problem past the screen: into its rules, data, failure modes, integrations, and operational consequences. I am growing toward architecture and technical leadership by learning to explain decisions as clearly as I implement them.

STATUS / LEARNINGDistributed systems · Event-driven architecture · Cloud architecture · Technical leadership

06 / CONTACT

Have a real system
worth building?

LET'S TALK
SANTO DOMINGO / DOMINICAN REPUBLICGITHUB ↗LINKEDIN ↗

QUICK NAVIGATION

↑↓ NAVIGATE / ENTER SELECT / ESC CLOSE

CASE STUDY / 01

Stamping Taller

Modernizing a workshop operation without losing the workflows that keep it moving.

01 / CONTEXT

Operational software across companies

The platform supports the service-order lifecycle and connects web and mobile work with Microsoft Dynamics 365 Business Central.

02 / CONSTRAINTS

Legacy behavior, live operations

Part of the work replaced a legacy application with no available source code. The new system also needed company-specific rules without separate product versions.

03 / ARCHITECTURE

A domain-centered integration layer

An Onion Architecture separates application and business rules from Angular, Flutter, SQL Server, SOAP, and Business Central concerns.

04 / IMPLEMENTATION

Critical flows, end to end

My contribution covered requirements, critical modules, reception and vehicle-checklist workflows, wizards, data models, RDLC reports, PDF generation, email notifications, and business validations.

05 / OUTCOME

One maintainable platform

The result is a production system used by multiple companies, integrating workshop traceability and service-time records with the ERP.