Back to jobs

Senior / Lead Platform Forward Deployed Engineer - Cogentiq I2C

Pay
Pay not listed
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting

What you’ll work on

Full posting
  • Own the deployment playbook as a product.

  • Coach junior Platform FDEs, reviewing their work against the standards you set and growing them toward deployment ownership.

From the employer’s posting
Run incident command during deployment and hypercare. When a deployment breaks in a client environment, you run the incident: triage across the data estate, the application database, and upstream ERP feeds; communicate honestly with the client; and land the fix and the post-incident correction to the playbook. Own the deployment playbook as a product. The quick-start guides, validation suites, and synthetic data configurations you leave behind must make the next deployment cheaper. The bar is that a newcomer deploys the platform from your playbook with one setup script. Coach junior Platform FDEs, reviewing their work against the standards you set and growing them toward deployment ownership.
Own the deployment playbook as a product. The quick-start guides, validation suites, and synthetic data configurations you leave behind must make the next deployment cheaper. The bar is that a newcomer deploys the platform from your playbook with one setup script. Coach junior Platform FDEs, reviewing their work against the standards you set and growing them toward deployment ownership. What You need

What you’ll bring

All qualifications

Core experience

  • 6 or more years in data platform or deployment engineering, with at least two years deploying into environments you did not control (client tenancies, regulated environments, or equivalent).
  • Strong Python and SQL, with the judgement to review pipeline code for idempotency, failure behaviour, and configuration hygiene, not just correctness.
Qualification wording
6 or more years in data platform or deployment engineering, with at least two years deploying into environments you did not control (client tenancies, regulated environments, or equivalent).
Strong Python and SQL, with the judgement to review pipeline code for idempotency, failure behaviour, and configuration hygiene, not just correctness.

About Fractal

Cogentiq I2C is Fractal's agentic AI platform for invoice-to-cash operations, spanning Collections, Cash Application, Deductions, Credit Risk, and Invoice Management.

In the employer’s words · Read in context

Apply at Fractal

Posting record

Report an error

Open 3 monthsWe first saw this posting 90 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 23, 202690 days ago
Recorded sightings
124
Last seen by us
Nov 16, 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 90

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

Well past Fractal’s usual: its jobs come down by about day 45.

From 633 similar postings that came down, and 28 of Fractal’s. Coming down is not always a hire.

Fractal is hiring

35 open jobs

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

  • Hiring at a steady pace
  • Takes jobs down at a usual pace
  • 3% of open jobs were reposted
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
  • Azure
  • Databricks
  • PostgreSQL
  • SAP
  • SQL Server
  • FastAPI
