HR systems fail on the org chart, not the individual record: a director with no reports, an employee ID that collides, a start date in the future. This generator produces the whole employment row so you can seed all of it at once.
What you can control
- Seniority filters to individual contributor or lead-and-above, which is how most permission models actually split.
- Employee IDs take your own prefix, so they match the convention already in your system.
- Salary bands come as a range rather than a point value, matching how compensation is usually stored.
- Locations carry a work-mode tag — on-site, hybrid or remote — for testing filters that depend on it.
Testing ideas
- Org charts. Include "reports to" and seed an org-chart component. Check deep reporting chains and people with many direct reports.
- Seniority filters. Generate individual contributors and leads separately to test filters and permission rules tied to level.
- Employee ID prefixes. Set your real prefix and confirm search, sorting and imports treat the IDs as strings, not numbers.
- Long titles. Titles like "Senior Principal Solutions Architect" overflow badges and table cells.
What this is not
Reporting lines are generated per row rather than as a consistent tree, so the same manager will not appear across records. If you need a real hierarchy, generate the people first and assign managers yourself.