# Weekly Career Research Automation

Use this playbook for recurring Codex runs that keep the tracker current.

## Goal

Keep `data/opportunities.json` accurate, useful, and focused on Rishabh's best lanes. The weekly briefing is the product. The opportunity list is supporting evidence.

- AI and platform SWE
- Devtools and cloud-native
- Fintech and data SWE
- Quant SWE
- GSoC and open-source mentorships

## Research Rules

Prefer official sources: company career pages, program pages, docs, GitHub org announcements, and university program pages. Use secondary sources only as discovery leads, then verify against official pages before adding or changing deadlines.

For every update:

1. Record `lastChecked` with the current date.
2. Set `confidence` to `official`, `official source to monitor`, `estimated from official timing`, or `manual strategy`.
3. Keep `automationNotes` specific enough that the next run knows what to verify.
4. Move expired items to `archive` only after checking whether a new term or replacement window exists.
5. Add a concise changelog entry to `changelog`.
6. Update `completedLog` before creating new tasks, so the plan accounts for work already done.
7. Update `weeklyBriefing.now`, `weeklyBriefing.plans`, `weeklyBriefing.weeklyWins`, and `weeklyBriefing.blocks` every run.

## Weekly Prompt

Research current career opportunities for Rishabh Sai and update this repository's tracker data.

Focus on Summer 2027 SWE internships, Fall 2026 and Spring 2027 mentorships, GSoC 2027 prep, LFX/CNCF/Meshery/Linux Foundation programs, and quant SWE recruiting. Prioritize official sources and verify dates before editing.

Before adding new tasks, read `completedLog`, `weeklyBriefing.weeklyWins`, and the existing `opportunities` list so the new plan accounts for what Rishabh already did. Update `weeklyBriefing` first with a readable weekly plan: `now`, `primaryFocus`, `secondaryFocus`, `theme`, `metric`, `weeklyWins`, `blocks`, and `plans`. Then update `briefingNotes`, `completedLog`, `opportunities`, and `changelog` as needed. Preserve the existing schema. Run `npm run check` before finishing and summarize what changed.

## Add Criteria

Add an opportunity only if at least one is true:

- It supports the AI/platform, devtools/cloud-native, fintech/data, or quant SWE lane.
- It has a real deadline, opening window, or preparation milestone.
- It gives strong open-source credibility for GSoC, LFX, CNCF, Meshery, or adjacent communities.
- It needs manual review because of eligibility, work authorization, Cisco overlap, or Penn State timing.

## Archive Criteria

Archive an item when:

- The deadline passed and no future window is visible.
- It conflicts with Cisco or school and has no useful preparation value.
- It no longer supports one of the active lanes.

Do not delete archived items unless the tracker becomes noisy. Archive first so the decision history stays visible.

## Briefing Quality Bar

The top of the page should read like a plan, not a list dump.

- Keep `weeklyBriefing.now` to 4 to 6 concrete actions.
- Keep each action tied to a due date or review date.
- Add new opportunities only when they change the plan or improve the watchlist.
- Put uncertainty in `review` status with a clear eligibility or verification question.
- Use `briefingNotes` for longer research synthesis, not random links.