Home / Careers

Careers

Open engineering roles in London and Belgrade, the four step hiring process, published salary bands and how we actually work.

Working here

Small team, serious systems, no theatre

Thirty eight people. Everyone senior. Everyone working on commerce platforms that carry real revenue. If you want a large organisation with a career ladder and a lot of process, this is not it.

  • You will own systems end to end, not a ticket queue in one layer of someone else’s design
  • You will talk to clients directly, because the person who built it explains it best
  • You will be on call for what you build, on a rota that is paid and properly staffed
  • You will get time to fix things properly, because the run service makes bad decisions expensive for us too
Nexum Forge engineers working together in a modern office

Open roles

What we are hiring for

We hire continuously for these profiles rather than in bursts. If the role you want is not listed, send us something anyway and tell us what you would want to work on.

RoleLocationExperienceFocus
Senior storefront engineerBelgrade or remote in CET6 years and upNext.js, TypeScript, performance engineering, design systems
Senior platform engineerBelgrade or remote in CET6 years and upNode or Go services, event driven integration, Kubernetes
Integration engineerBelgrade or remote in CET5 years and upSAP and Dynamics interfaces, message driven workers, EDI
Senior QA automation engineerBelgrade or remote in CET5 years and upPlaywright, Selenium, API and contract testing, CI pipelines, load testing with k6
Site reliability engineerBelgrade or remote in CET5 years and upTerraform, observability, incident response, capacity planning
Principal commerce architectLondon10 years and upDiscovery, target architecture, vendor selection, client leadership

Table 12. All roles are permanent. Contract engagements are considered for specialist integration work only.

Hiring process

Four steps, about two weeks

Step 01

Introduction call

Forty five minutes with the engineering lead for the discipline. What you have built, what you want to build next, and an honest description of what the work here actually looks like.

OutcomeBoth sides know whether it is worth continuing.
Step 02

Technical conversation

Ninety minutes reading and discussing real code from a sanitised version of one of our systems. No algorithm puzzles, no whiteboard, no live coding under a timer.

OutcomeWe see how you reason about someone else’s system.
Step 03

Design and incident session

Two hours with a principal architect. Half designing something from a real client brief, half walking through an incident from our own history and deciding what you would do next.

OutcomeWe see how you handle ambiguity and pressure.
Step 04

Offer

Made within two working days of the last session, with the salary band stated up front and no negotiation game. Feedback is given either way, in writing, whatever the outcome.

OutcomeA clear yes or a clear no, quickly.

01

Terms

  • Salary band published in every advert
  • Paid on call rota, never mandatory unpaid
  • Twenty five days holiday plus public holidays
  • Private health cover in both locations

02

How we work

  • Hybrid, two days a week in the office
  • Core hours 10:00 to 16:00 CET
  • No meetings before 10:00 and none on Fridays
  • Four hour minimum focus block every day

03

Growth

  • Conference and training budget per person per year
  • Ten percent of time on internal engineering work
  • Rotation across disciplines when you want it
  • Every engineer writes for the insights section

How to apply. Send a message through the contact form with the role in the message field, or email officeSales@nexumforge.com with your CV or a link to your work. Every application gets a written answer from a person, usually within three working days.

Next step

Tell us what is slowing your commerce platform down

Send the brief. A principal architect reads it, then you get a written technical assessment with options, effort and risk inside five working days. No sales call required first.