Frequently asked questions.
How engagements start, how I work with teams, and what to expect.
Working together
What kind of projects do you take on?
Backend systems, SaaS platforms, integrations, cloud infrastructure and AI integrations, plus architecture reviews and technical consulting. The common thread is software that has to be reliable in production.
How does an engagement start?
With a short conversation about the problem, followed by a discovery phase to understand requirements and constraints. You get a written proposal with scope, approach and timeline before any build work begins.
Do you work with existing teams?
Yes. I often work embedded with an in-house team, either leading the backend work or advising on architecture while your engineers build.
Can you sign an NDA?
Yes. Confidentiality agreements are standard, and case studies on this site are only published with permission.
Technical
Which languages and stacks do you use?
Mainly Go and Node.js / NestJS on the backend, gRPC, RabbitMQ and Kafka between services, PostgreSQL (with PostGIS), MongoDB, MySQL and Redis for data, and Kubernetes, Terraform and Jenkins for delivery.
Do you rewrite existing systems?
Only when it is clearly the cheapest path. Most systems improve faster through targeted, incremental changes.
Who owns the code?
You do. Code, documentation and infrastructure definitions live in your repositories and accounts.
Careers
Are you open to full-time roles?
I am open to conversations about Senior Software Engineer, Tech Lead and Software Architect positions. Use the contact form and choose "Career opportunity".
Have a complex problem worth solving?
Tell me about the product, the architecture or the engineering challenge. I reply to every relevant inquiry.