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 — usually 2–4 — that map directly to the duties listed in the job's classification specification.

Unlike a resume or cover letter, the SOQ is a scored exam. Hiring panels use a structured rubric to evaluate each response. Your score determines whether you advance to an interview. Panels are often 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 default)
• Single-spaced text within each response
• One blank line between prompt responses
• Maximum 2 pages — violations can disqualify you automatically
• Your name and the position title at the top

Always read the "Special Requirements" section of the CalCareers posting carefully. Some agencies specify different fonts (Times New Roman is occasionally requested), different page limits (1 page for entry-level, up to 3 for senior roles), or require you to restate each prompt before answering it.

If the posting does not specify a format, default to the above. Do not use headers, tables, or graphics unless the instructions allow it — keep the document clean and easy to score.

The STAR method is the most effective structure for each SOQ response:

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. Before each answer, write the prompt number or a shortened version of the prompt text. Raters need to be able to 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 classification spec or duty statement before writing. The SOQ prompts are pulled from it — 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
• Submitting a cover letter or resume instead of an SOQ
• Wrong font or font size
• Not addressing all required prompts

Scoring killers:

• Vague language — "I worked with a team to improve processes" gives raters 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 — raters should not have to guess where one response ends and the next begins
• Using "we" throughout — raters are scoring your individual contribution, not your team's
• Padding — restating the prompt at length, repeating yourself, or adding generic closing statements wastes your limited page count