Software Engineer (Fullstack)
Posted Updated
Description
- We are looking for a Fullstack Engineer with a keen interest in the development of modern web platforms, as well as the ambition for personal growth and innovation. As part of a cross-functional team, you’ll be taking a lead on some of the most important and core parts of our platform
- We’re a distributed team of engineers who believe in full ownership — not just of code, but of outcomes. Currently 6 strong and growing to 8, our team spans multiple countries and time zones, with a growing presence in Amsterdam
- We’re a true full-stack team. That means everyone has working knowledge across the stack, can pick up any part of the product when needed, and collaborates directly with product to shape what we build — not just how we build it. There are no silos here. You won’t be handed a spec and asked to execute; you’ll be expected to question, contribute, and own
- You’ll spend roughly 70% of your time on backend (Node.js, TypeScript, APIs, cloud infrastructure) and 30% on frontend (React, TypeScript). You’re not expected to be a specialist in both — but you are expected to be genuinely capable across the stack and comfortable context-switching between the two
- This is a role for someone who owns their work. That means being involved from the moment a problem is identified, helping break it down, making sound architectural decisions, shipping it, and making sure it stays healthy in production
- Design and build robust, scalable backend services and APIs using Node.js and TypeScript
- Develop and maintain React-based frontend interfaces that are performant and maintainable
- Collaborate closely with product and design to shape features from discovery through to delivery — not just implementation
- Take ownership of your work end-to-end: scoping, building, shipping, monitoring
- Contribute to and improve CI/CD pipelines, deployment processes, and cloud infrastructure
- Write secure, well-tested, production-ready code with real uptime requirements
- Participate in code reviews, architectural discussions, and technical decision-making
- Help maintain the reliability and observability of production systems — and respond when things go wrong
Benefits
- Awesome office, wear what you want
- Help build a unicorn
- Responsibilities, not tasks
- Focus on (personal) growth
- 50/50 office and remote
- We’re looking for a Full Stack Software Engineer at the upper mid-level — someone who is beyond executing tasks and is ready to drive meaningful technical work end-to-end
- Hands-on experience with cloud infrastructure — AWS, GCP, or Azure — in a production environment
- A working understanding of CI/CD pipelines and modern deployment practices
- A genuine sense of ownership — you don’t wait to be told what to do next, and you don’t consider your job done when the code is merged
- Strong, production-proven experience with Node.js and TypeScript — you know the ecosystem deeply, not just the basics
- The ability to work closely with product teams — you can translate between technical constraints and business needs, and you’re comfortable pushing back when necessary
- Solid React.js experience building and maintaining real frontend applications
- A security-conscious approach to development — you think about attack surfaces, data handling, and least-privilege access as a matter of habit
- Based in or willing to relocate to Amsterdam, Netherlands (preferred but not required)
- You’ve built and shipped production systems that real users depend on
- Experience in fintech — particularly payments, transactions, or regulated financial systems
- Terraform experience for infrastructure-as-code
- AWS experience specifically (preferred over other cloud platforms)
- Kubernetes for container orchestration
- You’ve been in an incident, diagnosed it, fixed it, and made sure it doesn’t happen again
- You’ve sat with a product manager to figure out what to build — not just been handed a ticket
- You write TypeScript that actually leverages the type system
- You’re not the most senior engineer in the room, but you don’t need to be — you’re the kind of engineer who makes the people around them better
- You think about what happens when your code fails, not just when it works
