Recipe · Apify Store · runs in a terminal
Mexico tech jobs on OCC: a senior title meant 2.4 times the advertised pay
Among 260 OCC Mundial listings from six tech searches, senior and lead titles advertised a median of MXN 63,000 a month. Data analyst listings advertised about half of what developer searches showed.
If you’re pricing a tech hire in Mexico, or checking an offer, the level in the job title says more than the keyword. I collected 260 OCC Mundial listings from six tech searches. 147 (57%) showed a monthly salary in pesos. Listings with a senior, lead, architect or manager title advertised a median of MXN 63,000 a month. Titles without a level word had a median of MXN 26,500, so the senior median was about 2.4 times higher. Junior and intern titles sat at MXN 17,250. The data analyst search came in at MXN 16,250, roughly half the medians of the five developer searches.
Pay by level in the title
I used automatic/occ-mx-scraper on November 18, 2026 UTC to run six keyword searches: desarrollador, programador, ingeniero de software, python, java and analista de datos. I read up to three pages per search. After removing 40 listings that appeared in more than one search, 260 remained. For a pay range, I used its midpoint. For a single amount, I used that amount. Every disclosed salary was marked monthly (Mensual) and was in MXN.
| Level word in the title | Listings | With pay | Median (MXN/month) | Middle half (MXN/month) |
|---|---|---|---|---|
| Junior, intern or graduate | 16 | 8 | 17,250 | 11,800–22,625 |
| No level word | 193 | 112 | 26,500 | 17,912–36,750 |
| Senior, lead, architect or manager | 51 | 27 | 63,000 | 45,750–80,270 |
The middle half runs from the first to the third quartile. Most listings, 193 of 260, had no level word. The junior row has eight salaries, so read it as a rough guide. The senior quartiles do not overlap the no-level quartiles. In this sample, “Sr” or “Líder” in a title went with clearly higher advertised pay.
Pay by search
| OCC search | Listings | With pay | Median (MXN/month) | Middle half (MXN/month) |
|---|---|---|---|---|
| desarrollador | 62 | 32 (52%) | 35,750 | 21,750–52,125 |
| java | 53 | 28 (53%) | 34,000 | 26,875–40,000 |
| programador | 37 | 28 (76%) | 32,000 | 25,000–73,885 |
| python | 62 | 34 (55%) | 31,250 | 21,750–54,750 |
| ingeniero de software | 51 | 28 (55%) | 29,500 | 21,738–49,472 |
| analista de datos | 35 | 20 (57%) | 16,250 | 15,325–22,125 |
A listing can appear under more than one search, so these rows add up to more than 260. The five developer searches had medians from MXN 29,500 to 35,750. Among the developer searches, java had the narrowest middle half. The searches also returned some non-software roles, such as construction scheduling under programador and a purchasing analyst under python. Treat each row as what the search returns, rather than a clean job category.
By location, Mexico City had the most listings (150), with a median of MXN 32,500 across 78 disclosed salaries. The Guadalajara area (Jalisco) had a higher median, MXN 39,500, from only 16 salaries. The Monterrey area (Nuevo León) had MXN 27,500 from 25. Locations elsewhere, or with no city, had MXN 19,250 from 28. Employers outside Mexico City were more likely to show pay: 71% in Nuevo León and 67% in Jalisco, compared with 52% in Mexico City.
Limits
These are advertised salaries from one job board on one day, not signed offers. OCC doesn’t say whether an amount is gross or net. Each search used the board’s own ranking, and both runs stopped at the 150-listing cap, so analista de datos contributed only 35 listings. The level groups come from title words. A “Gerente” outside software can therefore count as senior. The keyword searches also pulled in a few non-tech roles. I left those in, rather than hand-picking. The 43% of listings that hid their salary may differ from those that showed it.
Reproduce the tables
Download the captured analysis fields as occ.json. The snapshot preserves the returned order and keeps only the fields used here. Save the code as occ.py and run python3 occ.py occ.json.
import json
import re
import sys
from collections import defaultdict
from pathlib import Path
from statistics import median, quantiles
runs = json.loads(Path(sys.argv[1]).read_text())["runs"]
offers = {}
by_search = defaultdict(list)
for run in runs:
for offer in run["items"]:
by_search[offer["url"].split("/empleos/de-")[1].split("/")[0]].append(offer)
offers.setdefault(offer["id"], offer)
offers = list(offers.values())
def monthly_pay(offer):
"""Midpoint of a stated MXN range, or the single stated amount."""
if offer["salary_currency"] != "MXN" or not offer["salary_min"]:
return None
assert offer["salary"].endswith("Mensual")
return (offer["salary_min"] + (offer["salary_max"] or offer["salary_min"])) / 2
def level(title):
t = title.lower()
if re.search(r"\b(jr\.?|junior|becari[oa]|trainee|practicante|reci[eé]n egresad[oa])", t):
return "Junior, intern or graduate"
if re.search(r"\b(sr\.?|senior|lead|l[ií]der|arquitect[oa]|staff|principal"
r"|gerente|manager|head)\b", t):
return "Senior, lead, architect or manager"
return "No level word"
def area(location):
if "Ciudad de México" in (location or ""):
return "Mexico City"
if "Nuevo León" in (location or ""):
return "Nuevo León (Monterrey area)"
if "Jalisco" in (location or ""):
return "Jalisco (Guadalajara area)"
return "Elsewhere or unspecified"
def row(label, group):
pay = [p for p in map(monthly_pay, group) if p]
low, _, high = quantiles(pay, n=4, method="inclusive")
print(f"{label}: {len(group)} listings, {len(pay)} with pay ({len(pay) / len(group):.0%}), "
f"median {median(pay):,.0f}, middle half {low:,.0f}–{high:,.0f}")
print("Unique listings", len(offers))
row("All", offers)
print("Ranges", sum(bool(o["salary_max"]) for o in offers if monthly_pay(o)))
for search, group in by_search.items():
row(f"Search '{search}'", group)
for name in ("Junior, intern or graduate", "No level word", "Senior, lead, architect or manager"):
row(name, [o for o in offers if level(o["title"]) == name])
for name in ("Mexico City", "Nuevo León (Monterrey area)", "Jalisco (Guadalajara area)",
"Elsewhere or unspecified"):
row(name, [o for o in offers if area(o["location"]) == name])
To pull a fresh sample, use the saved input objects in the snapshot as the request bodies for POST https://api.apify.com/v2/acts/automatic~occ-mx-scraper/runs?maxTotalChargeUsd=0.15&timeout=300 with an Apify bearer token. When the run finishes, read defaultDatasetId from the run record, then fetch GET https://api.apify.com/v2/datasets/{datasetId}/items?format=json. Swap the new rows into items. Change queries for other roles. For company, salary or date fields missing from the search cards, set maxDetails to fill them from detail pages.
On November 18, 2026 UTC, the run records listed customer prices of $0.0008 per listing and $0.0025 per GB of memory per run start. These two 512 MB runs returned 150 listings each. At those prices, they’d cost a customer about $0.12 each. On the publisher account, they used $0.011 of platform usage.
Apify run IDs
| Searches | Run ID | Dataset ID | Result |
|---|---|---|---|
| desarrollador, programador, ingeniero de software | Ii4OZAtYxqgf7QmF0 |
7rHWQnDHvif1mafCX |
150 listings |
| python, java, analista de datos | 1pxnkR0gsgZBlUgww |
KmlOomrzpWIgilXHD |
150 listings |
Affiliate disclosure: The Apify Store link carries our referral code. If you sign up for a paid plan through it, ssh.autos may earn a commission at no cost to you.
Sources in this recipe
-
OCCMundial Mexico Jobs | OCC.com.mx Job Listings
Scrape OCCMundial (occ.com.mx) job offers: title, company, salary in MXN or USD, city, posting date and link.
Machine-readable: openapi.json · llms.txt