CSV Tools

Sample JSON File

A downloadable sample JSON file containing 30 fictional employee records as a flat array of objects — ready for testing parsers, API mocks, and converters.

Data JSON Text format
Download JSON

sample-employees.json

Data Preview

30 rows × 7 columns
1nameemaildepartmentrolesalarystart_dateoffice
2Marcus Chenmarcus.chen@example.comEngineeringSenior Software Engineer1550002019-03-15San Francisco
3Priya Sharmapriya.sharma@example.comEngineeringStaff Engineer1780002019-06-01San Francisco
4David Kimdavid.kim@example.comEngineeringSoftware Engineer1250002021-01-10New York
5Rachel Torresrachel.torres@example.comEngineeringEngineering Manager1680002020-02-20San Francisco
6James Okaforjames.okafor@example.comEngineeringJunior Developer920002024-06-15Austin
7Lena Vogtlena.vogt@example.comEngineeringDevOps Engineer1400002022-04-01New York
8Amir Patelamir.patel@example.comEngineeringBackend Engineer1320002023-01-09London
9Sofia Lindbergsofia.lindberg@example.comDesignLead Designer1450002019-09-12New York
10Carlos Riveracarlos.rivera@example.comDesignUX Designer1120002021-07-20San Francisco
11Hannah Beckerhannah.becker@example.comDesignUI Designer1050002022-11-01London
12Yuki Tanakayuki.tanaka@example.comDesignProduct Designer1180002023-03-14San Francisco
13Olivia Martinolivia.martin@example.comMarketingVP of Marketing1650002019-04-22New York
14Ethan Brooksethan.brooks@example.comMarketingContent Strategist950002021-10-05Austin
15Nina Kowalskinina.kowalski@example.comMarketingSEO Specialist880002022-08-15New York
16Daniel Ochoadaniel.ochoa@example.comMarketingMarketing Analyst910002023-05-20Austin
17Samira Hassansamira.hassan@example.comMarketingSocial Media Manager820002024-01-08London
18Tyler Washingtontyler.washington@example.comSalesSales Director1580002019-11-30New York
19Jessica Huangjessica.huang@example.comSalesAccount Executive1100002020-06-14San Francisco
20Ryan O'Brienryan.obrien@example.comSalesAccount Executive1050002021-03-22London
21Fatima Al-Rashidfatima.alrashid@example.comSalesSales Development Rep720002023-09-01Austin
22Kevin Dupontkevin.dupont@example.comSalesSolutions Engineer1350002022-01-17San Francisco
23Megan Stewartmegan.stewart@example.comSalesAccount Manager980002024-03-11New York
24Laura Chenlaura.chen@example.comHRHR Director1480002019-08-05New York
25Brian Nakamurabrian.nakamura@example.comHRHR Business Partner1050002020-12-01San Francisco
26Chloe Duboischloe.dubois@example.comHRRecruiter780002022-05-23London
27Angela Morettiangela.moretti@example.comHRPeople Operations850002023-07-10Austin
28Isaac Fernandezisaac.fernandez@example.comEngineeringFrontend Engineer1280002022-09-19New York
29Sarah Mitchellsarah.mitchell@example.comDesignDesign Systems Lead1380002020-04-06San Francisco
30Omar Farahomar.farah@example.comEngineeringQA Engineer950002024-02-12London
31Natalie Parknatalie.park@example.comMarketingGrowth Manager1080002021-11-28San Francisco

Raw File Contents

