How to Write an SOQ (Statement of Qualifications) for California State Jobs, With Examples

An SOQ, or Statement of Qualifications, is a written document required by many California state job postings. Applicants are asked to respond to a set of prompts (typically 1–5, with 2–4 being most common) that map to the duties, desirable qualifications, and competencies described in the job posting and duty statement.

Unlike a resume or cover letter, the SOQ is a scored selection instrument. Reviewers, often the hiring manager, and sometimes a panel of subject-matter experts, score each response against pre-developed rating criteria that differentiate "Not Qualified," "Qualified," and "Well Qualified" applicants. When the SOQ is part of an exam, it's scored. When it's a hiring-stage screen, the 2026 statewide Hiring Guide has reviewers sort applicants into "Interview – Yes," "Maybe," and "No" rather than assign numeric scores. Either way, your SOQ typically decides whether you advance to an interview. Reviewers are looking for: relevance of examples, specificity of actions taken, and measurable outcomes.

SOQs are used at all levels of state service, from entry-level classifications like Analyst I (formerly Staff Services Analyst) up through senior and supervisory roles. Each posting specifies its own prompts and format requirements in the "Special Requirements" section on CalCareers.

Many applicants treat the SOQ like a cover letter and lose points as a result. The two documents serve fundamentally different purposes:

For the SOQ, vague enthusiasm ("I am passionate about public service") earns zero points. Specific, evidence-backed examples tied to each prompt are what move the needle.

Note that many state postings do not require a cover letter, but almost always require an SOQ if one is listed as a requirement. Submitting a cover letter instead of an SOQ is a common disqualifying mistake.

California state job postings typically specify:

