Mid-Level Backend Engineer

Mid-level Backend Engineer Amsterdam | Distributed systems | Go, AWS, payment infrastructure | €85k + €20k stock + indefinite contract • Do you want to grow as a backend engineer on distributed systems where a payment has to be correct the first time, and still correct when a device retries? • Would you like to put your teeth into Go services around physical terminals, next to a CTO and a senior team where you can learn an insane amount fast? • And do you say yes to an indefinite contract from day one, up to €85.000 plus €20.000 in stock, in an Amsterdam team with more than 30 nationalities? Then this role is worth your attention. Your employer: payment infrastructure that now also has to work in the shop Every day, money moves through systems most people never think about. For a merchant it should feel instant. Behind that sits infrastructure that has to be available, observable and right, 24/7. Your future employer is an Amsterdam fintech scale-up building that layer cloud-native. Not a checkout widget. Core processing, already in production for serious customers. They are now adding the terminal. A device has to know which merchant it belongs to, which currency, which flows are allowed, how it gets provisioned without ever being able to act for the shop next door. Hardware comes from a partner. This team gets to invent the backend around it. That is the underlying need: you want to become stronger at systems where idempotency, encryption and failure handling are not exam questions. They are why a real shop can take a real payment. Here you still see the effect of your own code, because the company is small enough to know people by name and serious enough that a wrong state is real money. The people are sharp, low-ego and emotionally intelligent. They like CS fundamentals and first-principles reasoning. Strong opinions are welcome when you can walk them to the whiteboard. Your job: Backend Engineer Amsterdam (Go) As Backend Engineer Amsterdam you get the chance to grow in a small Go team that sits next to the CTO. This allows you to learn a lot quickly, be there where there is still a lot of design and have an amazing impact on the success of the company. In this team can put your teeth into the ugly, interesting problems. What happens when a device comes online twice? When a retry would charge twice? When configuration and merchant identity drift? How do you join certified, secure building blocks into something a merchant never has to understand? You take services through design, tests, deploy and production. Battle scars from running your own code are exactly what makes this fun: observability, change management, the 3am path you hope you designed out. Over time you can grow into a stronger senior backend engineer, and even lead engineer or team lead within the company. The path is meters in the code, in a product line that is still being born. What is required • 2 to 6 years as a backend engineer • Experience building and operating services in production, with the battle scars to prove it • Comfort with distributed systems: retries, idempotency, state that has to stay correct • Go in production, or a strongly typed backend language and a real wish to go deep in Go here • CS fundamentals and first-principles thinking; a technical MSc is a strong plus • You explain trade-offs clearly, in English, without hiding behind jargon • High emotional intelligence: low ego, hungry, you like being challenged by people who are better than you Nice to have • Payments, fintech, crypto, infra, platform, embedded • Security, encryption, device-adjacent backend • AWS, serverless, on-call What is offered • Salary up to €85.000 plus €20.000 in stock options, with the solid chance to 10x or more • Indefinite contract from day one • 25 holidays, excellent pension, flexible hours • Hybrid Amsterdam, at least three days in the office, more during onboarding • Travel expense reimbursement, laptop or MacBook • International engineering team, 30+ nationalities Would you like to grow as a backend engineer on problems where distributed systems, idempotency and production ownership actually matter, while a shop somewhere takes a payment that has to be right? Apply via the form or send your CV to Robert Hawker at r.hawker@codeguild.nl.