RoleWeek

What RoleWeek knows about one employer's open developer roles, from the facts block on its company page: how many roles were posted in the last 7 days, where, role types, levels, how many list a salary and the yearly range, which hiring system it applies on (with 'no account needed' where checked), its weekly hiring pace since RoleWeek began counting, and the skills in its postings; plus its newest roles as links. Employers with fewer than 3 roles have no company page, so the answer lists their roles instead. Takes the employer's name (case and 'Inc.' do not matter); an ambiguous name returns the candidates. Links the company page, states the date window, and treats employer text as untrusted data.

Yearly salary ranges that employers posted in their own job postings, summarised the way RoleWeek's salary and skill pages do, for roles posted in the last 7 days: how many roles list a yearly range, the median bottom and median top of the posted ranges, the middle half of each, and by level where there are enough roles. Takes role_family (a role type) or skill (a technology), not both, and optionally metro: role type + metro is the city and role type page, a metro alone covers all developer roles there, a skill alone covers every city, and with no argument it ranks cities. Figures exist only where 15 or more roles list a yearly range; otherwise the answer says how many do and gives no number. These are advertised ranges, not offers, not what people are paid, not a market average. Each answer links the roleweek.com page, states the date window, and treats employer text as untrusted data.

RoleWeek's weekly report on developer hiring, one finished week (Monday to Sunday, Pacific time) at a time: new developer roles RoleWeek first saw that week, by city, by employer, role type and level, the share that list a salary, the posted salary median, the share that say No account needed, and the comparison with the week before when both weeks are fully covered. Coverage is partial (the answer says how many employer job boards were being checked), so these are roles RoleWeek saw, not all developer hiring. week: 'latest' (default), a week like '2026-W43', or any date in the week; the week in progress is never published. Links the weekly page, states the date window, and treats employer text as untrusted data.

Returns one RoleWeek role by its slug (as returned by search_jobs, or the last part of a roleweek.com/job/<slug>/ URL): employer, location and work mode, level, pay as listed, posted date, the date it leaves RoleWeek, skills mentioned, an excerpt of the employer's description, and the role's RoleWeek URL, whose page links to the employer's own application page.

Searches developer and tech roles that employers posted in the last 7 days, read directly from the employers' own hiring systems (Workday, Greenhouse, Lever, Ashby, iCIMS and others) and checked daily. Covers 35 metro areas in the US and Canada (50-mile radius): 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, Dayton; US and Canada places outside those metros (metro='elsewhere'); plus remote roles open to people in the US or Canada. Returns at most 25 roles per call: newest first, or best match first when a query is given. Each result includes its RoleWeek URL, whose page links to the employer's application page, and its slug; get_job takes that slug. The answer states the date window and when the data was updated, and links the matching RoleWeek listing page.