Enterprise Delivery Lead

Lucentive; Eu; Remote; EUR 90,000 - 130,000; Full time

Job summary

Lucentive is seeking an Enterprise Delivery Lead to own delivery on an engagement end-to-end, in writing, before it gets relitigated under pressure.

You scope the operating model for a given client, turn that into a phased plan the engineering team can build against and the client's governance process can approve, and run the cadence that keeps the two in sync, until their own team runs it without Lucentive.

Responsibilities

• Scope each engagement
• Turn a client's stated need into a phased plan for the Context Architect and engineering team to build against
• Own the delivery cadence
• Own the delivery cadence: track what ships against the

Job description

Systems

• Open role

Run the engagement until the client can run it.

You scope the operating model for a client, turn it into a phased plan the team can build and their governance can approve, and run the cadence that keeps the two in sync, until their own team runs it without you.

Remote-first

• EU-based
• Some client travel
• Contract or full-time

Mission

What the role does and why it matters here.

The Enterprise Delivery Lead owns delivery on an engagement the way the Context Architect owns structure and the AI Systems Engineer owns runtime: end to end, in writing, before it gets relitigated under pressure. You scope what the operating model looks like for a given client, turn that into a phased plan the engineering team can build against and the client's governance process can approve, and run the cadence that keeps the two in sync. You are the person a client-side executive calls for a straight read on where the engagement stands, and the person internally who turns a technical roadmap into a delivery plan a bank's or insurer's risk function can actually sign off on. The bar is not a shipped feature; it's an operating model the client's own team can run without Lucentive standing behind every decision. That means you sit close enough to the architecture to represent a tradeoff accurately in a compliance conversation, and close enough to the client to know when "not yet" is the right answer.

Responsibilities

What you would own.

• Scope each engagement
• Scope each engagement: turn a client's stated need into a phased plan the Context Architect and engineering team can build against, and the client's governance process can approve.
• Own the delivery cadence
• Own the delivery cadence: track what ships against the