(Senior) Node.js Developer - Freelance

Netguru is a trusted partner in digital commerce. The company helps leading brands modernize B2B solutions, marketplaces, and retail ecosystems. Since 2008, it has empowered businesses with cutting-edge technology, AI-powered personalization, and world-class engineering and design teams. A certified B Corporation®, Netguru is trusted by major brands including IKEA, VW, OLX, Delivery Hero, Żabka, Wolt, Careem, and Vinted.

How freelancing works at Netguru?

As a Netguru freelancer, you can choose what works well for you. You decide when, where, and how you work on projects and tasks. 

We match you with work that fits your skills. Plus, you have access to various opportunities across different industries and companies. That means you will not only gain more experience, but also develop various skills.

But there's more. Netguru freelancers can benefit from full-time collaboration and really be a part of the team.

So, are you ready to make an impact? Join Netguru, and let's build beautiful software together.
We are looking for a Senior Node.js Developer

This role is fully remote, we accept candidates from anywhere around the globe, given that candidates are within an acceptable time-zone difference to UTC+4 (at least 5 hours of overlap)

Salary: up to 35 EUR/h (on a B2B)

Start date: September 2026

Duration: till 31.12.2026

Engagement: Full-time

We are looking for Software Engineers with:

(roughly 5-8 years of experience), able to do without supervision:

Design services using well-understood patterns for iterative, autonomous development and future scaling - bounded contexts, deliberately minimizing cross-service dependencies for resilience.

Design for expected peak load rather than average, know the limits of the services and third-party dependencies a feature relies on, and validate those limits by testing rather than by reasoning alone.

Build components other teams can adopt, with documentation and a migration path - treating other teams as consumers, not recipients.

Diagnose issues across service boundaries, not only within a single service.

Write architecture decision records that capture why a decision was made, not only what was decided.

Design with abuse in mind by default — rate limits, velocity checks, idempotency - and raise risk trade-offs during design and review rather than after launch.
Also required:

• Reading and being able to explain every line of AI-generated code you ship - no merging what you can't explain.
• Testing that actually covers edge and failure cases, not just happy-path coverage.
• Working command of OWASP Top 10 and secure-by-default habits (secrets management, input validation, data handling).
• Strong written English - most collaboration happens asynchronously via RFCs and reviews.
• A collaborative style: you bring options with trade-offs, argue with reasoning rather than seniority, and can lose a technical argument gracefully.

Responsibilities:

This isn't a "managed team" gig and it isn't ticket-closing work. The client has strong internal engineers already — what they're bringing in is deep system design judgement: help deciding what to build, where the boundaries sit, what breaks first under load, and what's expensive to change a year from now. You'll pair directly with their engineering manager and team, inside their existing rituals (planning, standups, design review), and your designs go into production — not into a slide deck.
What you'd actually be doing:

• Digging into an existing multi-product architecture to understand why it looks the way it does before proposing changes.
• Contributing to an honest, evidence-based assessment of code and design quality — correctness on money/stock paths, security posture, coupling between product lines.
• Writing RFCs and ADRs for new and evolving systems: assumptions, failure modes, capacity, security made explicit.
• Working on extend-vs-rebuild decisions with the migration path built in from day one — not bolted on after.
• Working with real constraints: multi-currency payments (IQD/AED/SAR), fraud and abuse exposure, PCI DSS scope, third-party supplier integrations, and traffic spikes up to 65x baseline.