The interesting part of a startup's job board isn't the day the round lands. It's what the board looks like a few weeks later, once the press cycle is over.

On October 17, Raydar rechecked eight Ashby job boards from rounds announced between September 16 and October 9, and compared each one, job ID by job ID, with the snapshot taken when we first wrote about it. The comparison shows what a funding headline cannot establish by itself.

Why the round and the board run on different clocks

A funding announcement has one date. A job board has many, and none of them is the date a seat was approved.

Ashby, the applicant tracking system all eight companies use, exposes a publishedAt timestamp for each posting. Its public job posting API documentation defines that field as when the job was "last published." That's not a creation date. A role can be unpublished and republished, and the timestamp moves with it.

That's why Raydar keeps three dates apart in every hiring story: when the company announced the money, when a posting was last published, and when we looked. Collapse them and you end up crediting a round with jobs that were open months earlier.

What 141 postings looked like at first check

The historical observations align with the dates in Raydar's earlier coverage. The announcement date, observation date and last-publication timestamp answer separate questions. In the retained snapshots:

  • Footprint: announcement 2026-09-16; first observation 2026-09-27; 11 listed IDs, with timestamps all before.
  • Confido: announcement 2026-09-22; first observation 2026-09-26; 34 listed IDs, with timestamps 32 before and two after.
  • Ando: announcement 2026-09-24; first observation 2026-09-25; 6 listed IDs, with timestamps all before.
  • Trebellar: announcement 2026-09-24; first observation 2026-09-26; 5 listed IDs, with timestamps all on the announcement date.
  • Miter: announcement 2026-09-30; first observation 2026-10-03; 14 listed IDs, with timestamps all before.
  • Namespace: announcement 2026-10-05; first observation 2026-10-06; 10 listed IDs, with timestamps all before.
  • Mecka: announcement 2026-10-07; first observation 2026-10-09; 51 listed IDs, with timestamps 30 before, 17 on the date and four after.
  • TypeSafe AI: announcement 2026-10-09; first observation 2026-10-13; 10 listed IDs, with timestamps nine before and one after.

Add it up and 112 of 141 postings carried timestamps before the announcement, 22 fell on announcement day and seven came after. Those timestamps do not connect the requisitions to a particular financing decision.

That isn't a knock on the companies. It's a reason to stop treating a funding headline as a hiring signal on its own.

What changed by October 17

Raydar pulled all eight boards through Ashby's public API on October 17, between eight and 31 days after the announcements. A separate publication review matched every current ID, title and timestamp in that retained morning capture against the live API.

  • Footprint (board): 13 postings. Ten of the original 11 are still listed; Head of IT/Compliance is not. Three new job IDs carry October 4, 14 and 16 timestamps: Member of Technical Staff (Backend, Rust), Sales Development Representative (Summer 2027) and Demand Generation Manager.
  • Confido (board): 37 postings. Twenty-nine of 34 remain. Five are no longer listed: Accounting Manager, Applied AI Data Analyst, New Grad Software Engineer, Office Manager and Sales Finance Manager. Eight new IDs carry September 27 to October 9 timestamps, including Data Engineering Manager, Head of Predictions & Optimization and Creative Director.
  • Ando (board): five postings. Four of six remain; Business Operations and Mobile Engineer are gone. One new posting, titled Wildcard, carries an October 9 timestamp.
  • Trebellar (board): the same five job IDs with the same September 24 timestamps.
  • Miter (board): 13 postings. Nine of 14 remain. Software Engineer (New Grad), GTM Recruiter, GTM Enablement Lead, Regional Sales Manager (Northeast) and Associate Customer Support Specialist are no longer listed. Four new IDs carry October 6 to 8 timestamps, all sales or customer roles: Manager, Customer Support; Manager, Sales Development; Mid-Market Sales Manager; and Strategic Customer Success Manager.
  • Namespace (board): 14 postings. All 10 originals remain. Four new IDs carry October 7 to 15 timestamps: two DevOps Engineer postings, Finance Lead and Senior Data Center Operations Manager.
  • Mecka (board): 55 postings. Forty-eight of 51 remain; three program and calibration roles are gone. Seven new IDs appeared. Six carry October 9 to 16 timestamps. One, Software Developer, Robotic Data & Deliveries, carries a September 30 timestamp even though it wasn't on the October 9 board (Mecka's original board and pay labels).
  • TypeSafe AI (board): 15 postings. All 10 originals remain. Five new IDs carry October 14 and 15 timestamps. Four are filed under Member of Technical Staff and one under Create your own role, including Data Platform Engineer and Software Engineer Generalist.

