01
Join your team
A senior engineer inside your team. I work in your codebase, standups and code reviews, and stay long enough to own a real part of the product. Under the hood: Laravel, Node.js, Python or AWS.
Full-time or long contract
Seven years of MySQL in Laravel apps, plus PostgreSQL where the product needed it. The pattern is the same: a report written as a loop, a missing index, a cache that was never invalidated on purpose.
I read the slow log and the actual screens. Then I change the query, add the index, or move the heavy read behind Redis. RDS read replicas when the primary should only take writes.
I do not “optimize” by adding hardware first. If the query is wrong, a bigger instance just hides it until the next launch.
What this includes
- •Slow-query review against the screens people actually open.
- •Composite indexes and query rewrites aimed at sub-100ms reads.
- •Redis caching with a clear invalidation rule, not a forever key.
- •Read replicas and backup checks on RDS so a restore is a drill, not a theory.
- •A short note on what changed, so the next person does not undo the index.
What you leave with
- •Pages that waited on the database stop waiting.
- •A primary that is not also serving every report.
- •A cache you can explain, not a layer nobody dares to clear.
How it starts
Send the slow screen or the slow endpoint. I trace it to the query, ship the fix, and show the before and after.
When to use it
Use this when the product is live and the complaint is speed, not a missing feature.
Engagement
Ways to work together
02
Work solely for your company
A dedicated engineer for one company. I take the product from planning to the live version: backend, data, hosting and screens, with your product as my focus.
Dedicated contract
03
One project
A clearly defined build, then a clean handover: an MVP, taking an AI-built prototype (Lovable, Bolt, Cursor) to production, a migration, or an AI feature. Get in touch to discuss scope and pricing.
Fixed-scope project