How to Write an SOQ for an Accounting Technician Position

Accounting Technician is a paraprofessional fiscal classification — the level that keeps a state accounting office running: processing invoices and payments, maintaining fiscal records, reconciling straightforward accounts, and preparing documents for professional accountants to review. The SOQ prompts test whether you've done that work reliably at volume.

Raters score responses against a rubric covering transaction accuracy, volume handling, error detection, and basic accounting knowledge (debits and credits, document flow, why a transaction posts where it does). You don't need a degree in accounting — you need concrete evidence you process fiscal work fast and correctly.

Postings for this classification carry working titles like "Accounts Payable Technician," "Payroll Assistant," or "Fiscal Assistant." The classification on the CalCareers posting is what matters — it sets the exam, the pay range, and the competencies your SOQ is measured against.

Typical requirements for Accounting Technician postings:

• 11- or 12-point Arial font — check each posting; both appear frequently
• Single-spaced responses
• 1–2 page maximum, set by the department
• 1-inch margins
• Name and JC number at the top of each page

These rules come from the department, not CalHR, so they change from posting to posting. Treat the SOQ instructions like a fiscal procedure: follow them exactly. An SOQ that ignores the page limit or font requirement can be screened out before anyone reads it — and for a classification built on document accuracy, that's an easy call for the screener.

Label each answer with its prompt number, in the order listed in the posting.

Build each response with the STAR method — Situation, Task, Action, Result — and make volume and accuracy the recurring theme.

For fiscal support experience prompts: Lead with scale and systems. "I processed 120–150 vendor invoices weekly in QuickBooks, verified them against purchase orders and receiving documents, and prepared payment batches totaling roughly $400K per month" gives the rater everything the rubric asks for. If you have state experience, name FI$Cal or the departmental system; if not, name whatever you used — the point is that you can show a real system, real volume, and a real verification step.

For accuracy and error-review prompts: Describe your checking procedure as a procedure. What did you compare against what (invoice vs. PO vs. receiver)? What errors did you commonly catch — duplicate invoices, wrong coding, math errors, missing approvals? What did you do when you found one? A specific save ("I caught a duplicate $18,000 invoice before payment issued") is a strong result.

For deadline prompts: Fiscal work runs on hard calendars — payment deadlines, payroll cutoffs, month-end and year-end close. Describe a real crunch (fiscal year-end is the classic), how you sequenced and batched the work, and the result: everything processed by the cutoff, with accuracy maintained. Naming the deadline pressure honestly and showing your method beats claiming you "work well under pressure."

Use "I," not "we" — raters score your individual contribution.

No volume numbers — this is the single most common gap. "Processed invoices" could mean 5 a week or 500. Count your real workload and state it.

Listing duties instead of telling a story — the prompts ask for experience and examples, not a resume paragraph. Pick one situation per prompt and go deep.

Skipping the verification step — describing what you processed without describing how you checked it. Error detection is a core rubric item for this classification.

Math or typo errors in the SOQ itself — an accuracy-focused role means your SOQ is read as an accuracy sample. Proofread it twice, and double-check any numbers you cite.

Underselling non-accounting experience — retail cash handling, bookkeeping for a small business, or processing claims all demonstrate the same competencies. Frame them in fiscal terms rather than leaving them out.