How RoleWeek works

Where roles come from

Each role comes from an employer’s public job board on its own hiring system. In the last 7 days: Workday, Greenhouse, Ashby, Oracle Cloud, Eightfold, SuccessFactors, iCIMS, Paylocity, Lever, JazzHR, Workable, BambooHR, Rippling, Gem, ADP Workforce Now, Jobvite, Teamtailor and Recruitee. RoleWeek does not copy other job sites. It filters out staffing agencies and roles that have been open for 120 days or more, a common sign that nobody is hiring for them.

How freshness works

• Posted date. The earlier of two dates: the employer’s own posted date, when its hiring system gives a real one, and the day RoleWeek first saw the role on the employer’s job board. We check every day, so a role with no employer date is usually dated within a day of the employer posting it. If an employer closes a role and posts it again within 60 days, it keeps its first date, so a repost does not look new.
• Daily check. RoleWeek checks each employer board it follows once a day. A role that disappears from the employer’s board comes off RoleWeek at the next update. A role we could not confirm in the last 48 hours is hidden.
• 7-day window. Each role stays up for 7 days from its posted date, then leaves, and its page returns “not found”. Sponsored roles can stay longer and are always labeled Sponsored.

What is covered

Developer roles (software engineering, frontend, backend, full-stack, mobile, data, machine learning & AI, DevOps & SRE, security, QA & testing, embedded & firmware and IT & infrastructure) in Seattle, San Francisco Bay Area, New York, Chicago, Toronto, Boston, Los Angeles, Vancouver, Washington DC, Dallas-Fort Worth, Denver-Boulder, Austin, Atlanta, Phoenix, Philadelphia, Minneapolis-St. Paul, San Diego, Raleigh-Durham, Detroit, Houston, Charlotte, St. Louis, Huntsville, Tampa, Salt Lake City, Montreal, Colorado Springs, Portland, Miami, Boise, Columbus, Pittsburgh, Hampton Roads, Nashville and Dayton, plus remote roles open to people in the US or Canada. As of Oct 16, 2026: 4,985 roles at 1,909 employers. RoleWeek doesn’t list every developer role yet. We read 54,413 employer job boards directly and add more every week.

What RoleWeek is not

RoleWeek is not the employer or a recruiter. You apply on the employer’s own site, and RoleWeek never sees applications. There are no accounts and no display ads. Paid placements are labeled Sponsored.

Use RoleWeek in Claude, ChatGPT or your editor

RoleWeek has a read-only connector (an MCP server) at https://roleweek.com/api/mcp. No sign-in. It lets an assistant search the same roles you see here and open a role’s details; every result links back to the role’s page on RoleWeek, which has the employer’s Apply button.

• Claude (web, desktop, mobile): Settings, Connectors, Add custom connector. Name it RoleWeek, paste the URL, no authentication. Custom connectors need a paid plan.
• Claude Code: claude mcp add --transport http roleweek https://roleweek.com/api/mcp
• ChatGPT: Settings, Apps & Connectors, Advanced settings, turn on Developer mode, then create a connector with the URL and no authentication (paid plans; workspace admins may need to allow it).
• Cursor and VS Code: add the URL as an HTTP MCP server in mcp.json.

These steps follow each app’s own documentation as of October 2026 (menu names change often); we have not yet checked them inside every app. If something differs, tell us at hello@roleweek.com.

For AI assistants and search engines

A plain-text summary is at /llms.txt. Every role page carries schema.org JobPosting data with the posted date and the date the role leaves RoleWeek (validThrough). The sitemap index is at /sitemap.xml.