layerz/finance-engineer-postings · Datasets

layerz/finance-engineer-postings · Datasets at Hugging Face Finance Engineer Job Postings (2026 Corpus) Every job posting we could verify, in July 2026, for an engineering role sitting inside a company's own finance function. 37 requisitions across 26 employers, coded by hand from full text, with the sampling frame, the adjudication rules and the exclusion counts published alongside. The role has no research literature. No occupational code, no salary survey, no professional body benchmark. Claims about it circulate as round numbers with no method attached. This dataset exists so the claims can be checked. What is in it `finance-engineer-postings.csv`, 37 rows, one per requisition. | Column | Meaning | | --- | --- | | `employer` | Company name as published on its own job board | | `ats` | `greenhouse` or`ashby`, the applicant tracking system the posting came from | | `department` | The department the employer itself assigns to the posting, verbatim | | `title` | Job title as posted | | `location` | Location as posted | | `published_date` | First publication date reported by the ATS | | `days_open_at_freeze` | Days between publication and the 2026-07-27 freeze | | `min_years_experience` | Minimum years required, when the posting states a number | | `tools_named` | Named tools, pipe separated (e.g.`Python|SQL|dbt|Snowflake`) | | `mentions_ai_agents` | Set when the posting references agents or LLMs | | `mentions_mcp` | Set when the posting names the Model Context Protocol | | `pay_band_usd` | Pay band exactly as posted, unparsed, currency and equity notes included | | `reporting_line` | Reporting line when the posting spells one out | | `posting_url` | Live posting URL at time of collection | | `archived_url` | Internet Archive snapshot, where the archiver was not blocked | | `collapsed_locations` | How many location variants of the same requisition were merged into this row | Blank means the posting did not state it, never that the value is zero. How i