I can join for a bounded backend task, take responsibility for a project area, or discuss full-time employment when the company needs a long-term backend owner.
A short diagnostic before a sprint, budget decision, or inherited backend area. Useful when the team needs an outside senior read before committing.
Usually starts with a call, repository or ticket review, and a short written decision note.A bounded backend task with clear release value: API, integration, service boundary, data flow, admin workflow, or production fix.
Works well as a project contract or recurring contractor setup.Regular product work where I own a backend area, reduce release risk, and stay close to product decisions instead of only closing isolated tickets.
This can move toward employment when the scope is durable and the team needs continuity.Suitable for project work, recurring development, and technical consulting when the company needs a contract, invoice, and acceptance documents.
Fast start without adding a full-time position.Suitable when the company prefers to formalize a defined scope through a civil-law agreement.
We fix the result, timeline, handover rules, and acceptance criteria.I am open to employment when the work is long-term, the backend responsibility is real, and the team needs a stable owner for product development.
Most interesting when engineering culture, product decisions, and release ownership are part of the role.We clarify the task, team context, expected duration, and who will make product and technical decisions.
No long discovery stage before we know whether there is a fit.We choose the setup that matches the risk: IP, civil-law contract, trial project, or full-time conversation.
The legal form follows the work, not the other way around.We write down scope, communication rhythm, acceptance criteria, and handover expectations.
This keeps the first release or first month easy to evaluate.