About iWorx
iWorx Systems is a small, engineer-owned company located in Dover, NH. For over 30 years, iWorx has been building data acquisition hardware and software for life science education and research. Our instruments are used in physiology, pharmacology, and biomedical engineering labs worldwide.
Who We Are Looking For
We seek an on-site entry-level electrical engineer to work directly alongside the hardware engineer who designs the boards and the software engineer and founder who is the principal architect of the primary host software. That’s the whole loop, and you’d own a third of it. There is no bureaucracy between you and a decision, and the people you work closest with are just down the hall.
Our Tech Stack
Our systems are built on 32-bit ARM microcontrollers running Zephyr RTOS, streaming data over high-speed USB (480 Mb/s) and Bluetooth to our acquisition and analysis software on Windows and macOS.
What You’ll Do
- C Firmware Development: Design, write, and maintain C firmware for 32-bit ARM microcontrollers across our data acquisition product line.
- End-to-End Ownership: Own projects from requirements and architecture through board bring-up, debugging, release, and post-launch support.
- Zephyr RTOS Management: Work in Zephyr RTOS, maintaining our internal fork and contributing changes back upstream to keep the fork thin and rebases simple.
- Test Automation: Build and maintain hardware-in-the-loop (HIL) test automation in Python.
- Target Debugging: Debug hardware and firmware using SWD/JTAG debuggers, logic analyzers, and oscilloscopes.
- Environment Ownership: Own the development environment - including toolchains, dependencies, and build setup across the engineering workstations (including your own).
- Technical Voice: On a team this small, you are expected to actively contribute ideas, designs, and architectural direction.
What We’re Looking For
Required
- C Language: Proficiency in C for embedded targets
- RTOS Experience: Hands-on experience with an RTOS. (Zephyr is a major plus; experience with FreeRTOS, ThreadX, or similar means you can ramp up quickly).
- Firmware Debugging: Strong debugging skills. This is the single most important thing on this list. Much of the work is finding out why something that should work, doesn’t.
- Version Control: Git fluency (branching, history, and confidently recovering prior versions of work).
- Linux Competency: Comfort in Linux, including managing your own Python environments and package dependencies without support.
- Self-Direction: Ability to work independently and thoroughly document your work.
Strong plus
- Direct experience with Zephyr RTOS
- Submitting pull requests to an upstream open-source project
- C++ experience
- Hardware-in-the-loop test automation
- High-speed USB and BLE
- Reading schematics and working alongside hardware bring-up
- Background in life science instrumentation, medical devices, or lab equipment
Note on Hardware Design:
Hardware design experience is not required. Familiarity with circuits, schematics, and PCBs is helpful, but we have a dedicated hardware engineer who owns schematic and board design.
Is This The Right Fit For You?
This role is for engineers who want ownership more than process. You will not be handed a decomposed ticket. You will be handed a problem, and the trade-offs will be yours to make.
That’s the main appeal, and the main demand. You’d be the only firmware engineer on-site. There is no large safety net, no mandatory code review culture, and no one to catch errors if you miss them. The engineers who thrive here are those who build their own safety net: tests, tooling, documentation, and the discipline to use them consistently.
If you want a large corporate team, formal approval layers, and a well-defined lane, this is not that job. If you’ve been the person on a big team who wished you could just fix the thing, it might be exactly that job.
Resume & Cover Letter
Please submit both your resume and a cover letter. Applications without a cover letter will not be reviewed.