Where the posting names them
- Deep Azure Databricks: Asset Bundles, workflows, Unity Catalog and metastore governance, cluster and library management, service-principal automation, and the CLI. - Strong Python and SQL, with the judgement to review pipeline code for idempotency, failure behaviour, and configuration hygiene, not just correctness. - PostgreSQL in production: schema evolution, write reliability, connection behaviour under load.
- Set and enforce the platform engineering standards: idempotent, rerunnable deployments; fail-fast error handling with no silent except-and-continue paths; environment-variable-driven parameterisation with a single point of change per client value; and configuration conventions that hold across Databricks today and Fabric tomorrow. - Own the shared utilities architecture: interface-function contracts and factory-pattern abstractions across Databricks, Fabric, PostgreSQL, SQL Server, and storage back ends, packaged as versioned wheel files through Azure Artifactory, so swapping a client's platform is a configuration change, not a rewrite. - Make the hard ingestion calls: auto-loader versus custom conflict-driven ingestion when the client will not provision Databricks, checkpoint and reprocessing strategy, retry and alerting design per pipeline, and writeback reliability to the application database.
About Cogentiq I2C Cogentiq I2C is Fractal's agentic AI platform for invoice-to-cash operations, spanning Collections, Cash Application, Deductions, Credit Risk, and Invoice Management. The platform runs on a four-tier architecture: a Next.js application layer, FastAPI services, the Cogentiq APA agentic orchestration layer, and a data estate built on Azure Databricks and PostgreSQL. Deployments land in client Azure tenancies against live ERP data (Dynamics 365, SAP), which means deployment engineering is a first-class discipline, not an afterthought to development. Why this role, now
Why this role, now The platform has crossed from being built to being deployed. Collections is entering pilot with enterprise clients, and the deployment machinery is real: Databricks Asset Bundles with one-click, script-based deployment; auto-loader ingestion running historical and incremental loads into a common data model; versioned bundles and wheel-file packages delivered through Git and Azure Artifactory; and a quick-start standard under which a newcomer must be able to stand up the full data platform by running one setup script. This role carries that machinery into client environments and makes it hold under client governance, client data, and client timelines. It owns everything between our release artefacts and a running, observable, correctly governed installation; candidates who want to work on agent behaviour and LLM integration should apply to the AI FDE track instead. What you will do
- 6 or more years in data platform or deployment engineering, with at least two years deploying into environments you did not control (client tenancies, regulated environments, or equivalent). - Deep Azure Databricks: Asset Bundles, workflows, Unity Catalog and metastore governance, cluster and library management, service-principal automation, and the CLI. - Strong Python and SQL, with the judgement to review pipeline code for idempotency, failure behaviour, and configuration hygiene, not just correctness.
- Navigate Unity Catalog and platform governance Client and internal IT control catalog and metastore provisioning, storage decisions, and access models. You will assess what their governance model means for our setup scripts, negotiate provisioning paths, and know when a shared-infrastructure convenience creates an SOW, NDA, or data-isolation problem that must be escalated rather than worked around. - Set and enforce the platform engineering standards: idempotent, rerunnable deployments; fail-fast error handling with no silent except-and-continue paths; environment-variable-driven parameterisation with a single point of change per client value; and configuration conventions that hold across Databricks today and Fabric tomorrow. - Own the shared utilities architecture: interface-function contracts and factory-pattern abstractions across Databricks, Fabric, PostgreSQL, SQL Server, and storage back ends, packaged as versioned wheel files through Azure Artifactory, so swapping a client's platform is a configuration change, not a rewrite.
- Own the shared utilities architecture: interface-function contracts and factory-pattern abstractions across Databricks, Fabric, PostgreSQL, SQL Server, and storage back ends, packaged as versioned wheel files through Azure Artifactory, so swapping a client's platform is a configuration change, not a rewrite. - Make the hard ingestion calls: auto-loader versus custom conflict-driven ingestion when the client will not provision Databricks, checkpoint and reprocessing strategy, retry and alerting design per pipeline, and writeback reliability to the application database. - Run incident command during deployment and hypercare. When a deployment breaks in a client environment, you run the incident: triage across the data estate, the application database, and upstream ERP feeds; communicate honestly with the client; and land the fix and the post-incident correction to the playbook.
- Strong Python and SQL, with the judgement to review pipeline code for idempotency, failure behaviour, and configuration hygiene, not just correctness. - PostgreSQL in production: schema evolution, write reliability, connection behaviour under load. - CI/CD for data platforms: Git-based release flows, semantic versioning, artefact repositories, and backward compatibility across component versions.
- CI/CD for data platforms: Git-based release flows, semantic versioning, artefact repositories, and backward compatibility across component versions. - Domain literacy in order-to-cash and accounts receivable data: invoices, receipts, remittances, customer masters, and ERP AR structures in Dynamics 365 or SAP. You cannot validate a deployment whose data you do not understand. - Client-facing composure: you will be the technical face of the deployment to client IT and finance stakeholders.

Your next step

Complete your application on fractal.wd1.myworkdayjobs.com. The employer’s form will show what is required.

Applying through Workday

  • You create an account with each employer before you can upload anything. Every Workday employer has its own account, so one sign-up doesn’t carry over.
  • “Autofill with Resume” comes right after sign-in, before the My Information and My Experience steps. Check every field it fills in those steps, since that’s what recruiters see.
  • Your application status lives in that employer’s Candidate Home, under the same sign-in.

Already applied? Track this application

Job description

View original posting ↗

It's fun to work in a company where people truly BELIEVE in what they are doing!

We're committed to bringing passion and customer focus to the business.

About Cogentiq I2C

Cogentiq I2C is Fractal's agentic AI platform for invoice-to-cash operations, spanning Collections, Cash Application, Deductions, Credit Risk, and Invoice Management. The platform runs on a four-tier architecture: a Next.js application layer, FastAPI services, the Cogentiq APA agentic orchestration layer, and a data estate built on Azure Databricks and PostgreSQL. Deployments land in client Azure tenancies against live ERP data (Dynamics 365, SAP), which means deployment engineering is a first-class discipline, not an afterthought to development.

