Hire me when you need senior engineering capacity that works with the team you have, the codebase you have, and the amount of time people actually have.
Most engagements run for a couple of months with a team of three to seven. I join as a contributor: stand-ups, reviews, planning, pull requests from day one. No need for perfect tickets, full technical designs, or two weeks of hand-holding before I can help.
Good fit
- You have a product team that needs senior hands without weeks of onboarding.
- Your technical lead, product owner, or senior engineers are stretched.
- The work involves domain complexity, legacy decisions, delivery pressure, or missing context.
- You want someone who contributes, reviews, asks questions, and improves the shape of the work.
Does one or more of these describe you? Then we're a good fit.
Pull requests from day one
Image: GitLab
I use AI tooling to get up to speed quickly on unfamiliar codebases, and I've been reading domain-heavy business software long enough to know where the real complexity hides. The business rule behind the function. What breaks when you change it.
I do not need the ideal setup before I can help. I can become useful before the team has had time to write down everything it knows.
Less load on senior people
When senior engineers, technical leads, or product managers are stretched, the last thing they need is another person to manage.
I take direction in the shape you have it: ticket, design note, conversation, failing test, bug report, or vague concern. I ask the missing questions, make the trade-offs explicit, and turn the work into pull requests. Sometimes that means implementation. Sometimes it means a small technical design first. Sometimes it means going back to the product question because the code is not the hard part yet.
When the domain is fuzzy, I reach for event storming or event modelling to make it explicit. I use AI for research and option comparison, then bring the result back to something the team can decide on.
Technical excellence
Image: GitLab
I care about the code being understandable six months from now. Good naming, clear boundaries, focused objects, and tests that catch real mistakes. That is technical quality as a product concern, not as a hobby.
- Object-oriented design: PHP, C#, Java. Code organized around the domain, with names and boundaries that help the next person recover context.
- Test automation: Behavior-driven development with Behat, Gherkin, or Cucumber. Mutation testing with Infection (PHP) or Stryker to check whether the tests would catch a real bug, not just pass by coincidence.
- Database work: Strong SQL in MySQL and PostgreSQL. I can work directly with the data model, write the query, and still keep the application code understandable.
- Stack and delivery: Laravel and Filament for PHP projects. CI/CD, Docker, GitLab, and the everyday work of getting changes reviewed, tested, and shipped.