Get more replies from employers
Send a job-specific resume in minutes.
Socket.dev in San Francisco is seeking a lead ML scientist to own the central problem of turning noisy physiological signals into continuous language. You will shape data collection, signal representation, model families, and evaluations, working closely with founders and sensing/ hardware leads.
We seek PhD-level research ability and production-quality coding speed, with the goal of building a product-ready, low-latency system that generalizes across people, sessions, and devices.
We are looking for the person who will own the central machine learning problem at Subvocal: turning weak, noisy, highly variable physiological signals into continuous language.
We have already built prototypes that decode subvocal speech at more than 200 words per minute. The much harder problem now is generalization. A model that works on one person, in one session, with one device placement is not a product. It needs to work when the same person returns the next day, when the hardware moves slightly, and eventually when a completely new person puts it on and gives us only a few minutes of calibration data.
You will lead that effort end to end. You will work directly with the founders and our sensing and hardware leads to decide what data we collect, how we represent the signal, which model families we pursue, and how we evaluate whether we are actually making progress.
Some of the problems you will work on include:
Our current ML stack is primarily Python, PyTorch, CUDA, and distributed GPU training, with custom infrastructure for signal processing, data collection, experiment tracking, and evaluation.
You might be a great fit if you have unusually strong experience in deep learning for speech (ASR), time series, biosignals, neuroscience, BCIs, radar, or another domain where signals are noisy and data distributions shift constantly. We are especially interested in people with PhD-level research ability, whether or not that came through a formal PhD, who are also comfortable writing production-quality code and moving quickly when the research direction changes.
This is not a role where you will be handed a model architecture and asked to improve it incrementally. You will help decide how the problem should be framed in the first place, build the initial ML organization around you, and directly determine whether this technology becomes a real product.
This is a full-time, in-person role in San Francisco.