CSV Tools

Sample XML File

A downloadable sample XML file with 30 fictional employee records wrapped in row elements — ready for testing parsers, XPath queries, and XML converters.

Data XML Text format
Download XML

sample-employees.xml

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

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 — text content that parses as an integer.
start_date date Hire date as ISO 8601 text (YYYY-MM-DD).
office string Office location — San Francisco, New York, Austin, or London.

About the XML Format

This sample wraps 30 employee records in the most conversion-friendly XML shape there is: a single <data> root containing one <row> element per record, with each of the seven fields as a child element. There are no attributes, no namespaces, no mixed content — every value lives in element text.

That structure matters because XML, unlike CSV or JSON, has no canonical way to represent a table. The same records could legally be encoded as attributes (<row name="..." salary="..."/>), as deeply nested department groupings, or with per-record element names. Tools that turn XML into rows and columns handle the element-per-field layout best, so this file is a reliable fixture for testing XML to CSV conversion — and the site’s CSV to XML tool produces exactly this shape in reverse.

Details worth knowing when you parse it:

  • Everything is text. XML carries no type system in the document itself; <salary>155000</salary> is a string until your code says otherwise. Schema languages (XSD) can declare types, but this sample ships without one, matching how most real-world data XML travels.
  • Declaration and encoding. The file opens with <?xml version="1.0" encoding="UTF-8"?> and contains no characters that need entity escaping — no &amp;, &lt;, or CDATA sections — so it parses under any conformant parser.
  • Verbosity. At roughly nine times the size of the equivalent CSV, the file is a concrete demonstration of XML’s tag overhead on tabular data.

The same 30 rows are available in eleven formats in this section — see the JSON sample for the object-based equivalent and the CSV sample for the flat baseline — so you can round-trip between formats and diff the output.

FAQ

4 questions
Does downloading this file send any data to a server?
No. The sample is a static file served directly by the site — nothing is uploaded, processed, or inspected. The XML and CSV tools linked below run entirely in your browser too.
Why are records wrapped in <row> elements instead of using attributes?
Element-per-field is the shape most XML-to-table converters expect: each <row> becomes a record and each child element becomes a column. Attribute-based layouts carry the same data but flatten less predictably, which makes them a poor default for a reference sample.
How do I query this file with XPath?
The document root is <data>, so /data/row selects all 30 records and /data/row[salary > 150000] filters on a field. Note that XPath 1.0 compares element text as strings unless you wrap values in number().
Is the employee data real?
No. All 30 records are fictional, and every email address uses the reserved example.com domain, so the file is safe for demos, tests, and documentation.

Work With XML Files 5 tools

XML to CSV

Convert XML data with repeating elements into CSV

CSV to XML

Transform CSV into well-formed XML documents

JSON to CSV

Convert JSON arrays to downloadable CSV

CSV Viewer

View and explore CSV files in a sortable table

CSV Converter

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