(Senior) Node.js Developer - Freelance
Summary
Netguru is seeking a senior Node.js developer for a freelance role to provide deep system design expertise for a client's multi-product architecture. The role involves writing RFCs and ADRs, ensuring system security and scalability, and collaborating directly with the client's engineering team.
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
Requirements
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.
Benefits
- 100% remote work;
- work with an experienced team of developers and continuous development of your hard and soft skills;
- long-term collaboration on challenging products
What will happen next?
- We will invite you for a meeting with our recruiter.
- Next, you'll participate in the client interview.
Curious to learn more about working as a Netguru freelancer? All the information you need is here: Netguru Talent Marketplace.
Looking for a full-time job? Check out our Career Page and find out more about our open recruitment processes.
If you need any disability-related adaptation at any step of the recruitment process – simply let the recruiter know! We'd be happy to help.
Don't hesitate and apply right away.
Skills
As published by workable · 8 questions · 3 written answers
Basics
First name, Last name, Email, Headline, Phone, Address, Experience, Resume, Where are you currently located?, What is the full name and location of your current company (employer)? If you work as a contractor, please write down the full name and location of the company you’re cooperating with.
Short answers (1)
- When are you available to start? / What is your notice period?
Pick from a list (4)
- Are you ready to take a full time job?
- Please let us know if you're able to work with us via B2B contract (if you have a sole proprietorship or willing to set it up after positive process) - for this specific project it's the only type of contract we can offer.
- Can you please confirm you are aware of our salary ranges for this position?
- After submitting the application form, you should receive a confirmation e-mail. If that doesn't happen, it means we didn't receive your application. In that case, please send an email to jobs@netguru.com informing our recruitment team about that. Thank you in advance! Please confirm that you understand by clicking "yes".
Written answers (3)
- Please share with us your citizenship.
- What is your current country of residence?
- What is your expected hourly rate?