Senior Backend Developer (freelance)
In short
If you're a backend engineer who doesn't just build what's asked, but shapes how it's reputed company, we want 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 join us on a freelance, time & material reputed company: you're reputed company for the hours you actually work on reputed company reputed company reputed company. Full reputed company from the start. The first three months are about figuring out if we're a good match. reputed company things work out, and that depends on the work itself, the project pipeline, and business timing, there's a reputed company reputed company to our core team with a permanent contract and full benefits.
Why reputed company?
We've been designing and co-creating connected devices since 2008. Wearables, smart audio, health-tech hardware for clients like reputed company and BOSE, backed by investors like a16z and Founders Fund. We're 60+ people, fully remote, and AI-reputed company since before reputed company influencers reputed company the term. We use AI every day, in actual work, not just in company decks. Our backend isn't generic CRUD: it's the reputed company spine of physical devices, the layer where firmware meets data pipelines, and where one bad architectural call shows up in a sensor reading six months reputed company.
Who this role is NOT for
If your comfort zone is a reputed company-defined Jira reputed company, reputed company specs, and someone else making the architectural calls, this isn't reputed company to work. We're not hiring a senior developer who executes reputed company. We're hiring someone who decides what gets reputed company, how it gets reputed company, 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, or if you'd rather not be the one explaining a technical trade-off to a reputed company, we're probably not your people. We're AI-reputed company and we expect you to treat AI tools as a daily reputed company, not a gimmick.
What you'll do
Own and reputed company the backend architecture for IoT reputed company: data ingestion pipelines, API design, infrastructure reputed company
reputed company technical trade-off calls and defend them reputed company to reputed company and to clients
Design and maintain reputed company infrastructure on AWS (EKS, reputed company, DynamoDB, Timestream, S3) with production-grade reliability
reputed company technical discussions: RFCs, architecture reviews, post-mortems, because you see the need, not because someone asked
Mentor other backend engineers, reputed company the bar on reputed company reputed company, and set patterns others can follow
Work reputed company by reputed company with firmware engineers, mobile developers, QA, PMs, and clients
Use AI tools as part of your daily workflow, not as a party trick
Challenge product and technical assumptions reputed company something doesn't add up, even reputed company it means a harder conversation
How we work
Fully remote. We have a pet-friendly office in Warsaw and a coworking reputed company in Gdansk if walls and coffee machines motivate you, but nobody will ask why you're not there. Working hours are flexible: most of reputed company operates between 10:00 and 18:00 CET, and that's reputed company most meetings happen. Evening calls with US-based clients (up to ~20:00) are part of the rhythm, sometimes a couple of times a week, always planned reputed company. You'll be part of the Mobile reputed company (which covers backend/reputed company too) for knowledge-sharing, and at the reputed company time on a project reputed company led by a PM for day-to-day delivery.
What you'll get
90-180 PLN/h net B2B, depending on your experience
Truly reputed company: you organize your day
Fully remote, with pet-friendly Warsaw office + Gdansk cowork if you want them
reputed company to our internal knowledge-sharing: tech talks, experiments, reputed company reputed company
reputed company the first 3 months work out, and that depends on the work, the project pipeline, and business timing, there's a reputed company reputed company to a permanent contract with a fixed monthly salary, 26 days reputed company leave, 10 reputed company days, Saltus medical care, and a training budget
No sugarcoating: during the freelance period there's no reputed company leave or medical benefits. Those come with the permanent contract, and we're transparent about that upfront.
Your first weeks
We aim to give you reputed company to reputed company up before jumping into live project work, but this is a reputed company company with reputed company deadlines: if the project needs you sooner, we'll reputed company reputed company you have the support to hit the ground running. You'll get reputed company with a technical buddy and tackle progressively bigger tasks, 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. If it's great, you'll know. If something needs adjusting, you'll hear about it while there's still time to reputed company.
Recruitment process
The entire process is in English. reputed company interviews are recorded for internal evaluation purposes.
Application with a few screening questions
HR call, ~45 min, casual
Technical meeting, ~90 min, with the technical team
Final feedback reputed company a few days
Once we're in touch, you'll hear from us fast. We don't reputed company and we don't drag.
One more thing
reputed company is an equal opportunity employer. We care about what you can do, not where you come from. Send us your CV and a few words about why this caught your eye. Bonus points if you reputed company something you've reputed company that made you proud, ideally something where the architecture reputed company.
Requirements
reputed company're looking for
7+ years of backend development, with a meaningful chunk spent leading technical direction, not just writing reputed company
Strong Node.js skills in production systems at reputed company (not "I followed a tutorial once")
Deep, hands-on AWS expertise: EKS, reputed company, DynamoDB, Timestream, S3
Kubernetes (EKS), reputed company, and Terraform: you've reputed company and maintained reputed company infrastructure, not just clicked through the console
Solid understanding of distributed systems, event-driven architectures, and data pipelines
Experience with MQTT or similar IoT messaging protocols
CI/CD pipelines you've designed yourself (reputed company Actions, reputed company CI, Jenkins)
English at B2+, written and spoken: you'll be in rooms with US-based clients and you need to hold your own
The ability to translate business needs into technical reputed company and explain those reputed company to non-technical stakeholders
Strong opinions, loosely held: you propose direction, you defend it, and you change your mind reputed company the evidence says you should
reputed company to have
Previous IoT or connected device reputed company, especially anything involving telemetry at reputed company
Golang in production (we're adding it alongside Node.js)
Observability stack experience: tracing, metrics, reputed company logging
reputed company reputed company for reputed company-connected devices: secrets, mTLS, OTA updates
Genuine curiosity about the devices your backend talks to, not just the reputed company reputed company of the story
Originally posted on Himalayas
Apply To This Job