compensation-analysis
Analyze compensation data, create salary bands, and ensure pay equity. Use this skill when benchmarking salaries, building compensation structures, or analyzing pay equity. Activate when: compensation, salary, pay equity, salary bands, compensation analysis, total rewards, salary benchmark.
What this skill does
# Compensation Analysis **Build fair, competitive compensation structures.** ## When to Use - Benchmarking salaries against market - Creating or updating salary bands - Analyzing pay equity - Planning compensation reviews - Building total rewards packages ## Compensation Structure ### Salary Band Framework ```markdown ## Band Structure | Level | Title Examples | Band Width | Typical Range | |-------|---------------|------------|---------------| | L1 | Associate, Junior | 20% | Entry level | | L2 | Mid-level, Specialist | 25% | 2-4 years exp | | L3 | Senior, Lead | 30% | 5-8 years exp | | L4 | Staff, Principal | 35% | 8-12 years exp | | L5 | Director, Senior Staff | 40% | 12+ years exp | ## Band Positioning | Position | % of Midpoint | When to Use | |----------|--------------|-------------| | Below Min | <80% | Rarely, new to role | | Min | 80% | New to level | | Target | 90-100% | Fully competent | | Midpoint | 100% | Market rate | | Above Mid | 100-120% | High performer | | Max | 120% | Exceptional, at cap | ``` ### Building Salary Bands ```markdown ## Step 1: Market Data - Gather salary data from 3+ sources - Sources: Radford, Mercer, Levels.fyi, Glassdoor, Payscale - Match to job families and levels ## Step 2: Determine Positioning | Strategy | Market Position | When to Use | |----------|----------------|-------------| | Lead | 75th percentile | Talent-competitive roles | | Match | 50th percentile | Standard roles | | Lag | 25th percentile | Budget constraints | ## Step 3: Set Band Width - Narrower bands (20%): Entry-level, structured roles - Wider bands (40%): Senior, variable roles ## Step 4: Calculate Ranges Midpoint = Market rate at target percentile Min = Midpoint × (1 - Band Width/2) Max = Midpoint × (1 + Band Width/2) Example (30% band, $100K midpoint): - Min: $100K × 0.85 = $85,000 - Max: $100K × 1.15 = $115,000 ``` ## Pay Equity Analysis ### Analysis Framework ```markdown ## Step 1: Data Collection Required fields: - Base salary - Job level/band - Department - Location - Tenure - Gender - Race/ethnicity (where legally collected) - Performance rating ## Step 2: Group Comparison Compare pay within: - Same job level - Same department - Same location - Similar tenure ## Step 3: Statistical Analysis - Calculate pay gap percentages - Run regression analysis controlling for: - Job level - Experience - Performance - Location - Education (if relevant) ## Step 4: Identify Outliers Flag individuals who are: - >5% below expected pay - >10% above expected pay - Unexplained by legitimate factors ``` ### Pay Gap Metrics ```markdown ## Raw Pay Gap (Avg Male Salary - Avg Female Salary) / Avg Male Salary × 100 ## Adjusted Pay Gap Difference after controlling for: - Job level - Department - Location - Experience - Performance ## Compa-Ratio Individual Salary / Band Midpoint × 100 Target: 90-110% ``` ## Total Compensation Components ```markdown ## Base Salary - Fixed annual pay - Typically 60-80% of total comp ## Variable Pay ### Bonus - Target %: [X]% of base - Performance multiplier: 0-200% - Payout timing: Annual/Quarterly ### Commission (Sales) - On-target earnings (OTE) - Split: [X]% base / [X]% variable - Accelerators above quota ## Equity ### Stock Options - Grant value at hire - Vesting: Typically 4 years, 1-year cliff - Refresh grants ### RSUs - Restricted Stock Units - Same vesting as options - Value = shares × stock price ## Benefits Value - Health insurance: $[X]/year - 401(k) match: [X]% up to $[X] - Other benefits: $[X]/year ## Total Rewards Statement Base Salary: $XXX,XXX Target Bonus: $XX,XXX Equity (annual): $XX,XXX Benefits: $XX,XXX Total Compensation: $XXX,XXX ``` ## Compensation Review Process ```markdown ## Annual Review Cycle ### Timeline | Month | Activity | |-------|----------| | Q3 | Budget planning, market data refresh | | Q4 | Manager recommendations | | Jan | Calibration sessions | | Feb | Final approvals | | Mar | Communication to employees | | Apr | New compensation effective | ### Manager Worksheet For each employee, consider: 1. Current compa-ratio 2. Performance rating 3. Time since last increase 4. Retention risk 5. Market movement 6. Budget constraints ### Calibration Questions - Are increases proportional to performance? - Are there pay equity concerns? - Are high performers above midpoint? - Are retention risks addressed? ``` ## Geographic Pay Differentials ```markdown ## Location-Based Adjustments | Tier | Example Locations | % of Base | |------|-------------------|-----------| | Tier 1 | SF, NYC, Seattle | 100% | | Tier 2 | LA, Boston, Denver | 90-95% | | Tier 3 | Austin, Chicago, Atlanta | 85-90% | | Tier 4 | Other metro areas | 80-85% | | Tier 5 | Rural / low COL | 75-80% | ## Relocation Considerations - Moving to higher tier: May increase - Moving to lower tier: Typically maintain (grandfathered) - New hires: Paid at location rate ``` ## Best Practices 1. **Update market data annually** - Compensation moves fast 2. **Be transparent** - Share bands and philosophy with employees 3. **Regular equity audits** - At least annually 4. **Document decisions** - Maintain records for all pay decisions 5. **Train managers** - They need to understand and communicate comp 6. **Consider total rewards** - Base salary isn't everything 7. **Budget realistically** - Plan for merit, promotions, and equity fixes
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.