We’re looking for a backend engineer who thinks beyond code – someone who not only builds APIs and services, but also cares deeply about how they run in production, how they scale, and how easy they are to operate and observe.
You’ll join a small, fast-moving team building a SaaS platform on top of Supabase and AWS Fargate. We don’t run Kubernetes and we don’t need to – but we do need engineers who are pragmatic, production-minded, and who can design systems that are simple, reliable, and maintainable.

🔭 What you’ll do:

• Design, build and maintain scalable backend services (TypeScript, Node.js, SQL/PostgreSQL, Redis)
• Write clean, maintainable code and thoughtful interfaces
• Take ownership of production readiness (observability, alerting, performance)
• Collaborate on internal tooling and improve dev workflows (e.g. monorepo, CI/CD)
• Help evaluate and integrate pragmatic tools – from monitoring to AI-based dev tools
• Investigate issues across the stack (infra, DB, API) and propose improvements
• Collaborate closely with product and other engineers in a fast-moving environmentWhat you’ll do

🧠 What we’re looking for:

• Solid experience building and maintaining production backends
• You’ve been on-call before or felt the pain of systems that don’t scale well
• Strong SQL/PostgreSQL skills and understanding of data modeling
• Hands-on experience with observability tooling (Grafana, Prometheus, or similar)
• A pragmatic mindset – you know when to build, when to buy, and when to simplify
• Bonus: experience with Supabase, Fargate, or serverless architectures.

💡 Why this role might be interesting:

• You want to build things end-to-end: from database schema to production dashboard
• You like simplicity and want to avoid overengineering
• You enjoy improving not just the product, but the way the product is built
• You want to work in a team that values high trust, low ego, and direct communication

We are looking forward to your applicaton! 🙂

-----

Hiring Prozess:

1. 15' Screening Call - phonecall / videocall

2. 15' CTO Call - videocall

3. 45' Peer Coding 1 - in the office

4. 45' Peer Coding 2 - in the office

5. 30' Founder Ref Call - videocall / in the office