1. LandOffer
  2. Blog
  3. All articles
  4. UiPath Certification: Choose Developer or Business Analyst and Check Exam Versions

Job search

UiPath Certification: Choose Developer or Business Analyst and Check Exam Versions

Choose a UiPath track by implementation or process-analysis responsibility, then check current exam scope, training evidence and purchase conditions.

9 min readLandOffer team

Choose a UiPath certification by the work you want to own: building and debugging automations, or defining the process, requirements and acceptance decisions around them. Within that role, compare Associate and Professional objectives with work you can explain and demonstrate. Completing an Academy learning plan does not itself award the corresponding proctored certification.

This comparison checks official information on October 23, 2026. It focuses on four Developer and Business Analyst exams, rather than every certification in UiPath’s expanding catalog. Two completed fictional records demonstrate the selection and purchase decisions; no exam, learning account or automation runtime was tested. Compare recent automation roles on LandOffer.ai with your actual contribution before choosing preparation.

An automation engineer builds a small mechanical sorter while a business analyst and colleague review its process, illustrating complementary responsibilities.

Select the responsibility before the level

The current certification directory distinguishes Automation Developer Associate from Automation Developer Professional. Associate targets simple independent solutions or contribution to a team handling complex work. Professional emphasizes independently building or leading complex production automations, including the Robotic Enterprise Framework, or REFramework.

The Business Analyst routes emphasize requirements, discovery, process analysis and automation implementation. Their technical content matters: a BA must understand the platform and explain what an automation should do. That differs from being accountable for its implementation, debugging and operation.

Do not translate “Professional” into a universal seniority requirement across employers. Read past the job title: an automation analyst may build Studio workflows, while a developer may also conduct process discovery. Use the deliverables, production responsibility and collaboration boundaries in the posting. The certification title supplies a study target, not proof that an employer uses the same division of labor.

Check the current exam document and product baseline

The four currently linked descriptions list these conditions:

Exam Current document Product baseline Listed duration and fee
Automation Developer Associate V1.6, January 2026 2024.10 and later 90 minutes; US$150
Automation Developer Professional V1.1, January 2026 2024.10 and later 120 minutes; US$300
Automation Business Analyst Associate V1.1, October 2025 2024.10 and above 90 minutes; US$150
Automation Business Analyst Professional V1.1, December 2025 2024.10 and above 90 minutes; US$300

All four list a 70% passing score, three-year validity and no prerequisite exams or certifications. That does not make every candidate equally prepared. It does mean an Associate pass is not a mandatory exam gate for these Professional routes. Recommended background and a formal prerequisite are different fields.

The Developer descriptions also explicitly warn that internal exam codes or score reports can retain a legacy 2023.10 suffix for administration. That suffix does not identify the product version assessed. Before buying a course, compare its content with the current objectives; matching a legacy internal code does not establish current coverage.

The program FAQ retains a historical October 2023 announcement about the move to 2022.10. Its maintenance note directs readers to the latest descriptions. For present preparation, use the January 2026 Developer documents rather than treating that historical announcement as the current baseline.

Compare the work inside the four outlines

The Developer Associate description spans Studio fundamentals, variables, control flow, debugging, exceptions, logging, UI automation, data manipulation and Orchestrator. It also includes API automation, Integration Service, version control and testing. Preparation limited to recording clicks would leave important gaps.

Developer Professional adds advanced manipulation and debugging, REFramework, attended automation, APIs, resource management and Autopilot. Its recommended candidate has at least twelve months of Automation Developer experience; Associate describes foundational training without prior experience or at least six months of hands-on experience. Neither background description replaces the explicit “None” prerequisite field.

Business Analyst Associate covers implementation methodology, business cases, process analysis, platform and discovery tools, change control and agentic concepts. Its recommended candidate has one or more years as a BA and participation in at least five UiPath automation projects. The outline includes a process design document, or PDD, and test-case scenarios.

Business Analyst Professional describes two or more BA years and at least five projects. It expands into UAT, AI/discovery solutions, change analysis and agent definitions, including grounding, tools, guardrails and escalations. The document’s section heading accidentally says “Associate”; its cover, credential and exam-details table identify Professional. Do not merge those two exams because of that heading.

These outlines overlap in platform and agentic knowledge. BA preparation is not automatically nontechnical, and Developer preparation is not a substitute for requirements ownership. Read each complete outline against what you can explain and what you still need to learn.

Completed responsibility record: a returns automation handoff

Nora is a fictional operations analyst on a stipulated UiPath returns project. She has eighteen months of BA experience and has participated in five automation projects. Her record contains discovery interviews, a PDD and acceptance scenarios, but no independently built Studio package. The invented project facts below are a completed paper analysis, not an inspected vacancy or executed automation.

The returns process receives 240 requests weekly. In this scenario, 180 contain all required fields, 40 lack purchase evidence and 20 concern damaged goods. The categories are stipulated and mutually exclusive; their total is 240. They describe routing requirements, not measured automation accuracy or guaranteed savings.

