<p class="p1"><strong>In short</strong></p><p class="p2">If you're a Senior Embedded C engineer who gets why a misbehaving radio at 2 AM is both annoying</p><p class="p2">and the best puzzle of your week, we'd love to talk. You'd be joining us on a freelance, time &</p><p class="p2">material basis: you're paid for the hours you actually work on real client projects. We're ready to</p><p class="p2">start right away, at full capacity. The first three months are about getting to know each other: if it</p><p class="p2">turns out we work well together, we'd love to bring you into our core team with a fixed monthly</p><p class="p2">salary, paid time off, and the whole benefits package. Not a promise, a real possibility we actively</p><p class="p2">root for.</p><p style="min-height: 1.7em;"></p><p class="p1"><strong>Why intent?</strong></p><p class="p2">We've been designing and co-creating connected devices since 2008. Wearables, smart audio,</p><p class="p2">health-tech hardware for clients like Oura, BOSE, and Neurable, backed by investors like a16z and</p><p class="p2">Founders Fund. We're 60+ people, fully remote, and we've been AI-native since before LinkedIn</p><p class="p2">influencers discovered the term. We use AI every day, in actual work, not just in company decks. If</p><p class="p2">your C code has ever made an antenna, a sensor, or a medical-grade device behave itself, you</p><p class="p2">already get why we love what we do.</p><p style="min-height: 1.7em;"></p><p class="p1"><strong>Who this role is NOT for</strong></p><p class="p2">If you like being handed a spec, a ticket, and a "wake me when it's done", we're probably not your</p><p class="p2">people. Embedded at intent means chasing edge cases across silicon, stacks, and radios, sometimes</p><p class="p2">in the same afternoon. We're looking for engineers who ask "why" before "how", who read a</p><p class="p2">datasheet and then actually question it, and who know that "it works on my bench" is the beginning</p><p class="p2">of the conversation, not the end. We're AI-native and we expect you to treat AI as a daily multiplier</p><p class="p2">(digging through vendor docs, drafting test harnesses, reasoning about tricky timing issues), not as a</p><p class="p2">gimmick. On freelance: we're not expecting you to rewrite our toolchain in week one. What we do</p><p class="p2">expect is ownership of what you touch, straight talk when things get complicated, and actual</p><p class="p2">curiosity about the device on the end of your JTAG.</p><p style="min-height: 1.7em;"></p><p class="p1"><strong>What you'll do</strong></p><p class="p2">• Build and maintain embedded firmware in C for STM32-based connected devices</p><p class="p2">• Work inside the Modus SDK and the broader Cypress/Infineon ecosystem to make hardware</p><p class="p2">do what the spec says, and a few things it didn't</p><p class="p2">• Integrate and tune FreeRTOS: tasks, priorities, queues, interrupts, the whole discipline of not</p><p class="p2">breaking real-time behavior</p><p class="p2">• Tackle multi-radio architectures in practice: BLE and Wi-Fi coexistence, arbitration, throughput</p><p class="p2">versus power trade-offs• Collaborate closely with hardware, mobile, QA, and the client's engineering team on cross-</p><p class="p2">functional problems</p><p class="p2">• Debug the unglamorous stuff: logic analyzer, scope, sniffer, logs that don't want to exist</p><p class="p2">• Contribute to architecture decisions, code reviews, and knowledge-sharing inside the</p><p class="p2">Firmware & Hardware chapter</p><p class="p2">• Use AI tools as part of your daily workflow, not as a party trick</p><p class="p1" style="min-height: 1.7em;"></p><p class="p1"><strong>How we work</strong></p><p class="p2">Fully remote. We have an office in Warsaw. The team operates between 10:00 and 18:00 CET, and that's when most meetings happen.</p><p class="p2">Depending on the project, occasional evening calls with US-based clients (up to ~20:00) may happen,</p><p class="p2">always scheduled in advance, never a surprise. You'll be part of the Firmware & Hardware chapter</p><p class="p2">for knowledge-sharing, and simultaneously on a project squad led by a PM for day-to-day delivery.</p><p class="p2" style="min-height: 1.7em;"></p><p class="p2"><strong>What you'll get</strong></p><p class="p2">• 110-190 PLN/h net B2B, depending on your experience</p><p class="p2">• Truly flexible hours (most of the team works 10-18 CET, but you organize your day)</p><p class="p2">• Fully remote (all Europe)</p><p class="p2">• Access to our internal knowledge-sharing: tech talks, experiments, side projects</p><p class="p2" style="min-height: 1.7em;"></p><p class="p2">No sugarcoating: during the freelance period there's no paid leave or medical benefits. Those come</p><p class="p2">with the permanent contract, and we're transparent about that upfront.</p><p style="min-height: 1.7em;"></p><p class="p1"><strong>Your first weeks</strong></p><p class="p2">We don't throw you into the deep end on day one. New engineers go through a structured ramp-up</p><p class="p2">period before landing on target projects: you'll work alongside the team, get paired with a technical</p><p class="p2">buddy, and tackle progressively bigger tasks so both sides can see how the collaboration feels.</p><p class="p2">Feedback comes early and often, no one waits three months to tell you something isn't working. We</p><p class="p2">believe in fast, honest signals: if it's great, you'll know. If something needs adjusting, you'll hear</p><p class="p2">about it while there's still time to adjust.</p><p style="min-height: 1.7em;"></p><p class="p1"><strong>Recruitment process</strong></p><p class="p2">The entire process is in English. All interviews are recorded for internal evaluation purposes.</p><ol><li><p class="p2">Application with a few screening questions</p></li><li><p class="p2">HR call (~45 min, casual)</p></li><li><p class="p2">Technical meeting (~90 min, with the technical team)</p></li><li><p class="p2">Final feedback within a few days.</p></li></ol><p style="min-height: 1.7em;"></p><br><br><p class="p1"><strong>What we're looking for</strong></p><p class="p2">• 5+ years of hands-on embedded C development on ARM Cortex-M platforms</p><p class="p2">• Strong, proven STM32 experience (not "I ran one tutorial")</p><p class="p2">• Real work with the Modus SDK, or at the very least solid time inside the Cypress/Infineon</p><p class="p2">ecosystem</p><p class="p2">• FreeRTOS: you know where the footguns are, and you don't find them by accident</p><p class="p2">• Proven experience with multi-radio architectures, especially BLE and Wi-Fi coexistence: timing,</p><p class="p2">arbitration, co-existence schemes, real-world throughput issues</p><p class="p2">• Comfortable reading schematics, board files, datasheets, and errata without flinching</p><p class="p2">• Fluent with the debugging toolkit: JTAG/SWD, logic analyzers, scopes, BLE sniffers, serial</p><p class="p2">tracing</p><p class="p2">• English at B2+, because our clients are mostly US-based</p><p class="p2">• Problem-solving over line-counting: we'll take a creative thinker over a fast typist any day</p><p class="p2">• Initiative, ownership, and the kind of communication where people don't have to guess what</p><p class="p2">you meant</p><p style="min-height: 1.7em;"></p><p class="p1"><strong>Nice to have</strong></p><p class="p2">• Exposure to MICS band or other medical-grade radio protocols</p><p class="p2">• Familiarity with medical device development standards (IEC 62304, ISO 13485, ISO 14971)</p><p class="p2">• Experience shipping firmware through formal V&V or regulatory processes</p><p class="p2">• Low-power optimization chops: sleep modes, duty cycling, battery life accounting</p><p class="p2">• Previous work with signal processing or sensor fusion on embedded targets</p><p class="p2">• Genuine curiosity about the devices you build, not just the code behind them</p><p style="min-height: 1.7em;"></p>