About the data

Whether you will be hired. No published data shows how far down a list an agency has reached, or where you personally sit on it. This site has no name search and no list number lookup. That is by choice.

How fast a list moves. The certification data shows that a list was used. It does not show how far down the list an agency went. Some titles get certified hundreds of times, because each job posting pulls just a few names. Uniformed titles get certified only a few times, in large batches instead. A high count means a title is hired often. It does not mean the list moves fast.

What you would earn. A title's salary range is what the City is allowed to pay, across every level of that job. Where we show a median instead, that is a different number from a different source. It describes what people currently in the job actually earn.

Anything about a person. The City's own data includes candidate names, exact scores, and credit flags. This site never asks for those columns. It never stores them and never publishes them. This is enforced in the code, not just promised here in writing.

A missing year. No exam here has an application period between July 2024 and June 2025. The City never published that year's schedule as open data. Our archive starts after this gap. We would rather start late than show a partial record that looks complete.

Our data lags the City's own pages. When DCAS extends an application period, its web pages update first. The open data can take weeks to catch up. On one check, the City's pages listed eight open exams, but the open data listed only two. So this site reads both sources every day, and lets the City's own pages win when the two disagree.

Cut-off names. The City's title catalog cuts every name at 30 characters. About half of all titles hit that limit. Where an exam or a list spells a title out in full, we show that fuller spelling instead.

Reused exam numbers. The City reuses exam numbers about every ten years. So any history shown for an exam only covers the years after that specific list started. This keeps an old, unrelated exam's history from being credited to a new one.

A scheduled job runs the pipeline once a day. It rebuilds the files this site reads, and it commits only when something actually changed.

Exam dates are also published as a calendar. Each exam page has a button to add that exam to your own calendar, with a reminder before it closes. If you want every exam at once, the whole feed is here. Most people only need one exam at a time, though.

The date shown on every page is the date the City's data says it is current as of. It is not the date this site last ran. Those are two different things. A build that runs perfectly every day, using data that stopped updating back in April, is exactly the failure this site is built to show you.