iSQI Certifications in 2026: Software Quality, Testing, Agile, and A4Q Paths

iSQI is best understood as an examination and certification provider for a wide collection of professional schemes rather than as the owner of one narrow certification ladder. Its catalog spans software testing and quality engineering, agile practices, requirements engineering and business analysis, software architecture, development, usability and accessibility, product and service design, and several artificial-intelligence-focused qualifications. That breadth makes the first planning question less about “which iSQI level comes next” and more about which certification body and subject area match the candidate's work.

iSQI certifications include exams developed under schemes such as ISTQB, A4Q, TMAP, IREB, and other specialist programs. iSQI then supplies the examination infrastructure, candidate administration, certificates, and multiple delivery options. Candidates should therefore distinguish the scheme owner, the syllabus, and iSQI's role as the exam provider when they research prerequisites or progression rules.

iSQI operates across several independent certification schemes

A candidate browsing iSQI in 2026 will encounter qualifications that come from different professional ecosystems. ISTQB provides internationally standardized software-testing syllabi. A4Q develops qualifications in areas such as Selenium, practical testing, software development engineering in test, artificial intelligence, digital accessibility, business analysis, and service design. TMAP focuses on quality engineering in modern delivery organizations. IREB addresses requirements engineering, while software-architecture programs serve professionals designing and evaluating complex systems.

This matters because credentials from different schemes do not necessarily form a single prerequisite chain. A person can use iSQI for an ISTQB exam and later use the same provider for an A4Q or TMAP qualification without those programs becoming one certification family. The rules of the individual scheme remain authoritative.

For planning, candidates should start with a role problem: Do they need a recognized software-testing foundation, automation skills, quality engineering for DevOps teams, requirements engineering, architecture, accessibility, or an AI-focused credential? Once the role is clear, the relevant syllabus and exam become much easier to identify.

ISTQB remains a major software-testing route available through iSQI

iSQI offers a substantial set of ISTQB examinations, including Foundation Level, Agile Tester, Advanced Level specializations, test automation, and newer specialist modules. ISTQB certifications have their own progression and prerequisite rules, so candidates should use ISTQB's current scheme documentation when deciding which advanced or specialist module they are eligible to attempt.

For many testers, the natural starting point is Certified Tester Foundation Level. The current CTFL v4.0 exam covers core testing principles, testing across the software-development lifecycle, static testing, test analysis and design, managing test activities, and tool support. Foundation knowledge is intentionally broad because later specialist and advanced qualifications assume that candidates can already reason about basic test processes and terminology.

iSQI also provides access to ISTQB exams through Pearson VUE and other supported delivery methods. That means a learner can separate syllabus preparation from exam logistics: study from the current ISTQB materials, then use iSQI's voucher and scheduling process for the examination.

A4Q expands the catalog beyond conventional testing credentials

A4Q programs give iSQI candidates options that are more focused on tools, emerging practices, and adjacent professional capabilities. Current offerings include Selenium 4 Tester Foundation, Software Development Engineer in Test, AI Essentials, AI compliance, security fundamentals, business analysis, digital accessibility, and practical-testing add-ons. This makes A4Q useful when a candidate's job requires a more specific capability than a broad foundation syllabus can provide.

For example, a tester working heavily with browser automation may find Selenium-specific study more immediately applicable than another general testing module. A developer moving into quality engineering may prefer an SDET-oriented syllabus. Teams affected by European accessibility requirements may use the A4Q digital-accessibility qualification to structure knowledge around WCAG, EN 301 549, and the European Accessibility Act.

The important practical distinction is that these qualifications are not interchangeable simply because iSQI sells all of them. A certification should be selected because the underlying syllabus validates skills the candidate expects to use, not because it appears next to another exam in the same storefront.

TMAP treats quality as a responsibility of modern delivery teams

TMAP qualifications are especially relevant to organizations using agile, DevOps, continuous delivery, and cross-functional product teams. TMAP Quality for cross-functional teams is the entry point and covers the whole-team approach, quality engineering, review practices, automation, CI/CD, metrics, reporting, continuous improvement, and the relationship between quality and business value.

iSQI currently lists TMAP Quality for cross-functional teams, High-performance quality engineering, Organizing built-in quality at scale, and Quality Engineering for SAP. The first module is recommended as the basis for the others. That structure allows an individual contributor to learn shared quality practices before moving toward specialist engineering or organization-scale quality concerns.

TMAP is a useful example of why modern testing certification is broader than test-case execution. Quality engineers increasingly work with pipelines, observability, code review, automation, risk analysis, team feedback loops, and production signals. The curriculum reflects that shift by placing testing inside a delivery system rather than treating it as a final isolated phase.

