Overview
Why this exists, what it does, and the part I owned.
Problem
Onboarding a new hire was a manual checklist stitched by hand across four tools, dependent on one person's memory, with no reliable audit trail.
What I built
A configurable, event-driven engine: one intake triggers the entire sequence, adapting automatically across five contract scenarios.
My role
Accountable as Product Director, partnering with People and Engineering leads to define the RACI and the rules engine logic.
Impact
Consistent onboarding across every contract type, full auditability, and a faster path from offer acceptance to day one.
New Joiner Intake
Recruiting submits one intake. JML derives the contract type and generates every downstream task automatically.
Detected pathway Full-Time · Engineering of 5 configured contract scenarios
Onboarding Pipeline Ready for Day One
One event-driven engine, five contract scenarios. Connected-tool tasks fire automatically; the rest route to a person.
Task Board
Connected-tool tasks close themselves. Manual tasks (like contract steps in the MVP) stay tracked here until someone clears them.
To do 2
In progress 1
Done 3
Audit Log
Every step is timestamped and attributed, connected-tool or manual, so there's a full record from offer acceptance to day one.
| Event | Actor | Time |
|---|---|---|
| 👤Welcome-email gate sent | S. Kowalski (HRBP) | May 28, 9:02 AM |
| ⚙️IT ticket auto-filed | JML engine | May 28, 9:02 AM |
| ⚙️Slack welcome posted | JML engine | May 28, 9:03 AM |
| 👤Contract step completed | HR Generalist | May 29, 11:47 AM |
| ⚙️Status set to Ready for Day One | JML engine | June 2, 8:00 AM |