What Is an SOQ? Job Applications and Procurement

An SOQ, or Statement of Qualifications, is a written document that demonstrates your relevant experience and skills in response to specific questions or criteria. SOQs show up in two main contexts: government job applications, where they function as a scored part of the hiring process, and professional services procurement, where businesses submit them to compete for contracts. If you’ve encountered the term on a job posting or a request for proposals, here’s what you need to know.

SOQs in Government Job Applications

Many government agencies require applicants to submit a Statement of Qualifications alongside their resume and standard application materials. Unlike a resume, which lists your job history and credentials in a structured format, an SOQ asks you to write narrative responses to specific questions about your experience. A job posting might ask something like, “Describe your experience managing a team of five or more employees,” and you’d respond with a few paragraphs detailing exactly how your background fits.

The SOQ serves multiple purposes at once. It lets reviewers evaluate whether you meet the desirable qualifications for the role, it acts as a writing sample that shows your communication skills, and it functions as a kind of written interview. Hiring panels often score SOQ responses as part of the application screening process, meaning a weak or missing SOQ can knock you out of the running before anyone looks at your resume.

Each job posting sets its own SOQ instructions, including the questions you need to answer, any page limits, font requirements, and formatting rules. There is no universal template. The California Department of Human Resources, for example, leaves all of those specifics up to individual hiring managers. What is universal: you must follow every instruction exactly. Failing to provide an SOQ when one is requested, exceeding the page limit, or skipping a question can result in disqualification from the entire hiring process.

How to Write a Strong SOQ for a Job

The most important rule is to answer the questions that are actually asked. Read each prompt carefully and structure your response around it. If the posting lists three desirable qualifications, address all three, ideally in the same order they appear.

Resist the urge to restate what’s already on your resume. Reviewers will have your resume separately. The SOQ is your chance to go deeper, to explain the context behind your experience, describe specific projects you led, quantify results, and connect your background directly to what the role requires. Think of it as making a case for yourself rather than listing bullet points.

A few practical tips that improve your chances:

  • Mirror the language of the posting. If the job description says “program evaluation,” use that exact phrase when describing your experience. SOQs are often scored against a rubric tied to the posted qualifications, so clear alignment matters.
  • Be specific. Instead of “I have experience with budgets,” write “I managed a $2.4 million annual operating budget and identified $180,000 in cost savings over two fiscal years.”
  • Stick to the format. If the posting says two pages, single-spaced, 12-point Arial, follow that precisely. Formatting compliance signals attention to detail, and non-compliance can disqualify you outright.
  • Proofread carefully. Because the SOQ doubles as a writing sample, grammar mistakes and unclear sentences count against you.

SOQs in Business Procurement

In the business world, an SOQ works differently. When a government agency or large organization needs professional services (engineering, architecture, consulting, construction management), it often issues a Request for Qualifications, or RFQ. Firms respond by submitting a Statement of Qualifications that showcases their experience, team credentials, and past project performance.

This process is rooted in what’s known as qualifications-based selection. Under the Brooks Act, a federal law that many state and local agencies follow, architecture and engineering contracts must be awarded based on qualifications rather than price. Firms submit their SOQs, a selection committee evaluates and ranks them, and only after a firm is chosen does cost negotiation begin. That means your SOQ cannot include pricing data, work-hour estimates, or fee proposals.

A typical business SOQ includes the firm’s relevant project history, key personnel and their credentials, organizational capacity, and any specialized expertise. Prime firms (the lead contractor) sometimes supplement their SOQs with subconsultants who bring niche skills. In many cases, the prime firm is required to perform at least 51 percent of the contract value itself, so the balance between in-house capability and subcontracted work matters. Some solicitations also set goals for including disadvantaged business enterprises (DBEs), and proposers must either meet those goals or demonstrate good-faith efforts to do so.

Key Differences Between Job and Business SOQs

While the name is the same, the two types of SOQs differ in audience, format, and stakes. A job SOQ is written by an individual applicant and typically runs one to three pages. A business SOQ is written by a firm, can be dozens of pages long, and often includes resumes of key staff, project sheets, organizational charts, and references. Job SOQs are scored during the hiring screening. Business SOQs are evaluated by selection committees that rank competing firms.

The core principle, however, is identical in both settings. An SOQ is your opportunity to prove, with concrete evidence, that you’re the right fit for a specific role or project. Generic responses that could apply to any position or any contract rarely score well. The strongest SOQs are tailored precisely to what the requester asked for, backed by specific examples, and written clearly enough that a reviewer can find what they need without hunting for it.