Process Analyst

Why this role exists

Discovery is the most under-resourced part of this model everywhere it's run, and it's the part everything else depends on. It also shouldn't be done by the most expensive person on the team. This is a real job on its own and the honest entry point into the forward deployed engineer track.

What you'll do

• •Run structured discovery interviews with client staff at every level, from owner to floor
• •Build the process map: every step, who does it, how often, how long, what it costs
• •Find the workarounds — the informal fixes people invented that reveal where the real problem is
• •Draft the systemization plan and rank candidates by hours returned per dollar
• •Hand a clean, quantified problem to the engineer so build starts on day one, not week three

What we need from you

• •You ask good questions and, more importantly, you shut up and listen to the answer
• •Rigorous with numbers — a process map with invented figures is worse than none
• •Comfortable in working environments: shop floors, kitchens, warehouses, job sites
• •Clear written English; you'll produce the document the whole engagement runs on

Nice to have

• •Operations, industrial engineering, or business analysis background
• •You've worked a frontline job in one of the industries we serve
• •Spanish
• •Light scripting or SQL

Your first 90 days

• •Week 1–2: shadow discovery on a live engagement and write the secondary process map
• •Week 3–6: run your own discovery under review
• •By day 90: owning discovery for Deploy Sprints independently, with maps engineers can build from without a rewrite