• 12-point Arial font (the most common, though 12-point Times New Roman is also frequently used)
• Single-spaced text within each response
• Maximum 2 pages: the most common limit; exceeding it can result in your response not being scored
• Your name and the job control number (JC-####) at the top of each page

Always read the "Special Requirements" section of the CalCareers posting carefully. Page limits vary by department and posting, typically 1, 2, or 3 pages, and are not tied to seniority level. Some postings also require you to restate the full prompt text before each response; follow whatever the posting says.

If the posting does not specify a format, default to the above. Avoid tables and graphics. Subheadings and bullets are fine if the posting doesn't prohibit them, and they help reviewers find your answer to each prompt.

The STAR method is a widely-used and effective structure for each SOQ response (it maps directly to state HR guidance, such as the Department of General Services' SOQ tips, to be specific about "where, when, what, how, and why"):

1. Situation: 1–2 sentences setting context: where you worked, your role, and any relevant background
2. Task: what you were responsible for or the problem you were asked to solve
3. Action: the specific steps you took; this is the longest section and should be the most detailed
4. Result: what happened as a result of your actions, ideally with a measurable or observable outcome

Practical tips:

• Label your responses. Many postings require you to restate the full prompt text before your answer, so check the instructions. At minimum, number each response so reviewers can follow along.
• Use first person and active voice. "I analyzed" outscores "analysis was conducted."
• Be specific. Name the project, the tool, the stakeholder, the outcome. Generic language reads as filler.
• Match the duty statement. Re-read the duty statement and desirable qualifications before writing. The SOQ prompts are drawn from them, so your examples should reflect the same language and priorities.
• Stay within the page limit. If you need to cut, cut context (Situation) before cutting specifics (Action + Result).

Here's a full STAR-structured response to a common prompt: "Describe your experience analyzing data and preparing written reports for management decision-making."

Weak version (what most applicants write):

"In my current role, I am responsible for analyzing data and preparing reports for my supervisor. I have strong analytical skills and enjoy working with data to support decision-making. I am confident I would bring these skills to this position."

This scores poorly: no situation, no specific action, no measurable result. A reviewer can't verify or differentiate this from any other applicant's answer.

Strong version (STAR-structured):

"As a Program Technician II with the Department of Health Care Services, I was responsible for tracking provider enrollment data across a caseload of 400+ applications monthly (Situation). My unit had no standardized way to flag applications approaching their 30-day statutory deadline, resulting in a backlog of 60+ overdue cases (Task). I built a tracking spreadsheet with conditional formatting to flag applications at 20 and 25 days, and proposed a weekly report to my supervisor summarizing at-risk cases by analyst (Action). Within two months, overdue cases dropped from 60+ to under 10, and the report I designed was adopted unit-wide (Result)."

Notice what makes it score well: a named role and department (verifiable), a specific problem with a number attached, a concrete action the applicant personally took, and a measurable before/after outcome. Adapt this structure to your own prompts. Copy the shape (Situation, Task, Action, Result), not the words.

Single responses are useful, but most people searching for an SOQ example want to see the whole document: the header, restated prompts, and responses. Below is a complete illustrative SOQ for a fictional Analyst I applicant coming from the private sector. Assume the posting asks for two prompts, 12-point Arial, single-spaced, no more than two pages, and the prompt restated before each response. Your posting's rules may differ, and the posting always wins.

Maria Lopez, JC-123456

Statement of Qualifications

1. Describe your experience researching information, analyzing it, and making recommendations.

As an operations coordinator at a regional property management company, I supported a portfolio of 1,200 rental units across 14 properties. In 2024 my manager asked me to find out why maintenance requests were taking an average of 11 days to close, against a company target of 5. I pulled 18 months of work-order data from our ticketing system and sorted it by property, request type, and vendor. I also interviewed three on-site managers about how requests were assigned. The analysis showed that 40% of delays came from two vendors who were assigned by default regardless of workload. I wrote a four-page memo recommending a rotation-based vendor assignment and a 48-hour escalation rule, with a cost comparison for each option. Leadership adopted both recommendations, and average close time fell to 6 days within one quarter.

2. Describe your experience communicating with stakeholders, both orally and in writing.

In the same role, I was the main contact between residents, on-site staff, and outside vendors for about 300 requests a month. When the company switched to a new online request portal, residents filed complaints because they didn't know how to use it, and staff were answering the same questions by phone. I wrote a one-page how-to guide in plain language, had it translated into Spanish, and led two 30-minute training calls for on-site staff so they could walk residents through the portal. I also drafted standard email responses for the five most common questions. Within two months, portal-related calls to the office dropped by about half, and on-site managers began using my guide for new-resident move-ins.

What this example does right:

• The header matches the instructions. Name and job control number at the top, with the prompts numbered and restated in bold, so reviewers know exactly which answer they're scoring.
• Each prompt gets its own example. The two responses draw on the same job but describe different work, and each answers only its own prompt.
• Non-state experience is written in state terms. Words like researching, analyzing, recommending, stakeholders, and written communication mirror the language Analyst-series postings use, so the reviewer doesn't have to translate.
• Every response ends on a number. "Close time fell to 6 days" and "calls dropped by about half" give the reviewer something concrete to score.
• It fits easily. Two responses this length come in well under a two-page limit in 12-point Arial, which leaves room to add detail if your prompts ask for more.

To use this as a template, copy the structure, not the content. Start from your posting's actual prompts, restate them exactly as written, and fill each one with your own Situation, Task, Action, and Result. For classification-specific prompts and examples, see our role guides, such as the Analyst I (formerly Staff Services Analyst) SOQ guide and the Analyst II (formerly AGPA) SOQ guide.

Whether a posting requires an SOQ, and the exact prompts to respond to, is listed in the "Special Requirements" section of the job posting on CalCareers. Some postings list the prompts directly; others say "See duty statement" and link to a separate PDF. Read this section before you start writing, since it also specifies format requirements (font, spacing, page limit) that vary by posting.

The SOQ is a separate required document from the STD 678 (California's standard state job application): submitting one does not satisfy the other. When you apply through CalCareers:

1. Complete and submit your STD 678 application for the job control (JC) number.
2. Upload your SOQ as a separate attachment where the posting instructs, usually in the "Attachments" step of the CalCareers application flow, sometimes emailed directly to the hiring contact if the posting specifies that instead.
3. Double-check the posting's required application package documents list before submitting: a complete STD 678 with a missing SOQ is still an incomplete application and can be screened out.

If a posting doesn't clearly say how to submit the SOQ, contact the hiring contact listed on the posting rather than guessing.

Automatic disqualifiers:

• Exceeding the stated page limit (some postings explicitly state that content beyond the limit will not be scored)
• Submitting a cover letter or resume instead of an SOQ
• Not addressing all required prompts

Significant disqualification risks:

• Wrong font or font size: most postings use the language "may be disqualified," so this is not always automatic, but treat it as one. Match the spec exactly.

Scoring killers:

• Vague language: "I worked with a team to improve processes" gives reviewers nothing to score
• Missing results: describing what you did without saying what happened
• One example for all prompts: each prompt needs a distinct, relevant example
• No separation between prompt responses: reviewers should not have to guess where one response ends and the next begins
• Using "we" throughout: reviewers are scoring your individual contribution, not your team's
• Padding: repeating yourself or adding generic closing statements wastes your limited page count. Note: many postings require you to restate the full prompt before your response. That is following instructions, not padding.