Senior Embedded Engineer

In short

If you're a Senior Embedded C engineer who gets why a misbehaving radio at 2 AM is both annoying

and the best puzzle of your week, we'd love to talk. You'd be joining us on a freelance, time &

material basis: you're paid for the hours you actually work on real client projects. We're ready to

start right away, at full capacity. 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, BOSE, and Neurable, 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. We use AI every day, in actual work, not just in company decks. If

your C code has ever made an antenna, a sensor, or a medical-grade device behave itself, you

already get why we love what we do.

Who this role is NOT for

If you like being handed a spec, a ticket, and a "wake me when it's done", we're probably not your

people. Embedded at intent means chasing edge cases across silicon, stacks, and radios, sometimes

in the same afternoon. We're looking for engineers who ask "why" before "how", who read a

datasheet and then actually question it, and who know that "it works on my bench" is the beginning

of the conversation, not the end. We're AI-native and we expect you to treat AI as a daily multiplier

(digging through vendor docs, drafting test harnesses, reasoning about tricky timing issues), not as a

gimmick. On freelance: we're not expecting you to rewrite our toolchain in week one. What we do

expect is ownership of what you touch, straight talk when things get complicated, and actual

curiosity about the device on the end of your JTAG.

What you'll do

• Build and maintain embedded firmware in C for STM32-based connected devices
• Work inside the Modus SDK and the broader Cypress/Infineon ecosystem to make hardware

do what the spec says, and a few things it didn't

• Integrate and tune FreeRTOS: tasks, priorities, queues, interrupts, the whole discipline of not

breaking real-time behavior

• Tackle multi-radio architectures in practice: BLE and Wi-Fi coexistence, arbitration, throughput

versus power trade-offs• Collaborate closely with hardware, mobile, QA, and the client's engineering team on cross-

functional problems

• Debug the unglamorous stuff: logic analyzer, scope, sniffer, logs that don't want to exist
• Contribute to architecture decisions, code reviews, and knowledge-sharing inside the

Firmware & Hardware chapter

• Use AI tools as part of your daily workflow, not as a party trick

How we work

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.

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 Firmware & Hardware chapter

for knowledge-sharing, and simultaneously on a project squad led by a PM for day-to-day delivery.

What you'll get

• 110-190 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 (all Europe)

• Access to our internal knowledge-sharing: tech talks, experiments, side projects

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 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. 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)

• Technical meeting (~90 min, with the technical team)

• Final feedback within a few days.

Requirements

What we're looking for

ecosystem

• FreeRTOS: you know where the footguns are, and you don't find them by accident
• Proven experience with multi-radio architectures, especially BLE and Wi-Fi coexistence: timing,

arbitration, co-existence schemes, real-world throughput issues

• Comfortable reading schematics, board files, datasheets, and errata without flinching
• Fluent with the debugging toolkit: JTAG/SWD, logic analyzers, scopes, BLE sniffers, serial

tracing

• English at B2+, because our clients are mostly US-based
• Problem-solving over line-counting: we'll take a creative thinker over a fast typist any day
• Initiative, ownership, and the kind of communication where people don't have to guess what

you meant

Nice to have

• Exposure to MICS band or other medical-grade radio protocols
• Familiarity with medical device development standards (IEC 62304, ISO 13485, ISO 14971)
• Experience shipping firmware through formal V&V or regulatory processes
• Low-power optimization chops: sleep modes, duty cycling, battery life accounting
• Previous work with signal processing or sensor fusion on embedded targets
• Genuine curiosity about the devices you build, not just the code behind them