Work decision Nora’s completed responsibility entry Owner and preparation implication
Define the normal route Complete requests require order reference, return reason and purchase evidence Nora documents the rule; Business Analyst Associate fits this requirements task
Handle missing evidence Forty requests enter a human follow-up route; the automation must not infer the receipt Nora specifies the exception and acceptance condition; developer implements it
Handle damage Twenty requests require a separate review even when fields are complete Nora records the business distinction and escalation; no automatic approval promised
Build the implementation No package, selectors, retry configuration or logs supplied in her record Developer ownership remains unproven; she does not choose Developer Professional from the project’s size
Accept a change A proposed change would allow one alternative proof document, subject to business approval Nora records the affected PDD rule and regression scenarios before implementation

Her completed acceptance specification contains three synthetic cases. R-01 has complete fields and no damage flag: expected route is normal processing. R-02 lacks purchase evidence: expected route is human follow-up, with no inferred approval. R-03 has complete fields and a damage flag: expected route is damage review rather than normal processing. These expected outcomes were specified, not run in UiPath.

Nora selects Business Analyst Associate preparation for requirements, PDD and acceptance work, while leaving Studio implementation ownership with the developer. Her background resembles its recommended profile, while her record lacks the broader AI/UAT responsibilities she would want to explain for Professional. She is permitted to consider either exam’s no-prerequisite route; the decision here concerns preparation fit.

Her application evidence statement is equally bounded: “Defined three mutually exclusive returns routes and their acceptance cases; handed implementation to the automation developer.” It does not claim 240 requests were automated or that a PDD demonstrates production coding. She can now discuss a concrete BA contribution without borrowing the developer’s deployment responsibility.

Separate Academy completion from exam readiness

The public Automation Developer Associate learning plan currently lists 45 hours 20 minutes, 21 courses and product version 2024.10. It says some courses were built on 2022.10 with relevant 2024.10 updates incorporated. An older course-origin label therefore does not, by itself, prove the whole plan is obsolete.

The page describes an unlocked learning credential and diploma. Preserve that exact achievement when describing completed training; passing the separately proctored examination is another event. The published duration is a curriculum estimate, not a prediction of how long every learner will need for exercises, revision or exam preparation.

A useful completion audit compares the current exam objectives with explanations and exercises you can reproduce without following a recording. Record whether each item is a guided exercise, an independently completed practice task or production work. Those categories should remain visible even after a course marks all lessons complete.

A learner checks a study folio against a small unfinished mechanism, using separate compartments for completed lessons, unresolved practice and an unspent exam budget.

Completed purchase record: an Academy completer’s gap decision

Evan is a separate fictional learner with no production UiPath work. For this constructed case, his supplied record is assumed to show the current Developer Associate plan completed; no private Academy achievement was inspected. His intended contribution is building small automations with code review. An invented $360 employer learning allowance covers exam fees and preparation; it is not a UiPath offer or an approved reimbursement claim.

He maps four concrete evidence items to the current Associate outline:

Evidence item Completed assessment of the supplied record Decision before booking
Synthetic supplier-list exercise A guided exercise maps three fields and removes duplicate supplier IDs Keep as guided learning; independently explain matching and data-type choices
Missing-input exception He can describe an error but supplied no independent recovery exercise Hold booking until a fresh synthetic failure case has an expected outcome and an observed result
Orchestrator resource choice Course completion recorded; no explanation distinguishes a reusable asset from a queue item Add a written comparison and a supervised practice task; no production access assumed
Version control and testing Lesson completion recorded; no independent change review or regression record Demonstrate these separately instead of presenting the diploma as evidence of all objectives

His finished decision is to retain Developer Associate as the target and delay purchasing an appointment. He does not buy Business Analyst Associate as an easier-sounding substitute, because his desired responsibility is implementation. He also defers Developer Professional: its advanced scope adds preparation needs while his Associate-level recovery, resource and testing evidence remains unfinished.

His pre-tax budget allocates $150 to one possible Associate attempt and $60 as an unquoted materials reserve, leaving $150 uncommitted. If he needs another $150 attempt, the modeled total becomes $360 and uses the entire allowance before tax. A Professional first attempt plus the same reserve would also total $360, without funding any further attempt. Only the arithmetic was checked locally. Tax, actual materials prices and any reimbursement conditions remain outside this modeled allowance; no purchase or examination result was verified.

Evan’s purchase hold has a specific release condition: independently explain the four gaps and save the practice evidence before choosing a date. No practice task is marked passed here. His present resume wording is “Completed Automation Developer Associate training”; “UiPath Certified Professional” remains unearned until the corresponding certification is actually awarded.

Preserve the booking and credential boundaries

The FAQ lists fees per attempt, plus applicable tax; free practice questions are static and repeat. A repeated high practice score does not guarantee a certification result. Its retake policy requires two weeks after the first failure and one month between subsequent attempts. It also specifies at least 48 hours for cancellation or rescheduling, with late changes and no-shows risking the fee. Confirm current conditions before committing funds.

Current credentials have three-year validity. The separate legacy UiRPA/UiARD recognition period was three years from October 13, 2023; that period has elapsed by this review date. An old badge name is therefore a reason to inspect its exact record, not to assume a current award or automatic conversion.

Save the selected exam name, document revision, product baseline and actual booking terms together. Then use recent roles on LandOffer.ai to compare required and preferred credentials with your documented responsibilities. Training, a certification pass and production ownership should each retain their own evidence.

Sources and Further Reading