Home › Companies › Intent › Senior Backend Developer (freelance)
Senior Backend Developer (freelance)
Intent · Warsaw, Warsaw, Mazowieckie, Poland · Remote · Active · Recruitee
Job facts
| Field | Value |
|---|---|
| Company | Intent |
| Title | Senior Backend Developer (freelance) |
| Normalized title | - |
| Department / team | Web Development |
| Location | Warsaw, Mazowieckie, Poland |
| Work model | Remote / Remote |
| Employment type | Full Time |
| Salary | PLN 15000 30000 month |
| Status | active |
| ATS provider | Recruitee |
| Posted / first seen | 2025-01-29 / 2026-05-30 |
| Changed / last seen | 2026-05-30 / 2026-06-06 |
Related slices
| Page | What it contains | Open |
|---|---|---|
| Company jobs | Active postings from Intent. | Open |
| Company breakdowns | Role, location, ATS, and work model facets for this company. | Open |
| ATS provider jobs | Active postings observed through Recruitee. | Open |
| Provider filtered search | The same provider as a filtered job collection. | Open |
| City jobs | Active postings in Warsaw. | Open |
| Department jobs | Active postings in Web Development. | Open |
| Work model jobs | Active Remote postings. | Open |
| Lifecycle events | Open, update, close, and reopen events for this posting. | Open |
| Original posting | Canonical source or apply URL captured from the ATS. | Open |
Linked records
| Company | Intent |
| Source | 56f75999-ffa7-42f4-a654-0a05543c4d34 |
| ATS provider | Recruitee |
Description
description
In short If you're a backend engineer who doesn't just build what's asked, but shapes how it's built, 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 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 figuring out if we're a good match. When things work out, and that depends on the work itself, the project pipeline, and business timing, there's a real path to our core team with a permanent contract and full benefits.
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 AI-native since before LinkedIn influencers discovered the term. We use AI every day, in actual work, not just in company decks. Our backend isn't generic CRUD: it's the cloud 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 later.
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, or 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.
What you'll do Own and evolve the backend architecture for IoT projects: data ingestion pipelines, API design, infrastructure decisions
Make technical trade-off calls 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, because you see the need, not because someone asked
Mentor other backend engineers, raise the bar on code quality, and set patterns others can follow
Work side by side 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 add up, even when it means a harder conversation
How we work Fully remote. We have a pet-friendly 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. Evening calls with US-based clients (up to ~20:00) are part of the rhythm, sometimes a couple of times a week, always planned ahead. You'll be part of the Mobile chapter (which covers backend/cloud too) for knowledge-sharing, and at the same time on a project squad led by a PM for day-to-day delivery.
What you'll get 90-180 PLN/h net B2B, depending on your experience
Truly flexible hours: you organize your day
Fully remote, with pet-friendly Warsaw office + Gdansk cowork if you want them
Access to our internal knowledge-sharing: tech talks, experiments, side projects
When the first 3 months work out, and that depends on the work, the project pipeline, and business timing, there's a real path to a permanent contract with a fixed monthly salary, 26 days paid leave, 10 sick days, Saltus medical care, and a training 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 aim to give you space to ramp up before jumping into live project work, but this is a real company with real deadlines: if the project needs you sooner, we'll make sure you have the support to hit the ground running. You'll get paired 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 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
Technical meeting, ~90 min, with the technical team
Final feedback within a few days
Once we're in touch, you'll hear from us fast. We don't ghost and we don't drag.
One more thing intent 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 share something you've built that made you proud, ideally something where the architecture mattered.
requirements
What we're looking for 7+ years of backend development, with a meaningful chunk spent leading technical direction, not just writing code
Strong Node.js skills in production systems at scale (not "I followed a tutorial once")
Deep, hands-on AWS expertise: EKS, Aurora, DynamoDB, Timestream, S3
Kubernetes (EKS), Docker, and Terraform: you've built and maintained real 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 (GitHub Actions, GitLab 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 decisions and explain those decisions to non-technical stakeholders
Strong opinions, loosely held: you propose direction, you defend it, and you change your mind when the evidence says you should
Nice to have Previous IoT or connected device projects, especially anything involving telemetry at scale
Golang in production (we're adding it alongside Node.js)
Observability stack experience: tracing, metrics, structured logging
Security mindset for cloud-connected devices: secrets, mTLS, OTA updates
Genuine curiosity about the devices your backend talks to, not just the cloud side of the story
sharing_description
In shortIf you're a backend engineer who doesn't just build what's asked, but shapes how it's built, we want to talk. We're looking for someone who can own the technical direction of a project end to
Full job record
| Job ID | d865ecbde5709dee06bd47ac91bd16d2f21c37c9 |
| Org ID | 6e419ec1-1878-4c7c-94d3-6075d504361e |
| Source ID | 56f75999-ffa7-42f4-a654-0a05543c4d34 |
| Board ID | 56f75999-ffa7-42f4-a654-0a05543c4d34 |
| Provider | recruitee |
| Provider Job Key | 2003574 |
| Title | Senior Backend Developer (freelance) |
| Normalized Title | — |
| Status | active |
| Active | yes |
| Location Text | Warsaw, Warsaw, Mazowieckie, Poland |
| Department | Web Development |
| Team | — |
| Employment Type | full_time |
| Workplace Type | remote |
| Remote Policy | remote |
| Country | Poland |
| Region | Mazowieckie |
| City | Warsaw |
| Salary Raw | PLN 15000 30000 month |
| Salary Min | — |
| Salary Max | — |
| Salary Currency | — |
| Salary Period | month |
| Source URL | https://intent.recruitee.com/o/senior-backend-developer-freelance |
| Apply URL | https://intent.recruitee.com/o/senior-backend-developer-freelance/c/new |
| First Seen At | 2026-05-30 05:49:28Z |
| Last Seen At | 2026-06-06 09:39:14Z |
| Last Checked At | 2026-06-06 09:39:14Z |
| Last Changed At | 2026-05-30 05:49:28Z |
| Inactive At | — |
| Source Posted At | 2025-01-29 20:32:50Z |
| Source Updated At | 2026-05-29 14:22:26Z |
| Raw Payload Uri | s3://job-postings-prod-raw-590183727216/raw/provider=recruitee/board=intent.recruitee.com/date=2026-06-06/2026-06-06T09-39-14-548Z-e52dc0c53ecfda74b0f72078e1b6e4024f6386b1e62c48ab08187f909e1b2d45.json |
Event Fields
{
"content_hash": "b444084669da90f50fd3cd9070bde95c4ed2e45c2ee076d587e189c85f059c98",
"source_hash": "2d0d7cc2e3ff5def41a0be572857c76bade599bfe9621502698d62b27f0a7f68",
"last_changed_at": "2026-05-30T05:49:28.963Z",
"active_status": "active"
}Parsed Structured
{
"language": "en",
"location": {
"raw": "Warsaw, Warsaw, Mazowieckie, Poland",
"city": "Warsaw",
"region": "Mazowieckie",
"country": "Poland",
"is_remote": true,
"confidence": 0.8
},
"salary_max": null,
"salary_min": null,
"inferred_at": "2026-06-06T09:39:14.791Z",
"launch_scope": {
"reason": "recruitee_production_catalog",
"included": true,
"location": {
"raw": "Warsaw, Warsaw, Mazowieckie, Poland",
"city": "Warsaw",
"region": "Mazowieckie",
"country": "Poland",
"is_remote": true,
"confidence": 0.8
},
"countries": [
"Poland"
]
},
"remote_policy": "remote",
"salary_period": "month",
"workplace_type": "remote",
"salary_currency": null
}Extensions
{}Native Structured
{
"id": 2003574,
"city": "Warsaw",
"guid": "b6aou",
"slug": "senior-backend-developer-freelance",
"tags": [
"backend"
],
"title": "Senior Backend Developer (freelance)",
"hybrid": false,
"remote": true,
"salary": {
"max": "30000",
"min": "15000",
"period": "month",
"currency": "PLN"
},
"status": "published",
"country": "Poland",
"on_site": false,
"close_at": null,
"location": "Remote job",
"position": 80,
"highlight": null,
"locations": [
{
"id": 44729,
"city": "Warsaw",
"name": "Warsaw",
"note": null,
"state": "Mazowieckie",
"street": "Aleje Jerozolimskie 93",
"country": "Poland",
"state_code": "14",
"postal_code": "02-001",
"country_code": "PL",
"translations": {
"en": {
"city": "Warsaw",
"name": "Warsaw",
"note": null,
"street": "Aleje Jerozolimskie 93",
"postal_code": "02-001"
}
}
}
],
"max_hours": 40,
"min_hours": 40,
"created_at": "2025-01-29 20:29:58 UTC",
"department": "Web Development",
"options_cv": "required",
"state_code": "14",
"state_name": "Mazowieckie",
"updated_at": "2026-05-29 14:22:26 UTC",
"careers_url": "https://intent.recruitee.com/o/senior-backend-developer-freelance",
"cover_image": null,
"description": "<h2><strong><span style=\"color:#1A1A1A\">In short</span></strong></h2><p><span style=\"color:#000000\">If you're a backend engineer who doesn't just build what's asked, but shapes how it's built, 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 </span><strong><span style=\"color:#000000\">freelance, time & material basis</span></strong><span style=\"color:#000000\">: you're paid for the hours you actually work on real client projects. Full capacity from the start. The first three months are about figuring out if we're a good match. When things work out, and that depends on the work itself, the project pipeline, and business timing, there's a real path to our core team with a permanent contract and full benefits.</span></p><h2><strong><span style=\"color:#1A1A1A\">Why intent?</span></strong></h2><p><span style=\"color:#000000\">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 AI-native since before LinkedIn influencers discovered the term. We use AI every day, in actual work, not just in company decks. Our backend isn't generic CRUD: it's the cloud 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 later.</span></p><h2><strong><span style=\"color:#1A1A1A\">Who this role is NOT for</span></strong></h2><p><span style=\"color:#000000\">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, or 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.</span></p><h2><strong><span style=\"color:#1A1A1A\">What you'll do</span></strong></h2><ul><li><p><span style=\"color:#000000\">Own and evolve the backend architecture for IoT projects: data ingestion pipelines, API design, infrastructure decisions</span></p></li><li><p><span style=\"color:#000000\">Make technical trade-off calls and defend them clearly to the team and to clients</span></p></li><li><p><span style=\"color:#000000\">Design and maintain cloud infrastructure on AWS (EKS, Aurora, DynamoDB, Timestream, S3) with production-grade reliability</span></p></li><li><p><span style=\"color:#000000\">Lead technical discussions: RFCs, architecture reviews, post-mortems, because you see the need, not because someone asked</span></p></li><li><p><span style=\"color:#000000\">Mentor other backend engineers, raise the bar on code quality, and set patterns others can follow</span></p></li><li><p><span style=\"color:#000000\">Work side by side with firmware engineers, mobile developers, QA, PMs, and clients</span></p></li><li><p><span style=\"color:#000000\">Use AI tools as part of your daily workflow, not as a party trick</span></p></li><li><p><span style=\"color:#000000\">Challenge product and technical assumptions when something doesn't add up, even when it means a harder conversation</span></p></li></ul><h2><strong><span style=\"color:#1A1A1A\">How we work</span></strong></h2><p><span style=\"color:#000000\">Fully remote. We have a pet-friendly 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. Evening calls with US-based clients (up to ~20:00) are part of the rhythm, sometimes a couple of times a week, always planned ahead. You'll be part of the Mobile chapter (which covers backend/cloud too) for knowledge-sharing, and at the same time on a project squad led by a PM for day-to-day delivery.</span></p><h2><strong><span style=\"color:#1A1A1A\">What you'll get</span></strong></h2><ul><li><p><span style=\"color:#000000\">90-180 PLN/h net B2B, depending on your experience</span></p></li><li><p><span style=\"color:#000000\">Truly flexible hours: you organize your day</span></p></li><li><p><span style=\"color:#000000\">Fully remote, with pet-friendly Warsaw office + Gdansk cowork if you want them</span></p></li><li><p><span style=\"color:#000000\">Access to our internal knowledge-sharing: tech talks, experiments, side projects</span></p></li><li><p><span style=\"color:#000000\">When the first 3 months work out, and that depends on the work, the project pipeline, and business timing, there's a real path to a permanent contract with a fixed monthly salary, 26 days paid leave, 10 sick days, Saltus medical care, and a training budget</span></p></li></ul><p><span style=\"color:#000000\">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.</span></p><h2><strong><span style=\"color:#1A1A1A\">Your first weeks</span></strong></h2><p><span style=\"color:#000000\">We aim to give you space to ramp up before jumping into live project work, but this is a real company with real deadlines: if the project needs you sooner, we'll make sure you have the support to hit the ground running. You'll get paired 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 adjust.</span></p><h2><strong><span style=\"color:#1A1A1A\">Recruitment process</span></strong></h2><p><span style=\"color:#000000\">The entire process is in English. All interviews are recorded for internal evaluation purposes.</span></p><ol><li><p><span style=\"color:#000000\">Application with a few screening questions</span></p></li><li><p><span style=\"color:#000000\">HR call, ~45 min, casual</span></p></li><li><p><span style=\"color:#000000\">Technical meeting, ~90 min, with the technical team</span></p></li><li><p><span style=\"color:#000000\">Final feedback within a few days</span></p></li></ol><p><span style=\"color:#000000\">Once we're in touch, you'll hear from us fast. We don't ghost and we don't drag.</span></p><h2><strong><span style=\"color:#1A1A1A\">One more thing</span></strong></h2><p><span style=\"color:#000000\">intent 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 share something you've built that made you proud, ideally something where the architecture mattered.</span></p>",
"postal_code": "02-001",
"company_name": "intent",
"country_code": "PL",
"published_at": "2025-01-29 20:32:50 UTC",
"requirements": "<h2><strong><span style=\"color:#1A1A1A\">What we're looking for</span></strong></h2><ul><li><p><span style=\"color:#000000\">7+ years of backend development, with a meaningful chunk spent leading technical direction, not just writing code</span></p></li><li><p><span style=\"color:#000000\">Strong Node.js skills in production systems at scale (not \"I followed a tutorial once\")</span></p></li><li><p><span style=\"color:#000000\">Deep, hands-on AWS expertise: EKS, Aurora, DynamoDB, Timestream, S3</span></p></li><li><p><span style=\"color:#000000\">Kubernetes (EKS), Docker, and Terraform: you've built and maintained real infrastructure, not just clicked through the console</span></p></li><li><p><span style=\"color:#000000\">Solid understanding of distributed systems, event-driven architectures, and data pipelines</span></p></li><li><p><span style=\"color:#000000\">Experience with MQTT or similar IoT messaging protocols</span></p></li><li><p><span style=\"color:#000000\">CI/CD pipelines you've designed yourself (GitHub Actions, GitLab CI, Jenkins)</span></p></li><li><p><span style=\"color:#000000\">English at B2+, written and spoken: you'll be in rooms with US-based clients and you need to hold your own</span></p></li><li><p><span style=\"color:#000000\">The ability to translate business needs into technical decisions and explain those decisions to non-technical stakeholders</span></p></li><li><p><span style=\"color:#000000\">Strong opinions, loosely held: you propose direction, you defend it, and you change your mind when the evidence says you should</span></p></li></ul><h2><strong><span style=\"color:#1A1A1A\">Nice to have</span></strong></h2><ul><li><p><span style=\"color:#000000\">Previous IoT or connected device projects, especially anything involving telemetry at scale</span></p></li><li><p><span style=\"color:#000000\">Golang in production (we're adding it alongside Node.js)</span></p></li><li><p><span style=\"color:#000000\">Observability stack experience: tracing, metrics, structured logging</span></p></li><li><p><span style=\"color:#000000\">Security mindset for cloud-connected devices: secrets, mTLS, OTA updates</span></p></li><li><p><span style=\"color:#000000\">Genuine curiosity about the devices your backend talks to, not just the cloud side of the story</span></p></li></ul>",
"translations": {
"en": {
"title": "Senior Backend Developer (freelance)",
"highlight": null,
"description": "<h2><strong><span style=\"color:#1A1A1A\">In short</span></strong></h2><p><span style=\"color:#000000\">If you're a backend engineer who doesn't just build what's asked, but shapes how it's built, 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 </span><strong><span style=\"color:#000000\">freelance, time & material basis</span></strong><span style=\"color:#000000\">: you're paid for the hours you actually work on real client projects. Full capacity from the start. The first three months are about figuring out if we're a good match. When things work out, and that depends on the work itself, the project pipeline, and business timing, there's a real path to our core team with a permanent contract and full benefits.</span></p><h2><strong><span style=\"color:#1A1A1A\">Why intent?</span></strong></h2><p><span style=\"color:#000000\">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 AI-native since before LinkedIn influencers discovered the term. We use AI every day, in actual work, not just in company decks. Our backend isn't generic CRUD: it's the cloud 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 later.</span></p><h2><strong><span style=\"color:#1A1A1A\">Who this role is NOT for</span></strong></h2><p><span style=\"color:#000000\">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, or 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.</span></p><h2><strong><span style=\"color:#1A1A1A\">What you'll do</span></strong></h2><ul><li><p><span style=\"color:#000000\">Own and evolve the backend architecture for IoT projects: data ingestion pipelines, API design, infrastructure decisions</span></p></li><li><p><span style=\"color:#000000\">Make technical trade-off calls and defend them clearly to the team and to clients</span></p></li><li><p><span style=\"color:#000000\">Design and maintain cloud infrastructure on AWS (EKS, Aurora, DynamoDB, Timestream, S3) with production-grade reliability</span></p></li><li><p><span style=\"color:#000000\">Lead technical discussions: RFCs, architecture reviews, post-mortems, because you see the need, not because someone asked</span></p></li><li><p><span style=\"color:#000000\">Mentor other backend engineers, raise the bar on code quality, and set patterns others can follow</span></p></li><li><p><span style=\"color:#000000\">Work side by side with firmware engineers, mobile developers, QA, PMs, and clients</span></p></li><li><p><span style=\"color:#000000\">Use AI tools as part of your daily workflow, not as a party trick</span></p></li><li><p><span style=\"color:#000000\">Challenge product and technical assumptions when something doesn't add up, even when it means a harder conversation</span></p></li></ul><h2><strong><span style=\"color:#1A1A1A\">How we work</span></strong></h2><p><span style=\"color:#000000\">Fully remote. We have a pet-friendly 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. Evening calls with US-based clients (up to ~20:00) are part of the rhythm, sometimes a couple of times a week, always planned ahead. You'll be part of the Mobile chapter (which covers backend/cloud too) for knowledge-sharing, and at the same time on a project squad led by a PM for day-to-day delivery.</span></p><h2><strong><span style=\"color:#1A1A1A\">What you'll get</span></strong></h2><ul><li><p><span style=\"color:#000000\">90-180 PLN/h net B2B, depending on your experience</span></p></li><li><p><span style=\"color:#000000\">Truly flexible hours: you organize your day</span></p></li><li><p><span style=\"color:#000000\">Fully remote, with pet-friendly Warsaw office + Gdansk cowork if you want them</span></p></li><li><p><span style=\"color:#000000\">Access to our internal knowledge-sharing: tech talks, experiments, side projects</span></p></li><li><p><span style=\"color:#000000\">When the first 3 months work out, and that depends on the work, the project pipeline, and business timing, there's a real path to a permanent contract with a fixed monthly salary, 26 days paid leave, 10 sick days, Saltus medical care, and a training budget</span></p></li></ul><p><span style=\"color:#000000\">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.</span></p><h2><strong><span style=\"color:#1A1A1A\">Your first weeks</span></strong></h2><p><span style=\"color:#000000\">We aim to give you space to ramp up before jumping into live project work, but this is a real company with real deadlines: if the project needs you sooner, we'll make sure you have the support to hit the ground running. You'll get paired 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 adjust.</span></p><h2><strong><span style=\"color:#1A1A1A\">Recruitment process</span></strong></h2><p><span style=\"color:#000000\">The entire process is in English. All interviews are recorded for internal evaluation purposes.</span></p><ol><li><p><span style=\"color:#000000\">Application with a few screening questions</span></p></li><li><p><span style=\"color:#000000\">HR call, ~45 min, casual</span></p></li><li><p><span style=\"color:#000000\">Technical meeting, ~90 min, with the technical team</span></p></li><li><p><span style=\"color:#000000\">Final feedback within a few days</span></p></li></ol><p><span style=\"color:#000000\">Once we're in touch, you'll hear from us fast. We don't ghost and we don't drag.</span></p><h2><strong><span style=\"color:#1A1A1A\">One more thing</span></strong></h2><p><span style=\"color:#000000\">intent 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 share something you've built that made you proud, ideally something where the architecture mattered.</span></p>",
"requirements": "<h2><strong><span style=\"color:#1A1A1A\">What we're looking for</span></strong></h2><ul><li><p><span style=\"color:#000000\">7+ years of backend development, with a meaningful chunk spent leading technical direction, not just writing code</span></p></li><li><p><span style=\"color:#000000\">Strong Node.js skills in production systems at scale (not \"I followed a tutorial once\")</span></p></li><li><p><span style=\"color:#000000\">Deep, hands-on AWS expertise: EKS, Aurora, DynamoDB, Timestream, S3</span></p></li><li><p><span style=\"color:#000000\">Kubernetes (EKS), Docker, and Terraform: you've built and maintained real infrastructure, not just clicked through the console</span></p></li><li><p><span style=\"color:#000000\">Solid understanding of distributed systems, event-driven architectures, and data pipelines</span></p></li><li><p><span style=\"color:#000000\">Experience with MQTT or similar IoT messaging protocols</span></p></li><li><p><span style=\"color:#000000\">CI/CD pipelines you've designed yourself (GitHub Actions, GitLab CI, Jenkins)</span></p></li><li><p><span style=\"color:#000000\">English at B2+, written and spoken: you'll be in rooms with US-based clients and you need to hold your own</span></p></li><li><p><span style=\"color:#000000\">The ability to translate business needs into technical decisions and explain those decisions to non-technical stakeholders</span></p></li><li><p><span style=\"color:#000000\">Strong opinions, loosely held: you propose direction, you defend it, and you change your mind when the evidence says you should</span></p></li></ul><h2><strong><span style=\"color:#1A1A1A\">Nice to have</span></strong></h2><ul><li><p><span style=\"color:#000000\">Previous IoT or connected device projects, especially anything involving telemetry at scale</span></p></li><li><p><span style=\"color:#000000\">Golang in production (we're adding it alongside Node.js)</span></p></li><li><p><span style=\"color:#000000\">Observability stack experience: tracing, metrics, structured logging</span></p></li><li><p><span style=\"color:#000000\">Security mindset for cloud-connected devices: secrets, mTLS, OTA updates</span></p></li><li><p><span style=\"color:#000000\">Genuine curiosity about the devices your backend talks to, not just the cloud side of the story</span></p></li></ul>",
"sharing_image": "https://recruitee-main.s3.eu-central-1.amazonaws.com/offers/2003574/normal_sharing_bnyl6llhc236.jpg",
"sharing_title": "Senior Backend Developer (freelance)",
"locations_question": "What is your preferred work location?",
"sharing_description": "In shortIf you're a backend engineer who doesn't just build what's asked, but shapes how it's built, we want to talk. We're looking for someone who can own the technical direction of a project end to "
}
},
"category_code": "information_technology",
"mailbox_email": "[email protected]",
"options_phone": "required",
"options_photo": "off",
"options_title": "off",
"sharing_image": "https://recruitee-main.s3.eu-central-1.amazonaws.com/offers/2003574/normal_sharing_bnyl6llhc236.jpg",
"sharing_title": "Senior Backend Developer (freelance)",
"dynamic_fields": [],
"education_code": "bachelor_degree",
"open_questions": [
{
"id": 2951537,
"body": "Please give your monthly salary expectations in PLN (provide net amount for B2B):",
"kind": "string",
"options": {},
"position": 1,
"required": true,
"translations": {
"en": {
"body": "Please give your monthly salary expectations in PLN (provide net amount for B2B):"
}
},
"open_question_options": []
},
{
"id": 2951538,
"body": "When are you available to join us?",
"kind": "string",
"options": {
"length": 120
},
"position": 2,
"required": true,
"translations": {
"en": {
"body": "When are you available to join us?"
}
},
"open_question_options": []
},
{
"id": 2951539,
"body": "Please indicate your English level:",
"kind": "single_choice",
"options": {
"length": 120
},
"position": 3,
"required": true,
"translations": {
"en": {
"body": "Please indicate your English level:"
}
},
"open_question_options": [
{
"id": 4297692,
"body": "A1 - Beginner/Elementary",
"position": 0,
"translations": {
"en": {
"body": "A1 - Beginner/Elementary"
}
}
},
{
"id": 4297693,
"body": "A2 - Pre Intermediate",
"position": 1,
"translations": {
"en": {
"body": "A2 - Pre Intermediate"
}
}
},
{
"id": 4297694,
"body": "B1 - Intermediate",
"position": 2,
"translations": {
"en": {
"body": "B1 - Intermediate"
}
}
},
{
"id": 4297695,
"body": "B2 - Upper Intermediate",
"position": 3,
"translations": {
"en": {
"body": "B2 - Upper Intermediate"
}
}
},
{
"id": 4297696,
"body": "C1 - Advanced",
"position": 4,
"translations": {
"en": {
"body": "C1 - Advanced"
}
}
},
{
"id": 4297697,
"body": "C2 - Proficient/Native",
"position": 5,
"translations": {
"en": {
"body": "C2 - Proficient/Native"
}
}
}
]
},
{
"id": 2951541,
"body": "Do you have any experience with IoT/connected devices related projects?",
"kind": "text",
"options": {
"length": 120
},
"position": 4,
"required": true,
"translations": {
"en": {
"body": "Do you have any experience with IoT/connected devices related projects?"
}
},
"open_question_options": []
},
{
"id": 2951545,
"body": "Do you have commercial experience with AWS? If yes, describe a recent project where you designed and deployed a backend system using AWS (EKS, S3, Aurora, DynamoDB, etc.)",
"kind": "string",
"options": {},
"position": 5,
"required": true,
"translations": {
"en": {
"body": "Do you have commercial experience with AWS? If yes, describe a recent project where you designed and deployed a backend system using AWS (EKS, S3, Aurora, DynamoDB, etc.)"
}
},
"open_question_options": []
},
{
"id": 2951551,
"body": "How many years of commercial experience do you have with Node.js?",
"kind": "string",
"options": {},
"position": 6,
"required": true,
"translations": {
"en": {
"body": "How many years of commercial experience do you have with Node.js?"
}
},
"open_question_options": []
},
{
"id": 2951542,
"body": "Did someone recommend you to apply?",
"kind": "string",
"options": {
"length": 120
},
"position": 7,
"required": false,
"translations": {
"en": {
"body": "Did someone recommend you to apply?"
}
},
"open_question_options": []
},
{
"id": 2951543,
"body": "<p>I agree to the processing of my personal data provided in the recruitment application by intent sp. z o. o. with its registered seat in Warsaw for the purposes of the recruitment process in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.</p>",
"kind": "infobox",
"options": {
"length": 120
},
"position": 8,
"required": false,
"translations": {
"en": {
"body": "<p>I agree to the processing of my personal data provided in the recruitment application by intent sp. z o. o. with its registered seat in Warsaw for the purposes of the recruitment process in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.</p>"
}
},
"open_question_options": []
},
{
"id": 2951544,
"body": "<p>I agree to the processing of my personal data provided in the recruitment application by intent sp. z o. o. with its registered seat in Warsaw for the purposes of future recruitment processes for a period of 2 years in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.</p>",
"kind": "legal",
"options": {
"length": 120
},
"position": 9,
"required": false,
"translations": {
"en": {
"body": "<p>I agree to the processing of my personal data provided in the recruitment application by intent sp. z o. o. with its registered seat in Warsaw for the purposes of future recruitment processes for a period of 2 years in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.</p>"
}
},
"open_question_options": []
}
],
"experience_code": "experienced",
"careers_apply_url": "https://intent.recruitee.com/o/senior-backend-developer-freelance/c/new",
"locations_question": "What is your preferred work location?",
"max_hours_per_week": "40",
"min_hours_per_week": "40",
"options_salutation": "off",
"sharing_description": "In shortIf you're a backend engineer who doesn't just build what's asked, but shapes how it's built, we want to talk. We're looking for someone who can own the technical direction of a project end to ",
"employment_type_code": "fulltime_fixed_term",
"options_cover_letter": "off",
"locations_question_type": "multiple_choice",
"location_question_visible": false,
"locations_question_required": true
}Get this page with API
Rendered from the bluedoor Job Postings API. Reproduce it:
GET https://api.bluedoor.sh/job-postings/v1/jobs/d865ecbde5709dee06bd47ac91bd16d2f21c37c9?include=descriptionJSONGET https://api.bluedoor.sh/job-postings/v1/orgs/6e419ec1-1878-4c7c-94d3-6075d504361eJSONGET https://api.bluedoor.sh/job-postings/v1/sources/56f75999-ffa7-42f4-a654-0a05543c4d34JSONGET https://api.bluedoor.sh/job-postings/v1/jobs/d865ecbde5709dee06bd47ac91bd16d2f21c37c9/eventsJSON