Tagup
Tagup2 open roles

Forward Deployed Engineer

$120–150kVirginia; California; Florida; Idaho; Salt Lake City, UTHybridMidFull-time

Posted Sep 15, 2026

The role in short

Embed with defense customers to integrate the platform with government systems, onboard data, build custom workflows, and ship production code.

Tagup is a defense technology company founded at MIT that is delivering logistics decision advantage with next-generation AI. We’re growing rapidly and are looking for change-makers passionate about delivering innovative technologies to solve the most challenging problems in the world’s highest stakes environments. This is an exciting opportunity to engage in meaningful work that strengthens national security and contributes to the success of U.S. and allied forces. Join us in shaping the future of defense logistics for a safer tomorrow.

Forward Deployed Engineers work inside customer programs rather than at a distance from them. You’ll integrate our platform with government data and systems under real constraints, onboard messy real-world data, build the workflows a program runs on, and support deployments in customer environments, including on-site when a program needs it.

The work reaches users quickly. What you ship often gets into the hands of the people making readiness decisions within weeks, and what you learn in the field feeds back into the product.

Responsibilities

  • Integrate our platform with government data and systems under real constraints, and onboard the imperfect data programs actually run on
  • Configure the product against program requirements and support releases, including in government cloud environments
  • Build custom workflows that drive adoption, usage, and engagement with key customers
  • Triage and resolve customer-reported issues in their environments rather than passing them along
  • Own a component or program workstream end to end, returning working systems from a requirements document rather than closed tickets
  • Spend time on-site with customers, become their technical counterpart, and bring what you learn back to the product team
  • Write, test, and review code to a standard the rest of the team can build on

Desired Skills

  • 2+ years of professional software engineering experience, or equivalent demonstrated ability
  • Proficiency in Python and/or TypeScript, with SQL and data-heavy work: ETL, integration, and wrangling imperfect real-world data
  • Clear communication with technical and non-technical stakeholders, and comfort working directly with customers
  • Bias toward ownership: handed a requirements document, you return a working system
  • Willingness to travel to customer sites (military installations across the U.S.)
  • U.S. citizenship and eligibility to obtain a U.S. government security clearance

Bonus Points

  • Military service or experience supporting defense programs. Veterans are strongly encouraged to apply
  • Familiarity with service supply, maintenance, and readiness data systems
  • Experience deploying software in government cloud or other constrained or air-gapped environments
  • An active security clearance

You don’t need to check every box. If the mission and the work resonate, we'd love to hear from you!

What Success Looks Like in Year One

  • Customer decisions that used to run on spreadsheets and tribal knowledge are running on data you helped instrument.
  • The product team is shipping features that came directly from patterns you spotted on the ground.
  • Manual reporting that used to eat days of analyst time is automated and trusted.
  • When senior leadership at a customer command wants to know how their logistics operation is really performing, the answer comes from a system you helped build.

Salary

The estimated salary range for this position is between $120,000  and $150,000 annually. We strive to provide a competitive salary and benefits package that aligns with our employees’ experience and qualifications. Our primary objective is to attract and retain top talent, and we firmly believe in compensating our employees fairly for their invaluable contributions.

As a rapidly expanding technology company, we extend part-ownership to all team members through an Employee Stock Option Plan. Additionally, we offer comprehensive health insurance benefits, access to the company’s 401K plan, and foster a team-oriented work environment with regular company outings!

Why Join Us

  • The mission is real. Our software runs in front of people whose job is to keep the fleet moving — the consequences of getting it right are tangible.
  • Small team, high leverage. You'll have visibility from the engineering trenches to the executive team, and your work will compound.
  • Hard problems worth solving. Reinforcement learning applied to logistics at the scale of a military service is genuinely novel work.
  • Competitive comp, meaningful equity, and the kind of professional growth that comes from being trusted with big things early.

Tagup is an equal opportunity employer and individuals seeking employment with us are considered without regard to race, color, religion, national origin, age, sex, marital status, physical or mental disability, veteran status, gender identity, sexual orientation, or any other characteristic protected by law.

Citizenship: Due to the nature of our work with the U.S. Department of Defense, applicants must be authorized to work for any employer in the U.S. We are unable to sponsor visas at this time.

Prep for this interview

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

  1. 1Integrations and APIs
    They wrote: “Proficiency in Python and/or TypeScript, with SQL and data-heavy work: ETL, integration, and wrangling imperfect real-world 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.

  2. 2Cloud, deployment and security
    They wrote: “U.S. citizenship and eligibility to obtain a U.S. government security clearance”

    The customer's security team sends a 200-question review. How do you handle it?

    How to answer

    Why they ask: Security reviews often block deals. FDEs help get through them.

    1. Start from your company's standard answers (SOC 2 report, past reviews)
    2. Answer clearly; don't oversell
    3. Bring in your security team for anything you're unsure of
    4. Keep the new answers for the next customer

    Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.

  3. 3Travel
    They wrote: “Willingness to travel to customer sites (military installations across the U.S.)”

    How do you handle being on the road with customers for weeks at a time?

    How to answer

    Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.

    1. Your past travel or on-site experience
    2. How you stay productive away from the team
    3. What travel level works for you, said plainly

    Tip: Be honest about what works for you. A mismatch here hurts both sides later.

  4. 4Discovery and scoping
    They wrote: “Configure the product against program requirements and support releases, including in government cloud environments”

    Tell me about a time the customer asked for one thing but needed another.

    How to answer

    Why they ask: Good FDEs spot when a request is a guess at a solution. They want proof you can redirect a customer without losing their trust.

    1. What they asked for, and the detail that made you doubt it
    2. How you tested the doubt (shadowed users, looked at logs, ran a quick prototype)
    3. How you made the case to the customer
    4. What shipped and what changed for them

    Tip: Pick a story where you checked your hunch with data or users before pushing back.

  5. 5Coding
    They wrote: “2+ years of professional software engineering experience, or equivalent demonstrated ability”

    Build a small in-memory cache. Then add expiry. Then a size limit.

    How to answer

    Why they ask: Staged exercises show how your code holds up when requirements change mid-interview, like at a customer.

    1. Start with get and set on a dictionary, plus tests
    2. Store an expiry time with each value and check it on read
    3. Track use order and evict the least recently used entry when full
    4. Say what you'd change for many threads or many machines

    Tip: Keep the first version simple and well tested so the next stage is a small change.

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 Tagup

Similar roles at other companies

Tagup

$120–150k · Hybrid

Apply