Why this role, now

The platform has crossed from being built to being deployed. Collections is entering pilot with enterprise clients, and the deployment machinery is real: Databricks Asset Bundles with one-click, script-based deployment; auto-loader ingestion running historical and incremental loads into a common data model; versioned bundles and wheel-file packages delivered through Git and Azure Artifactory; and a quick-start standard under which a newcomer must be able to stand up the full data platform by running one setup script. This role carries that machinery into client environments and makes it hold under client governance, client data, and client timelines. It owns everything between our release artefacts and a running, observable, correctly governed installation; candidates who want to work on agent behaviour and LLM integration should apply to the AI FDE track instead.

What you will do
  • Own the deployment architecture of client installations from environment readiness through hypercare: bundle strategy, environment topology (Dev, QA, production; per-client catalogs), release sequencing, and sign-off that the installation meets the validation standard.

  • Navigate Unity Catalog and platform governance Client and internal IT control catalog and metastore provisioning, storage decisions, and access models. You will assess what their governance model means for our setup scripts, negotiate provisioning paths, and know when a shared-infrastructure convenience creates an SOW, NDA, or data-isolation problem that must be escalated rather than worked around.

  • Set and enforce the platform engineering standards: idempotent, rerunnable deployments; fail-fast error handling with no silent except-and-continue paths; environment-variable-driven parameterisation with a single point of change per client value; and configuration conventions that hold across Databricks today and Fabric tomorrow.

  • Own the shared utilities architecture: interface-function contracts and factory-pattern abstractions across Databricks, Fabric, PostgreSQL, SQL Server, and storage back ends, packaged as versioned wheel files through Azure Artifactory, so swapping a client's platform is a configuration change, not a rewrite.

  • Make the hard ingestion calls: auto-loader versus custom conflict-driven ingestion when the client will not provision Databricks, checkpoint and reprocessing strategy, retry and alerting design per pipeline, and writeback reliability to the application database.

  • Run incident command during deployment and hypercare. When a deployment breaks in a client environment, you run the incident: triage across the data estate, the application database, and upstream ERP feeds; communicate honestly with the client; and land the fix and the post-incident correction to the playbook.

  • Own the deployment playbook as a product. The quick-start guides, validation suites, and synthetic data configurations you leave behind must make the next deployment cheaper. The bar is that a newcomer deploys the platform from your playbook with one setup script.

  • Coach junior Platform FDEs, reviewing their work against the standards you set and growing them toward deployment ownership.

What You need
  • 6 or more years in data platform or deployment engineering, with at least two years deploying into environments you did not control (client tenancies, regulated environments, or equivalent).

  • Deep Azure Databricks: Asset Bundles, workflows, Unity Catalog and metastore governance, cluster and library management, service-principal automation, and the CLI.

  • Strong Python and SQL, with the judgement to review pipeline code for idempotency, failure behaviour, and configuration hygiene, not just correctness.

  • PostgreSQL in production: schema evolution, write reliability, connection behaviour under load.

  • CI/CD for data platforms: Git-based release flows, semantic versioning, artefact repositories, and backward compatibility across component versions.

  • Domain literacy in order-to-cash and accounts receivable data: invoices, receipts, remittances, customer masters, and ERP AR structures in Dynamics 365 or SAP. You cannot validate a deployment whose data you do not understand.

  • Client-facing composure: you will be the technical face of the deployment to client IT and finance stakeholders.

  • Nice to have: Microsoft Fabric, observability design (OpenTelemetry, Application Insights), and experience taking a data product through pilots at multiple clients in parallel.

Success in the first year
  • Two client deployments taken from environment readiness through hypercare, each validated against the standard suite and signed off on schedule.

  • A deployment playbook that demonstrably reduced the cost of the deployment that followed it, measured in elapsed time from access granted to validated installation.

  • Platform standards (idempotency, fail-fast, parameterisation) adopted across the data engineering codebase, evidenced in review practice, not just documentation.

  • At least one governance or infrastructure negotiation with client IT resolved without escalation to leadership.

If you like wild growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!

Not the right fit?  Let us know you're interested in a future opportunity by clicking Introduce Yourself in the top-right corner of the page or create an account to set up email alerts as new job postings become available that meet your interest!

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

Bengaluru

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.