> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/employee-data/bundles.md). # Employee Data Bundles Explore the four employee data bundles, including core employee data, employer information, career intelligence, and social influence. Employee data includes more than 300 fields that address questions such as who the employee is, where they have worked, which companies are associated with each role, how their career is progressing, and how they are represented publicly on their professional network. The fields are grouped into bundles by the questions they help answer, rather than by their location in the underlying schema. Each field belongs to one of four bundles. Explore them below or review the [complete record sample](/employee-data/record-sample.md). *** {% content-ref url="/pages/aKxZK6yl4gEgCjHVpq3y" %} [Core](/employee-data/bundles/core.md) {% endcontent-ref %} The **Core employee bundle** captures the foundations of every employee record and their professional identity from end to end. It includes identifying details, name and headline, links to a person's public profile and social presence, location, current role, full work history, education, skills and languages, network size and activity, credentials and recognition, research output, open-source contributions, investment and event activity, and a record of recent profile changes. *** {% content-ref url="/pages/rhHA0SGF6RffVxUdoGh6" %} [Employer Information](/employee-data/bundles/employer-information.md) {% endcontent-ref %} The **Employer Information bundle** expands on the company details already linked to each position in an employee's work history. It covers company identity and classification, size and reach, social presence, headquarters, revenue and funding history, headcount growth, and record metadata, all tied to the position. *** {% content-ref url="/pages/6tE0bBhoieKUtszSJkcu" %} [Career Intelligence](/employee-data/bundles/career-intelligence.md) {% endcontent-ref %} The **Career Intelligence bundle** provides signals about career trajectory and market value, derived from work history. Tenure and promotion metrics estimate how long employees stay in a role, the rate of internal promotions, and the time spent in management. Compensation projections estimate base pay, additional pay, and total compensation for an employee's current title and company, benchmarked against public salary data. *** {% content-ref url="/pages/nlaO5HhrDFwy0mgboxmR" %} [Social Influence](/employee-data/bundles/social-influence.md) {% endcontent-ref %} The **Social Influence bundle** covers employees’ posts on their professional network, how those posts perform, and who they engage with. It includes posting frequency and overall influence, month-by-month activity trends, engagement received, and the topics, people, and companies they mention. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.coresignal.com/employee-data/bundles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.