Backend engineering
Designing application logic, service boundaries, APIs, integrations, and systems that support real business workflows.
I’m a senior full stack engineer with experience across Laravel, Vue, Node.js, Java, Spring, MySQL, MongoDB, Oracle, CI/CD, and product-focused delivery. I’ve worked on SaaS platforms, internal tools, workflow-heavy applications, and systems where backend architecture matters just as much as the UI.
I’m the kind of engineer who likes clarity: clear systems, clear responsibilities, and software that behaves predictably under real usage. I’m strongest when a team needs someone who can think across the stack, reason through architecture, and still stay close to product and delivery. I tend to do my best work on systems that are operationally important, not just visually polished.
Use the filters to scan the stack quickly. This is the kind of tooling I’ve worked with across product development, enterprise software, and operational systems.
Designing application logic, service boundaries, APIs, integrations, and systems that support real business workflows.
Building admin interfaces, dashboards, and product-facing workflows with an eye for usability and operational clarity.
Comfortable with relational and document databases, query optimization, stored procedures, and data-backed application design.
Supporting the path from development to deploy with practical CI/CD, Linux, server, and environment work.
Experience acting as tech lead and shaping service design, logical flow, and architecture decisions for new systems.
Translating ideas into production software by moving between frontend, backend, data, and implementation details without losing the product thread.
Experience working inside large products with mature codebases, heavy data requirements, and long-lived application logic.
Tech lead experience, cross-functional delivery, and the ability to help move projects from concept through implementation with other engineers.
These projects reflect the kind of work I naturally gravitate toward: software with meaningful workflows, real users, and a lot of practical engineering underneath.
A MERN stack trivia platform used in hundreds of restaurants, schools, and corporate offices. It’s the kind of product I enjoy building most: realtime, user-facing, operationally practical, and shaped by how people actually engage with it in live environments.
MongoDB · Express · React · Node.js · realtime product flows · live-hosted usageA digital voting and governance platform built for HOAs, condo boards, and associations. The interesting engineering here is in workflow design, trust, admin tooling, backend coordination, and making a sensitive product feel reliable.
Workflow systems · admin interfaces · backend coordination · product iterationA live audience-voting bracket platform where people join from their phones and affect outcomes in real time. This kind of work hits a nice mix of product simplicity, timing, UX, and state management under the hood.
Realtime flows · engagement UX · event-driven product thinkingA lesson-planning platform oriented around curriculum alignment and teacher workflows. A good example of software where a strong product outcome comes from reducing friction in a structured daily process.
Workflow design · SaaS product thinking · full stack deliveryA caregiver dispatch and scheduling platform coordinating availability, routing, and real-time operational visibility. This is the kind of system where backend clarity matters because real-world operations depend on it.
Scheduling logic · logistics workflows · operational softwareA legal-tech platform for intake, role-based workflows, and document-driven service delivery. Systems like this are a reminder that software quality often starts with modeling the business process correctly.
Role-based systems · workflow tooling · backend process modelingI’m at my best on products that need clear architecture, strong backend thinking, and someone who can move between data, services, UI, and delivery without losing the shape of the product.
Architecture · maintainability · execution · product judgmentMore than a decade building software across enterprise products, SaaS platforms, internal systems, and full stack applications.
Worked as a full stack developer across several applications, contributing across backend, frontend, and delivery. The role also included leadership responsibilities when moving projects from concept into production.
Developed and maintained multiple applications in a SaaS environment, balancing feature delivery with architectural thinking and service design.
Worked on a talent management system, shipping enhancements, fixing bugs, and building internal product tooling within a fast-moving agile environment.
Built and maintained scalable code for a core student information system, working across backend application logic, frontend frameworks, and enterprise data systems.
Different teams and products, same priorities: understand the workflow, design the system carefully, and keep the implementation practical.
I like understanding the workflow, tradeoffs, and user outcomes behind a system — not just the tickets attached to it.
A lot of the value in software lives behind the UI: permissions, data modeling, integrations, service design, and business logic.
I care about maintainability, but I’m not interested in overengineering. The goal is software that’s reliable, clear, and able to evolve.
I’m usually the best fit for teams building meaningful products or internal systems that need someone comfortable across architecture, backend logic, frontend delivery, and execution.