Press & data

For journalists: the data, the method, and a bio you can quote.

The job-posting numbers behind the posts come from employers' own public hiring boards, not from job boards. Here is how they are collected, what they cannot show, and how to reach me.

Quote-ready

Bio

Short, first person

I write Rust and Android code for two kinds of people: job seekers tired of ghost postings, and people whose phone might be taken away.

Third person

Alan Wisper is a software engineer in the United States working in Rust, Android and security. Current work: a browser extension and a daily crawl of employers' public hiring boards that show a job posting's real age, and a Rust storage library for Android, built to survive a phone seizure, with machine-checked proofs in Verus.

For print and web

Photo

Alan Wisper

Download JPEG, 386 × 460
[higher-resolution version for print]

How the numbers are made

Data and method

  • Source: the public, unauthenticated job-board endpoints of Greenhouse, Lever and Ashby, the systems behind the “Apply” button at most tech companies. No job board (LinkedIn, Indeed, Glassdoor) is crawled.
  • Age is measured from the employer's first-published date: first_published (Greenhouse), createdAt (Lever), publishedAt (Ashby).
  • What the data cannot show: why a posting stays open, and whether a closed posting was filled or withdrawn. Every post says this again in its limitations section.

Downloads: [CSV and SQLite snapshot with the crawl date, from the first weekly issue]

License: [for example CC BY 4.0: free to use with a link back]

Contact

Data under embargo, before a post goes out.

Full data under embargo before a post goes out: ask by email.

[Signal and PGP fingerprint, if wanted]