Instrument design requires engineers with broad interests and diverse skills.

We are particularly interested in people with experience in one or more of the following areas: analog and digital control, precision analog electronics, low-noise design, RF electronics, ADCs and DACs, PLLs, microcontrollers, FPGA design, firmware, signal processing, schematic capture and PCB design.

But individual skills are only part of the picture. We value engineers who can understand an instrument as a whole: electronic designers who can read and write code, firmware developers who understand the hardware they control, and people who can use Python to interface with instruments, automate measurements and analyze data.

No endless meetings, forced brainstorming sessions or management rituals. We prefer to spend our time designing, building and testing instruments.

If you own a soldering iron, have built electronic boxes, written code to control an experiment, spent too much time tracking down a few nanovolts of noise, or simply enjoy making instruments work, we would probably have things to talk about.

There is no single educational path that defines a good instrument designer. Scientific and engineering education is valuable, but practical experience, curiosity and the ability to make things work matter just as much.