Embedded Systems Engineer

Cryomagnetics, Inc. | Oak Ridge, TN | Full-time, on-site

We've built superconducting magnets and cryogenic systems in Oak Ridge for more than 40 years. Our systems end up in universities, national labs, and industrial facilities worldwide. We enable research for cyclotron resonance, ion trapping, materials science, medical devices, quantum computing, energy, gyrotron development, and more. We pioneered cryogen-free magnet systems and build nearly everything in-house, seeing projects through from design to delivery.

Magnet power supplies, cryogenic temperature monitors, and level meters connect to customer test environments over serial, USB, and Ethernet, and more of that traffic moves onto a network every year. This role owns the software that makes it work, from the firmware running on the microcontroller to the driver running on the customer's PC.

You'll be the technical authority on firmware architecture, microprocessor and module integration, connectivity, and product cybersecurity. Where outside specialists make sense, you decide that and direct the work rather than absorbing all of it yourself. You'll report to the Engineering Manager and work day to day with our electronics engineer, applications engineers, and service group.

Parts of our firmware have been maintained by capable generalists for years, and some of it predates the connectivity we now ship. Part of this job is deciding what to carry forward, what to rebuild, and in what order, then making that case to people who will ask you to justify it.

Connected instruments also do not stop needing attention once they ship. Modules meet their EOL, operating systems get patched, and vulnerabilities get published. Maintenance after release is a permanent part of this role, not an afterthought.

• Own firmware architecture across the instrument line, including microprocessor communication, peripheral and module integration, and the structure that keeps new features from breaking old ones
• Develop and maintain embedded firmware in C and C++ for instrument control, measurement, and communication
• Integrate and maintain network connectivity, including Ethernet interfaces, across module firmware and operating system updates
• Own product cybersecurity, including our internal risk assessment, the working relationship with TUV for vulnerability analysis and penetration testing, and a secure, authenticated path for field updates
• Develop and maintain host-side software and instrument drivers in C# or Python for customer test environments
• Define and maintain instrument command sets and remote interfaces, including SCPI over serial, USB, and Ethernet
• Support board bring-up with the electronics engineer, from first power-on through validation
• Establish firmware release practice, including version control, reproducible builds, release notes, field update procedure, and traceability to product and board revision
• Triage escalated field issues involving firmware, connectivity, or host software, and drive fixes back into the released product
• Judge when a problem warrants an outside specialist, scope that work, and hold the vendor to it

• Bachelor of Science in Electrical Engineering, Computer Engineering, Computer Science, or a related field
• 7+ years of professional embedded development, including at least one connected product you shipped and then maintained in the field
• Strong C and C++ on microcontrollers, including peripheral configuration, interrupts, real-time control loops, and serial protocols such as UART, SPI, and I2C
• Demonstrated ownership of firmware architecture, not feature work alone. You should be able to describe a system you structured and why you structured it that way
• Experience with network-connected embedded devices, including TCP/IP stacks, sockets, and Ethernet or serial device servers
• Working understanding of embedded security practice, including authenticated firmware update, credential and key handling, attack surface reduction, and the common vulnerability classes that affect instruments on a customer network
• Host-side development in C# or Python, with experience producing drivers others depend on
• Able to read a schematic and a datasheet, and to debug with an oscilloscope or logic analyzer instead of guessing
• Git or comparable version control, used in a released-product context rather than personal projects
• Willing to work inside legacy code you did not write and improve it incrementally without breaking instruments…