Process Discovery & Transformation Lead
Job description
About the role
This role defines and scales discovery for Eliza service offerings by turning enterprise workflows into structured AI build plans. You convert ambiguity into clear, executable plans that engineering teams can build.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Bottlenecks, inefficiencies, and revenue leakage are identified to highlight obstacles that block value in existing processes.
Business processes are translated into AI use cases to articulate clear return on investment for client stakeholders and ownership groups.
Expected outcomes are quantified where stated to capture potential revenue lift, cost reduction, and cycle time improvement.
Findings are converted into structured AI project plans defining inputs, outputs, decision logic, and system integrations.
Plans are shaped in close collaboration with engineering teams to ensure they respect technical constraints and remain executable.
Clarity, scope discipline, and measurable outcomes are driven to ensure solutions reflect real workflows and deliver intended value.
Requirements
Experience in process improvement, operations, or transformation roles within large organizations is required.
A background in Six Sigma, Lean, or similar structured methodologies for analyzing workflows and identifying improvements is required.
A proven track record of delivering measurable impact in large organizations through transformation and optimization initiatives is required.
Strong experience conducting stakeholder interviews and synthesizing insights across diverse functions and audiences is required.
The ability to translate business processes into structured frameworks and execution plans that guide implementation and governance is required.
Comfort with collaboration across business and technical teams, navigating hierarchies and disciplines to advance initiatives is required.
Nice to have
Working with or within private equity-backed companies to understand accelerated delivery contexts and heightened performance expectations is a plus.
Exposure to digital transformation, automation, or AI initiatives in complex environments with evolving requirements is a plus.
Practical notes
This role operates in the United States and requires full-time onsite or hybrid engagement as defined by Eliza policies. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Process discovery translates operational complexity into actionable build plans that connect business needs to technical execution. Success depends on structured analysis methods and clear communication across technical and business audiences to avoid misalignment. Modern AI solutions rely on well-defined inputs, outputs, and decision logic to deliver reliable and measurable outcomes. Documentation and translation turn ambiguous workflows into repeatable system designs that teams can implement consistently. Cross-functional collaboration aligns stakeholder expectations with technical implementation and delivery constraints.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.