🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
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 end-to-end, including how a request flows from intake through automated synthesis to result and where the software seams and pain points are. Shipped meaningful improvements or features into production, with tests and documentation. Engaged with the existing roadmap and critical path to identify and sequence their own near-term priorities, flagging dependencies and risks along the way. By Day 90, You Will Have Delivered at least one core service or system component that other teams build against, with a clear interface and a solid understanding of its failure modes. Established or strengthened the engineering practices around your work (testing, deployment, observability) so the team can move faster with confidence. Seen your work run under real production load as we (ambitiously) begin shipping platform deliveries to customers — making real-world impact by the end of this window. Partnered with the automation and chemistry teams to ensure platform runs produce structured, traceable data through the systems you work on. By Year 1, You Will Have Become a primary owner of a major surface area of the platform, making architectural decisions on it independently. Kept those systems reliable as the underlying chemistry and automation requirements shifted, evolving the architecture to hold up under real change. Raised the engineering bar on the team through the systems you build, the reviews you give, and the practices you help establish. By Year 5, You Will Have Become a recognized technical leader within Satomic, shaping how the company builds software and mentoring strong engineers. Built core platform systems that have scaled through multiple generations of chemistry capability without accumulating architectural debt that slows the company down. Made the software platform a durable competitive advantage in how Satomic runs chemistry at scale. What You Will Own The areas you'll own and help shape: Design, implementation, and operation of core platform services, APIs, and the orchestration layer behind Satomic's "API to Atoms." The data model and data systems that capture, track, and expose what happens across the platform, in collaboration with the teams that produce and consume that data. Internal tooling that operators, chemists, and other engineers depend on to do their work. Engineering quality and operation of the systems you work on: testing, deployment, infrastructure-as-code, observability, running them in production, and the architectural decisions that keep them correct as the platform evolves. Proactive discovery of platform needs, working directly with the chemistry and automation teams not just to fill requests but to show them what's newly possible and surface features and improvements they wouldn't have thought to ask for. Technical judgment calls (build-vs-buy, where complexity lives, which abstractions to commit to) for your area of the platform, made in coordination with the broader Development team on anything that touches shared infrastructure. You run what you build. Operating your services in production is part of the role: owning the deployment, instrumentation, alerting, and debugging for what you ship. As the platform matures and carries real customer load, this includes joining a light on-call rotation for the systems the team owns. We're not there yet: we'll build the rotation, runbooks, and alerting thresholds together as production demand makes it necessary, rather than imposing a heavy on-call burden before the platform warrants it. This Role Is What This Role Is (and Is Not) A senior, hands-on role building core software systems on Satomic's platform. A full-stack software engineering role (backend services, data, and frontend) where systems thinking, sound architecture, and the ability to own problems end-to-end matter. A role where you operate what you build, with infrastructure and on-call shared across the team as the platform matu
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.