Across the eight boards, the count moved from 141 to 157. Of the original postings, 125 are still listed and 16 are not. Thirty-two new job IDs appeared, and 31 of them carry timestamps after their company's announcement.

Three things that look like signals and aren't proof

An old role with a new date. Three Confido postings kept the same job ID but now show later timestamps. Senior ML Ops Engineer moved from July 6 to October 15, Finance & Strategy Manager from July 21 to October 8, and Executive Assistant from September 16 to October 12. Anyone checking for the first time today would see three "post-round" roles. Our September 26 snapshot shows all three were already listed, with timestamps before the September 22 announcement.

A posting that disappeared. Sixteen originals dropped off the public lists. That can mean a hire, a pause, a merged requisition or a posting moved to a direct link only. The public data doesn't say which, so don't assume a role was filled, and don't assume a track like new-grad engineering is closed for good. Ask.

A new posting with an old date. Mecka's Software Developer, Robotic Data & Deliveries role shows a September 30 timestamp but wasn't listed on October 9. A timestamp can predate the day a role first became visible to you.

The 31 new IDs with post-announcement timestamps are candidates for follow-up, especially when titles align with a stated use of funds. Namespace said its round would fund product work and data-center expansion; its board now has a Senior Data Center Operations Manager posting. That's worth a question in your first call. It still doesn't prove the round funded that seat.

How to read a startup's board after a round

Use the board to prepare specific questions about the work and its approval. It is a public recruiting surface, not a complete account of the company's finances or staffing decisions.

  1. Write down three dates. The announcement, the posting's timestamp and the day you looked. Keep them separate in your notes.
  2. Check twice. Look at the board when the news breaks and again a week or two later. Count job IDs, not titles: Namespace and Mecka both run more than one posting under similar titles.
  3. Compare new postings with the stated use of funds. Treat those stated uses as company claims, then ask whether your role is part of the plan.
  4. Read the pay label before the number. On October 17, 138 of the 157 postings had a non-empty structured compensation-tier summary. That count includes hourly pay and does not measure comparable annual salary disclosures. Ando and Trebellar had no such summaries, and Namespace had seven of 14. A missing structured summary does not prove the description omits pay. Raydar's guide to startup pay bands covers why salary, base and OTE aren't interchangeable.
  5. Ask the recruiter directly. Is this seat new since the round, a backfill or a repost? When was it approved? Is the published range still the approved range? How long has the search run?

Those questions aren't confrontational. They're the same ones a good hiring manager should already be able to answer, and the answers tell you a lot about how clear the plan really is.

What it means for founders

If you announce a round and say you're hiring, candidates will read your board as the evidence. Several boards provide structured compensation summaries, but candidates still need the applicable pay label, currency and period before comparing an offer. Republishing a role changes its public publishedAt timestamp, so be ready to say how long a search has actually been open. And if a role from your announcement week is no longer listed, a short note on the careers page beats letting candidates guess.

Method and limits

This is a selected, non-random set of eight companies covered by Raydar between September 25 and October 13. Historical IDs, titles and timestamps came from a retained evidence export of the original board snapshots. Historical observation dates were checked against the earlier publication records, rather than restored file modification dates. The original raw-file hashes are reported by that export; this review did not independently reconstruct those raw historical files. Each board was pulled again through Ashby's public posting API on October 17 at 7:14 AM PT. Counts use listed job IDs. Posting timestamps were compared with announcement dates by UTC calendar date. Funding announcements do not establish which seats they funded. Removed postings were not checked for hires or closures, and new IDs were not checked for approved budgets. This is a small, non-random sample of startups, not a market survey, and it makes no pay comparison across companies.