Skip to content
All projects

Enterprise workflow simulation · AI evaluation

TalentFlowEnterprise Recruiting Platform & AI Training Environment

I co-led a high-fidelity recruiting product simulation for AI agent training and evaluation. The engineering challenge was keeping connected hiring workflows and their observable state coherent across a broad enterprise interface.

Co-Lead · Product Simulation EngineeringTuring (Microsoft Research Programs)04/2026 — 06/2026

Actual dashboard from the AI training environment; shown as a simulation, not a live recruiting customer system.

01 / Snapshot

At a glance

Built
Recruiting workflow simulation spanning 20+ interconnected modules
Problem
Agent tasks need realistic, stateful enterprise behavior to evaluate
Ownership
Co-lead: module delivery, canonical models, parity, RCA, contributor review
Delivery
Training and evaluation environment; no commercial ATS customer claim

02 / Context

The engineering problem

An agent can complete one screen and still leave the product in an impossible state. Jobs, candidates, interviews, scorecards, approvals, offers, CRM, and reports have to tell a consistent story after each action.

The environment also needs observable before/after state for evaluation. The existing State Diff screen compares a fixture-derived baseline with current local state, making task effects inspectable in the captured build.

03 / System

System architecture

Connected workflow model

A logical map of the modules and consistency work described in the project record and visible in the product captures. It does not assert an unverified backend topology.

Shared relationship

Shared workflow state

Canonical models and parity checks keep entities aligned across modules

  • Jobs + candidatesRoles, applications, and pipeline stages
  • Interviews + scorecardsScheduling and structured evaluation
  • Approvals + offersDecision steps and downstream outcomes
  • CRM + sourcingProspect and talent relationships
  • Dashboards + reportsViews over connected workflow data
  • EvaluationScenarios, state diff, and RCA

The diagram describes product relationships. Screenshots confirm the visible modules and State Diff UI; the broader canonical-model and RCA work comes from the owner's project record.

04 / Judgment

Engineering choices & trade-offs

01

Model workflows as connected state

Problem
Isolated screens cannot support end-to-end agent tasks reliably.
Implementation
The project record describes canonical data models and parity frameworks across hiring, CRM, approvals, and reporting modules.
Implication / limit
A change in one workflow must stay coherent in related views; this increases the cost of fixture design and validation.

Owner project record; visible pipeline, CRM, and dashboard screens

02

Make task effects inspectable

Problem
A plausible UI alone cannot show whether an agent changed the intended entities.
Implementation
Evaluation scenarios and RCA methods are documented in the project record; the captured State Diff view compares fixture baseline with current local state.
Implication / limit
Inspectability helps diagnose behavior, while the screenshot alone does not establish the full evaluator implementation.

State Diff screenshot; owner project record

03

Build for product parity across modules

Problem
A simulation loses training value when related workflows disagree or omit expected states.
Implementation
The team delivered 20+ connected modules and used parity frameworks, implementation review, and contributor guidance to keep behavior aligned.
Implication / limit
Breadth required coordination and review; the record does not quantify agent performance gains.

Owner project record; walkthrough and product screenshots

05 / Execution

Hard problems, concrete responses

Cross-module consistency

A candidate can move through pipeline, interview, approval, and offer views that depend on shared state.

Response. Canonical modeling and parity review provide a common contract for those surfaces, according to the project record.

Evaluation fidelity

A task needs realistic starting conditions and a visible state change, not just a clickable path.

Response. Scenarios and RCA methods were built for agent evaluation; the captured State Diff view exposes fixture-to-current changes.

06 / Status

Delivery & outcome

Implemented

AI training environment

A high-fidelity recruiting simulation covering jobs, candidates, interviews, scorecards, approvals, offers, CRM, sourcing, dashboards, reports, and related workflows.

Implemented

Evaluation and collaboration

The project record attributes canonical models, parity frameworks, evaluation scenarios, RCA, contributor guidance, and implementation reviews to the co-lead work.

Foundation / boundary

Commercial recruiting use

This was a product simulation for AI training and evaluation. The case study does not claim real hiring customers or production ATS adoption.

07 / Proof

Real product evidence

The gallery shows the dashboard, fixture State Diff, jobs, candidate pipeline, CRM, and reporting surfaces. The owner walkthrough is preserved. Screens prove visible UI; deeper architecture claims are limited to the project record.

Product captures

Actual interfaces, reference demonstrations, and their source details.

TalentFlow hiring workflow screenshot 1

Dashboard overview for the recruiting workflow.

TalentFlow hiring workflow screenshot 2

State comparison view for workflow evaluation.

TalentFlow hiring workflow screenshot 3

Jobs page for managing open roles.

TalentFlow hiring workflow screenshot 4

Candidate pipeline view for a job workflow.

TalentFlow hiring workflow screenshot 5

Candidate listing and recruiting workspace.

TalentFlow hiring workflow screenshot 6

Candidate profile with hiring details.

TalentFlow hiring workflow screenshot 7

CRM workspace for recruiting relationships.

TalentFlow hiring workflow screenshot 8

Reports view for recruiting analytics.

08 / Stack

Technology by responsibility

Application
React · Next.js · TypeScript · Tailwind CSS
Product and evaluation
Workflow modeling · Product parity · AI agent evaluation · RCA