OutSystems Professional Developer exam-day guide
OutSystems Professional Developer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the exact ID name that matches your registration. If you are testing remotely, confirm with the provider which ID types and names are accepted before test day; name mismatches are a common reason for being turned away.
Registration confirmation and exam appointment details
Save the confirmation email offline (screenshot or PDF on your phone and laptop). It contains your appointment time, provider name, and support contact if something goes wrong with check-in.
Quiet, private test space (remote testing)
Clear your desk of papers, phones, and second screens. Confirm with the provider whether a whiteboard or scratch paper is allowed; if not stated, assume none and plan to work without it.
Stable internet and a backup connection
Test your connection and webcam the day before. Have a phone hotspot ready as a fallback, and know the provider's support number in case the session drops.
Compatible browser and system check
Run the provider's system or equipment check in advance. Update the browser, close background apps, and disable notifications. Confirm with the provider which browsers are supported.
Review OutSystems core concepts, not trivia
Focus on entities and relationships, aggregates, server vs. client actions, screens and blocks, roles and permissions, exceptions, and deployment between environments. These are the areas most likely to appear in scenario questions.
Practice reading logic and data model descriptions
The exam is scenario-based. Rehearse tracing an aggregate's output, predicting what a server action returns, and spotting why a screen or role check fails, all from written descriptions rather than a live environment.
Confirm exam format and scoring with the provider
Question count, time limit, pass score, and whether the exam is proctored or open-book vary and can change. Check the official exam page or your registration email rather than relying on secondhand reports.
Plan timing per question
Divide the total time by the question count to get a per-question budget, then add buffer for flagged questions. Confirm the actual time limit with the provider before relying on this.
Rest, water, and a light meal beforehand
Scenario questions reward clear reasoning. Avoid cramming new topics the night before; sleep matters more than one more practice set.
Backup power and a charged device
Charge your laptop and phone fully. For remote testing, plug in the laptop so a battery warning does not interrupt the session.
Know the reschedule and retake policy
Check with the provider how late you can reschedule, whether there is a fee, and how retakes work. Do this before test day so a last-minute problem is not a surprise.
Plan the day
Do one full timed practice run under exam-like conditions, then review only the topics you got wrong. Stop learning new material. Re-read your notes on entities, aggregates, roles, exceptions, and deployment, and write a one-page summary you can skim on the morning of the test.
Run the provider's system check, verify your ID name matches your registration, and confirm the appointment time in your own time zone. If anything is unclear, contact the provider now rather than the day before.
Light review only: skim your one-page summary and re-read a few scenario questions you previously missed. Prepare your desk, ID, charger, and login details. Confirm your internet and webcam work. Go to bed at a normal hour.
Eat a real meal, hydrate, and avoid heavy cramming. Do a five-minute skim of your summary. Log in early to handle check-in, ID verification, and any room scan the provider requires. Close all other apps and silence your phone.
Read each scenario fully before looking at the answers, and eliminate clearly wrong options first. Answer easy questions quickly to bank time. Flag anything uncertain and return to it after a first pass. Watch the clock against your per-question budget, and leave a few minutes at the end to review flagged items.
If a question depends on a detail you cannot recall, reason from OutSystems principles (for example, how aggregates filter at the database level or how role checks gate screens) rather than guessing randomly. Do not spend more than roughly double your per-question budget on any single item.
Note which topics felt weak while it is fresh. If the provider reports results immediately, record your score; if not, confirm how and when results are delivered.
Rules to check
Bring valid government-issued photo ID with a name matching your registration. If you are unsure which ID forms are accepted, confirm with the provider before test day.
Follow the provider's rules on permitted materials. Unless the exam is explicitly open-book, assume notes, second screens, and phones are not allowed, and confirm with the provider if you are unsure.
For remote proctoring, stay in the camera's view, keep your desk clear, and do not leave the room during the session except as the proctoring rules allow. Confirm break rules with the provider, since many exams do not permit breaks.
Do not communicate with anyone else during the exam, and do not share, record, or reproduce exam questions afterward. Treat the content as confidential.
If your session disconnects or you hit a technical problem, stop and contact the provider's support immediately rather than restarting on your own; follow their instructions to preserve your attempt.
Scoring and passing standards are set by the provider and can change. Check the official exam page for the current pass score, question count, and time limit rather than relying on forum reports.
If you need to reschedule or cancel, do so within the provider's stated window to avoid losing your fee. Confirm the deadline and any fees with the provider.
Arrive or log in early. Late arrivals may be refused entry or have time deducted, so confirm the provider's check-in cutoff and plan to be ready well before your appointment.