How to Write an SOQ for an Office Technician Position

A Statement of Qualifications (SOQ) is a written exam required by many California state job postings. For Office Technician positions, it typically consists of 2–3 prompts that map to the core duties of the role: managing high-volume administrative tasks, working independently, and interacting with the public or internal stakeholders.

Unlike a cover letter, the SOQ is scored by a panel. Evaluators use a rubric to assess how well your examples demonstrate the competencies the position requires. Vague statements like "I am organized and reliable" earn no points — specific examples with context, actions, and outcomes do.

The Office Technician classification is one of the most frequently posted in California state government, which means competition is high. A strong SOQ is often the deciding factor between equally qualified applicants.

Most Office Technician postings specify:

• 12-point Arial font (the CalHR standard)
• Single-spaced text within each response
• Maximum 1–2 pages — read the posting carefully; some agencies allow 2 pages, others only 1
• 1-inch margins on all sides
• Your name and position title at the top of page 1

Always re-read the "Special Requirements" section of the specific CalCareers posting. The page limit and font requirements are set by the department, not CalHR, and they vary. Exceeding the page limit is grounds for automatic disqualification at many agencies.

Label each response with the prompt number before your answer. Evaluators review multiple applications and need to be able to match your answer to the correct rubric item instantly.

Use the STAR method for each response:

1. Situation — where you worked, your role, and the volume or complexity involved (e.g., "At the [Employer], I processed approximately 150 customer transactions daily in a 6-person team...")
2. Task — what you were specifically responsible for
3. Action — what you did, in detail: tools used, procedures followed, decisions made
4. Result — what the outcome was, ideally with a number or observable change

For multi-tasking prompts: Be specific about the volume. "I managed a high volume of tasks" is vague. "I processed 80–100 data entry records daily while responding to 30–40 phone inquiries and coordinating mail processing for a team of 10" gives evaluators something to score.

For independent work prompts: Describe the absence of supervision explicitly. "My supervisor was available only two days a week, so I independently managed the daily mail distribution, document routing, and public counter for the other three days" is far stronger than "I can work independently."

For customer service prompts: Pick a challenging interaction. Describe the conflict or difficulty (the other person's concern or frustration), what you said or did to resolve it, and what happened next. A resolved complaint or a compliment are strong results; a calm de-escalation also works.

Avoid using "we" throughout your answer. Evaluators are scoring your individual contribution — not your team's.

Parroting your resume — writing a narrative version of your employment history instead of answering the prompt with a specific example. The prompt asks for a situation — give them one.

Vague metrics — "high volume," "many tasks," "various duties." Replace these with numbers whenever possible: number of records, calls, transactions, or days.

Exceeding the page limit — the most common disqualifier. If you're running long, cut from the Situation section first. Evaluators care most about Action and Result.

One example for multiple prompts — each prompt needs a distinct, relevant example from a different situation or role if possible. Reusing the same example for two prompts signals limited depth of experience.

Not labeling prompt responses — if you write continuously without marking which paragraph answers which prompt, evaluators may not be able to score your responses correctly.

Typos and informal language — the SOQ is a writing sample. Grammar, spelling, and professional tone are evaluated alongside content.