Currently on a full-time contract
I'm not taking on additional full-time work, but I have capacity for smaller pieces alongside it. If you've got a discrete bit of work that would fit around an existing engagement, get in touch.
What I do
Embedded engineering
Joining a team for a fixed period as a senior IC or tech lead. I'll pick up the difficult architectural pieces, lead the technical direction of the work, review the team's output, and unblock the developers around me. What I won't do is own the team as employees: performance, and the HR side stay with whoever does that already. Best when the team needs senior depth they can't justify hiring full-time for.
Architectural review
Looking at an existing system and writing up what's working, what isn't, and what to do about it. Good fit for teams that have outgrown their original architecture or are about to commit to a major direction and want a senior outside read first.
Greenfield architecture
Designing the shape of a new application before it gets built. This is the work I enjoy most. I prefer to be involved early, when there are still real decisions to make, rather than retrofitting structure onto something already in motion.
Code review on retainer
Recurring deep reviews of a team's output. Not surface-level "did you forget a semicolon" review, but the kind of review that catches architectural drift, identifies emerging patterns worth formalising, and pushes back on shortcuts before they become load bearing. Good for teams with mid-level developers shipping a lot of code without senior oversight.
Specific feature or package work
Discrete builds with a clear deliverable. A piece of infrastructure, a custom package, a critical feature that needs senior judgement. Fixed scope, fixed outcome, in and out.
Writing & content
If you want me to write Laravel articles, documentation, or technical content for your team or product, that's something I'm open to. Same approach as my own writing: source-driven, accurate, willing to be specific about how things actually work.
Technical interviewing and CV review
Sitting in on interviews as the senior technical voice, evaluating candidates' code, or reviewing CVs and take-home tests. Useful for teams that don't have a senior engineer free to spend half a day on a hiring loop, or that want an outside read on their bar. Usually ad-hoc rather than ongoing, and often happens alongside other work.
What I don't do
Code-monkey work
I don't want to follow someone else's plan or stitch packages together to spec. If the design decisions are already made and you just need someone to type them out, you don't want me, and it's not something I'd like to do.
Validation
If you're looking for someone to nod along with decisions you've already made, you'll be disappointed. I'll tell you what I think, including when I think you're wrong.
Employee management
Happy to lead a team through a piece of work: breaking it down, reviewing it, unblocking the developers, making the technical calls. Not interested in owning the employees themselves: performance reviews, 1:1s, career progression, the HR side. If you need a tech lead, that's me. If you need an engineering manager, that's a different hire.
How it works
Engagements vary. Hourly, daily, fixed project, monthly retainer, depending on what makes sense for the work. I'll usually suggest a shape after the first conversation rather than asking you to pick one up front.
First contact is the form below. Tell me roughly what you're looking for, what shape it might take, and what timeline you're working to. I'll come back with whether it's a fit and what I'd suggest from there. If it's clearly not a match, I'll say so.
Get in touch
I haven't put testimonials on this page. If you want to know how I think and what I build, the articles and projects are a more honest read than a paragraph from a previous client could be. Spend ten minutes with The Hidden Parts of Laravel or Sprout's documentation and you'll know whether we'd work well together.