Senior Firmware Engineer

About Readybit

Readybit builds an IoT platform that monitors industrial chemical storage containers in the field. Battery-powered, cellular-connected devices sit on tanks in the real world, sample what's happening inside them, and report back to our cloud, which turns that signal into monitoring, alerting, and analytics for the people who depend on those containers. The firmware on those devices is the foundation everything else stands on. If it sleeps too much it misses events; if it sleeps too little it dies in the field. Getting that balance right is the job.

The role

We're looking for a senior firmware engineer to build the embedded software running on our field devices. You'll work close to the hardware across sensor integration, power budgeting, the on-device sensing-to-reporting cycle, configuration handling, and over-the-air updates, and you'll bring the kind of judgment that keeps deployed devices safe and predictable.

You'll also work shoulder-to-shoulder with the cloud team. The contract between firmware and cloud, what a device reports, how it's configured remotely, how updates roll out, is shared territory, and your input on both sides of it matters.

What you'll do

• Build and extend the firmware running on our battery-powered, cellular-connected field devices.
• Shape the device codebase architecture: RTOS task design and inter-process communication.
• Integrate sensors and improve the on-device sensing-to-reporting pipeline.
• Optimize for power: extend battery life in the field without sacrificing the responsiveness the product needs.
• Harden remote configuration and over-the-air updates so changes roll out safely to devices already in the field.
• Help maintain the data contract between firmware and cloud, and evolve it without stranding deployed devices.
• Debug behavior on real hardware: logic analyzers, serial logs, and field units that misbehave in ways no bench setup reproduces.
• Hold the bar on deterministic, safe, testable embedded software.

What we're looking for

Required

• Senior-level experience shipping production firmware on resource-constrained, battery-powered devices.
• Strong embedded C and C++.
• Hands-on RTOS experience and solid IPC architecture skills: task design, synchronization, message passing, and the failure modes that come with them.
• A track record of building deterministic and safe embedded software, code whose timing and behavior you can reason about and trust in the field.
• ARM Cortex experience (Cortex-M and/or Cortex-A).
• Comfort working close to the metal: datasheets, peripherals (I2C/SPI/UART/ADC), interrupts, and low-power design.
• Experience with cellular or other wireless-connected devices, and the realities of intermittent, expensive, high-latency links.
• A field mindset: you design for the device that's already deployed and can't easily be touched, not just the one on your desk.

Nice to have

• Embedded Linux experience.
• Edge AI / on-device inference experience.
• Experience with OTA update systems and the safety mechanisms that keep a bad update from bricking a fleet.
• Familiarity with cellular IoT platforms and webhook-style cloud integration.

Preferred AI qualifications

• A track record of putting AI tooling to work on real workflows, redesigning or streamlining how things get done, with results you can point to (faster cycle times, fewer defects, higher-quality output).
• Experience using AI responsibly in practice: weighing risks before deployment, checking outputs for accuracy and bias, and building review steps into AI-assisted work.
• Evidence that you keep sharpening your AI skills (prompt and context engineering, agent orchestration, multi-tool workflows) and stay on top of the field as it moves.

Why it's a good job

• Real ownership. You'll shape the device firmware and its architecture on a small team building the software layer for a big, modernizing industry. Your decisions carry weight.
• Code that ships to the real world. Your firmware runs on battery-powered devices sitting on tanks in the field, not in a lab. You'll see it work where it counts.
• Real problems. Physical hardware in harsh environments, intermittent connectivity, and power budgets measured in months. The constraints are real and the craft matters.
• Modern stack, no legacy baggage. A strict, tested toolchain, AI tooling in the daily workflow, and the freedom to use the best tools for the job.
• Fully remote. Work from wherever you do your best work.

If you build firmware you can trust in the field and want it running against the physical world, get in touch.