1

Biotech Software Jobs (NOW HIRING)

... software, or life sciences * Strong network within the biotech ecosystem, including emerging companies, incubators, and industry organizations * Proven track record consistently meeting or exceeding ...

... software applications, enterprise databases, data platforms, and computerized systems within pharmaceutical, biotechnology, medical device, or other regulated industries. · Demonstrated experience ...

... software applications, enterprise databases, data platforms, and computerized systems within pharmaceutical, biotechnology, medical device, or other regulated industries. · Demonstrated experience ...

... software applications, enterprise databases, data platforms, and computerized systems within pharmaceutical, biotechnology, medical device, or other regulated industries. Demonstrated experience ...

... software applications, enterprise databases, data platforms, and computerized systems within pharmaceutical, biotechnology, medical device, or other regulated industries. • Demonstrated experience ...

Global Software Sales Manager

Pomona, CA · Remote

$140K - $160K/yr

PSC Software, a division of PSC Biotech, is a leading provider of cutting-edge, cloud-based quality management and regulatory compliance solutions. Our software helps organizations streamline ...

Biotech Program Manager Location: South San Francisco Type: Full-time Ohalo is hiring a Biotech ... software systems, ensuring dependencies and critical paths are explicit and managed. * Define ...

Minimum of 3 years of experience in computerized system validation, automation software, and manufacturing systems within regulated life science industries (i.e. pharma, biotech) Well-versed in ...

Biotech Program Manager Location: South San Francisco Type: Full-time Ohalo is hiring a Biotech ... software systems, ensuring dependencies and critical paths are explicit and managed. * Define ...

Biotech Program Manager Location: South San Francisco Type: Full-time Ohalo is hiring a Biotech ... software systems, ensuring dependencies and critical paths are explicit and managed. * Define ...

BioTech Data Engineer

Saint Louis, MO · On-site

$111K - $133K/yr

Job Title: Biotech Data Engineer Job Type: FTE Work Mode: Remote The Biotech Data Engineer focuses on designing, building, and maintaining scalable Azure Databricks-based data pipelines and ...

About GenScript Founded in 2002 in New Jersey, GenScript Biotech Corporation accelerates innovation ... Own the Software Development Life Cycle (SDLC) for instrument control software: design, implement ...

next page

Showing results 1-20

Biotech Software information

See salary details

$48K

$111.8K

$166K

How much do biotech software jobs pay per year?

As of Jul 26, 2026, the average yearly pay for biotech software in the United States is $111,845.00, according to ZipRecruiter salary data. Most workers in this role earn between $90,000.00 and $130,000.00 per year, depending on experience, location, and employer.

What is the difference between Biotech Software vs Laboratory Technician?

AspectBiotech SoftwareLaboratory Technician
Required CredentialsDegree in biotech, computer science, or related field; knowledge of biotech software toolsAssociate's or Bachelor's in laboratory sciences; technical certifications often preferred
Work EnvironmentOffice or lab setting focused on software development, data analysis, and biotech applicationsHands-on lab environment performing experiments and sample analysis
Employer & Industry UsageBiotech companies, software firms, research institutionsResearch labs, hospitals, biotech manufacturing facilities

Biotech Software professionals focus on developing, implementing, and maintaining software solutions for biotech research and development, while Laboratory Technicians perform hands-on lab work to conduct experiments and analyze samples. Both roles are essential in the biotech industry but differ in skills, environment, and daily tasks.

What is biotech software?

Biotech software refers to computer programs and platforms designed specifically to support research, development, and operations in the biotechnology industry. These tools can help with tasks such as DNA sequencing, data analysis, laboratory management, and simulation of biological processes. Biotech software enables scientists and organizations to manage large datasets, automate experiments, and accelerate discoveries in areas like genetics, pharmaceuticals, and medical diagnostics. The software is crucial for improving accuracy, efficiency, and compliance in biotech workflows.

What are the key skills and qualifications needed to thrive as a Biotech Software Engineer, and why are they important?

To thrive as a Biotech Software Engineer, you need a strong background in computer science, bioinformatics, or related fields, often supported by a relevant degree and experience in software development for biological or healthcare applications. Familiarity with programming languages such as Python or R, databases, cloud platforms, and tools like BLAST or Genome Analysis Toolkit (GATK) is typically required. Excellent problem-solving ability, teamwork, and clear communication help professionals integrate complex biological data and collaborate with interdisciplinary teams. These skills are crucial for developing robust software solutions that enable scientific discovery and advance biotechnology research.