sample-employees.json
[
  {
    "name": "Marcus Chen",
    "email": "marcus.chen@example.com",
    "department": "Engineering",
    "role": "Senior Software Engineer",
    "salary": 155000,
    "start_date": "2019-03-15",
    "office": "San Francisco"
  },
  {
    "name": "Priya Sharma",
    "email": "priya.sharma@example.com",
    "department": "Engineering",
    "role": "Staff Engineer",
    "salary": 178000,
    "start_date": "2019-06-01",
    "office": "San Francisco"
  },
  {
    "name": "David Kim",
    "email": "david.kim@example.com",
    "department": "Engineering",
    "role": "Software Engineer",
    "salary": 125000,
    "start_date": "2021-01-10",
    "office": "New York"
  },
  {
    "name": "Rachel Torres",
    "email": "rachel.torres@example.com",
    "department": "Engineering",
    "role": "Engineering Manager",
    "salary": 168000,
    "start_date": "2020-02-20",
    "office": "San Francisco"
  },
  {
    "name": "James Okafor",
    "email": "james.okafor@example.com",
    "department": "Engineering",
    "role": "Junior Developer",
    "salary": 92000,
    "start_date": "2024-06-15",
    "office": "Austin"
  },
  {
    "name": "Lena Vogt",
    "email": "lena.vogt@example.com",
    "department": "Engineering",
    "role": "DevOps Engineer",
    "salary": 140000,
    "start_date": "2022-04-01",
    "office": "New York"
  },
  {
    "name": "Amir Patel",
    "email": "amir.patel@example.com",
    "department": "Engineering",
    "role": "Backend Engineer",
    "salary": 132000,
    "start_date": "2023-01-09",
    "office": "London"
  },
  {
    "name": "Sofia Lindberg",
    "email": "sofia.lindberg@example.com",
    "department": "Design",
    "role": "Lead Designer",
    "salary": 145000,
    "start_date": "2019-09-12",
    "office": "New York"
  },
  {
    "name": "Carlos Rivera",
    "email": "carlos.rivera@example.com",
    "department": "Design",
    "role": "UX Designer",
    "salary": 112000,
    "start_date": "2021-07-20",
    "office": "San Francisco"
  },
  {
    "name": "Hannah Becker",
    "email": "hannah.becker@example.com",
    "department": "Design",
    "role": "UI Designer",
    "salary": 105000,
    "start_date": "2022-11-01",
    "office": "London"
  },
  {
    "name": "Yuki Tanaka",
    "email": "yuki.tanaka@example.com",
    "department": "Design",
    "role": "Product Designer",
    "salary": 118000,
    "start_date": "2023-03-14",
    "office": "San Francisco"
  },
  {
    "name": "Olivia Martin",
    "email": "olivia.martin@example.com",
    "department": "Marketing",
    "role": "VP of Marketing",
    "salary": 165000,
    "start_date": "2019-04-22",
    "office": "New York"
  },
  {
    "name": "Ethan Brooks",
    "email": "ethan.brooks@example.com",
    "department": "Marketing",
    "role": "Content Strategist",
    "salary": 95000,
    "start_date": "2021-10-05",
    "office": "Austin"
  },
  {
    "name": "Nina Kowalski",
    "email": "nina.kowalski@example.com",
    "department": "Marketing",
    "role": "SEO Specialist",
    "salary": 88000,
    "start_date": "2022-08-15",
    "office": "New York"
  },
  {
    "name": "Daniel Ochoa",
    "email": "daniel.ochoa@example.com",
    "department": "Marketing",
    "role": "Marketing Analyst",
    "salary": 91000,
    "start_date": "2023-05-20",
    "office": "Austin"
  },
  {
    "name": "Samira Hassan",
    "email": "samira.hassan@example.com",
    "department": "Marketing",
    "role": "Social Media Manager",
    "salary": 82000,
    "start_date": "2024-01-08",
    "office": "London"
  },
  {
    "name": "Tyler Washington",
    "email": "tyler.washington@example.com",
    "department": "Sales",
    "role": "Sales Director",
    "salary": 158000,
    "start_date": "2019-11-30",
    "office": "New York"
  },
  {
    "name": "Jessica Huang",
    "email": "jessica.huang@example.com",
    "department": "Sales",
    "role": "Account Executive",
    "salary": 110000,
    "start_date": "2020-06-14",
    "office": "San Francisco"
  },
  {
    "name": "Ryan O'Brien",
    "email": "ryan.obrien@example.com",
    "department": "Sales",
    "role": "Account Executive",
    "salary": 105000,
    "start_date": "2021-03-22",
    "office": "London"
  },
  {
    "name": "Fatima Al-Rashid",
    "email": "fatima.alrashid@example.com",
    "department": "Sales",
    "role": "Sales Development Rep",
    "salary": 72000,
    "start_date": "2023-09-01",
    "office": "Austin"
  },
  {
    "name": "Kevin Dupont",
    "email": "kevin.dupont@example.com",
    "department": "Sales",
    "role": "Solutions Engineer",
    "salary": 135000,
    "start_date": "2022-01-17",
    "office": "San Francisco"
  },
  {
    "name": "Megan Stewart",
    "email": "megan.stewart@example.com",
    "department": "Sales",
    "role": "Account Manager",
    "salary": 98000,
    "start_date": "2024-03-11",
    "office": "New York"
  },
  {
    "name": "Laura Chen",
    "email": "laura.chen@example.com",
    "department": "HR",
    "role": "HR Director",
    "salary": 148000,
    "start_date": "2019-08-05",
    "office": "New York"
  },
  {
    "name": "Brian Nakamura",
    "email": "brian.nakamura@example.com",
    "department": "HR",
    "role": "HR Business Partner",
    "salary": 105000,
    "start_date": "2020-12-01",
    "office": "San Francisco"
  },
  {
    "name": "Chloe Dubois",
    "email": "chloe.dubois@example.com",
    "department": "HR",
    "role": "Recruiter",
    "salary": 78000,
    "start_date": "2022-05-23",
    "office": "London"
  },
  {
    "name": "Angela Moretti",
    "email": "angela.moretti@example.com",
    "department": "HR",
    "role": "People Operations",
    "salary": 85000,
    "start_date": "2023-07-10",
    "office": "Austin"
  },
  {
    "name": "Isaac Fernandez",
    "email": "isaac.fernandez@example.com",
    "department": "Engineering",
    "role": "Frontend Engineer",
    "salary": 128000,
    "start_date": "2022-09-19",
    "office": "New York"
  },
  {
    "name": "Sarah Mitchell",
    "email": "sarah.mitchell@example.com",
    "department": "Design",
    "role": "Design Systems Lead",
    "salary": 138000,
    "start_date": "2020-04-06",
    "office": "San Francisco"
  },
  {
    "name": "Omar Farah",
    "email": "omar.farah@example.com",
    "department": "Engineering",
    "role": "QA Engineer",
    "salary": 95000,
    "start_date": "2024-02-12",
    "office": "London"
  },
  {
    "name": "Natalie Park",
    "email": "natalie.park@example.com",
    "department": "Marketing",
    "role": "Growth Manager",
    "salary": 108000,
    "start_date": "2021-11-28",
    "office": "San Francisco"
  }
]

