openripplingbiocom
Senior Software Engineer
Satomic
LocationSAN DIEGO, California, United States
WorkplaceON_SITE
EmploymentSALARIED_FT
Posted2026-06-05T15:35:16.672000-07:00
Last observed2026-06-13 05:24:10.532353
Job idbiocom-satomic-ai:rippling:48384892-1b6b-4b6f-808e-97de20d45512
About Satomic Satomic’s mission is to close the gap from idea to molecule with faster navigation of chemical space. We are building an automated chemistry platform that integrates laboratory robotics, software, and AI to transform small-molecule synthesis and drug discovery. Satomic has raised a $15M Seed from fantastic investors including Riot Ventures, HOF Capital, and Compound VC, and our team includes alumni from leading large pharmas, small biotechs, and AI labs. This role is critical to Satomic’s mission of closing the gap from idea to molecule by building the chemistry search engine that lets our customers see, query, and reach into Satomic’s accessible chemical space: trillions of multistep-accessible molecules grounded in the platform’s actual synthesis capabilities. As Satomic builds toward an “API to Atoms,” this role ensures that the interface our partners query against is reliable, low-latency, and grounded in the real synthetic capabilities of the platform. The medicinal chemists, computational scientists, and generative-model-driven design teams will depend on the product of your work to navigate chemical space as they solve the most important challenges in medicine and human health. About the Role This is a senior, hands-on engineering role on the Development team. You'll be building, not managing a team. You'll work on the core software platform at the center of Satomic's chemistry operations: the orchestration layer, internal tooling, and data systems that move a synthesis request from intake through execution to result. You'll work closely with the hiring manager and the rest of Development, alongside automation engineers, chemists, and our ML and cheminformatics teams, with the scope you own growing as the platform does. The right candidate is a strong, full-stack software engineer who owns problems end-to-end. You will design services and APIs, model the data that flows through the platform, and build the operator- and scientist-facing interfaces that sit on top of it, working across the stack from the database up to the UI. You'll help drive the architectural decisions that keep the system correct as the platform grows, spanning request orchestration and job scheduling, data capture and storage, the services other teams build against, and the internal web tools your colleagues use every day. We are deliberately looking for an engineer whose craft is not tied to a single language. Day to day, this role is mostly Python on the backend and TypeScript/React on the frontend, and we expect real fluency across that full stack. But we care far more about the judgment underneath: how you decompose a problem, model data, reason about failure, and choose the right tool for the job. The strongest engineers we know treat languages as instruments, comfortable across the stack today and equally ready to pick up a performance-oriented language like Rust, Go, or C++ (or something else entirely) when a problem calls for it. If "what language?" is the first question you ask rather than "what's the actual problem?", this probably isn't the right fit. Technologies and systems you may work with include: Python on the backend and TypeScript/React on the frontend, with the freedom to reach for the right tool when a problem warrants it Relational databases and SQL (e.g. Postgres), plus the data pipelines and event-driven systems that move data through the platform REST/gRPC APIs, message queues, and distributed systems design for experiment orchestration and platform control Cloud infrastructure (AWS / GCP / Azure), infrastructure-as-code, CI/CD, observability, and testing frameworks Integration points with laboratory automation systems, ML/conversion models, and the cheminformatics search engine This is a hands-on role for an engineer who likes owning problems across the stack and working closely with a small, multidisciplinary team. Expected Outcomes By day 30, you will have: Developed a working understanding of the platform en
This page is generated from the committed OpenOpps static snapshot. Use the source posting or apply link for the employer's current canonical posting state.