Hiring & Recruiting
Recruitment strategy for seed-to-Series A startups. Outcome-based JDs, structured interviews, equity mechanics, pipeline design, and org trade-offs using your people context. This is still a catalog page: it shows the available skills, but the surrounding product and solution context lives elsewhere.
Skills
Job Description Writer
@jdGenerate outcome-based job descriptions with stage-appropriate tone and explicit 3/6/12-month milestones instead of generic credential lists.
Examples
@jd Senior Engineer, focus on 90-day outcomes@jd Head of Sales, YC execution tone@jd adapt our PM JD for remote-first@jd make this JD more inclusiveCandidate Evaluation
@evaluateScore candidates against a structured scorecard with evidence-based assessment, visible data gaps, and bias-resistant reasoning.
Examples
@evaluate score this candidate for the Staff Eng role@evaluate compare our top 3 finalists@evaluate debrief template for the PM interviews@evaluate red flags in this candidate's background?Interview Designer
@interviewBuild scorecards, behavioral question banks, and structured interview plans that reduce drift and confirmation bias.
Examples
@interview scorecard for Staff Engineer@interview behavioral questions for VP Sales@interview Who method walkthrough guide@interview culture fit questionsOffer Builder
@offerStructure offers with clear equity mechanics, vesting terms, and market-aware compensation trade-offs.
Examples
@offer Senior Eng, 0.15% equity, SF market@offer structure VP package with signing bonus@offer compare our offer to market for this role@offer how much equity for employee #15?Hiring Pipeline
@pipelineDesign hiring pipelines, identify candidate drop-off points, and forecast time-to-fill by role and stage.
Examples
@pipeline design stages for our first engineering hire@pipeline where are engineering candidates dropping off?@pipeline forecast when we fill the 3 open roles@pipeline hiring velocity this quarterOrg Design & Team Strategy
@org_designPlan role sequencing, founder delegation, and build-vs-buy staffing decisions using your people context.
Examples
@org_design what should our next 3 hires be?@org_design should we hire a VP Eng or a senior IC?@org_design which responsibilities should I delegate first?@org_design build vs contract vs tool for customer success?Need more than the pack?
Bridge back to product surfaces, use cases, and resources
Use the catalog to pick a capability. Use the rest of the site when you need the broader product map, the workflow story, or detailed guidance.
Platform overview
Use the platform overview when you need the system map before choosing a capability.
Use cases
Use /solutions when the question is about a workflow or use case rather than a specific capability.
Platform surfaces
Use /platform when you already know the surface you want to work in.
Resources hub
Use /resources for help, developer docs, security, and higher-level guidance around the capability layer.