What developer candidates do on RoleWeek

RoleWeek lists developer roles posted in the last 7 days, straight from employers’ own hiring systems, at no charge. These are RoleWeek’s own counts, each with its dates and sample size. They describe RoleWeek, not every job board, and they count clicks and page reads, not people.

82%of Apply clicks came within 3 days of a role’s posted date

11.0 vs 1.4Apply clicks per 100 listed roles, remote vs on-site or hybrid

1,125of 5,612 listed roles read by AI assistants in 24 hours

What we counted

Most Apply clicks come within 3 days of a role’s posted date. Of the Apply clicks on roles RoleWeek first listed Oct 22 to 28, 2026, 59% came by the day after the role’s posted date and 82% within 3 days (266 clicks, Oct 22 to Nov 4). RoleWeek shows the newest roles first and takes an unpaid role off its lists 7 days after its posted date, so this describes RoleWeek, not every job board.
Remote roles drew more Apply clicks per role. Remote roles, open to people in the US or Canada, got 11.0 Apply clicks per 100 listed roles; on-site and hybrid roles got 1.4 (1,513 and 7,021 roles, same dates). AI assistants also read remote roles more: 80 reads per 100 listed roles, against 23 for the others.
Entry-level roles drew more Apply clicks per role than other levels. They got 9.2 Apply clicks per 100 listed roles, all other levels together 2.8 (368 and 8,166 roles; 34 of the 266 clicks, a small sample). AI assistants read entry-level roles 74 times per 100 listed, other levels 32.
AI assistants read roles one page at a time. From Nov 4, 9:00 AM to Nov 5, 9:00 AM PT, AI assistants answering people read 1,125 of the 5,612 roles listed on RoleWeek at least once (20%), at 742 of 2,283 employers. ChatGPT made 2,928 of the 2,944 reads.

Per 100 listed roles	Apply clicks	AI reads
Remote (US or Canada)	11.0	80
On-site or hybrid	1.4	23
Entry level	9.2	74
Other levels	2.8	32

Apply clicks: roles first listed Oct 22 to 28, 2026, clicks Oct 22 to Nov 4. Reads: Nov 4, 9:00 AM to Nov 5, 9:00 AM PT, per role listed on Nov 5, 7:32 AM PT.

What this suggests if you want more applicants

Suggestions, not promises. Each one follows from the counts above or from how RoleWeek reads a role.

Check that your roles are listed. It’s free. RoleWeek lists developer roles from public job boards on hiring systems like Workday, Greenhouse, Lever and Ashby, at no charge, and candidates apply on your own careers site. If yours are missing or wrong, tell us.
Be ready for applicants in the first days. Most Apply clicks on RoleWeek come within 3 days of a role’s posted date, so post a role when your team can start reading applications.
If a role is remote, say so where your hiring system publishes it. RoleWeek marks a role remote from its location and workplace fields; the description alone does not make it remote. Remote roles drew more Apply clicks per role.
Name the level in the title. RoleWeek reads a role’s level from its title, and candidates filter by level. If a role is open to early-career developers, say so in the title: that is how RoleWeek files it as entry level.
Write the posting for someone reading it in an answer. An assistant that reads your role on RoleWeek reads the role’s own page, which shows your posting as your hiring system publishes it, with its title, place and, when the posting has one, salary range. What an assistant can say about your role is what your posting says.
A paid option: sponsor a role. In each city you sponsor, the role stays in the lists for 30 days instead of 7, in a reserved spot right after the first 6 unpaid roles, labeled Sponsored, with its real posted date. $149 per city for 30 days. Founding offer: the first 10 employers that sponsor a role get its first 30 days free in one city (10 of 10 left). No employer has sponsored a role on RoleWeek yet, so we can’t say how many Apply clicks a sponsored role gets. Sponsor a role

How we counted

Apply clicks are clicks on RoleWeek’s Apply button, which opens the employer’s own application page. They are not applications: RoleWeek never sees those. About half of all Apply clicks on RoleWeek come in quick repeated runs that look like one heavy user or tool working down a list, so these numbers leave most such runs out (266 of 678 clicks on these roles remain). With the runs left in, 66% came by the day after the posted date and 83% within 3 days.

AI assistant reads are fetches of a RoleWeek page by an assistant answering someone, from the site’s crawler log, with each assistant’s published addresses checked. Nov 4, 9:00 AM to Nov 5, 9:00 AM PT; per 100 roles listed on Nov 5, 7:32 AM PT.

Every number here is a count of clicks or reads, not of people. RoleWeek counts without cookies and identifies no visitor. These numbers show what happened on RoleWeek in these dates, not what will happen to one role: we can’t promise any number of views, clicks or hires. Measured Nov 5, 2026.