I go deep.
or I don't go in.
I don't take on tasks just to bill hours. I take them when I understand why it matters to the business and can deliver a result. Usually that means long-term contracts — minimum 3 months, iterations every 1–2 weeks, transparency by default.
Sometimes — focused interventions: when the product is stuck, the backend can't handle load, or a feature hasn't shipped in three months. I come in fast, find the real problem, leave clean code.
Not a fit if
- You need someone to close tickets without context
- The budget is sized for a junior or offshore team
- There's no time for proper onboarding in the first week
- You need results 'yesterday' without a real conversation first
Work formats
Long-term contract
I work as part of the team: get deep into the domain, participate in architecture decisions, ship iterations every 1–2 weeks. Best for stable products that need a reliable engineer for the long run.
- Duration
- 3+ months
- Rhythm
- 1–2 week iterations
- Stack
- Python · FastAPI · Django · PostgreSQL
- Format
- Async-first, calls when needed
Product Rescue
Product stuck: fragile MVP, backend breaking under load, feature not shipping for three months. I come in fast, find the real problem, fix it, and leave clean code behind.
- Duration
- 2–6 weeks
- Rhythm
- Intensive, daily status
- Stack
- Situation-dependent
- Outcome
- Fixed, measurable
Architecture Audit
I look at the code and architecture from the outside: what holds, what will break under load, what slows down development. Written report with concrete recommendations.
- Duration
- 1–2 weeks
- Format
- Review + document + debrief
- Outcome
- Written report
- Optional
- Prioritised change roadmap
Questions & answers
How fast do you respond?
On working days — within a few hours. I work async-first: I prefer written communication over calls, but I don't disappear for a day.
What if the task changes mid-project?
That's normal — it's part of any living project. We note the change, update the scope, move on. I don't cling to the original agreement if it no longer makes sense.
Do you work in a team or only solo?
In a team — yes: code reviews, collaborative architecture decisions, onboarding colleagues. Team lead role is a separate conversation.
Do you take frontend tasks?
No. Backend, API, infrastructure — yes. If you need a fullstack engineer I'll tell you honestly and won't take it on.
Do you give pricing upfront?
After the first conversation about the task — yes. I don't give quotes before understanding the scope and context: it's not fair to either side.
Do you work with NDAs and contracts?
Yes, standard practice. I sign NDAs and work under a contract. I have templates available — happy to discuss.
What does the start of work look like?
Short call (30 min) → one-page scope doc → repo and environment access → first tasks in the first week. No bureaucracy.
Got a task — let's talk
I reply within 24 hours. No sales pitch — just figuring out if we're a fit.