How to Write a Statement of Qualifications (SOQ)

A Statement of Qualifications (SOQ) 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 Staff Services Analyst (SSA) 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, but subheadings and bullets are fine — CalHR's own guidance recommends them for readability.

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"):

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 — 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 — 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).

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 not padding, it is following instructions.