Software Engineer (Open Level)

Responsibilities

• Design, build, and ship production software that accelerates drug development - from internal tools to user-facing products to platform capabilities.
• Use AI tools (LLMs, agentic coding systems, retrieval-augmented pipelines) as a core part of how you work.
• Get close to the business. Understand the clinical, regulatory, or operational problem you're solving well enough to make good product decisions without waiting for a spec.
• Build for composability. Clean APIs, structured schemas, machine-readable documentation - what you build needs to be discoverable and extensible by people and agents who aren't engineers.
• Review and enable contributions from non-engineers. PMs, designers, and domain experts across the company are shipping code. You help ensure quality, security, and maintainability.
• Build the guardrails that lift technical quality. Proactively create automated tools - security scanners, skill files for end users, agents that clean up and standardize non-engineer code.
• Prototype rapidly. Many ideas should be live and testable within days, not weeks. Build the tool, get feedback, iterate.
• Collaborate across engineering, data science, product, and domain teams.

Requirements

• A track record of shipping production systems in ambiguous, fast-moving environments.
• You build with AI tools daily. Claude Code, Copilot, agentic workflows - whatever the best current tools are, you're already using them and have opinions about what works.
• Strong fundamentals: you write clean, maintainable code, you understand distributed systems and cloud infrastructure (AWS, GCP, or Azure), and you can debug hard problems.
• You're drawn to the problem space, not just the stack. You'd rather understand why a clinical operations team needs a tool than debate framework choices in isolation.
• Comfortable with ambiguity. You've worked in 0-to-1 settings or early-stage environments where the playbook didn't exist.
• Excellent communicator. You can explain technical trade-offs to non-technical stakeholders and align a room around a decision.
• Experience in pharma, biotech, or life sciences. Genuine curiosity about the domain.
• You want to operate at a higher tempo and a higher standard than you have before.

Nice to Haves

• Experience with LLMs, agentic coding systems, retrieval-augmented pipelines