depthfirst
depthfirst2 open roles

Forward Deployed Engineer

San Francisco, CAOn-siteMidFull-time

Posted yesterday

The role in short

Build and ship customer-facing features, APIs, and integrations while working directly with enterprise customers to deploy and operate depthfirst solutions.

About This Role

We’re looking for a Forward-Deployed Engineer to solve technical problems for our customers and build the software they need to succeed with depthfirst. You’ll work directly with enterprise engineering and security teams to understand their needs and own delivery from initial discovery through production.

Your work will span building customer-facing features, developing integrations, and helping customers deploy and operate depthfirst in their environments. Depending on the problem, you might extend a product capability, build an API integration, debug an application issue, or work through a complex deployment constraint. You’ll implement solutions yourself and turn recurring customer needs into lasting improvements across our product and platform.

We welcome engineers with different strengths. You might be a backend or full-stack engineer who wants to work more closely with customers, or an infrastructure engineer with deep experience in cloud systems, Kubernetes, and networking. You don’t need to arrive with expertise in every area. We’re looking for engineers who take ownership, learn unfamiliar systems, and ship solutions.

You’re excited about this role because you will…

  • Build and ship customer-facing features, APIs, and integrations that solve real customer problems.
  • Work directly with customers to understand their workflows, identify technical blockers, and define practical solutions.
  • Own delivery from discovery and technical design through implementation, testing, rollout, and iteration.
  • Help customers integrate, deploy, and operate depthfirst within their existing systems and technical constraints.
  • Investigate problems across application code, integrations, and infrastructure, and implement fixes.
  • Turn solutions developed for individual customers into reusable product capabilities, tooling, and automation.
  • Communicate technical tradeoffs and progress clearly, keeping customer and internal teams aligned.

Qualifications

  • A strong engineering background in at least one of the following:

    • Backend or full-stack software engineering: experience designing, building, and shipping production applications, services, APIs, or integrations.
    • Infrastructure or platform engineering: deep hands-on experience deploying and debugging production systems across cloud infrastructure, Kubernetes, and networking, with experience developing software and tooling.
  • Proficiency in a programming language such as Python, Go, TypeScript, or Java, and experience writing, testing, and maintaining production code.

  • Ability to take an ambiguous problem, identify a useful solution, and carry it through to production.

  • Strong debugging skills and a willingness to work across unfamiliar systems.

  • Strong communication skills and an interest in working directly with customers. Prior customer-facing experience is helpful but not required.

  • Ownership, practical judgment, and the ability to move quickly while building reliable software.

Bonus Points For

  • Experience delivering customer-facing features or owning technical engagements with enterprise customers.
  • Experience integrating software with enterprise APIs, authentication systems, and developer workflows.
  • Experience with cloud infrastructure, Kubernetes, networking, or enterprise deployment requirements.
  • Experience with AI platforms, developer tools, or security products.

What We Offer

  • Competitive salary with meaningful equity.
  • Health, vision, and dental insurance.
  • Office lunch and dinner when working from our San Francisco office.
  • Direct impact on customer success and product direction.
  • The opportunity to work at the cutting edge of AI and security.

depthfirst is an equal opportunity employer and does not discriminate on the basis of race, gender, sexual orientation, gender identity/expression, national origin, disability, age, genetic information, veteran status, marital status, pregnancy or related condition, or any other basis protected by law.

To all recruitment agencies: depthfirst does not accept agency resumes. Please do not forward resumes to depthfirst employees. depthfirst is not responsible for any fees related to unsolicited resumes and will not pay fees to any third-party agency or company that does not have a signed agreement with the Company.

Prep for this interview

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

  1. 1Coding
    They wrote: “Proficiency in a programming language such as Python, Go, TypeScript, or Java, and experience writing, testing, and maintaining production code.”

    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.

  2. 2Integrations and APIs
    They wrote: “Build and ship customer-facing features, APIs, and integrations that solve real customer problems.”

    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. 3Discovery and scoping
    They wrote: “Own delivery from discovery and technical design through implementation, testing, rollout, and iteration.”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  4. 4Cloud, deployment and security
    They wrote: “Infrastructure or platform engineering: deep hands-on experience deploying and debugging production systems across cloud infrastructure, Kubernetes, and networking, with experience developing software and tooling.”

    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.

  5. 5Ownership and working with customers
    They wrote: “Ability to take an ambiguous problem, identify a useful solution, and carry it through to production.”

    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 depthfirst

Similar roles at other companies

depthfirst

On-site

Apply