How are titles assigned to each level?

Titles scale with depth: the root is the CEO, level one holds VPs, then directors, managers, and individual contributors at the leaves. Each level draws from a title pool appropriate to its seniority.

What does the flat JSON format contain?

Each employee has an id, name, title, department, and a managerId pointing to their manager, with the CEO's managerId set to null. That shape plugs directly into most org chart and tree-building libraries.

How is the number of reports decided?

Each manager gets a random span of direct reports up to the maximum you set. The span varies per manager, so the chart is uneven and realistic rather than a perfect pyramid.

Are employee names guaranteed unique?

The generator tracks used names and retries to avoid duplicates within a chart. In the rare case the name pool is exhausted it appends a counter to keep ids and names distinct.

How are departments handled?

Departments are assigned at the first level below the CEO and then inherited down each branch, so a director and their reports share the same department, mirroring how real orgs are structured.

Org Chart Data Generator

An org chart data generator that builds a fake company hierarchy with a CEO at the top, leaders below, and individual contributors at the leaves. It produces either an indented tree to read or flat JSON with managerId links for feeding org chart visualizers and HRIS demos.

How it works

You choose two parameters: how many levels deep the hierarchy runs and the maximum number of direct reports any manager may have. Starting from a single CEO, the generator gives each manager a random span of reports up to your maximum, so the tree is uneven rather than a tidy pyramid. Titles scale by depth — CEO, then VPs, directors, managers, and finally individual contributors — and departments are set at the top level and inherited down each branch.

Every employee carries an id, name, title, department, and a managerId that points to their manager, with the CEO’s manager set to null. The whole structure is seeded for reproducibility, and Regenerate advances the seed for fresh names and shape.

Tips and example

For a mid-size demo org, try four levels with a maximum of three reports — that yields a few dozen employees across several departments. A flat record looks like this:

{
  "id": "E5",
  "name": "Mia Patel",
  "title": "Director",
  "department": "Engineering",
  "managerId": "E2",
  "level": 2
}

Use the indented tree to sanity-check who reports to whom, then copy the flat JSON for code that needs managerId links. Keep the span modest to avoid generating an unwieldy number of nodes at deeper levels.