Generate a structured interview rubric and scoring framework to evaluate operator candidates consistently across technical skills, execution ability, and operational fit.
You are an expert recruiting operations consultant. Build a detailed hiring scorecard for evaluating {{operatorRole}} candidates.
Context:
- Team size: {{teamSize}}
- Key responsibilities: {{keyResponsibilities}}
- Critical skills: {{criticalSkills}}
- Company stage: {{companyStage}}
- Hiring timeline: {{hiringTimeline}}
Create a scorecard that includes:
1. **Evaluation Dimensions** (5–8 criteria)
- For each dimension, provide:
- Clear definition of what you're assessing
- Why it matters for this role
- Relative weight (% of total score)
2. **Scoring Rubric** (1–5 scale for each dimension)
- Level 1: Clear definition of unacceptable performance
- Level 2: Below expectations
- Level 3: Meets expectations
- Level 4: Exceeds expectations
- Level 5: Exceptional/role model
- Include 2–3 behavioral anchors per level (specific examples)
3. **Interview Questions** (2–3 per dimension)
- Behavioral or situational questions that surface evidence
- Avoid yes/no questions
4. **Scoring Guidance**
- How to calculate weighted total score
- Minimum score thresholds for hire/no-hire/maybe decisions
- Red flags that override high scores
5. **Calibration Notes**
- Common scoring mistakes to avoid
- How to compare scores across multiple candidates
Format as a practical document a hiring manager can use immediately in interviews.1. Fill in the six input fields with your operator role details, team context, and critical success factors. 2. Run the prompt to generate a customized scorecard. 3. Review the evaluation dimensions and adjust weights if needed to match your priorities. 4. Print or share the scorecard with all interviewers before the interview loop. 5. During interviews, take notes against each dimension and score immediately after each conversation. 6. After all interviews, calculate weighted scores and use the decision matrix to make a hire/no-hire call. 7. Document scores and rationale for each candidate to build a hiring record and calibrate future scorecards.
{
"operatorRole": "Revenue Operations Manager",
"teamSize": "Reports to VP Revenue, manages 1 coordinator, partners with Sales, CS, and Finance",
"keyResponsibilities": "Salesforce administration and optimization, sales process design, quota and commission management, monthly revenue reporting",
"criticalSkills": "Salesforce expertise, SQL or data analysis, process design, stakeholder management, attention to detail, ability to work independently",
"companyStage": "Series B SaaS (ARR $5M–$20M)",
"hiringTimeline": "Standard (4–6 weeks)"
}# Revenue Operations Manager Hiring Scorecard ## Evaluation Dimensions (Weighted) ### 1. Salesforce Expertise & Technical Proficiency (25%) **Definition:** Hands-on ability to configure, troubleshoot, and optimize Salesforce for sales operations. **Why it matters:** This role owns the CRM; weak Salesforce skills create bottlenecks and data quality issues. **Scoring Rubric:** - **Level 5 (Exceptional):** Has administered Salesforce for 3+ years; can design custom objects, workflows, and reports; proactively identifies optimization opportunities. - **Level 4 (Exceeds):** 2+ years Salesforce admin experience; comfortable with standard configurations and troubleshooting; has improved existing processes. - **Level 3 (Meets):** 1–2 years Salesforce experience; can execute standard admin tasks; learns new features with guidance. - **Level 2 (Below):** Limited Salesforce exposure; can perform basic tasks but struggles with troubleshooting or design. - **Level 1 (Unacceptable):** No Salesforce experience or unable to demonstrate basic admin knowledge. **Interview Questions:** - "Walk me through a Salesforce configuration you designed. What problem did it solve, and how did you test it?" - "Tell me about a time you had to troubleshoot a broken Salesforce workflow or report. How did you approach it?" --- ### 2. Process Design & Optimization (20%) **Definition:** Ability to map, analyze, and improve sales and revenue operations workflows. **Why it matters:** This role drives efficiency; weak process thinking leads to manual workarounds and scalability issues. **Scoring Rubric:** - **Level 5:** Has led cross-functional process redesigns; uses data to identify bottlenecks; communicates changes clearly to stakeholders. - **Level 4:** Has improved 2–3 existing processes; gathers feedback and iterates; documents changes. - **Level 3:** Can analyze a process and suggest improvements; implements changes with support. - **Level 2:** Recognizes process problems but struggles to design or execute solutions. - **Level 1:** No demonstrated process improvement experience. **Interview Questions:** - "Describe a process you redesigned. What metrics did you use to measure success?" - "How do you prioritize which processes to optimize first?" --- ### 3. Data Analysis & SQL (15%) **Definition:** Ability to query, analyze, and visualize data to answer business questions. **Why it matters:** Monthly reporting and quota analysis require independent data work; weak SQL skills create dependency on engineering. **Scoring Rubric:** - **Level 5:** Writes complex SQL queries independently; creates dashboards; identifies data quality issues proactively. - **Level 4:** Writes standard SQL queries (JOINs, aggregations); uses BI tools to create reports. - **Level 3:** Can write basic queries with guidance; interprets reports and dashboards. - **Level 2:** Understands SQL concepts but rarely writes queries independently. - **Level 1:** No SQL experience. **Interview Questions:** - "Show me an example of a report or analysis you built. How did you approach it?" - "If you needed to calculate commission payouts by rep, how would you do it?" --- ### 4. Stakeholder Management & Communication (20%) **Definition:** Ability to influence Sales, CS, and Finance teams; communicate clearly; manage competing priorities. **Why it matters:** This role sits between teams; poor communication creates friction and missed deadlines. **Scoring Rubric:** - **Level 5:** Proactively communicates changes; builds trust with stakeholders; navigates conflicts diplomatically; influences without authority. - **Level 4:** Communicates clearly; responds to stakeholder needs; handles disagreements professionally. - **Level 3:** Communicates adequately; may need reminders to loop in stakeholders. - **Level 2:** Communication is unclear or infrequent; stakeholders feel surprised by changes. - **Level 1:** Poor communication; creates friction or misalignment. **Interview Questions:** - "Tell me about a time you had to push back on a stakeholder request. How did you handle it?" - "Describe a time you had to communicate a process change that people didn't like. How did you get buy-in?" --- ### 5. Execution & Attention to Detail (15%) **Definition:** Ability to deliver accurate, on-time work; catch errors; manage multiple projects. **Why it matters:** Revenue operations requires precision; errors in commission or quota calculations have direct financial impact. **Scoring Rubric:** - **Level 5:** Consistently delivers error-free work; proactively identifies and prevents mistakes; manages multiple projects without dropping balls. - **Level 4:** Delivers accurate work on time; catches own mistakes; manages workload well. - **Level 3:** Generally accurate; occasional errors caught by others; manages workload adequately. - **Level 2:** Frequent errors or missed deadlines; requires close oversight. - **Level 1:** Unreliable; significant errors or missed deliverables. **Interview Questions:** - "Tell me about a time you made a mistake at work. How did you handle it?" - "How do you manage multiple projects with competing deadlines?" --- ## Scoring Guidance **Weighted Score Calculation:** - Salesforce (25%) + Process Design (20%) + Data Analysis (15%) + Stakeholder Management (20%) + Execution (15%) = 100% - Example: (5 × 0.25) + (4 × 0.20) + (3 × 0.15) + (4 × 0.20) + (5 × 0.15) = 1.25 + 0.80 + 0.45 + 0.80 + 0.75 = **4.05 / 5.0** **Decision Thresholds:** - **Hire:** 4.0–5.0 (Strong fit across dimensions; can ramp quickly) - **Maybe:** 3.5–3.9 (Solid in some areas; may need support in others; consider for second round) - **No Hire:** Below 3.5 (Significant gaps; unlikely to succeed in role) **Red Flags (Override High Scores):** - Salesforce score below 3 (role requires hands-on admin) - Execution score below 3 (errors in revenue operations are costly) - Stakeholder management score below 3 (role requires cross-functional influence) ## Calibration Notes - **Common Mistake:** Scoring high on "culture fit" or "likability" instead of job-specific competencies. Stick to the five dimensions. - **Comparing Candidates:** Use the weighted score to rank candidates objectively. If two candidates have similar scores, review red flags and dimension breakdowns to decide. - **Recalibration:** After hiring, revisit the scorecard in 90 days. Did high scorers succeed? Did low scorers struggle? Adjust dimensions or weights based on what actually predicted performance.