What you would work on

• - Microcontroller firmware, drivers, and protocol integration
• - IoT-connected devices, gateways, and field telemetry flows
• - Automation systems, test tools, and deployment-ready engineering assets
• - Technical documentation that supports production and handoff

How we operate

We are remote-first, review-driven, and biased toward concrete progress. That means written updates, architecture clarity, test evidence, and honest discussion of risk.

The environment suits people who want responsibility early and who are comfortable owning details instead of waiting for heavily layered process.

Who tends to fit well

• - You debug patiently and care about root cause, not just visible symptoms
• - You can explain tradeoffs clearly in writing and in reviews
• - You are comfortable moving between hardware constraints and software behavior
• - You prefer shipping useful work over polishing slides about possible work

How to reach out

Even when no formal role is published, we welcome concise introductions from engineers, technical writers, and collaborators who align with the work.

• - Include what you build, what stack you are strongest in, and what kind of work you want.
• - Link a GitHub profile, portfolio, firmware write-up, or project note if you have one.
• - Keep the introduction specific. We care more about signal than volume.