Founding Engineer

0TO9 is a bank for entrepreneurship built by and for financial innovators. We provide infrastructure for entrepreneurs ready to start and scale the next generation of financial products and platforms. Founded in 2025 were already 200 co-workers across Europe and growing fast. Our name reflects our mission: from zero to success from idea to impact from now to whats next.

Were early and in stealth so heres what we can say: its a new banking business separate from anything else in the group aimed at a market we think is badly served today. The company is already led by a CEO. The customer the product and the wedge are what youll help us find.

What were not doing is a hiring cycle to backfill a team. Youre early enough that the first architecture calls the first engineering culture and a good share of the product thinking are genuinely yours.

This is the part wed be lying about if we said everyone does it.

We build on .NET and SQL on the backend and TypeScript on the frontend (React and Vue). Prior experience in these helps but it isnt the bar what matters is that you want to build in them. Agentic tools make an unfamiliar stack cheap to learn; they dont make an unwilling one work. The fundamentals below are what we cant teach you in the first month:

• Engineering standards loaded as a skill so agents apply them automatically.

• A git-backed knowledge base that agents read and extend.

• Agent workflows that take a change from branch to reviewed PR.

• An automated reviewer in CI that counts as an approving review on a pull a team of one that last one matters.

Were not looking for someone curious about whether this works. Were looking for someone who already builds this way - and will push it further than we have.

1. Compress the distance between idea and working software: prototype put it in front of real people and let what you learn kill or grow it. Implementation is the fast part of this job; deciding what deserves to exist is the hard part.

2. Sit close to the problem not the backlog: youll be in customer conversations and in the room where the business model gets argued about. We expect that to change your technical choices not just inform them.

3. Make fast reversible decisions: simple boring architecture that can be thrown away. We dont have scale yet and pretending otherwise is the most expensive mistake available to us right now.

4. Set how engineering works here: tooling workflow standards guardrails for whoever joins after you.

Agentic tools help you pick up anything unfamiliar fast - but these fundamentals should already be there:

• Backend: .NET and SQL.

• Frontend: TypeScript React and Vue.

• AWS-native: ECS/Fargate S3 least-privilege IAM.

• Container fluency: build ship and debug in production.

• Security by default: WAF encryption at rest and in transit.

• EU data residency: aware of why region matters (eu-north-1).

• Microservices & DDD: boundaries by domain not layer.

• API/event-driven: no shared databases.

• Resilience patterns: retries backoff idempotency.

• Clean SOLID code: safe for a human or an agent to extend.

• CI/CD fluency: GitHub Actions or equivalent.

• Test-driven habits: 80% coverage no exceptions.

• Reviewable PRs: small diffs no self-merges.

• Supply-chain hygiene: dependency & SCA scanning before ship.

• Structured logging & tracing: CloudWatch Datadog or equivalent.

• Zero hardcoded secrets: Secrets Manager or equivalent always.

• Encryption everywhere: KMS at rest TLS in transit.

• .NET / TypeScript experience: youll ramp faster. Coming from another ecosystem is fine if youre genuinely happy writing C#.

• Fintech / regulated-industry background: youll ramp faster.

• Agentic tools as your daily driver: Claude Code Cursor or similar.

• Builder not just coder: youve shipped real products (side projects count) and know the difference between working and done.

• AI-native: you already lean on LLMs and agentic tools daily and are curious how far that can go you see them as leverage not a shortcut.

• Comfortable with ambiguity: you dont need a fully specified problem to start making progress.

• Business-minded: you can hold a conversation about unit economics customer needs or go-to-market and let that shape your technical choices.

• Pragmatic generalist: deep specialization matters less than range and judgment; you can move across the stack as needed.

• Within weeks not months youve helped ship a working prototype we can put in front of real users.

• Youve established a lightweight AI-augmented way of building that lets a tiny team punch far above its weight.

• The founders trust you as a thinking partner not just a pair of hands.

• Whoever we hire next inherits a codebase and a way of working thats simple fast and easy to build on.

Find out more at wed love to hear from you!