tech-employer-branding

Designs an engineering employer-brand strategy with EVP, channel ranking, and measurement baselines.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/developer-relations-skills --skill tech-employer-branding-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-employer-branding
Source: https://github.com/samber/developer-relations-skills/tree/main/skills/tech-employer-branding
Command: npx skills add https://github.com/samber/developer-relations-skills --skill tech-employer-branding-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Companies struggle to attract software engineers because their employer brand claims are contradicted by review sites, compensation databases, and anonymous forums, and their business cases rest on unsourced statistics. This Skill produces an honest, evidence-tiered engineering employer-brand plan instead of generic culture marketing. ## Core Features & Use Cases - EVP Design: Builds the employee value proposition against the EmpAt five values, forces specifics, and produces an explicit "what we don't offer" list checked against the four trust-eroding mismatch patterns. - Verification-Surface Audit: Audits employer-review sites, compensation databases, and anonymous forums before any content spend, with a ~70% offer-acceptance floor gating top-of-funnel investment. - Channel Ranking by Stage and Seniority: Ranks channels (posting fixes, transparency artifacts, referrals, blog, talks, OSS-as-funnel) by efficiency, value, effort, and compliance cost, matched to company stage and candidate seniority tier. - Statistic Debunking: Refuses the three circulating zombie statistics (72% blog-check, Gartner 69%, LinkedIn 50%) by name and supplies tier-labelled grounded replacements. - Use Case: A VP People preparing a board deck for an employer-brand budget gets the unsourced figures replaced with defensible ones; a founder with a 58% offer-acceptance rate gets a trust-audit-first plan instead of a blog calendar. ## Quick Start Ask the assistant to build an engineering employer-brand strategy for your company, describing your stage, target seniority, current offer-acceptance rate, and review-site ratings.

Frequently Asked Questions about tech-employer-branding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an employer brand strategy to attract software engineers?

Start by instrumenting source-of-hire and offer-acceptance tracking, then define an honest EVP using the EmpAt five values, audit verification surfaces like review sites and comp databases, and rank channels by efficiency and seniority fit. The Skill produces a plan with 2-4 channel bets, never the content artifacts themselves.

Should we publish salary bands in engineering job postings?

Yes in most cases: reward-specific information measurably improves candidate fit assessment, and pay-transparency law may already require ranges. Published bands need comp and legal sign-off and read as a pay cut if walked back, so treat them as a committed transparency artifact.

Is the '72% of developers check a company's engineering blog before applying' statistic real?

No. It is untraceable, a distortion of two different uncited vendor-guide claims, and no publisher stands behind it. Use grounded alternatives instead, such as Glassdoor's finding that a 0.5-star rating increase yields about 20% more job clicks.

When does hiring from an open-source community work as a recruiting channel?

OSS-as-funnel works only when the product has a genuine open-source core and the mandate is compounding rather than a one-off push, since it costs maintainer-years before returning hires. Fund it properly with paid contributors and a contributor-to-employee path, or skip it entirely.

What should we do when our offer-acceptance rate is low but leadership wants more content?

If engineering offer-acceptance sits below roughly 70%, stop top-of-funnel spend and audit the gap between marketed brand and what review sites and forums say first. Content on top of a trust problem amplifies the problem rather than fixing it.

Can we ask employees to leave positive reviews to fix a low employer rating?

No. Incentivized or solicited reviews are astroturfing, and engineers treat manufactured sentiment as a stronger negative signal than the weakness it hides. The legitimate moves are responding to existing reviews and fixing the operational issues the reviews allege.