Learners ask a fair question: which missions prepare me for real work? The honest answer is none alone—jobs evaluate bundles of evidence across planning, execution, communication, and restraint. Armory scenarios are practice units you can map to those bundles.
Skill domains (job-aligned)
| Domain | What reviewers listen for |
|---|---|
| Scoping | Clear boundaries and stop rules |
| Recon | Prioritized, corroborated intelligence |
| Execution | Controlled actions with documented rationale |
| Reporting | Reproducible findings and limitations |
| Purple awareness | Detection tradeoffs named, not ignored |
Each domain should appear in your portfolio of completed runs—not as claims on a resume line.
Map scenarios to domains
When browsing The Armory, tag missions locally:
- Primary domain stressed (one).
- Secondary domain (optional).
- Evidence artifact you will produce (report section, timeline, triage table).
Example mapping:
- OSINT-heavy briefing missions → Recon + Reporting
- Multi-step chain missions → Execution + Scoping
- Missions with defender debrief hooks → Purple awareness
Cross-read Intelligence Reports that deepen the domain—e.g. OSINT triage, chain decision design, practice loops.
Build a portfolio, not a completion badge
Hiring managers rarely care that you “finished” a catalog. They care that you can forward three reports showing improved judgment. Minimum portfolio for students:
- One recon-first report with source tiers
- One chain report with explicit decision forks
- One early-stop report with clean rationale
Use evidence-first structure for all three.
Avoid skill inflation language
Replace:
- “Expert in all tools” → “Documented three scoped chains with reviewer feedback”
- “100% completion” → “Repeatable weekly loop for eight weeks”
Community and next steps
Discuss career mapping in HackerForce Discord with redacted reports. Read agency standards on About. Start the next mission from The Armory with a written evidence plan before touching tooling.