Backend Expert (node.js)

April 30, 2026

Other Jobs To Apply

In shortIf you’re a backend engineer who doesn’t just build what’s asked but shapes how it’s built, we’d love to talk. We’re looking for someone who can own the technical direction of a project end to end: architecture, infrastructure, trade-offs, and the conversations that come with them. You’d be joining us on a freelance, time & material basis: you’re paid for the hours you actually work on real client projects. Full capacity from the start. The first three months are about getting to know each other: if it turns out we work well together, we’d love to bring you into our core team with a fixed monthly salary, paid time off, and the whole benefits package. Not a promise, a real possibility we actively root for.Why intent?We’ve been designing and co-creating connected devices since 2008. Wearables, smart audio, health-tech hardware for clients like Oura and BOSE, backed by investors like a16z and Founders Fund. We’re 60+ people, fully remote, and we’ve been AI-native since before LinkedIn influencers discovered the term. Our backend systems power the data layer behind physical products that people wear, listen to, and rely on every day. If you’ve ever designed a system that had to be right because a device on someone’s wrist depended on it, you already get why we love what we do.Who this role is NOT forIf your comfort zone is a well-defined Jira board, clear specs, and someone else making the architectural calls, this isn’t going to work. We’re not hiring a senior developer who executes well. We’re hiring someone who decides what gets built, how it gets built, and why. Someone who walks into a room full of ambiguity and starts creating structure, not waiting for it. If you need a ticket to start moving, if "that’s not in the requirements" is a sentence you use often, if you’d rather not be the one explaining a technical trade-off to a client: we’re probably not your people. We’re AI-native and we expect you to treat AI tools as a daily multiplier, not a gimmick. We look for engineers who ask "why" before "how", who challenge assumptions, and who occasionally break things because they were trying something better.What you’ll do<ul><li>Own and evolve the backend architecture for IoT projects: from data ingestion pipelines to API design to infrastructure decisions</li><li>Make technical trade-off decisions and defend them clearly to the team and to clients</li><li>Design and maintain cloud infrastructure on AWS (EKS, Aurora, DynamoDB, Timestream, S3) with production-grade reliability</li><li>Lead technical discussions: RFCs, architecture reviews, post-mortems. Not because someone asked you to, but because you see the need</li><li>Mentor other backend engineers, raise the bar on code quality, and set patterns others can follow</li><li>Collaborate closely with firmware engineers, mobile developers, QA, PMs, and clients</li><li>Use AI tools as part of your daily workflow, not as a party trick</li><li>Challenge product and technical assumptions when something doesn’t make sense, even if it means a harder conversation</li></ul>How we workFully remote. We have an office in Warsaw and a coworking space in Gdansk if walls and coffee machines motivate you, but nobody will ask why you’re not there. Working hours are flexible: most of the team operates between 10:00 and 18:00 CET, and that’s when most meetings happen. Depending on the project, occasional evening calls with US-based clients (up to ~20:00) may happen, always scheduled in advance, never a surprise. You’ll be part of the backend/cloud chapter for knowledge-sharing, and simultaneously on a project squad led by a PM for day-to-day delivery.What you’ll get<ul><li>135-220 PLN/h net B2B, depending on your experience</li><li>Truly flexible hours (most of the team works 10-18 CET, but you organize your day)</li><li>Fully remote, with Warsaw office + Gdansk cowork if you want them</li><li>Access to our internal knowledge-sharing: tech talks, experiments, side projects</li><li>A genuine path to the core team: if the first 3 months go well, you get a permanent contract with a fixed monthly salary regardless of project availability, 26 days paid leave, 10 sick days, Saltus medical care, training budget, and mentoring budget</li></ul> No sugarcoating: during the freelance period there’s no paid leave or medical benefits. Those come with the permanent contract, and we’re transparent about that upfront.Your first weeksWe don’t throw you into the deep end on day one. New engineers go through a structured ramp-up period before landing on target projects: you’ll work alongside the team, get paired with a technical buddy, and tackle progressively bigger challenges so both sides can see how the collaboration feels. Feedback comes early and often: no one waits three months to tell you something isn’t working. We believe in fast, honest signals. If it’s great, you’ll know. If something needs adjusting, you’ll hear about it while there’s still time to adjust.Recruitment processThe entire process is in English. All interviews are recorded for internal evaluation purposes. <ol><li>Application with a few screening questions</li><li>HR call (~45 min, casual, recorded)</li><li>Technical meeting (~90 min, with the technical team)</li><li>Final feedback within a week</li></ol> <ul><li>7+ years of backend development experience, with a meaningful chunk spent leading technical direction, not just writing code</li><li>Deep, hands-on AWS expertise: EKS, Aurora, DynamoDB, Timestream, S3, IAM. Not "I set up an EC2 once"</li><li>Strong Node.js skills in production systems at scale</li><li>Kubernetes (EKS), Docker, and Terraform: you’ve built and maintained real infrastructure, not just followed tutorials</li><li>Solid understanding of distributed systems, event-driven architectures, and data pipelines</li><li>Experience with MQTT or similar IoT messaging protocols</li><li>CI/CD pipelines you’ve designed yourself (Jenkins, GitLab CI, GitHub Actions)</li><li>English at B2+ minimum, written and spoken: you’ll be in rooms with US-based clients and you need to hold your own</li><li>The ability to translate business needs into technical decisions and explain those decisions to non-technical stakeholders</li><li>Strong opinions, loosely held: you propose direction, you defend it, and you change your mind when the evidence says you should</li></ul>Nice to have<ul><li>Experience leading or bootstrapping a project from scratch as the sole or primary backend engineer</li><li>Previous IoT, connected device, or hardware-adjacent projects</li><li>Familiarity with time-series data, real-time streaming, or edge computing patterns</li><li>Background in system design interviews or architecture review boards</li><li>Contributions to open-source projects or technical writing that shows how you think</li><li>Genuine curiosity about the physical devices your code powers, not just the services behind them</li></ul>

Back to blog

Ads

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...

DISCLAIMER