Proud-to-Take Job Search

Criteria

• Labels each condition as must-have or preference, so trade-offs are visible
• States the mission or values requirement and at least two disqualifying red flags
• Gives a salary range and scope checked against public market data

Sources

• O*NET OnLine onetonline.orgTypical duties, pay and outlook for a role.
• Levels.fyi levels.fyiCompensation by role, level and company.

Watches

• Searches “job postings target role title target industry” weekly

Criteria

• Names the team or problem being targeted, not the brand
• Has one dated signal per company, such as a hire, launch or funding, with source
• Names an outreach path: a referral, recruiter or team member
• Explains fit with evidence, such as a mission statement or public repository activity

Sources

• GitHub REST API docs.github.comOrganisation repository activity as a signal of engineering priorities.
• Company signals (fictional) api.company-signals.example.comFictional feed of news, funding and hires for listed companies.

Watches

• Searches “target company hiring OR funding OR product launch” weekly
• Follows Role criteria

Criteria

• Shows stage and the date it was entered, so time in stage is visible
• Gives every open application a follow-up date and owner
• Records an outcome reason on closed applications so patterns appear
• Links each application to a company and role in the other sections

Sources

• Hacker News: Who is hiring news.ycombinator.comMonthly threads that surface small teams not on job boards.

Watches

• Searches “target role job opening” weekly
• Follows Target companies

Criteria

• Each story states a measured outcome or decision made, not duties performed
• Tags each story by skill and names the target roles that value it
• Records where the evidence comes from, such as a review, project result or reference

Watches

• Follows Role criteria
• Follows Target companies