Phylo, Inc.
Phylo, Inc.2 open roles

Member of Technical Staff - Forward Deployed Engineer

South San Francisco, CA · TorontoOn-siteMidFull-time

Posted 4 days ago

The role in short

Own end-to-end technical delivery of Phylo's AI platform for enterprise customers by building integrations, deploying infrastructure, and supporting production systems.

About Phylo

Phylo is an applied research lab building agentic intelligence to accelerate discovery for every biomedical scientist. We believe AI agents will fundamentally transform how biomedical research is done.

Our fast-growing team brings together world-class researchers and engineers across AI and biology, commercializing the Biomni Lab platform. Backed by a $38M seed round led by a16z and Menlo Ventures, and advised by Nobel Prize laureates and pioneering biologists, Phylo is building the next generation of AI systems for the life sciences.

About the Role

We're looking for a Forward Deployed Engineer to own the end-to-end technical delivery of Phylo's AI platform for our enterprise customers.

You'll work directly with leading pharmaceutical companies, biotech organizations, and research institutions to bring Biomni into their environments, integrate it with their existing systems, and make sure it works reliably at scale. This is a highly technical, customer-facing engineering role. You'll own the entire deployment lifecycle: understanding customer requirements, designing solutions, provisioning infrastructure, building integrations, navigating enterprise security requirements, and supporting production systems.

You'll operate at the intersection of our customers and our core engineering team, solving complex problems in real-world enterprise environments while turning what you learn into reusable infrastructure, integrations, and product improvements.

We're looking for someone who thrives on ownership, enjoys solving ambiguous technical problems, and is equally comfortable writing code, debugging distributed systems, and working directly with customer engineering teams.

What you'll do

  • Own enterprise deployments end-to-end: Lead each enterprise account from technical discovery and architecture through rollout and ongoing operations.
  • Build customer integrations: Write production code connecting Biomni to enterprise data, APIs, identity systems, and scientific infrastructure.
  • Solve complex technical problems: Diagnose and resolve cross-stack issues spanning applications, networking, infrastructure, and data systems.
  • Partner directly with enterprise customers: Translate customer requirements into technical designs and work with their teams to deliver successful deployments.
  • Shape the product: Bring customer insights to engineering, AI, and scientific teams and contribute improvements to the core platform.

What We're Looking For

  • Strong software engineering fundamentals: 2+ years of hands-on experience in software, infrastructure, or platform engineering, with strong Python skills and experience building production systems.
  • Customer-facing engineering: Experience in forward-deployed engineering, solutions engineering, technical consulting, or a similar customer-facing technical role; able to translate customer requirements into solutions and drive implementations.
  • AI-native engineering: Hands-on experience building or deploying LLM applications and AI agents, including model APIs, tool execution, or agent orchestration; enthusiastic about applying AI to real-world problems.
  • Cloud infrastructure and sandboxes: Experience with AWS, GCP, or Azure, Docker, Kubernetes, cloud networking, IAM, and secure, isolated sandbox environments for agent code and tool execution.
  • Enterprise infrastructure and security: Experience deploying enterprise software into single-tenant, customer-hosted, or highly regulated environments using infrastructure-as-code and CI/CD; familiarity with enterprise networking, SSO, secrets management, and security requirements.
  • Integration experience: Experience building integrations with REST APIs, Model Context Protocol (MCP), authentication systems, databases, and data pipelines to connect agents securely with enterprise tools and data.
  • Ownership and problem-solving: Thrive in ambiguous, fast-moving environments; diagnose complex cross-stack issues, make pragmatic trade-offs, and take problems from requirements through production resolution.

Nice to Haves

  • Experience with scientific computing, bioinformatics infrastructure, HPC environments, workflow engines, or batch schedulers such as Slurm, Nextflow, Snakemake, or AWS Batch.
  • Experience integrating with enterprise data platforms, object storage, distributed filesystems, or research data management systems.
  • Experience working with pharmaceutical, biotechnology, healthcare, or research organizations.
  • Experience with TypeScript, Go, or other backend and infrastructure programming languages.

Why Join Us?

  • Competitive salary and equity share in building the future of biomedical discovery
  • Full medical, dental, and vision coverage, including free therapy sessions and eyewear stipend
  • 401(k) to help you build long-term financial security (US only)
  • Unlimited PTO to recharge when you need it (US only)
  • Lunch and snacks when you're in the office
  • Regular team offsites and company events
  • A culture of excellence and speed - we move fast, think big, and support each other every step of the way
  • Your work will directly impact our mission to 100X biomedical discoveries through AI

Prep for this interview

5 questions likely to come up at Phylo, Inc., each matched to a line in this posting.

  1. 1Cloud, deployment and security
    They wrote: “Cloud infrastructure and sandboxes: Experience with AWS, GCP, or Azure, Docker, Kubernetes, cloud networking, IAM, and secure, isolated sandbox environments for agent code and tool execution.”

    How would you debug a deployment that works in staging but fails at the customer's site?

    How to answer

    Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.

    1. Compare versions, config and environment variables
    2. Check network rules, proxies and certificates (common in enterprise)
    3. Look at resource limits and permissions
    4. Add the missing check to your install steps afterwards

    Tip: List the usual suspects and how you'd check each without full access.

  2. 2Integrations and APIs
    They wrote: “Integration experience: Experience building integrations with REST APIs, Model Context Protocol (MCP), authentication systems, databases, and data pipelines to connect agents securely with enterprise tools and data.”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  3. 3Coding
    They wrote: “Strong software engineering fundamentals: 2+ years of hands-on experience in software, infrastructure, or platform engineering, with strong Python skills and experience building production systems.”

    Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.

    How to answer

    Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  4. 4LLMs, RAG and agents
    They wrote: “AI-native engineering: Hands-on experience building or deploying LLM applications and AI agents, including model APIs, tool execution, or agent orchestration; enthusiastic about applying AI to real-world problems.”

    A customer wants a chatbot over their internal documents. How do you build it?

    How to answer

    Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.

    1. Collect and clean the documents; handle permissions per user
    2. Split them into chunks, embed, and store with source links
    3. Retrieve, then answer with citations; say “I don't know” when retrieval is weak
    4. Build a test set of real questions with expected answers before launch

    Tip: Spend more time on the data and on testing than on the model.

  5. 5Ownership and working with customers
    They wrote: “Ownership and problem-solving: Thrive in ambiguous, fast-moving environments; diagnose complex cross-stack issues, make pragmatic trade-offs, and take problems from requirements through production resolution.”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

More at Phylo, Inc.

Similar roles at other companies

Phylo, Inc.

On-site

Apply