How to Write an SOQ for an Analyst III Position

Analyst III is one of the classifications created by CalHR's Generalist Class Consolidation, approved by the State Personnel Board and effective January 1, 2026. The consolidation collapsed dozens of legacy analyst and program-specialist titles into a single statewide series: Analyst I through IV, plus Supervisor I–II and Manager I–II.

In that series, Analyst III sits above Analyst II (the journey-level title that replaced Associate Governmental Program Analyst / AGPA) and below Analyst IV. It is generally treated as an advanced journey-level role: for analysts who have moved past independently executing projects and into work that involves broader scope, higher-stakes recommendations, and often some responsibility for guiding less experienced staff.

Because the classification is new, there isn't yet a large body of "typical" Analyst III duty statements to generalize from: read the specific posting's duty statement closely, since agencies are still settling into how they use the title. What's consistent across postings is that Analyst III work sits a clear step above Analyst II in complexity and independence.

Like other analyst-series SOQs, this one is a scored written exam, not a cover letter. Evaluators use a rubric tied to the classification's core competencies, and for Analyst III those competencies typically run heavier on:

• Scope and stakes: projects with statewide, multi-program, or cross-departmental impact, not single-team initiatives
• Independent judgment at a higher altitude: recommending policy or program direction, not just executing an assigned analysis
• Communicating with management and executives: framing findings and recommendations for decision-makers, sometimes under time pressure or political sensitivity
• Technical leadership: reviewing others' work, mentoring less experienced analysts, or leading a workgroup, even without formal supervisory authority

If your best examples read like solid Analyst II work (you were assigned a project, you executed it well, you delivered a result), that's a good foundation, but for Analyst III prompts you want to show the next layer: why your recommendation mattered beyond your own assignment, or how you helped shape the approach other people used.

Confirm the exact requirements on each posting's Special Requirements section: Analyst III postings, like other analyst-series roles, commonly specify:

• 12-point Arial font
• Single-spaced paragraphs, with a blank line between responses for readability
• Maximum 2 pages in most postings (some allow more; never assume, always check)
• Your name and the Job Control (JC) number at the top of each page
• Clearly label each response with its prompt number

Exceeding the stated page limit is one of the most common disqualifiers across all SOQ-based recruitments; don't let a strong answer get cut for a format violation.

Use the STAR method (Situation, Task, Action, Result), but calibrate the content to the level:

1. Situation: set the scale explicitly: how many programs, stakeholders, or dollars were involved; why the analysis mattered beyond your immediate team
2. Task: your specific ownership, especially anything involving advising management or guiding other staff
3. Action: the longest section. Walk through your analytical approach, how you validated it, who you briefed, and how you handled pushback or competing priorities
4. Result: a concrete outcome: a decision made, a policy adopted, a process changed statewide or across multiple units, measurable improvement

For the mentoring/leadership prompt, don't overstate formal authority you didn't have. "I reviewed and provided feedback on two colleagues' analyses before they went to our unit chief" is honest and still demonstrates the competency; you don't need to have been anyone's supervisor.

Avoid "we" throughout. Raters are scoring your individual contribution, even in team-based work.

Writing at the Analyst II level: describing solid independent project work without showing the added scope, stakes, or advisory dimension that Analyst III prompts are looking for.

Ignoring the specific posting's duty statement: because Analyst III is new, agencies use it somewhat differently. Don't assume every posting wants the same emphasis; read the duty statement and mirror its priorities.

Overclaiming supervisory authority: if you haven't formally supervised staff, don't imply you have. Frame mentoring and technical leadership honestly.

Exceeding the page limit: still the most common avoidable disqualifier.

No measurable result: especially at this level, evaluators want to see that your recommendation or analysis actually changed something.