Time since we first saw it
Day 2
Early. Similar jobs usually come down between day 4 and day 77.
From 51 similar postings that came down. Coming down is not always a hire.
Armenia; Azerbaijan; Georgia; Kazakhstan; Kyrgyzstan; Uzbekistan
Actively hiring, first seen by us 2 days agoWork setup in the employer’s posting: TELECOMMUTEFrom the employer’s posting
Run demo-and-feedback loops with use case owners, domain owners and stewards to turn their needs into specs
Own the BMAD spec chain so no code is written without an approved spec
Build glossary search, browse and term pages in the DLE, including term links to entities and contract fields
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
Collaborate directly with the people who will use the glossary
ensuring no code is written without an approved spec
Deliver glossary features inside the DLE, including search and browse of terms by domain
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
We are looking for a Data Forward Deployed Engineer to join EPAM in delivering data products on an enterprise Intelligence Platform built on Databricks. Each product begins with a data contract, and you will partner with 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 main entry point for business users into the platform. The prototype is developed 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, with the FDE directing and reviewing 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 Qualifications in 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)
Actively hiringFirst seen by us 2 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 2
Early. Similar jobs usually come down between day 4 and day 77.
From 51 similar postings that came down. Coming down is not always a hire.
673 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordCheck the employer’s posting for the current role and application details.
Already applied? Track this application
Yes. We’ve followed one other Data Forward Deployed Engineer with Databricks job there since November 2026. It is still up.
New AI Engineer postings at the employers we follow are up 134% over the last 6 weeks compared with the 6 before.
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.
We file this job under AI Engineer, by the work the posting describes.
AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.
Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.
An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Armenia; Azerbaijan; Georgia; Kazakhstan; Kyrgyzstan; Uzbekistan
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.
We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting