This dataset is a listing of all active City of Chicago employees, complete with full names, departments, positions, employment status (part-time or full-time), frequency of hourly employee –where applicable—and annual salaries or hourly rate. Please note that "active" has a specific meaning for Human Resources purposes and will sometimes exclude employees on certain types of temporary leave. For hourly employees, the City is providing the hourly rate and frequency of hourly employees (40, 35, 20 and 10) to allow dataset users to estimate annual wages for hourly employees. Please note that annual wages will vary by employee, depending on number of hours worked and seasonal status. For information on the positions and related salaries detailed in the annual budgets, see https://www.cityofchicago.org/city/en/depts/obm.html

Data Disclosure Exemptions: Information disclosed in this dataset is subject to FOIA Exemption Act, 5 ILCS 140/7 (Link:https://www.ilga.gov/legislation/ilcs/documents/000501400K7.htm)

Public authorities are required by Section 2800 of Public Authorities Law to submit annual reports to the Authorities Budget Office that include salary and compensation data. The dataset consists of salary data by employee reported by State Authorities that covers 8 fiscal years, which includes fiscal years ending in the most recently completed calendar year.

Annual salary information including gross pay and overtime pay for all active, permanent employees of Montgomery County, MD paid in calendar year 2023. This information will be published annually each year.

Annual salary information including gross pay and overtime pay for all active, permanent employees of Montgomery County, MD paid in calendar year 2024. This information will be published annually each year.

Unlock valuable salary insights with our comprehensive Salary Dataset, designed for businesses, recruiters, and job seekers to analyze compensation trends, workforce planning, and market competitiveness.

Dataset Features

Job Listings & Salaries: Access structured salary data from top job platforms, including job titles, company names, locations, salary ranges, and compensation types. Employer & Industry Insights: Extract company-specific salary trends, industry benchmarks, and hiring patterns. Geographic Pay Disparities: Compare salaries across different regions, cities, and countries to identify location-based compensation trends. Job Market Trends: Monitor salary fluctuations, demand for specific roles, and hiring trends over time.

Customizable Subsets for Specific Needs Our Salary Dataset is fully customizable, allowing you to filter data based on job titles, industries, locations, experience levels, and salary ranges. Whether you need broad market insights or focused data for recruitment strategy, we tailor the dataset to your needs.

Popular Use Cases

Workforce Planning & Talent Acquisition: Optimize hiring strategies by analyzing salary benchmarks and compensation trends. Market Research & Competitive Intelligence: Compare salaries across industries and competitors to stay ahead in talent acquisition. Career Decision-Making: Help job seekers evaluate salary expectations and identify high-paying opportunities. AI & Predictive Analytics: Use structured salary data to train AI models for job market forecasting and compensation analysis. Geographic Expansion & Business Strategy: Assess salary variations across regions to plan business expansions and remote workforce strategies.

Whether you're optimizing recruitment, analyzing salary trends, or making data-driven career decisions, our Salary Dataset provides the structured data you need. Get started today and customize your dataset to fit your business objectives.

Employee payroll data for all Cook County employees excluding Forest Preserves, indicating amount of base salary paid to an employee during the County fiscal quarter. Salaries are paid to employees on a bi-weekly basis. Any pay period that extended between quarters will be reported to the quarter of the Pay Period End Date. (e.g. If a Pay Period runs 02/21-03/05, that pay period would be reported in the Q2 period, as the end of the pay period falls in March - Q2) The county fiscal quarters are: Q1: December - February Q2: March - May Q3: June - August Q4: September - November The Employee Unique Identifier field is a unique number assigned to each employee for the purpose of this data set, that is not their internal employee ID number, and allows an employee to be identified in the data set over time, in case of a name change or other change. This number will be consistent within the data set, but we reserve the right to regenerate this number over time across the data set. ISSUE RESOLVED: As of 4/19/2018 there was an issue regarding employee FY2016 and FY2017 payroll in which records were duplicated in the quarterly aggregation, resulting in inflated base pay amounts. Please disregard any data extracted from this dataset prior to the correction date and use this version moving forward. KNOWN ISSUE: Several records are missing Bureau and Office information. We are working on correcting this and will update the dataset when this issue has been resolved. For data prior to Fiscal Year 2016, see datasets at https://datacatalog.cookcountyil.gov/browse?tags=payroll

The payroll data represents the amount paid to an employee during the reported time period. In addition to regular pay, these amounts may include other pay types such as overtime, longevity, shift differential or terminal pay. This amount does not include any state share costs associated with the payroll i.e. FICA, state share retirement, etc. This amount may vary from an employee’s ‘salary’ due to pay adjustments or pay period timing. The payroll information will be updated monthly after the end of the month. For example, July information will be added in August after the 15th of the month.

The Employee Salary dataset contains payroll and position data, including: position description, department, FLSA status, pay range, pay grade and step (if applicable), bargaining unit, and base salary information. Each row contains relevant data for a single employee or vacant position. A data dictionary with descriptions of the fields included in the dataset can be downloaded here. The core dataset is updated semi-annually and supporting files on an as-needed basis.Additional supporting files include: Salary bands for each pay grade and step (if applicable) for the four labor groups:Boulder Municipal Employee’s Association – BMEA International Association of Fire Fighters – IAFFBoulder Police Officer’s Association – BPOAManagement / Non-Union – MGMTList of currently used job classes by labor group and grade

This dataset includes Baltimore City employee salaries and gross pay from fiscal year 2011 through last fiscal year and includes employees who were employed on June 30 of the last fiscal year. For fiscal years 2020 and prior, data are extracted from the ADP payroll system. For fiscal year 2023, the data are combined from the ADP system and the Workday enterprise resource planning system which now includes payroll.Change Log- Added FY2023 data- Metadata added- Columns renamed to a standard format- Youth workers not employed by City removed- Agency names reformatted with Workday conventions-7/25/24: Added FY2024 data. To leave feedback or ask a question about this dataset, please fill out the following form: Baltimore City Employee Salaries feedback form.

This dataset has been published by the Human Resources Department of the City of Virginia Beach and data.virginiabeach.gov. The mission of data.virginiabeach.gov is to provide timely and accurate City information to increase government transparency and access to useful and well organized data by the general public, non-governmental organizations, and City of Virginia Beach employees.

Distributed by

data.virginiabeach.gov

2405 Courthouse Dr.

Virginia Beach, VA 23456

Entity

Employee Salaries

Point of Contact

Human Resources

Attributes

Column: Department

Description: 3-letter department code

Column: Department Division

Description: This is the City Division that the position is assigned to.

Column: PCN

Description: Tracking number used to reference each unique position within the City.

Column: Position Title

Description: This is the title of the position (per the City’s pay plan).

Column: FLSA Status

Description: Represents the position’s status with regards to the Fair Labor Standards Act (FLSA)

“Exempt” - These positions do not qualify for overtime compensation – Generally, a position is classified as FLSA exempt if all three of the following criteria are met: 1) Paid at least $47,476 per year ($913 per week); 2) Paid on a salary basis - generally, salary basis is defined as having a guaranteed minimum amount of pay for any work week in which the employee performs any work; 3) Perform exempt job duties - Job duties are split between three classifications: executive, professional, and administrative. All three have specific job functions which, if present in the employee’s regular work, would exempt the individual from FLSA. Employees may also be exempt from overtime compensation if they are a “highly compensated employee” as defined by the FLSA or the position meets the criteria for other enumerated exemptions in the FLSA.

“Non-exempt” – These positions are eligible for overtime compensation - positions classified as FLSA non-exempt if they fail to meet any of exempt categories specified in the FLSA.

Column: Initial Hire Date

Description: This is the date that the full-time employee first began employment with the City.

Column: Date in Title

Description: This is the date that the full-time employee first began employment in their current position.

Column: Salary

Description: This is the annual salary of the full-time employee or the hourly rate of the part-time employee.

Frequency of dataset update

Monthly

Louisville Metro Human Resources (HR) Department, with the support of department leaders and their agency HR Representatives, provides support to all metro agencies in personnel management, benefits administration, labor relations, training, recruitment, occupational health & safety, payroll administration and onboarding. This data is presented in a publicly available report, located HERE

Please review the FAQ located at https://louisvilleky.gov/government/human-resources/salary-data-faq

Field Name

Field Description

Cal Year

Calendar year the row data is referencing

Employee Name

Full employee name (LAST, FIRST MIDDLE)

Department

Metro department of employee during the referenced calendar year

job Title

Job title of employee during the referenced calendar year

Annual Rate

Yearly compensation rate of employee (Hourly Rate X Annual Work Hours)

Regular Rate

Gross payments received in the referenced calendar year for hours worked

Overtime Rate

Amount of overtime payment(s) within the calendar year referenced

Incentive Allowance

Additional payments for work allowances (i.e.: uniform allowances, call out payments etc.)

Other

Any additional payments issued to employee not captured in the other categories

YTD Total

Year To Date (YTD) compensation paid

Data is collected because of public interest in how the City’s budget is being spent on salary and overtime pay for all municipal employees. Data is input into the City's Personnel Management System (“PMS”) by the respective user Agencies. Each record represents the following statistics for every city employee: Agency, Last Name, First Name, Middle Initial, Agency Start Date, Work Location Borough, Job Title Description, Leave Status as of the close of the FY (June 30th), Base Salary, Pay Basis, Regular Hours Paid, Regular Gross Paid, Overtime Hours worked, Total Overtime Paid, and Total Other Compensation (i.e. lump sum and/or retro payments). This data can be used to analyze how the City's financial resources are allocated and how much of the City's budget is being devoted to overtime. The reader of this data should be aware that increments of salary increases received over the course of any one fiscal year will not be reflected. All that is captured, is the employee's final base and gross salary at the end of the fiscal year. In very limited cases, a check replacement and subsequent refund may reflect both the original check as well as the re-issued check in employee pay totals.

NOTE 1: To further improve the visibility into the number of employee OT hours worked, beginning with the FY 2023 report, an updated methodology will be used which will eliminate redundant reporting of OT hours in some specific instances. In the previous calculation, hours associated with both overtime pay as well as an accompanying overtime “companion code” pay were included in the employee total even though they represented pay for the same period of time. With the updated methodology, the dollars shown on the Open Data site will continue to be inclusive of both types of overtime, but the OT hours will now reflect a singular block of time, which will result in a more representative total of employee OT hours worked. The updated methodology will primarily impact the OT hours associated with City employees in uniformed civil service titles. The updated methodology will be applied to the Open Data posting for Fiscal Year 2023 and cannot be applied to prior postings and, as a result, the reader of this data should not compare OT hours prior to the 2023 report against OT hours published starting Fiscal Year 2023. The reader of this data may continue to compare OT dollars across all published Fiscal Years on Open Data.
NOTE 2: As a part of FISA-OPA’s routine process for reviewing and releasing Citywide Payroll Data, data for some agencies (specifically NYC Police Department (NYPD) and the District Attorneys’ Offices (Manhattan, Kings, Queens, Richmond, Bronx, and Special Narcotics)) have been redacted since they are exempt from disclosure pursuant to the Freedom of Information Law, POL § 87(2)(f), on the ground that disclosure of the information could endanger the life and safety of the public servants listed thereon. They are further exempt from disclosure pursuant to POL § 87(2)(e)(iii), on the ground that any release of the information would identify confidential sources or disclose confidential information relating to a criminal investigation, and POL § 87(2)(e)(iv), on the ground that disclosure would reveal non-routine criminal investigative techniques or procedures. Some of these redactions will appear as XXX in the name columns.

View H-1B visa salary data aggregated by city. Compare salaries in major metropolitan areas and other locations across the US.

The payroll data represents the amount paid to an employee during the reported time period. In addition to regular pay, these amounts may include other pay types such as overtime, longevity, shift differential or terminal pay. This amount does not include any state share costs associated with the payroll i.e. FICA, state share retirement, etc. This amount may vary from an employee’s ‘salary’ due to pay adjustments or pay period timing.

The dataset contains the name, gender, county or city of residence (when possible), official title, total salary received during each fiscal year, base salary for the employee, and traveling and subsistence expense reimbursed to state personnel beginning with Fiscal Year 2007. A status of "TERMINATED" in the column providing the base salary does not indicate that the employee was fired, only that the person no longer works in that position.

Dataset Card for Data Science Job Salaries

  Dataset Summary





  Content

Column Description

work_year The year the salary was paid.

experience_level The experience level in the job during the year with the following possible values: EN Entry-level / Junior MI Mid-level / Intermediate SE Senior-level / Expert EX Executive-level / Director

employment_type The type of employement for the role: PT Part-time FT Full-time CT Contract FL Freelance

job_title… See the full description on the dataset page: https://huggingface.co/datasets/hugginglearners/data-science-job-salaries.

The ATO (Australian Tax Office) made a dataset openly available (see links) showing all the Australian Salary and Wages (2002, 2006, 2010, 2014) by detailed occupation (around 1,000) and over 100 SA4 regions. Sole Trader sales and earnings are also provided. This open data (csv) is now packaged into a database (*.sql) with 45 sample SQL queries (backupSQL[date]_public.txt).See more description at related Figshare #datavis record. Versions:V5: Following #datascience course, I have made main data (individual salary and wages) available as csv and Jupyter Notebook. Checksum matches #dataTotals. In 209,xxx rows.Also provided Jobs, and SA4(Locations) description files as csv. More details at: Where are jobs growing/shrinking? Figshare DOI: 4056282 (linked below). Noted 1% discrepancy ($6B) in 2010 wages total - to follow up.#dataTotals - Salary and WagesYearWorkers (M)Earnings ($B) 20028.528520069.4372201010.2481201410.3584#dataTotal - Sole TradersYearWorkers (M)Sales ($B)Earnings ($B)20020.9611320061.0881920101.11122620141.19630#links See ATO request for data at ideascale link below.See original csv open data set (CC-BY) at data.gov.au link below.This database was used to create maps of change in regional employment - see Figshare link below (m9.figshare.4056282).#packageThis file package contains a database (analysing the open data) in SQL package and sample SQL text, interrogating the DB. DB name: test. There are 20 queries relating to Salary and Wages.#analysisThe database was analysed and outputs provided on Nectar(.org.au) resources at: http://118.138.240.130.(offline)This is only resourced for max 1 year, from July 2016, so will expire in June 2017. Hence the filing here. The sample home page is provided here (and pdf), but not all the supporting files, which may be packaged and added later. Until then all files are available at the Nectar URL. Nectar URL now offline - server files attached as package (html_backup[date].zip), including php scripts, html, csv, jpegs.#installIMPORT: DB SQL dump e.g. test_2016-12-20.sql (14.8Mb)1.Started MAMP on OSX.1.1 Go to PhpMyAdmin2. New Database: 3. Import: Choose file: test_2016-12-20.sql -> Go (about 15-20 seconds on MacBookPro 16Gb, 2.3 Ghz i5)4. four tables appeared: jobTitles 3,208 rows | salaryWages 209,697 rows | soleTrader 97,209 rows | stateNames 9 rowsplus views e.g. deltahair, Industrycodes, states5. Run test query under **#; Sum of Salary by SA4 e.g. 101 $4.7B, 102 $6.9B#sampleSQLselect sa4,(select sum(count) from salaryWageswhere year = '2014' and sa4 = sw.sa4) as thisYr14,(select sum(count) from salaryWageswhere year = '2010' and sa4 = sw.sa4) as thisYr10,(select sum(count) from salaryWageswhere year = '2006' and sa4 = sw.sa4) as thisYr06,(select sum(count) from salaryWageswhere year = '2002' and sa4 = sw.sa4) as thisYr02from salaryWages swgroup by sa4order by sa4

Standard, overtime, and other pay totals for Ramsey County employees by year. This data includes deferred compensation and pandemic pay as part of an employee's overall compensation. It does not include vaccination incentives or COVID-19 testing payments.

Employees with start dates of "Jan 1, 1901" are missing an official start date in their record and we are working to update this data.

This is a multi-year state agency salary report. To learn more about state salaries visit the Oregon Transparency Program website. https://www.oregon.gov/transparency/Pages/index.aspx. To learn more about state jobs and salaries visit https://www.oregon.gov/das/hr/pages/index.aspx.

Wage and classification information of City of Seattle Employees. Exclusions may apply for vulnerable populations.