Schema

Field Type Description
name string Employee full name.
email string Work email address on the fictional example.com domain.
department string One of Engineering, Sales, Marketing, HR, or Design.
role string Job title within the department.
salary number Annual salary in USD, stored as a JSON number (integer).
start_date date Hire date as an ISO 8601 string (YYYY-MM-DD).
office string Office location — San Francisco, New York, Austin, or London.

About the JSON Format

This sample is a single JSON document: an array of 30 objects, one per employee, each with the same seven keys in the same order. Values use natural JSON types — salary is a number, everything else is a string, and start_date sticks to ISO 8601 (YYYY-MM-DD) so it sorts lexicographically and parses unambiguously.

The structure is deliberately boring, which is exactly what you want in a test fixture:

  • No nesting. Every object is flat, so the file maps directly onto a CSV, a SQL table, or a dataframe without any flattening step.
  • Uniform keys. All 30 objects share the same schema — no optional fields, no mixed types within a column.
  • Pretty-printed. Two-space indentation makes the raw contents readable in a diff or code review, at the cost of a few extra bytes.

It is a convenient target for quick command-line checks — jq '.[0]' grabs the first record, jq 'map(.salary) | add / length' computes the average salary — and a realistic payload for mocking a REST endpoint that returns a collection.

This file is one of eleven formats that all express the same 30 employee rows, so you can convert between any pair and diff the results. The closest sibling is the JSONL sample, which holds the identical records with one object per line instead of one enclosing array — better for streaming, worse for pretty-printing. The CSV sample is the flattened equivalent.

To go from this file to a spreadsheet-friendly format, use JSON to CSV; to go the other way, CSV to JSON rebuilds the array-of-objects shape from any CSV.

FAQ

4 questions
Does downloading this file send any data to a server?
No. The sample is a plain static file served directly by the site — downloading it is a simple file fetch. Nothing you do here is uploaded, processed, or inspected, and the converters linked below run entirely in your browser too.
Is the employee data real?
No. All 30 records are fictional — names, salaries, and dates are invented, and every email uses the reserved example.com domain — so the file is safe to use in demos, tests, and documentation.
Why is the JSON a flat array instead of a nested structure?
Flat, uniform objects are the shape most tools expect: they map one-to-one onto CSV rows, database tables, and dataframes. If you need to test nested JSON handling, wrap or nest these records yourself — the flat version round-trips cleanly through any converter.
How do I convert this JSON to CSV?
Drop it into the JSON to CSV tool at /json-to-csv/. The conversion runs in your browser, and because every object has the same seven keys you get a clean 30-row CSV with a single header row.

Work With JSON Files 5 tools

JSON to CSV

Convert JSON arrays to downloadable CSV

CSV to JSON

Convert CSV files to clean, structured JSON

JSONL to CSV

Convert JSONL (NDJSON / JSON Lines) data into CSV format

CSV Viewer

View and explore CSV files in a sortable table

CSV Converter

Every CSV conversion tool on the site, searchable in one place.