Requirements, architecture, and development paths broaden iSQI's relevance

Testing failures often originate before execution begins: ambiguous requirements, poor architectural decisions, weak acceptance criteria, or software that was difficult to test by design. iSQI's requirements-engineering and software-architecture offerings address those upstream concerns. IREB's CPRE programs provide structured requirements knowledge, while architecture qualifications help practitioners reason about design decisions, quality attributes, tradeoffs, and communication.

For developers, iSQI also offers exams such as A4Q SDET and secure-software-engineering qualifications. These can make sense for engineers who write production code but also own automation, security, or quality responsibilities. A developer does not need to change job title to benefit from testing knowledge when the team uses shared ownership of quality.

This is where cross-scheme planning can be powerful. Someone may combine a broad testing foundation with requirements engineering, automation, or architecture because their actual role crosses those boundaries. The goal is a coherent skills profile, not a large collection of unrelated certificates.

Exam delivery is flexible but candidates must follow the correct booking route

iSQI currently supports several examination models. Pearson VUE test-center exams are available for many certifications, and numerous vouchers can also be used with Pearson OnVUE remote proctoring where offered. iSQI also operates FLEX remote-proctored exams through its own supported booking workflow, and organizations can arrange onsite examination options.

The booking process depends on the selected exam. For Pearson delivery, candidates generally purchase an iSQI voucher, receive instructions, create or use a Pearson account, and schedule at a test center or through the eligible online option. FLEX exams use a different remote-proctor booking route. Candidates who require time extensions or accommodations should complete that process before they make an incompatible booking.

Results can be available quickly, but identity requirements, technical checks, cancellation rules, voucher validity, and the specific exam's delivery options still need to be verified before test day. An otherwise well-prepared candidate can create unnecessary risk by treating logistics as an afterthought.

Preparation should start with the syllabus rather than a generic question bank

Because iSQI administers many independent schemes, there is no universal “iSQI exam technique.” Each exam has its own learning objectives, question count, pass standard, duration, and cognitive expectations. TMAP Quality for cross-functional teams, for example, uses a defined syllabus and a 66 percent passing threshold, while an ISTQB advanced exam may emphasize a very different mix of knowledge and applied analysis.

A good study plan begins by downloading or reviewing the current syllabus and sample examination for the exact version being taken. Candidates should map topics into three groups: concepts they can explain, concepts they can apply to a scenario, and concepts that remain weak. Practice questions should then test those gaps rather than replace the syllabus.

For ISTQB candidates in particular, understanding the certification process and current scheme structure is useful before choosing later modules. The ISTQB certification process discussion can provide additional context, but the current official syllabus remains the controlling source for what is examinable.

Choose certifications that match the team's delivery model

A traditional test analyst, an SDET, a product-quality engineer, a requirements specialist, and an accessibility practitioner can all find relevant examinations through iSQI, but their optimal paths will look very different. A tester in a regulated environment may need strong process and analysis credentials. A DevOps-oriented team may benefit more from TMAP quality engineering and automation. A product organization facing accessibility obligations may prioritize the digital-accessibility track.

Candidates should also consider how the employer actually organizes quality. If testers are embedded in cross-functional teams, certifications centered on collaboration, automation, and continuous feedback may produce more practical value than a narrow manual-testing specialization. If testing remains a separate assurance function, deeper test analysis and management modules may be more appropriate.

That role alignment is more durable than choosing an exam because it is popular. A certificate becomes useful when its concepts improve the decisions a professional makes during requirements, design, coding, testing, release, or operations.

iSQI is most valuable as a gateway to well-defined specialist schemes

The main strength of iSQI's 2026 catalog is choice. Candidates can access globally recognized testing credentials, quality-engineering programs, requirements and architecture certifications, automation qualifications, and newer AI and accessibility options through a common examination provider. The challenge is avoiding an unfocused path across too many unrelated schemes.

A disciplined approach is to identify the role, select one primary body of knowledge, confirm the current syllabus and prerequisites, and then add adjacent certifications only when they solve a real skills need. A CTFL holder might move into advanced test analysis, automation, or TMAP depending on the work. A business analyst might favor requirements engineering and then add agile or quality knowledge. A developer may choose SDET and security-oriented study.

For 2026 candidates, the key is to separate the examination provider from the certification scheme. iSQI supplies flexible access and administration, but professional value comes from mastering the subject defined by ISTQB, A4Q, TMAP, IREB, or another program and applying that knowledge in real delivery work.