PASC
More study resources
Cheat sheet
Keep the key ideas within reach.
ExploreKey terms
Get comfortable with the vocabulary.
ExploreStudy plan
Give each week a clear focus.
ExploreCommon mistakes
Understand the traps and how to avoid them.
ExploreCase studies
Put your knowledge to work in context.
ExploreExam-day guide
Prepare for the day ahead.
ExploreAbout this exam
The Professional Assessment of Software Competency (PASC) is an independent, multiple-choice examination intended to gauge whether a practitioner has the working knowledge expected of a mid-level software engineer across the full delivery lifecycle. It suits developers, testers, analysts, and technical leads who want an external check on breadth rather than a certificate in one language or framework. The exam is organized into eight domains: requirements and analysis, design and architecture, construction and implementation, testing and quality assurance, configuration and release management, project management and process, maintenance and evolution, and professional ethics. Weighting leans toward design and construction, with testing and requirements close behind, so a candidate who only knows how to write code will find gaps. Preparation is best done by working through each domain against your own project history: read a standard software engineering text, then map every concept to something you have actually built, reviewed, or debugged. Practice explaining trade-offs out loud, since multiple-choice options often differ only in nuance. This page is an independent study resource and is not affiliated with, endorsed by, or operated by the exam's governing body; always confirm current administrative details at the official source before you register.
What you'll study
About PASC preparation
What is the PASC exam format?
It is a multiple-choice assessment covering eight software engineering domains in a single sitting. Expect scenario-style items that ask you to pick the best or most appropriate action rather than recall a definition. Confirm the current delivery method, whether test-center or remote-proctored, on the official body's website, as arrangements can change between windows.
How many questions are there and how long do I get?
The official body publishes the current question count and time limit for each exam window; check its site for the authoritative figures rather than relying on secondhand reports. As a planning habit, assume roughly a minute to ninety seconds per item so you can practice pacing under realistic conditions.
What score do I need to pass, and what does it cost?
Passing scores, fees, and any regional pricing are set and published by the official body, and they are not reproduced here because they change. Visit the official site or your registration portal for current numbers. Budget separately for any rescheduling or retake charges, which are usually governed by a distinct policy.
How hard is the exam?
Difficulty comes from breadth, not trickery. Most candidates find the design, architecture, and testing domains hardest because the options are all defensible and you must choose the most appropriate one. If you have two or more years of hands-on delivery experience and can reason about trade-offs, the material is learnable in a focused study period.
Can I retake it if I fail, and how soon?
Retake eligibility and any waiting period are set by the official body, so confirm the current policy before you sit the exam. Practically, treat a first attempt as diagnostic: note which domains you missed, study those specifically, and avoid simply rereading material you already know, which is the most common wasted effort.
In what order should I study the domains?
Follow the lifecycle: requirements, then design, construction, testing, configuration and release, project process, maintenance, and ethics. That order builds dependencies naturally. Weight your time by domain weight, but do not skip ethics or maintenance, which are small, self-contained, and easy points that candidates routinely neglect.
What are the most common failure modes?
Three recur: memorizing terminology without being able to apply it to a scenario, over-studying construction because it feels familiar, and ignoring the process and ethics domains entirely. Another frequent error is choosing the theoretically purest answer instead of the most appropriate one given stated constraints such as budget, legacy code, or team size.
How should I prepare in the final week?
Stop reading new material. Take timed practice sets, review every wrong answer to understand why the correct option was better, and rehearse explaining key trade-offs aloud. Revisit your weakest two domains only. Sleep and logistics matter more than one more chapter at that point.
Is this page official?
No. This is an independent study resource and is not affiliated with or endorsed by the exam's governing body. Domain names and weights shown here are provisional and unverified. Always treat the official website as the single source of truth for eligibility, scheduling, fees, and scoring.