About | Brandon Mojica

ENGINEERING PROFILE

Backend Engineer and Systems Architect focused on enterprise platforms, API architecture, and critical software for finance and operations.

I design and build systems where operational clarity, domain modeling, and backend reliability matter more than surface-level complexity.

My work is centered on ERP platforms, financial systems, and API-driven backend platforms used daily by operational and administrative teams.

That means translating real business rules into stable architecture, defining service boundaries, and building backend platforms that can evolve without disrupting operations.

ERP Platforms

Backend Architecture

Financial Systems

FastAPI

AWS

What I Build

Platforms shaped by operational constraints, not demo assumptions.

Enterprise platforms

ERP and internal systems that integrate finance, sales, inventory, human resources, and reporting into a single operational model.

Backend service layers

API platforms with explicit business logic, traceable state transitions, and service boundaries that support long-term maintainability.

Financial workflows

Credit, payments, reconciliation, statements, and account controls where correctness and auditability are part of the architecture.

Professional Background

A profile shaped by building systems inside live business operations.

I currently lead systems architecture and internal platform development at Elements Of Steel, where since 2019 I have been responsible for designing, building, and evolving systems that are critical to business operations.

The most representative example of that work is Businext ERP, an enterprise platform built from scratch to support finance, sales, inventory, human resources, operational dashboards, and administrative workflows in production.

My academic background includes a Bachelor's degree in Computer Systems Engineering and a Master's degree in Data Science for Business, both from UTEL. That combination strengthened both my software engineering discipline and my approach to data-informed decision making.

Verification and public references

This portfolio is backed by public professional profiles and engineering writing that align with the systems described across the site.

LinkedIn GitHub Contact

How I Think About Systems

Architecture should reduce operational risk and make complexity easier to reason about.

Model the business before the code

I start from workflows, responsibilities, and failure points before designing the technical model. Useful architecture reflects how the business actually works, not the other way around.

Keep logic close to the domain

In business systems, correctness depends on where rules live. I prefer service layers and explicit domain logic over thin CRUD wrappers around the database.

Optimize for maintainability under growth

Systems become expensive when every module knows too much. I care about boundaries, naming, and evolution paths so platforms can absorb new features without turning fragile.

Treat reliability as a design decision

Auditability, predictable state transitions, and operational visibility are not post-launch concerns. They should exist in the system model from the start.

Technology Focus

Tools I use most often to build and operate backend-heavy systems.

Backend

Python

FastAPI

SQLAlchemy

Pydantic

REST APIs

Frameworks and supporting libraries

Frontend

React

TypeScript

TailwindCSS

MUI

Axios

Infrastructure

AWS EC2

AWS S3

Linux

Nginx

Production deployment

Architecture

ERP systems

Microservices

Service layers

DDD concepts

Operational automation

What I'm Looking For

Work where backend engineering and systems thinking directly influence the quality of the product.

I am interested in roles where backend engineering and systems thinking directly influence product quality.

I want to contribute as a senior backend engineer or systems architect on platforms where I can design and evolve complex systems.