Brandon Mojica logoBrandon Mojica

About

Software engineer focused on software architecture and backend systems, designing and leading the evolution of business-critical platforms.

ENGINEERING PROFILE

Software engineer focused on software architecture and backend systems.

I design and lead the evolution of business-critical platforms around real operational constraints.

My work connects business rules, domain modeling, backend architecture, and maintainable APIs across enterprise and financial workflows.

I design and evolve ERP, credit, and financial systems by translating domain rules into explicit services, APIs, state transitions, and operational controls.

The focus is practical: make boundaries clear, keep rules close to the domain, and build systems that can evolve without losing operational clarity.

ERP Platforms
Backend Architecture
PostgreSQL
System Design
Engineering Workflow

Systems I design and build

Systems shaped by real operational constraints rather than demonstration assumptions.

Enterprise platforms

ERP platforms that integrate finance, sales, inventory, human resources, dashboards, and accounting workflows.

Backend service architecture

API platforms with explicit business logic, traceable state transitions, and clear service boundaries.

Financial systems

Credit, interest, payments, reconciliation, and account statements where consistency and traceability are part of the architecture.

Professional path

A progression inside real business operations, from QA and junior development through project leadership, systems leadership, and full-stack development.

I joined Elements Of Steel in 2019. Over time, my work progressed through QA, junior software development, project leadership, and ultimately Head of Systems together with full-stack software development.

The focus throughout this progression has been connecting software with the real needs of business operations. I design and evolve systems where domain rules, service boundaries, and maintainability are part of the engineering work.

My academic background includes a Computer Systems Engineering degree and a Master’s Degree in Data Science for Business from UTEL.

How I engineer software

In current work, I use specifications and architecture-first planning to make scope, constraints, decisions, and acceptance evidence explicit before implementation.

Problem framing → Discovery → SDD / Architecture → Implementation plan → Specialized AI-assisted roles → Implementation → Independent review → Evidence / QA → Release gate

AI can accelerate bounded analysis and implementation support, but engineering responsibility remains human. Handoffs record decisions, evidence, open questions, and acceptance criteria.

Architecture principles

Architecture should reduce operational risk and make system complexity explicit, understandable and evolvable.

Model the business before the code

Start with business flows, responsibilities, and failure points before designing the technical model.

Keep logic close to the domain

Use service layers and explicit domain logic instead of thin CRUD around the database.

Make boundaries explicit

Clear domain boundaries and expressive APIs help systems evolve without becoming fragile.

Design for traceability

Predictable state transitions, auditability, and operational controls belong in the system model from the beginning.

Technology focus

A curated technical focus for designing, building, and evolving enterprise systems with a strong backend orientation.

Backend & APIs

Python
FastAPI
SQLAlchemy
Pydantic
REST APIs

Data & Persistence

PostgreSQL
MySQL / MariaDB
Relational integrity
Transaction boundaries

Architecture & System Design

Domain modeling
Concurrency
Idempotency
Authorization boundaries
Multi-tenant isolation

Product, Platform & Workflow

React
TypeScript
AWS
Nginx
SDD
Independent review
Release gates