How to Write an SOQ for an Information Technology Associate Position

The Information Technology Associate is an associate-level IT classification (one rung above the IT Technician) used across most California state agencies. Because applicants range from recent graduates to career-changers, the SOQ is designed to surface actual technical exposure — not just enthusiasm for the field.

Most ITA postings require an SOQ as a vacancy-specific supplemental document. It is not the same as the statewide ITA classification examination on CalCareers — that exam is a multiple-choice test (or, in some bulletins, a Training and Experience evaluation) you take once to land on the 12-month eligible list. The SOQ is separate, set by the hiring department, and used as a written-interview-style screening for that particular vacancy.

Most ITA SOQs have two to four prompts covering:

1. Technical background — your education, training, and hands-on experience with specific technologies
2. Troubleshooting or problem-solving — a specific situation where you diagnosed and resolved a technical issue
3. User support or stakeholder communication — working with non-technical people to deliver or explain technology

Under CalHR's consolidated IT series, ITA work is limited to three of the six official IT domains: Business Technology Management, Client Services, and Software Engineering (the more advanced ITS I covers all six). Some ITA postings explicitly tie the vacancy to one of these domains; others stay general. Either way, the same principle applies: generic responses score lower than specific ones. Per CalHR's SOQ guidance, panels rate responses against criteria designed to distinguish Not Qualified, Qualified, and Well Qualified — and naming the actual technologies, systems, and tools you've used, with real outcomes, is what moves a response into the Well Qualified band.

There is no single statewide SOQ format for ITA — every posting sets its own limits in the Special Requirements section of the CalCareers ad. Patterns you'll often see:

• 12-point Arial font (or as specified in the posting)
• Single-spaced within each response
• 1-inch margins on all sides
• Page limit — most ITA postings cap the SOQ at two pages, but some allow only one and a few accept up to three
• Your name and the Job Control number in a header (some agencies also ask for the title "Statement of Qualifications")
• Responses numbered to correspond to each prompt

Always re-read the "Special Requirements" section before formatting. Departments deviate in real ways — some require the prompt to be restated before your response, some specify a smaller font or tighter margins (e.g., 10-point font or 0.5-inch margins).

Whatever page limit the posting allows is a hard cap — exceeding it can result in disqualification. If you're going over, cut summary language first — phrases like "I have always been passionate about technology" and "I believe I would be a great fit" waste space that could be used for specific examples.

Technical background prompt:

This is not a request for your resume. It's asking you to demonstrate technical depth and breadth. Structure it as a narrative covering:

• Specific technologies and tools — operating systems, programming languages, applications, hardware, cloud platforms (be precise: "Windows Server 2019, Active Directory, Group Policy" rather than "Windows and networking")
• Context for each technology — where you used it, at what scale, and what you accomplished
• Education and certifications — mention these briefly, but lead with hands-on experience

A strong opening: "Over three years of helpdesk and sysadmin support work, I've administered Windows 10/11 and macOS endpoints across a 200-user environment, managed Active Directory and Group Policy configurations, and supported Microsoft 365 for 150 staff — including mailbox migrations, SharePoint permissioning, and Intune device enrollment."

Troubleshooting prompt:

Use the STAR method:

1. Situation — what was the system, who was affected, what was the stakes (production system, number of users impacted, time-sensitivity)
2. Task — your specific responsibility for resolving it
3. Action — the diagnostic steps you actually took: what you checked, what you ruled out, what tools you used (event logs, network analyzers, ticketing systems)
4. Result — the resolution, how long it took, what you did to prevent recurrence

Don't describe a vague "difficult problem." Describe a specific incident: a VPN authentication failure affecting remote workers, a corrupted user profile that crashed Outlook on startup, a misconfigured DNS record that broke a web application.

User support / communication prompt:

Focus on a situation where you explained a technical issue or solution to someone without a technical background. What was the gap between their understanding and the technical reality? How did you bridge it — did you use analogies, walk them through step-by-step, create documentation? What was the outcome? Reviewers want to see that you can translate technology into language that enables decision-making.

Listing tools without context — "I know Python, Java, SQL, and JavaScript" is a keyword list, not evidence of skill. Every technology you name should appear within a project or task context.

Using "we" instead of "I" — SOQ raters score your individual contribution. "Our team built a new ticketing system" tells them nothing about what you did. Say "I configured," "I led," "I documented."

Writing a prose version of your resume — the background prompt is not asking for your job history. Lead with capabilities and supporting examples, not employers and dates.

Generic troubleshooting stories — "I troubleshot many issues over the years and helped many users" is unscorable. Name a specific incident, tool, and resolution.

Exceeding the page limit — automatic disqualification at many agencies. Set your margins, set your font, write your draft, then edit it down to fit.

Not labeling responses — if there are three prompts, label your responses 1, 2, and 3 so reviewers can score each one without hunting for where the answer starts.