Data Center Co-op Watch
Overview
Find and triage public data-center-related leads without mixing them into university portal submission workflow. This skill handles discovery, scoring, hard-gate review, and local saving.
Use $ats-resume-tailor for concrete resume tailoring and $external-coop-apply for employer portal execution. Use $oscarplus-coop-apply only for university portal postings or upload/submission steps.
Boundaries
- Do not log into job boards, bypass gated pages, scrape credentials, upload documents, or submit applications.
- Prefer official company pages. Use mirrors only for discovery; mark
manual-company-check.
- Do not assume full-time, trainee, apprentice, or technician roles count as co-op. Mark
manual-review until eligibility, hours, dates, pay, and employer documentation are clear.
- Save only useful or watch-worthy leads.
- Default to software/infrastructure adjacency first: cloud/platform, network automation, observability, monitoring, backend/internal tools, data platforms, AI infrastructure, and infrastructure testing.
- Promote pure hardware/facility roles only when student, intern, co-op, trainee, junior, entry-level, paid training, or recruiter-confirmed compatibility is plausible.
Private Sources
Read from private career-config.json:
paths.jobQueue
paths.resumeSystem
paths.resumeSummary
paths.jobLeadsDir
Read references/employer-watchlist.md when the task mentions hyperscalers, cloud infrastructure, paid training, data centers, facility operations, critical environment, power, cooling, network operations, or infrastructure monitoring.
Workflow
Establish scope.
- Use term, geography, target roles, and preferred lanes from config unless the user overrides them.
De-duplicate.
- Read queue IDs and existing digest rows.
- Treat same company + similar title + same city as likely duplicate.
Search current public sources.
- Official careers pages first.
- Mirrors only for discovery or when official pages block indexing.
- If current availability cannot be verified, mark
manual-company-check or watch-only.
Hard-gate.
- Mark
skip for expired, clearly senior-only, unpaid, unrelated, or legally impossible roles.
- Mark
manual-review for unclear term dates, full-time labels, clearance, residency/citizenship, bilingual requirements, driver/vehicle, relocation, rotating shift, or heavy electrical/mechanical credentials.
Score:
priority = resume_fit * 0.40 + co_op_legality * 0.25 + software_infra_fit * 0.15 + salary * 0.10 + city * 0.05 + brand_or_referral * 0.05 - friction
Caps:
- Hardware/facility roles requiring 2+ years, trade credentials, maintenance ownership, or deep rack/cabling cap at
3.4 unless student/trainee compatibility is explicit.
- Senior facility ownership, licensed trades, or project manager scope cap at
3.1 unless the user wants salary intelligence only.
- Software infrastructure co-ops can exceed
4.2 even when data-center-adjacent rather than physically in a data center.
Thresholds:
apply-now: 4.2+ and no hard gate.
fit-check: 3.7+ and details mostly clear.
manual-review: high upside with unresolved gate.
lead-inbox: useful watch target.
skip: low fit, expired, or blocked.
Resume Lane Selection
Use lanes from private config. Typical choices:
software-data: cloud/devops, infrastructure DevOps, network automation, monitoring, observability, AI tools, backend, database, analytics, internal platforms.
industrial-automation-ot: data center technician, critical environment intern, facility operations intern, power/cooling monitoring, BMS/BAS/EPMS data workflows, network hardware test automation.
domain-specialist: energy, utilities, process systems, or other candidate-specific domain.
For concrete tailoring, invoke $ats-resume-tailor.
Saving Contract
Append a lead object to the private queue only when new and useful:
{
"id": "public-<company>-<role-slug>-<location-or-requisition>-YYYYMMDD",
"company": "",
"role": "",
"date": "YYYY-MM-DD",
"status": "fit-check | manual-review | lead-inbox | watch-only | skip",
"source": "public-company-page | public-job-board/manual-company-check",
"sourceUrl": "",
"fitScore": 4.1,
"resumeVersion": "software-data",
"hardGates": [],
"feedback": "",
"next": ""
}
Output Contract
Report:
- what was saved and where
- top leads in priority order
- company, title, location, pay if known, status, lane, match reason, and hard gates
- which facts are from official pages versus mirrors
- soft infrastructure matches separately from hardware/facility exceptions
1---2name: data-center-coop-watch3description: Use when finding, monitoring, scoring, or saving external public data center, hyperscaler, cloud infrastructure, network operations, critical environment, facility operations, power/cooling, NOC, AI infrastructure, or paid trainee/co-op leads. Public-safe template version that relies on the candidate's private career config.4---56# Data Center Co-op Watch78## Overview910Find and triage public data-center-related leads without mixing them into university portal submission workflow. This skill handles discovery, scoring, hard-gate review, and local saving.1112Use `$ats-resume-tailor` for concrete resume tailoring and `$external-coop-apply` for employer portal execution. Use `$oscarplus-coop-apply` only for university portal postings or upload/submission steps.1314## Boundaries1516- Do not log into job boards, bypass gated pages, scrape credentials, upload documents, or submit applications.17- Prefer official company pages. Use mirrors only for discovery; mark `manual-company-check`.18- Do not assume full-time, trainee, apprentice, or technician roles count as co-op. Mark `manual-review` until eligibility, hours, dates, pay, and employer documentation are clear.19- Save only useful or watch-worthy leads.20- Default to software/infrastructure adjacency first: cloud/platform, network automation, observability, monitoring, backend/internal tools, data platforms, AI infrastructure, and infrastructure testing.21- Promote pure hardware/facility roles only when student, intern, co-op, trainee, junior, entry-level, paid training, or recruiter-confirmed compatibility is plausible.2223## Private Sources2425Read from private `career-config.json`:26271. `paths.jobQueue`282. `paths.resumeSystem`293. `paths.resumeSummary`304. `paths.jobLeadsDir`3132Read `references/employer-watchlist.md` when the task mentions hyperscalers, cloud infrastructure, paid training, data centers, facility operations, critical environment, power, cooling, network operations, or infrastructure monitoring.3334## Workflow35361. Establish scope.37 - Use term, geography, target roles, and preferred lanes from config unless the user overrides them.38392. De-duplicate.40 - Read queue IDs and existing digest rows.41 - Treat same company + similar title + same city as likely duplicate.42433. Search current public sources.44 - Official careers pages first.45 - Mirrors only for discovery or when official pages block indexing.46 - If current availability cannot be verified, mark `manual-company-check` or `watch-only`.47484. Hard-gate.49 - Mark `skip` for expired, clearly senior-only, unpaid, unrelated, or legally impossible roles.50 - Mark `manual-review` for unclear term dates, full-time labels, clearance, residency/citizenship, bilingual requirements, driver/vehicle, relocation, rotating shift, or heavy electrical/mechanical credentials.51525. Score:5354```text55priority = resume_fit * 0.40 + co_op_legality * 0.25 + software_infra_fit * 0.15 + salary * 0.10 + city * 0.05 + brand_or_referral * 0.05 - friction56```5758Caps:5960- Hardware/facility roles requiring 2+ years, trade credentials, maintenance ownership, or deep rack/cabling cap at `3.4` unless student/trainee compatibility is explicit.61- Senior facility ownership, licensed trades, or project manager scope cap at `3.1` unless the user wants salary intelligence only.62- Software infrastructure co-ops can exceed `4.2` even when data-center-adjacent rather than physically in a data center.6364Thresholds:6566- `apply-now`: 4.2+ and no hard gate.67- `fit-check`: 3.7+ and details mostly clear.68- `manual-review`: high upside with unresolved gate.69- `lead-inbox`: useful watch target.70- `skip`: low fit, expired, or blocked.7172## Resume Lane Selection7374Use lanes from private config. Typical choices:7576- `software-data`: cloud/devops, infrastructure DevOps, network automation, monitoring, observability, AI tools, backend, database, analytics, internal platforms.77- `industrial-automation-ot`: data center technician, critical environment intern, facility operations intern, power/cooling monitoring, BMS/BAS/EPMS data workflows, network hardware test automation.78- `domain-specialist`: energy, utilities, process systems, or other candidate-specific domain.7980For concrete tailoring, invoke `$ats-resume-tailor`.8182## Saving Contract8384Append a lead object to the private queue only when new and useful:8586```json87{88 "id": "public-<company>-<role-slug>-<location-or-requisition>-YYYYMMDD",89 "company": "",90 "role": "",91 "date": "YYYY-MM-DD",92 "status": "fit-check | manual-review | lead-inbox | watch-only | skip",93 "source": "public-company-page | public-job-board/manual-company-check",94 "sourceUrl": "",95 "fitScore": 4.1,96 "resumeVersion": "software-data",97 "hardGates": [],98 "feedback": "",99 "next": ""100}101```102103## Output Contract104105Report:106107- what was saved and where108- top leads in priority order109- company, title, location, pay if known, status, lane, match reason, and hard gates110- which facts are from official pages versus mirrors111- soft infrastructure matches separately from hardware/facility exceptions