Lead software engineer
I build production software, lead engineering teams, and keep expanding the stack — without leaving the foundations behind.
Lead software engineer with a backend core. A decade in production systems, a path from PHP developer to leading teams, and a habit of treating every new language as an extension of the last.
A decade building software · Full stack · Backend · Cloud · Technical leadership
For hiring teams
The facts a recruiter or engineering leader usually needs first. Detail lives below.
01 — About
I entered software the way durable engineers often do: by learning how business applications actually behave. PHP was the first language that paid the bills and taught me how databases, requests, and real users collide.
That was never the ceiling. Each role asked for more of the system — then more of the people building it. Senior engineer meant owning production. Full-stack meant caring about the interface as much as the query. Technical lead meant the work was no longer only mine.
I still like writing code. I also like the part that does not show up in a ticket: understanding the constraint, choosing the simpler design, and helping a team ship something that holds up.
The stack has changed. The habit has not. Learn the system, then make it better.
02 — Tech journey
Not a list of tools. A record of how the work got larger — from writing features to owning systems, then helping other people ship them.
Learning how backend systems earn their keep.
Business applications, databases, and the unglamorous work of making software useful. PHP taught production before it taught fashion.
Owning larger systems and the problems they create.
The shift from completing work to being accountable for it. Production incidents, data, and the difference between code that runs and code that lasts.
Crossing the boundary between API and interface.
JavaScript and the frontend stack made the product whole. The backend still mattered most — but the user-facing system had to be treated as part of the same design.
Thinking past the ticket.
Helping a team ship software: sequencing work, unblocking people, and keeping the system coherent while the feature list grows.
Broader ownership, still close to the work.
Mentoring, architecture conversations, and the judgment that comes from having built the thing yourself. Leadership as a consequence of understanding — not a replacement for it.
Deepening the modern backend and the systems around it.
Go, Python, FastAPI, Node.js, React, cloud, and distributed systems. The same foundation, a wider range. Still building. Still learning.
03 — Experience
Developer → Senior Developer → Technical Lead → Team Lead → engineering leadership. Titles changed because the scope did.
Dates omitted where they are not on record here. The progression is the point.
Airpay
Most recent role: leading engineering work in a production payments environment. The kind of system where correctness, reliability, and operational discipline are part of the job — not extras.
LearningMate Solutions
The move from individual contribution into technical leadership: helping teams deliver software, keeping the system coherent, and being accountable for more than a single ticket.
Samco Securities
Senior engineering in a securities environment. Larger systems, more ownership, and the production problems that come with software people actually depend on.
Convergence IT Services
Where the professional work began. Learning the fundamentals of backend engineering, databases, and business applications — the foundation everything else is built on.
04 — Engineering stack
Core expertise is what I have shipped with. Exploring is what I am deliberately adding. The distinction matters.
Core expertise
The foundation: production APIs, relational data, and business systems.
Core expertise
Interfaces and clients treated as part of the same system, not an afterthought.
Production & infrastructure
Experience and exposure operating software after it leaves a laptop.
Actively expanding
Honest about the difference between shipped experience and current study.
Also used
WordPress, Joomla, Cordova, Composer, MySQL Workbench, HeidiSQL — tools from earlier product and delivery work, kept in the record because they were part of the job.
05 — How I think
Technologies change. The way I approach a system has been more stable than any one framework.
Reliability and maintainability are not polish. They are the job. Software has to survive real users, real data, and the next person who touches it.
APIs, databases, queues, infrastructure, and the frontend are one design. I would rather see the connections than optimize a single layer in isolation.
The stack has changed repeatedly. PHP remains a foundation, not a fence. New languages get added because the problems got larger, not because the old ones expired.
A ticket is a slice of a business problem. I like understanding the constraint underneath — what the software is actually for — before choosing the implementation.
Technical leadership is more useful when it comes from knowing the system and the people building it. Authority without context is just a calendar.
I still write code. Leadership that drifts too far from the material becomes decoration. I want both: the craft, and the wider ownership around it.
07 — Contact
If you need someone who can go deep on backend systems, work across the stack, and grow into broader technical ownership — without treating any of those as slogans — let’s talk.
The next chapter is the same as the last: stay close to the work, and get better at the systems around it.