Senior Backend Developer Available by the Hour
Code review, architecture consulting, and small well-defined tasks. No retainer, no project scope — you book the time, we use it on what you need.
When hourly makes sense
Not every problem is a project. Some things are too small, too undefined, or too advisory to justify a fixed-scope engagement — but they still need a senior developer's attention.
Hourly work is the right format when you need focused, skilled time without the overhead of scoping a full project. The minimum is 4 hours — enough to go deep on something specific and come back with something useful.
What you can use the time for
- Code review — a focused read of a specific part of your codebase, with written feedback on correctness, security, and maintainability
- Architecture consulting — advice on a technical direction before you commit to building it; webhook design, database schema, API structure, service boundaries
- Technical due diligence — reviewing a codebase you're considering acquiring, hiring for, or depending on
- Debugging and diagnosis — finding the root cause of a production issue or persistent bug that your team hasn't been able to isolate
- Small, well-defined tasks — a specific integration, a configuration fix, a one-off script, or a tool that doesn't need a full project scope
- Second opinion — if your team has made a technical decision and you want an outside read before shipping it
What hourly is not good for
Hourly work doesn't suit open-ended or ongoing development. If you always have something in the backlog and expect to keep needing development support, a monthly retainer is more efficient — no renegotiation each time, priority access, and a developer who already knows the codebase.
Similarly, if you have something specific to build with a clear outcome, a fixed-scope project gives you a flat rate and a defined deliverable, which is usually better value than hourly for anything over 10–15 hours.
How a session works
You send a description of what you need covered and the relevant context — a link to the repo, a description of the system, the specific question or area to review. We agree on the number of hours. I do the work and deliver findings in writing — not a call, a document you can reference later.
If the work runs over the booked time and you want to extend, we agree on it before continuing. No silent overruns.
Frequently asked questions
What is the minimum booking?
4 hours. Anything smaller doesn't allow enough depth — even a focused code review benefits from time to read context, ask questions, and write up findings clearly.
How does billing work?
For a fixed block (4-hour review session, for example) the full amount is invoiced upfront. For ongoing hourly work, billed weekly with a time log. Rate is €100/hr.
Do I get a call or a written deliverable?
Written. A call produces nothing you can reference later. Written feedback is more useful, more specific, and forces clarity. If a call is genuinely the right format for something, we can discuss it — but the default is written output.
Can this lead into a longer engagement?
Yes. Some clients start with a few hours to evaluate fit, then move into a fixed-scope project or a retainer once the direction is clear. No obligation either way.
What stack do you work in?
Go, Node.js / Express, vanilla JS for tooling, self-hosted infrastructure. Backend and infrastructure only — not frontend frameworks or mobile.
Book time
Describe what you need covered — code review, architecture question, debugging, or a small task. Include the relevant context and how many hours you think you need.