How to Write an SOQ for an Analyst II Position (Formerly AGPA)

Effective January 1, 2026, California implemented CalHR’s Generalist Class Consolidation. For rank-and-file analyst roles, the statewide titles changed:

• Associate Governmental Program Analyst (AGPA) → Analyst II
• Staff Services Analyst (SSA) → Analyst I
• New Analyst III and Analyst IV classifications sit above the former AGPA / current Analyst II journey level.

Exams and lists: The AGPA examination was discontinued December 22, 2025. AGPA eligible lists were abolished December 23, 2025, with new Analyst II eligibility established under the consolidation.

After January 1, 2026: New appointments to Analyst II serve a 12-month probationary period (per CalHR consolidation materials).

Minimum qualifications for the new Analyst series were broadened: qualifying experience can include analytical, technical, clerical, or customer service work, and accredited college or university education may substitute year-for-year for experience where the class specification allows.

Everything below still applies to writing SOQs for Analyst II vacancies — the skills and expectations mirror what agencies previously tested for AGPA.

A Statement of Qualifications (SOQ) is a written exam used by California state agencies to screen applicants before interviews. Unlike a cover letter, the SOQ is scored — reviewers evaluate your command of the subject matter, your use of specific examples, and the quality of your writing.

For Analyst II positions (legacy AGPA recruitments), SOQs typically run 1–2 pages and ask you to respond to 2–4 prompts that mirror the core duties of the role: complex analysis, independent program management, written and oral communication with management, and cross-organizational coordination.

Because Analyst II is a journey-level classification, reviewers expect more than task execution. They are looking for evidence that you can work independently, exercise professional judgment, and move a project forward without close supervision.

Analyst II sits above Analyst I (formerly Staff Services Analyst) in the statewide analyst series. Analyst III and Analyst IV are above Analyst II if you are targeting those classifications instead.

The key distinction in the SOQ is the level of autonomy and complexity your examples should reflect:

If your examples read like "I was assigned X and I completed it," you are writing at the Analyst I level. Analyst II responses should show that you defined the approach, managed ambiguity, and owned the outcome.

This does not mean you need supervisory experience — but your examples should demonstrate initiative, complexity, and impact.

Most Analyst II job postings specify:

• 12-point Arial font
• Single-spaced within paragraphs unless the bulletin requires double-spacing
• Blank lines between paragraphs or prompt responses can improve readability — follow the posting if it specifies spacing; otherwise use clear paragraph breaks
• Maximum 2 pages in many postings (violations can disqualify you automatically)
• Unless the posting says otherwise, include your name and the Job Control Number (JC#) at the top of each page; many bulletins also ask for "Statement of Qualifications" in the header

Always re-read the Special Requirements section of the CalCareers posting — agencies vary. Some postings allow three or four pages, sometimes double-spaced; length and spacing are never universal defaults. Some departments require you to restate each prompt (list the original questions) before your answers.

Use the STAR method for each prompt:

1. Situation — briefly set the context (where you worked, your role, and the complexity or scale of the situation)
2. Task — what you were responsible for, emphasizing the degree of independent ownership
3. Action — the specific steps you took: how you structured the analysis, who you engaged, what you decided — this is the longest section
4. Result — measurable or observable outcome (policy adopted, process improved by X%, decision made, stakeholder alignment achieved)

For Analyst II–level prompts, the Action section is where most points are won or lost. Be specific about how you approached the problem, not just what the problem was. Raters are scoring your analytical process and professional judgment — not just your output.

Avoid vague language like "I collaborated with the team" or "I helped with the project." Say who you coordinated with, what role you played, and what you specifically contributed.

• Writing at the wrong level — describing task completion rather than independent analytical work; Analyst II screeners will score this low even if the example is otherwise good
• Exceeding the page limit — disqualifying at many agencies
• Not labeling prompt responses — reviewers need to know which prompt you're answering
• Using a generic SOQ — raters score based on how well your examples match this duty statement
• Using "we" throughout — raters are scoring your individual contribution, not your team's
• Passive voice and vague language — say "I developed the methodology" not "a methodology was developed"
• No result — describing what you did without saying what changed or what decision it drove
• Forgetting transferable skills — private-sector, nonprofit, or federal experience counts; map your examples directly to the prompts