TL;DR
An SOQ is a scored written exam, not a cover letter. This guide covers what evaluators look for, how to format your response, and how to write examples that score in the top tier. If you'd rather start from a draft than a blank page, dandy writes a first-pass SOQ from your experience and the job's prompts, free.
What is an SOQ (Statement of Qualifications)?
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. Your score typically determines 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.
SOQ vs. cover letter: key differences
Many applicants treat the SOQ like a cover letter and lose points as a result. The two documents serve fundamentally different purposes:
| SOQ | Cover Letter | |
|---|---|---|
| Purpose | Scored exam | Expression of interest |
| Audience | Hiring manager or panel using rating criteria | Hiring manager |
| Format | Prescribed (font, page limit) | Flexible |
| Content | Specific examples tied to prompts | General interest + fit |
| Weight | Often determines interview eligibility | Supplemental |
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.
Formatting your SOQ
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, but subheadings and bullets are fine: CalHR's own guidance recommends them for readability.
How to write strong SOQ responses
The STAR method is a widely-used and effective structure for each SOQ response (it maps directly to CalHR's own guidance to address "where, when, what, how, and why"):
- Situation: 1–2 sentences setting context: where you worked, your role, and any relevant background
- Task: what you were responsible for or the problem you were asked to solve
- Action: the specific steps you took; this is the longest section and should be the most detailed
- 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).
SOQ examples: what a strong response looks like
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.
Get a draft written like the strong example, from your experience. dandy drafts a STAR-structured response to each of the job's prompts, so you're editing, not staring at a blank page.
Finding and submitting your SOQ on CalCareers
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:
- Complete and submit your STD 678 application for the job control (JC) number.
- 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.
- 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.
Mistakes that get SOQs disqualified or scored low
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.
Most of these mistakes come from writing without a structure. dandy drafts every prompt in STAR form, matched to the job's rating criteria, so the vague-answer problem is handled before you start editing.
Frequently asked questions
What does SOQ stand for?
Where do I find the SOQ prompts for a job?
What if the posting doesn't list SOQ prompts, just says "SOQ required"?
How long should each SOQ response be?
Can I use the same SOQ for multiple job postings?
What experience counts if I've never worked for the state?
Related guides
Now write yours — starting from a draft, not a blank page
dandy takes the job's SOQ prompts and your experience and writes a STAR-structured first draft for each one. You edit and submit; it does the staring-at-the-cursor part.