How does a Biotech Software professional typically collaborate with scientists and laboratory staff?

Biotech Software professionals frequently work alongside scientists, researchers, and laboratory staff to develop, customize, and maintain software tools that support experimental workflows and data analysis. Regular communication is essential to ensure that software solutions meet the specific needs of biological research, from managing large datasets to automating laboratory processes. This collaboration often involves requirements gathering, user training, troubleshooting, and iterative improvements based on user feedback. Building strong interdisciplinary relationships is key to delivering effective and user-friendly software in the biotech environment.
More about Biotech Software jobs
What cities are hiring for Biotech Software jobs? Cities with the most Biotech Software job openings:
What states have the most Biotech Software jobs? States with the most job openings for Biotech Software jobs include:
What job categories do people searching Biotech Software jobs look for? The top searched job categories for Biotech Software jobs are:
Infographic showing various Biotech Software job openings in the United States as of July 2026, with employment types broken down into 4% Locum Tenens, 2% As Needed, 86% Full Time, 1% Part Time, 1% Temporary, and 6% Contract. Highlights an 82% Physical, 3% Hybrid, and 15% Remote job distribution, with an average salary of $111,845 per year, or $53.8 per hour.

Staff Frontend Engineer (Design Systems & UX)

Deep Origin

South San Francisco, CA • On-site

Full-time

Medical, Dental, Vision, Life

Posted 10 days ago


Job description

About Deep Origin
Deep Origin is a biotech startup building an operating system for science that transforms how life science research is conducted. Led by Michael Antonov, co-founder of Oculus, and backed by Formic Ventures, we are redefining the infrastructure behind modern drug discovery. Our AI-driven platform enables scientists to accelerate discovery, reduce cost, and bring breakthrough innovations to life faster. As we scale, engineering excellence is a critical lever in advancing our mission to dramatically reduce disease and extend human healthspan.
Role Description
This is a Staff-level frontend engineering role for someone with strong product and UX judgment. You'll architect and ship the front-end systems behind an operating system for science, while helping define whether the product is actually good to use, not just functional. We don't have a dedicated product design team, so frontend engineers play a direct role in shaping interaction design, usability, and product quality. We want an engineer who can look at a complex scientific workflow, identify what is unclear or inefficient, propose a better direction, and ship high-quality product UI in close collaboration with the team.
As a Staff engineer you set technical direction for the front end: component architecture, the design system, state management patterns, performance budgets, and the standards that keep the codebase coherent as the team and product grow. You also bring strong product and UX judgment to how our tools look, feel, and behave across drug discovery tools, simulation interfaces, data explorers, and research workflows. In this role, frontend architecture and product UX are tightly connected: you help define the point where design quality meets production code. You raise the team's craft through architecture, shared patterns, code review, pairing, and pragmatic product judgment, helping the team ship interfaces that are coherent, usable, and technically sound.
Requirements
  • 7+ years building production web applications, with deep command of React, TypeScript, JavaScript, CSS, and HTML, and a track record of owning front-end architecture from design through ship.
  • Real technical leadership. You've set front-end standards, made architecture decisions, and pulled up the engineering bar for a team, not just shipped your own features.
  • Strong design instincts and spatial sense. You notice when the padding is off, when a flow has one step too many, when a table is burying the column that matters.
  • Experience with data-heavy, workflow-heavy, or tool-heavy products: scientific software, developer tools, analytics platforms, design tools, or similar.
  • Comfort with ambiguity. Hand you a loosely defined problem and you'll sketch a few approaches and make the case for one.
  • Product thinking at the interaction level. You ask whether the flow makes sense and whether the user has enough context, not just whether the screen looks good.
  • Solid front-end fundamentals at scale: state management, responsive and cross-browser work, testing, performance profiling, and clean version control habits.
  • Comfort with data visualization past the standard chart library, where the visualization is the interface.
  • A portfolio or body of work that shows craft, ideally with code you can talk through.

Nice to have
  • Experience with scientific or biotech software.
  • Background in or exposure to computational chemistry, biology, or physics, scientific research workflows, or drug discovery.
  • Experience establishing design patterns or component standards on a team without dedicated product designers.
  • Familiarity with 3D rendering or molecular visualization libraries (e.g., Mol*, NGL, 3Dmol.js) or WebGL.

