How to Write an SOQ for a Supervisor I (Staff Services Manager I) Position

First, a naming note: on January 1, 2026, CalHR's generalist consolidation retitled this series. Staff Services Manager I became Supervisor I, and the Associate Governmental Program Analyst (AGPA) classification most people promote from became Analyst II. You'll see both old and new titles on postings and duty statements for a while — they describe the same first-line supervisory role, and everything in this guide applies to both.

Supervisor I is the first supervisory level in the state's administrative series: managing a small unit of analysts and support staff while personally handling the most difficult or sensitive work. (Under the old SSM I classification there was also a non-supervisory "specialist" flavor; that track now lives in the new Analyst III and IV classifications, so a Supervisor I posting means supervision.)

Evaluators are answering one question: has this person actually led people and owned outcomes, or have they only been a strong individual contributor? The prompts probe classic first-line management competencies:

• Assigning, reviewing, and evaluating the work of others
• Setting unit priorities and managing competing deadlines
• Coaching, feedback, and handling performance problems
• Representing the unit to leadership and stakeholders
• Implementing policies and changes your staff may not like

If you've never held the title "supervisor," you can still score well — lead person assignments, training new analysts, running projects with matrixed teams, and acting/limited-term supervisory stints all count. What doesn't score is describing analytical work, however impressive, when the prompt asks about leading people.

Most SSM I postings specify:

• 12-point Arial font
• Single-spaced text
• Maximum 2 pages — though some postings allow 3 and some only 1; check every time
• 1-inch margins
• Your name and Job Control (JC) number on each page

At the managerial level, format compliance is itself part of the evaluation — an SSM I candidate who can't follow written instructions undermines their own case. Number your responses to match the prompts and keep them in order.

One SSM-specific note: postings at this level increasingly ask for the SOQ to address the duty statement as a whole rather than numbered questions. When that happens, organize your response with brief headings mapped to the duty statement's major functions (e.g., supervision, program management, stakeholder communication) so evaluators can score each area.

Use the STAR method, but shift what you emphasize compared to an analyst SOQ:

Lead with scope. Open each example by establishing what you were responsible for: "As lead analyst over a 4-person contracts unit processing roughly 200 agreements a year..." Size of team, budget, program, or caseload gives evaluators the scale to score against.

For supervision prompts: Cover the full cycle — assigning work, setting expectations, reviewing output, giving feedback — and include a hard case. A performance issue you addressed (documented expectations, coaching plan, improvement or progressive next step) is the strongest evidence available that you can do the uncomfortable part of the job. Keep the employee anonymous and the tone professional.

For program/workload management prompts: Show the management layer, not the analysis layer. How you triaged competing priorities, what you delegated and why, how you tracked the unit's output, and what changed as a result — a cleared backlog, a met statutory deadline, an audit finding closed.

For difficult communication prompts: Pick a genuinely unpopular decision — a policy change staff resisted, a denied request, a reorganization. Describe how you prepared, how you delivered it (directly, with the reasons), how you handled the reaction, and where things landed. Evaluators are looking for candidates who absorb friction rather than pass it up or down.

Quantify results at the unit level. "My unit's average processing time dropped from 21 to 12 days" outscores any adjective. If you improved a person, a process, and a number, you've written a Supervisor I answer.

If you're an Analyst II (formerly AGPA) without formal supervision, mine your lead experience: training and mentoring analysts, reviewing others' work products, coordinating workgroups, and acting assignments. Name them explicitly as leadership — "I functioned as lead for three junior analysts, assigning and reviewing their casework" — rather than hoping the evaluator infers it.

Writing an analyst SOQ — the #1 failure. Detailed accounts of your own analyses, reports, and regulations work answer a question the prompts didn't ask. Every example should have other people's work in it.

Claiming leadership without evidence — "I have strong leadership skills and lead by example" scores zero. Named responsibilities, team sizes, and outcomes score.

Avoiding conflict examples — candidates skip performance-problem and unpopular-decision stories because they feel negative. They're the highest-value content in the SOQ; handled professionally, they're what distinguishes managers from senior analysts.

Taking sole credit for team results — the opposite failure. At this level the skill being scored is producing results through others: "I redesigned the intake process" reads worse than "I led my unit through redesigning the intake process, assigning the workflow analysis to two staff and reviewing their recommendations."

Applying to the wrong classification — if what you actually want is the non-supervisory expert track, that's now Analyst III/IV, not Supervisor I. A supervision-light SOQ for a Supervisor I posting misses the rubric; the duty statement tells you which competencies to weight.

Recycling your Analyst II (AGPA) SOQ — evaluators at the same department may have literally read it. The promotion case requires new, bigger examples.