More study resources

About this exam

The ACM Software Engineering Certification (ACM-SW) is a multiple-choice credential intended for practitioners who want independent evidence that they can apply software engineering fundamentals across the full delivery lifecycle, not just write code in one language. It suits working developers moving toward senior or lead roles, testers and analysts broadening into engineering, and graduates who want a structured target for their study. The published content outline, which candidates should treat as provisional until confirmed against the official body's materials, spans eight areas: requirements, design, construction, testing, maintenance and evolution, configuration and project management, process and quality, and professional practice and ethics. Design and construction together carry the largest share, so expect a strong emphasis on architecture, modularity, abstraction, and code-level judgment rather than trivia. Preparation works best in two passes: first read a general software engineering text end to end to rebuild vocabulary and mental models, then work through scenario-style questions that ask you to choose the best trade-off rather than recall a definition. Track your weak domains by percentage, not by gut feel. This page is an independent study resource and is not affiliated with or endorsed by the certifying organization; always confirm current administrative details on the official site before you register.

What you'll study

Common questions

About ACM-SW preparation

What is the exam format?

Questions are multiple choice, one best answer each, covering the eight published domains. The exam is delivered as a timed sitting, but the current length, item count, and delivery method are set by the certifying body and change over time, so check the official site rather than relying on secondhand figures.

How long is the exam and how many questions are there?

Those numbers are published by the official certification body and are updated periodically. Look them up on the certifying organization's own site immediately before you schedule, since third-party study guides and forum posts are frequently out of date on both counts.

How hard is it, really?

The difficulty comes from judgment, not memorization. Most items describe a situation and ask which approach is best, so candidates who know definitions but have never weighed trade-offs tend to lose points. If you have shipped and maintained real systems, the scenarios will feel familiar; if not, practice explaining why one design beats another.

What does it cost and what is the passing score?

Fees and the passing threshold are administrative details controlled by the certifying body and are revised from time to time. Neither is fixed here. Consult the official site for the current fee schedule, the passing score, and any regional pricing or member discounts that may apply.

Can I retake it if I fail, and how soon?

Retake rules, waiting periods, and any additional fees are set by the certifying organization and are not standardized across its programs. Check the official policy page before you book, and factor a possible retake into your schedule so a single bad sitting does not derail your timeline.

How long is the certification valid?

Validity periods and renewal or recertification requirements are determined by the certifying body and can differ between its credentials. Confirm the current policy on the official site, and note whether renewal requires continuing education units, a fee, or a repeat examination.

In what order should I study the domains?

Start with requirements and design, because construction, testing, and maintenance questions all assume you can reason about specifications and structure. Then take construction and testing together, since they share vocabulary. Finish with process, management, and ethics, which are lighter on technique and reward careful reading more than deep study.

What are the most common ways candidates fail?

Three recurring mistakes: studying only definitions and freezing on scenario questions; neglecting the lower-weighted domains such as ethics and configuration management, where easy points are lost; and misreading stems that ask for the best answer rather than a correct one, when several options are technically true.

Do I need professional experience to pass?

No formal prerequisite is assumed here, but the scenario items reward people who have debugged a failing release, negotiated a requirement change, or argued about a design in review. Without that context, substitute deliberate practice: read case studies and justify your chosen answer in writing before checking it.

Is this page an official study guide?

No. This is independent material prepared for study purposes and is not affiliated with, endorsed by, or sponsored by the certifying organization. Domain names and weights shown here are unverified and may not match the current official outline, so treat the certifying body's published outline as authoritative.