Back to jobs

Forward Deployed Engineer, Finance Solutions

Pay
Pay not listed
Work setting
Remote — work setting source
Listed location: Remote
Read the full posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering — team source
Department: Engineering
From the employer’s posting

What you’ll bring

All qualifications

Core experience

  • 5+ years building with data in production, with deep SQL fluency and comfort in Python
  • Familiarity with ERP and planning systems (NetSuite, Workday, SAP, Oracle)
  • Experience working directly with enterprise customers, including the parts that are uncomfortable: scoping, pushing back, and delivering bad news early
Qualification wording
5+ years building with data in production, with deep SQL fluency and comfort in Python
Familiarity with ERP and planning systems (NetSuite, Workday, SAP, Oracle)
Experience working directly with enterprise customers, including the parts that are uncomfortable: scoping, pushing back, and delivering bad news early

About Preql AI

You will be the loop between what customers need and what we build.

In the employer’s words · Read in context · Company website ↗

Apply at Preql AI

Posting record

Report an error

Open 3 monthsWe first saw this posting 103 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.

Status in our records
Live
First seen by us
Aug 11, 2026103 days ago
Recorded sightings
34
Last seen by us
Nov 22, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 103

Up longer than most. Similar jobs usually come down between day 3 and day 42.

From 633 similar postings that came down. Coming down is not always a hire.

Preql AI is hiring

2 open jobs

  • No new data jobs since August
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • BigQuery
  • Databricks
  • dbt
  • SAP
  • Snowflake
Where the posting names them
What we are looking for - 5+ years building with data in production, with deep SQL fluency and comfort in Python - Direct experience with cloud warehouses (Snowflake, Databricks, BigQuery) and transformation tooling (dbt or equivalent)
- 5+ years building with data in production, with deep SQL fluency and comfort in Python - Direct experience with cloud warehouses (Snowflake, Databricks, BigQuery) and transformation tooling (dbt or equivalent) - Real working knowledge of financial data. You know why the finance team's definition of revenue is different from the data team's, and you have modeled a chart of accounts, an allocation, or a close process before
Strong signals - Familiarity with ERP and planning systems (NetSuite, Workday, SAP, Oracle) - Background in consulting, solutions architecture, or professional services at a data or AI company

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

About Preql

Preql helps enterprises clean, unify, and govern messy internal data so it actually works for AI, analytics, and reporting. We work with large organizations navigating complex data environments and high-stakes operational workflows. Based in New York, our team comes from data infrastructure, AI, and enterprise software.

 

How we work

We’re a small team with little bureaucracy. Leadership expects individuals to take ownership, move quickly, and make good decisions for the company with support from their teammates. The curious do well here, are comfortable operating in ambiguity, and are willing to form opinions and act on their convictions instead of waiting for instructions.

You will sit inside customer environments, learn how a specific finance organization actually closes its books and plans its year, and build the semantic models that make that work. You will be the person who understands both a customer's GL and our platform internals well enough to get the numbers right and defend them to a controller.

This is not a support role and it is not pure services. Every deployment you run should make the next one faster. The work you do by hand in month one should be a product capability by month six. You will be the loop between what customers need and what we build.

What you will own

  • The business outcomes for a portfolio of enterprise accounts, from kickoff through production and expansion

  • Semantic models for finance logic: revenue recognition, cost allocation, GL and cost center hierarchies, headcount and driver based planning

  • Source integration and mapping across ERPs, planning systems, and warehouses, including the reconciliation problems that surface once real data lands

  • Working sessions with controllers, FP&A leads, and customer data teams, translating between finance language and data models

  • The judgment call on what is a modeling problem, a source data problem, or a product gap, and routing each one to the right place

  • A steady stream of product feedback backed by specifics, not anecdotes, so engineering builds against real customer friction

  • Reusable models, templates, and documentation that shrink time to value on every subsequent account

What success looks like

  • 90 days: you have taken an account from install to first trusted output, and you can explain any number in a customer's reporting back to its source

  • 6 months: time to first value for a comparable account has dropped measurably because of models and assets you built, and customers ask for you by name

  • 12 months: the delivery playbook is yours, expansion conversations start with work you did, and the next engineers we hire ramp against what you wrote

What we are looking for

  • 5+ years building with data in production, with deep SQL fluency and comfort in Python

  • Direct experience with cloud warehouses (Snowflake, Databricks, BigQuery) and transformation tooling (dbt or equivalent)

  • Real working knowledge of financial data. You know why the finance team's definition of revenue is different from the data team's, and you have modeled a chart of accounts, an allocation, or a close process before

  • Experience working directly with enterprise customers, including the parts that are uncomfortable: scoping, pushing back, and delivering bad news early

  • High tolerance for ambiguity. Early accounts will not have a playbook, and you will write the playbook

  • Judgment about when to solve something for one customer and when to solve it for all of them

Strong signals

  • Familiarity with ERP and planning systems (NetSuite, Workday, SAP, Oracle)

  • Background in consulting, solutions architecture, or professional services at a data or AI company

  • You have worked with regulated buyers

  • You have been the first or second technical hire on a customer facing team

  • Time spent inside a finance or accounting function, or close enough to one to have felt a close

Demand for Forward Deployed Engineer roles

New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.

Weekly new Forward Deployed Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 51, the most 267, and the latest week had 217.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Forward Deployed Engineer, by the work the posting describes.

Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.

Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.

An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Remote

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.