Back to jobs

Data Forward Deployed Engineer with Databricks

Pay
Pay not listed
Work setting
Remote — work setting source
Work setup in the employer’s posting: TELECOMMUTE
From the employer’s posting
Employment
Not stated

What you’ll work on

Full posting
  • Gather glossary needs from use case owners, data owners and stewards and turn them into specs

  • Build glossary search, browse and term pages inside the DLE

  • Link terms to entities and contract fields via semantic_term_urn

  • Design an impact view of products and consumers that depend on a term

  • Build a propose-or-change flow that routes to steward review and then Git merge request

From the employer’s posting
Collaborate directly with the people who will use the glossary
Deliver glossary features inside the DLE, including search and browse of terms by domain
Implement links from terms to entities and to contract fields, populating the DLE's existing semantic_term_urn field
Design an impact view showing which products and consumers depend on a term
Build a propose-or-change flow that routes requests to steward review and then into Git as a merge request

Tools in this posting

  • Databricks
Source — Tool mentions in context
We are seeking a Data Forward Deployed Engineer to join EPAM in delivering data products on an enterprise Intelligence Platform built on Databricks. Every product starts from a data contract, and you will work alongside the client's data team to build a working prototype that adds business-glossary features to the Data Landscape Explorer (DLE) — the client's register of domains, entities, owners and data products, and the primary entry point for business users into the platform. The prototype is built spec-first on the Databricks stack with Claude, where specs are written and approved before any code; Claude agents draft, build and test against those specs, and the FDE directs and reviews their work. Responsibilities Collaborate directly with the people who will use the glossary — use case owners, domain data owners and stewards — translating their needs into specs and running short demo-and-feedback loops Own the spec chain using BMAD: product brief → PRD → architecture → stories with acceptance criteria, ensuring no code is written without an approved spec and every merge request traces back to a story and its acceptance tests Deliver glossary features inside the DLE, including search and browse of terms by domain, and a page per term showing its definition, synonyms, data owner, steward, status and version Implement links from terms to entities and to contract fields, populating the DLE's existing semantic_term_urn field Design an impact view showing which products and consumers depend on a term Build a propose-or-change flow that routes requests to steward review and then into Git as a merge request Develop the UI using Databricks Apps, governed by Unity Catalog for comments, tags, permissions and lineage, and deploy via Asset Bundles Embed security into the design: authentication fails closed, on-behalf-of auth must never silently fall back to a service principal, and access is governed by Unity Catalog Operate entirely within the client's VDI and Coder workspaces, ensuring no client data leaves the secured perimeter Record decisions as ADRs in the platform's knowledge base Hand over a working demo, a runbook and a backlog for evolving the prototype into a product Requirements 5+ years of experience as a Forward Deployed Engineer, Data Engineer or Full-Stack Engineer delivering data products in close collaboration with business stakeholders Expertise in Databricks, including Databricks Apps, Unity Catalog and Asset Bundles Proficiency in spec-first delivery methodologies such as BMAD, writing product briefs, PRDs, architecture docs and stories with acceptance criteria Background in building data catalog, glossary or metadata management solutions, with familiarity with DataHub as a stewardship tool Skills in designing and implementing data contracts and governed release flows through Git Understanding of semantic models, business glossaries and lineage concepts, including linking terms to entities and contract fields Competency in secure authentication patterns, including on-behalf-of auth and fail-closed design Capability to work with AI coding agents such as Claude to draft, build and test against approved specs, directing and reviewing their output Experience recording architectural decisions as ADRs and producing runbooks and handover documentation Flexibility to use restricted development environments such as VDI and Coder workspaces while respecting data perimeter constraints Strong communication skills for running demo-and-feedback loops with use case owners, domain data owners and stewards Excellent command of written and spoken English (B2+ level)
Check the employer’s page ↗

Posting record

Report an error

Actively hiringFirst seen by us 11 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 11, 202611 days ago
Recorded sightings
10
Last seen by us
Nov 21, 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 11

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.

EPAM Systems is hiring

892 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

Your next step

Check the employer’s posting for the current role and application details.

Already applied? Track this application

Has EPAM Systems posted this job before?

Yes. We’ve followed one other Data Forward Deployed Engineer with Databricks job there since November 2026. It is still up.

  1. Place not statedStill up after 11 days, first seen Nov 11
  2. This jobUp 11 days so far, first seen Nov 11

Job description

View original posting ↗

We are seeking a Data Forward Deployed Engineer to join EPAM in delivering data products on an enterprise Intelligence Platform built on Databricks. Every product starts from a data contract, and you will work alongside the client's data team to build a working prototype that adds business-glossary features to the Data Landscape Explorer (DLE) — the client's register of domains, entities, owners and data products, and the primary entry point for business users into the platform. The prototype is built spec-first on the Databricks stack with Claude, where specs are written and approved before any code; Claude agents draft, build and test against those specs, and the FDE directs and reviews their work. Responsibilities Collaborate directly with the people who will use the glossary — use case owners, domain data owners and stewards — translating their needs into specs and running short demo-and-feedback loops Own the spec chain using BMAD: product brief → PRD → architecture → stories with acceptance criteria, ensuring no code is written without an approved spec and every merge request traces back to a story and its acceptance tests Deliver glossary features inside the DLE, including search and browse of terms by domain, and a page per term showing its definition, synonyms, data owner, steward, status and version Implement links from terms to entities and to contract fields, populating the DLE's existing semantic_term_urn field Design an impact view showing which products and consumers depend on a term Build a propose-or-change flow that routes requests to steward review and then into Git as a merge request Develop the UI using Databricks Apps, governed by Unity Catalog for comments, tags, permissions and lineage, and deploy via Asset Bundles Embed security into the design: authentication fails closed, on-behalf-of auth must never silently fall back to a service principal, and access is governed by Unity Catalog Operate entirely within the client's VDI and Coder workspaces, ensuring no client data leaves the secured perimeter Record decisions as ADRs in the platform's knowledge base Hand over a working demo, a runbook and a backlog for evolving the prototype into a product Requirements 5+ years of experience as a Forward Deployed Engineer, Data Engineer or Full-Stack Engineer delivering data products in close collaboration with business stakeholders Expertise in Databricks, including Databricks Apps, Unity Catalog and Asset Bundles Proficiency in spec-first delivery methodologies such as BMAD, writing product briefs, PRDs, architecture docs and stories with acceptance criteria Background in building data catalog, glossary or metadata management solutions, with familiarity with DataHub as a stewardship tool Skills in designing and implementing data contracts and governed release flows through Git Understanding of semantic models, business glossaries and lineage concepts, including linking terms to entities and contract fields Competency in secure authentication patterns, including on-behalf-of auth and fail-closed design Capability to work with AI coding agents such as Claude to draft, build and test against approved specs, directing and reviewing their output Experience recording architectural decisions as ADRs and producing runbooks and handover documentation Flexibility to use restricted development environments such as VDI and Coder workspaces while respecting data perimeter constraints Strong communication skills for running demo-and-feedback loops with use case owners, domain data owners and stewards Excellent command of written and spoken English (B2+ level)

About EPAM Systems

People
About 3,012 in 2024.Benefit plan filings (Form 5500)
Company
Listed as EPAM.
H-1B visas
21 approved for new hires in fiscal 2025.US Citizenship and Immigration Services

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

Turkiye

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

Work authorization

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

AI answers unavailable

We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting