How to Write an SOQ for an Information Technology Technician Position

California state IT jobs are posted under a working title — Service Desk Technician, Help Desk Analyst, Desktop Support Technician — but the civil service classification underneath is usually Information Technology Technician (or Information Technology Associate for more advanced roles). The classification, not the working title, determines the exam you take, the salary range, and the minimum qualifications.

IT Technician is the entry level of the state's IT classification series, which runs from IT Technician up through IT Associate, IT Specialist I–III, and IT Supervisor and Manager levels. Positions are assigned to one or more domains; service desk and desktop support work falls under the Client Services domain, which is the most common domain for IT Technician postings.

This matters for your SOQ: the prompts are written around the classification's core competencies — technical troubleshooting, customer service, and documentation — so your responses should demonstrate those even if your job title never included the word "technician."

Most IT Technician postings specify:

• 12-point Arial font — check the posting; some specify 11-point
• Single-spaced text
• Maximum 1–2 pages — strictly enforced
• 1-inch margins
• Your name and Job Control (JC) number at the top of each page

The format rules live in the "Special Requirements" or "Statement of Qualifications" section of the CalCareers posting, and they vary by department. Follow them exactly — HR analysts screen out non-compliant SOQs before evaluators ever read them.

Number each response to match the posting's prompts, in the same order. If the posting asks you to address specific duty statement items rather than numbered questions, use short headings that mirror the posting's language.

Structure each response with the STAR method (Situation, Task, Action, Result), and be concrete about three things evaluators consistently score:

Name your stack. "Provided technical support" earns little; "supported ~400 users on Windows 11 and Office 365, handled password resets and account provisioning in Active Directory, imaged laptops with SCCM, and managed tickets in ServiceNow" earns points. List the operating systems, ticketing systems, remote-support tools, and hardware you've actually worked with — the evaluator is checking your experience against the position's technical requirements.

Quantify your support volume. Tickets per day or week, users supported, first-call resolution rate, average resolution time — any honest number gives the evaluator something to score. If you worked to a service-level agreement, say what it was and whether you met it.

Show the human side. At the IT Technician level, customer communication is weighted as heavily as technical skill. Pick an example involving a frustrated or non-technical user: describe how you listened, how you explained the problem without jargon, and how the interaction ended. De-escalating an upset user and walking a novice through a fix step-by-step are exactly the behaviors the rubric rewards.

Handle the escalation question honestly. Prompts often ask about issues you could not resolve. The right answer isn't "I resolve everything" — it's showing good judgment: what you tried first, how you documented your troubleshooting steps in the ticket, and how you handed it off so the next tier didn't start from scratch.

Help desk experience from any sector counts — private companies, universities, the military, managed service providers, even structured volunteer IT support. Home-lab and coursework experience is worth mentioning for a first IT job, but lead with any experience supporting real users.

Listing certifications instead of experience — CompTIA A+ or Network+ belong on your application and resume; the SOQ needs examples of you doing the work. A certification supports an example ("applying the troubleshooting methodology from my A+ training, I...") but doesn't replace one.

Jargon without context — dropping tool names with no indication of what you did with them. "Used ServiceNow" says less than "logged, prioritized, and resolved 25–35 ServiceNow tickets daily, escalating network issues to Tier 2 with full troubleshooting notes."

Ignoring the customer service prompt — technical candidates often write one strong troubleshooting answer and a thin communication answer. Both are scored. Give the customer service example the same STAR structure and detail.

Team credit — "our team supported 2,000 users" hides your contribution. Write in the first person: your tickets, your resolutions, your users.

Exceeding the page limit or wrong font — instant screening failures that have nothing to do with your qualifications.

Skipping the SOQ because you attached a resume — for state IT jobs, the SOQ is a scored exam component. "See resume" responses are typically disqualified.