# GitHub sourcing role brief

Copy the blank brief for a vacancy you are authorized to fill. Keep unknown fields visible. The example below is an editorial exercise using a public job advertisement; Automattic is not presented as a Metix customer and no role was activated or outreach sent on its behalf.

## Blank brief

- Role / internal vacancy ID:
- Hiring manager / approval owner:
- Vacancy authorization and hiring status:
- Outcomes the person must own:
- Mandatory criteria and acceptable evidence for each:
- Trainable skills and acceptable tradeoffs:
- Location, working hours, compensation and employment constraints (confirmed, not inferred from a profile):
- Relevant projects / why each relates to the role:
- People-search query / project-search query / surface / observation time:
- Public source link and exact commit when inspecting code:
- Observed facts / interpretation / unresolved questions:
- Technical reviewer / questions for that reviewer:
- Alternative evidence route for people without public code:
- Current interest and permitted contact route:
- Next action / owner / approval:
- Decision: continue / revise search / stop, with reason:

## Filled editorial example: Experienced Software Engineer

Source: https://automattic.com/work-with-us/job/experienced-software-engineer/ (read October 19, 2026).

- Role: Automattic's public Experienced Software Engineer advertisement. No internal vacancy ID or hiring-manager authorization available to this exercise.
- Work: production software, debugging through abstraction layers, and systems used at scale. The advertisement describes PHP and JavaScript as main languages and asks for comfort becoming an expert; this brief does not impose prior mastery of both.
- Evidence to discuss: a concrete debugging change, tests around its failure mode, and the contributor's account of review decisions and responsibility. Public code alone cannot establish production ownership.
- Trainable / excluded shortcuts: repository language is a discovery hint; account age, stars and followers are not seniority criteria. London is not a mandatory filter for this global role.
- Project path: tested WordPress/PHP repository query returned WooCommerce; a separate WordPress organization query found Gutenberg with TypeScript as its primary language.
- Worked source: WooCommerce pull request 69956; head 6ba126422919da9c004169b4fa33e8e39600fc6e. The permission check uses the actual order type and adds regression cases. The public author declares the fix and test were written by Claude Code and reviewed by the author.
- Interpretation: useful permission-boundary example for a technical conversation, not an assessment of the contributor's candidacy. This exercise read the patch and did not run its tests.
- Unknown: contribution responsibility beyond the declaration, production scale, broader language experience, interest, employment eligibility and compensation. No candidate was qualified, contacted or represented to the employer.
- Next action for your own vacancy: have your technical reviewer examine evidence against your mandatory criteria, ask the person about their decisions through an appropriate contact route, and record what remains unknown. Offer equivalent evidence from private or employer-owned work.

## Handoff to your own hiring workflow

Use your own authorized vacancy and a named reviewer. If you test Metix, create that role, review its match evidence and approve outreach. This document does not establish a native GitHub import, people-search API or MCP integration. Metix self-serve does not include staff shortlist review; Delivery is quoted separately. A downloaded worksheet or a signup is not a real role activation or a hiring outcome.