What This Isn't
  • A visual or graphic design role. We're not looking for someone to make marketing assets.
  • A design-only role where you hand off specs. You write and ship the code.
  • A standard frontend role with a "design eye." The title says Frontend Engineer because you architect and ship code at a Staff level, but you'll be driving UX and design decisions, not implementing someone else's.
  • A design manager role. This is hands-on IC work.

What you'll do
  • Architect and ship the front end. Lead component architecture, the design system, and shared front-end infrastructure in React and TypeScript. You write reusable, well-tested code that holds up as the team and product grow. You're a committer, not a consultant: you open PRs, review frontend code, and hold the quality bar in the codebase yourself.
  • Set front-end technical direction. Drive decisions on state management, rendering strategy, performance budgets, and the patterns that keep the platform coherent, and write the RFCs and reviews that get the rest of the team on the same page.
  • Turn ambiguous product intent into concrete UI direction. Pull context from Product, Science, Engineering, leadership, customer feedback, Slack threads, prototypes, and existing workflows. Synthesize that input into clear flows, lightweight specs, implementation plans, and shippable UI.
  • Define the UX patterns the platform runs on: Shape patterns for navigation, data display, workflow composition, error and empty states, loading behavior, progressive disclosure, and complex multi-step flows. Turn repeated product needs into reusable component and interaction standards
  • Make user flows coherent end to end. Context should carry through each step, the next action should be obvious, and the surrounding UI should help rather than get in the way. The flow has to solve the user's problem, not just look clean.
  • Prototype and build production UI for complex scientific workflows: work on multi-step pipelines, parameterized simulations, molecular viewers, results dashboards, and other data-heavy research workflows.
  • Work directly with complex scientific and technical data. Understand what a researcher needs to see, how they need to manipulate it, and how to make dense workflows, structured results, simulations, and visualizations understandable and actionable.
  • Integrate the front end with backend APIs and distributed platform services. Keep the product reliable and fast across browsers, devices, and environments.
  • Treat performance and accessibility as engineering work, not polish. Set performance expectations, chase down bottlenecks, improve accessibility, and pay down UI and technical debt as part of normal product development.
  • Find and fix UX debt. Improve screens that were never fully designed, flows that were stitched together over time, and inconsistencies that accumulated as the product evolved.
  • Set and evolve frontend engineering standards. Help define expectations for automated testing, code review, CI gates, component quality, accessibility, and maintainability as the platform scales.
  • Raise the team's product and frontend craft. Pair with engineers, review code, share patterns, and make product-quality concerns visible early. Help the whole team build better judgment so quality does not depend on one person being in every conversation.
  • Make pragmatic product and interaction decisions. Use strong judgment on layout, hierarchy, motion, and interaction design. When the path is clear, move quickly; when tradeoffs are meaningful, frame the options and drive alignment with Product, Engineering, Science, and leadership.

Values & Working Style
  • High agency. You do not wait for perfect specs. You pull context, identify the missing decisions, propose a path forward, and create momentum.
  • Ownership. You care about the full path from product intent to production behavior. You stay close to the details until the product works well for users.
  • Comfort with ambiguity. You can operate in an early, fast-moving company where requirements are incomplete, priorities shift, and the best way to align is often to make the work concrete.
  • Clear communicator. You work well with both technical and non-technical people. You can explain tradeoffs, frame options, and make complex product or technical decisions easier to reason about.
  • Pragmatism. You optimize for impact, not for being right. You know when to prototype, when to systematize, when to pay down debt, and when to move quickly.
  • Bias toward working software. You use prototypes, preview environments, and production code to make product discussions concrete.

Location, Work Authorization & Benefits
  • This role requires working onsite in San Francisco at least 3 days per week.
  • Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time.
  • Competitive compensation package with meaningful equity.
  • Comprehensive health, dental, and vision coverage.
  • Annual team gatherings and company events.
  • Free lunch, snacks, beverages, and onsite gym access (for in-office employees).
  • The opportunity to shape the future of health, longevity, and our ability to simulate life.

Why This Role Matters Now
As we scale our AI platform and expand into new scientific initiatives, the quality of our interfaces directly shapes what researchers can accomplish. Complex science becomes more useful when the product makes workflows understandable, decisions clear, and powerful tools accessible. This role sets the craft bar for the frontend engineering and product UX at a point where we're growing fast. The job is making complex science usable, to turn ambiguity into shippable product, and to help the team build interfaces that are coherent, fast, reliable, and worthy of the science behind them.