GitHub Certified: Agentic AI Developer exam-day guide
GitHub Certified: Agentic AI Developer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
The name on the ID must match your registration exactly. Bring a second form of ID if you have one. Confirm which ID types the proctoring provider accepts before exam day.
Appointment / registration confirmation
Have your confirmation email, registration ID, and the platform login URL handy. Confirm whether the provider requires a printed copy or accepts a digital one.
Working webcam, microphone, and speakers/headset
Most remote-proctored exams require a live camera and audio check during check-in. Confirm the exact hardware requirements with the provider; some prohibit headsets.
Stable primary internet connection plus a backup
Have a phone hotspot or second network ready in case your primary connection drops mid-exam. Test the failover once before exam day.
Quiet, private, well-lit room
No other people entering, no clutter in camera view. A closed door and even lighting on your face are typically required. Confirm whether the room must be scanned with the camera at check-in.
Clean desk - nothing but the allowed items
Move phones, smartwatches, second monitors, printed notes, and paper out of reach. Assume only your computer, ID, and (if permitted) a clear glass of water may be on the desk.
All other applications closed and notifications silenced
Quit chat clients, email, browser tabs, and screen-recording/remote-access tools before check-in. Silence phone notifications even if the phone is out of reach.
Platform login credentials verified
Log in to the testing platform (and your GitHub account if the exam links to it) the day before so a password reset never happens during check-in.
The official exam skills outline / domains
Download the authoritative objectives from the certification page and skim them the morning of. Verify the current exam code and whether this credential is standalone or part of a larger track.
Notepad policy understood
Determine in advance whether scratch paper is prohibited and whether an on-screen notepad is provided. Policies differ by provider - confirm before exam day.
Break and timing policy understood
Know the total seat time, whether scheduled or unscheduled breaks exist, and whether the clock stops. Confirm with the provider.
System pre-check completed
Run the provider's system/browser test at least 24 hours ahead so you have time to fix camera, mic, or network issues.
Plan the day
Stop adding new topics. Re-read the official skills outline and convert weak areas into short summary notes. Do timed practice on scenario-style questions: read the last line of the stem first, then eliminate options that violate a stated constraint.
Get hands-on once more in a scratch repository - for example, exercise an agentic workflow end to end (task definition, tool/function calling, guardrails, evaluation of outputs) so that terminology in the questions maps to something you have actually done.
Confirm logistics: exact appointment time in your local time zone, platform URL, ID requirements, and whether any pre-check-in step must be completed. Resolve name mismatches with support now, not on exam day.
Run the full system check (camera, mic, browser, bandwidth). Charge laptop and backup devices; set up the hotspot. Tidy and photograph your exam space so you know exactly what must be cleared.
Light review only: skim your summary notes and the skills outline for 45–60 minutes, then stop. Prioritize sleep over one more practice set.
Eat, hydrate, and do a 20-minute recap of your own notes - no new material. Reconfirm the appointment time and log in to the platform early to catch any account issues.
Clear the desk, silence devices, close all applications, and place your ID within reach. Start the check-in process 15–30 minutes before your slot in case of queueing or re-scans.
Read the instructions and question count first, then budget time per question. Do a fast first pass answering what you know, flag long scenario items, and return to them - never leave a blank if there is no penalty for guessing.
Separate what the question asks from what is merely true. Prefer the option that satisfies the stated constraint (least privilege, least operational overhead, safety/guardrail requirement) rather than the most impressive-sounding tool.
Keep an eye on the clock at the halfway mark. If a technical issue occurs, stay in the session and contact proctor support immediately; do not restart the exam on your own.
Note whether a provisional score or later email is used, and save the score report. Check the provider's retake and badge-issuance process.
Rules to check
Bring ID whose name matches your registration exactly. If your legal name differs from your account name, contact the certification provider before exam day to correct it - do not attempt check-in with a mismatch.
Do not use any unauthorized aid during the exam: no second screen, phone, notes, browser tabs, AI assistants, or another person in the room. Proctors may void the attempt and this can affect eligibility for future attempts.
Assume the exam content is confidential. Do not screenshot, copy, record, or discuss specific questions afterward; doing so typically breaches the candidate agreement.
Follow the proctor's instructions during check-in, including room scans and desk shows. If a proctor asks you to do something that conflicts with the printed rules, ask for clarification rather than refusing.
Break policy varies by delivery mode and provider. Confirm in advance whether breaks are allowed, whether the timer runs during them, and what re-verification is required on return - do not assume.
Scoring, pass marks, and result timing are set by the certification provider and are not always shown immediately. Confirm the pass threshold and score-report delivery method with the provider rather than relying on secondhand reports.
Retake and rescheduling terms are provider-specific. Check the window for rescheduling without penalty and the wait period between attempts before you book.
If you are disconnected or the platform fails, rejoin if possible and contact support right away, documenting times and any error messages. Do not start a new attempt without support authorization, as that may be treated as an extra attempt.