Confido
Confido

Forward Deployed Engineer

$200–270kNew York, NYOn-siteMidFull-time

Posted Oct 20, 2026

The role in short

Embed with enterprise customers to translate financial workflows into production software, building integrations and AI-powered document ingestion features.

The brands on your kitchen shelf are run by people doing extraordinary work that nobody sees.

We're building the platform they run on, and a brand they'll be proud to be part of.

Confido is the AI operating system that runs cash application, deductions, trade and planning in one place for CPG brands. That means Finance, Sales, and Ops finally work on the same number.

We’re trusted by 250+ brands managing $30B+ in revenue, including Daisy, OLIPOP, Simple Mills, Idahoan, and more. We've achieved best-in-class growth and recently raised a $55M Series B led by Insight Partners to accelerate our momentum.

If you want your work on shelves everywhere — and outsized ownership while you build — we'd love to meet you.

The Role

We are looking for a Forward Deployed Engineer to work directly with enterprise customers to turn real-world financial workflows into production software.

This role sits at the intersection of engineering, product, and customer implementation.

You’ll help customers go from kickoff → live while shaping the core platform.

Check out this site for more info about Engineering @ Confido.

What You'll Do

  • Work directly with enterprise customers during onboarding and implementation
  • Translate operational workflows into scalable Confido product features
  • Build integrations with customer systems and data sources
  • Extend the platform to support complex financial workflows
  • Identify product gaps and collaborate with product/engineering to close them

Typical projects include:

  • AI-powered document ingestion for financial data
  • Retailer and freight portal integrations (ex: Kroger)
  • Financial analytics and forecasting pipelines
  • Internal tools and customer-facing product features

What We're Looking For

Required

  • 2+ years of software engineering experience
  • Comfort working directly with customers and ambiguous problems

Nice to Have

  • Experience with data pipelines, AI systems, or integrations
  • Strong communication and product intuition
  • Interest in early-stage startups and high ownership roles
  • CS degree or equivalent experience

Stack

  • Backend: Rails, Python
  • Frontend: Typescript, React, Vue
  • Data: Postgres, Snowflake
  • Infra: AWS, Datadog, Appsignal, Mezmo
  • Product Analytics: PostHog
  • AI: Claude SDK + foundation models

🌴 Perks + Benefits

  • Equity — own a meaningful piece of the company you’re helping build
  • Fully paid health coverage through Aetna — we cover 100% of employee premiums
  • Top-tier dental and vision coverage through Guardian
  • Carrot Fertility Pro — comprehensive fertility and family-forming support
  • 12 weeks of paid parental leave
  • Unlimited PTO — plus regular 4-day holiday weekends we actually take
  • 401(k) through Vestwell
  • Paid relocation support — we’ll help you make the move to NYC
  • Fully equipped workspace from day one — laptop, monitor, keyboard, and a $200 stipend to personalize your setup
  • Team perks — catered Friday lunches, team dinners, and unlimited coffee + snacks featuring products from the brands we work with

Confido provides equal employment opportunities to all employees and applicants for employment and prohibits discrimination and harassment of any type without regard to race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state or local laws.

Prep for this interview

4 questions likely to come up at Confido, each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “Build integrations with customer systems and data sources”

    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. 2Data and SQL
    They wrote: “Experience with data pipelines, AI systems, or integrations”

    How would you design a daily pipeline that feeds customer data into our product?

    How to answer

    Why they ask: Tests basic data engineering: scheduling, failures, re-runs and monitoring.

    1. Extract with timestamps or change tracking, not full dumps, when possible
    2. Transform in steps you can re-run without creating duplicates
    3. Validate row counts and key fields before loading
    4. Alert a person on failure, with enough detail to fix it

    Tip: Make re-running safe (same input, same result) and say how you'd know it failed.

  3. 3Coding
    They wrote: “We are looking for a Forward Deployed Engineer to work directly with enterprise customers to turn real-world financial workflows into production software.”

    How do you keep quality high when you ship fast at a customer site?

    How to answer

    Why they ask: Speed is the job, but broken code at a customer is costly. They want your guardrails.

    1. Tests for the parts that touch customer data or money
    2. Code review even when it's fast, ideally by someone on the product team
    3. Feature flags and an easy way to roll back
    4. Clean up the shortcuts in the next release, and write them down

    Tip: Name the few checks you never skip, and what you skip on purpose.

  4. 4Ownership and working with customers
    They wrote: “If you want your work on shelves everywhere — and outsized ownership while you build — we'd love to meet you.”

    Tell me about something you shipped that broke in production.

    How to answer

    Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.

    1. What broke and who it affected
    2. How you found out and what you did in the first hour
    3. The root cause, said plainly
    4. What you changed so it can't happen the same way again

    Tip: Pick a real one with a cost. Spend most of the answer on what you changed.

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.

Similar roles at other companies

Confido

$200–270k · On-site

Apply