employer-brand
Employer Brand
When to Use
Activate when the user asks to write careers page copy, create a culture document, draft an engineering blog post, build "day in the life" content, document company values, or generally improve how the company presents itself to prospective hires. Also activate when the user is struggling to differentiate their startup from competitors in the talent market.
Context Required
- From startup-context: Company name, mission, stage, team size, founding story, values (stated or practiced), remote/hybrid/onsite policy, notable perks, and any existing brand voice guidelines.
- From user: The specific content type needed, target audience (engineers, designers, go-to-market, general), existing content to build on (if any), and what makes the company genuinely distinctive as a workplace.
Workflow
- Identify the authentic story — Ask the user what is genuinely true and distinctive about working at this company. Employer brand must be rooted in reality or it backfires at onboarding. Probe for specific stories, rituals, and decisions that reveal culture.
- Choose the content format — Select from: careers page, values document, engineering blog post, "day in the life" feature, team spotlight, hiring process transparency post, or culture deck.
- Draft the content — Write using the Voice-Evidence-Proof framework (see below). Lead with what candidates care about (impact, growth, people, flexibility), not what the company cares about (mission statements in a vacuum).
- Ground every claim in evidence — For each cultural claim, attach a specific example, policy, or anecdote. "We value work-life balance" becomes "We have no meetings on Wednesdays and our average team member works 42 hours/week."
- Calibrate the tone — Match the company's actual communication style. A developer tools startup sounds different from a healthcare company. Avoid generic startup voice.
- Review for authenticity — Flag any claims that feel aspirational rather than current. Mark those explicitly or remove them. Candidates trust specificity and distrust superlatives.
More from shawnpang/startup-founder-skills
terms-of-service
When the user needs to draft, review, or update terms of service for their SaaS product or web application.
63pitch-deck
When the user wants to create, review, or restructure a fundraising pitch deck for seed or Series A. Also activates when the user mentions "deck", "pitch", "investor presentation", or "slide structure".
54review-mining
When the user wants to research customer pain points, complaints, or sentiment using review platforms like Trustpilot, G2, Capterra, or app stores. Also use when the user mentions "what are users saying", "competitor reviews", "pain points", or "voice of customer research".
52competitive-analysis
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
50prd-writing
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
48landing-page
When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.
46