In short
If 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 for
If 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
Own and evolve the backend architecture for IoT projects: from data ingestion pipelines to API design to infrastructure decisions
Make technical trade-off decisions and defend them clearly to the team and to clients
Design and maintain cloud infrastructure on AWS (EKS, Aurora, DynamoDB, Timestream, S3) with production-grade reliability
Lead technical discussions: RFCs, architecture reviews, post-mortems. Not because someone asked you to, but because you see the need
Mentor other backend engineers, raise the bar on code quality, and set patterns others can follow
Collaborate closely 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 when something doesn’t make sense, even if it means a harder conversation
How we work
Fully 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
135-220 PLN/h net B2B, depending on your experience
Truly flexible hours (most of the team works 10-18 CET, but you organize your day)
Fully remote, with Warsaw office + Gdansk cowork if you want them
Access to our internal knowledge-sharing: tech talks, experiments, side projects
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
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 weeks
We 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 process
The entire process is in English. All interviews are recorded for internal evaluation purposes.
Application with a few screening questions
HR call (~45 min, casual, recorded)
Technical meeting (~90 min, with the technical team)
Final feedback within a week