Featured Learning Paths, capstone projects worth showing in a portfolio, and the team training arrangement we run with enterprise client clients. Three sections, one page, no quote calculator.
We built these paths because most learners cannot tell yet which course is for them. Each path runs three of our nine courses in a sequence we have seen work; you can deviate at any step.
A grounded path for analysts and IT support engineers moving into RPA development for the first time. Foundations covers the studios; Bridge teaches you to refactor recordings; Bot Developer Track is where you become useful in a small team.
Built for backend or QA engineers stepping sideways into RPA. The Bot Developer Track teaches our REFramework patterns; Hybrid Design teaches you to choose between API and UI per step; Document Understanding closes the loop on the harder enterprise work.
For senior developers and CoE leads moving up. Discovery Blueprint teaches you to scope intelligently; Orchestrator Deployment Pro teaches you the boring-but-critical platform work; the Capstone forces you to defend a 12-month roadmap in writing.
Each capstone produces something you can show in an interview without redacting your employer\'s data — they all run against synthetic, in-house corpora.
A document understanding pipeline reading 220 synthetic invoices, routing low-confidence cases to a review queue, and reporting accuracy in language a finance lead can read.
From: Document Understanding Bots
A hybrid bot calling four APIs, driving two web UIs, and producing a hand-off document for a partner team. Ships with a written architectural decision record.
From: API & RPA Hybrid Design
Promote a real package across dev, test, and prod tenants in Automation Cloud, then practise the rollback drill until it is muscle memory.
From: Orchestrator Deployment Pro
Scope a fictitious enterprise client portfolio for the next twelve months, build a governance model, and present the architectural review to a panel of three reviewers.
From: Automation Architect Capstone
Below is the actual sequence of how a Studio or Agency engagement works. We do not send you a quote in PDF form on day one — we want to read your existing automations first.
25 minutes with Yoon Min-su and one mentor. We read your last three internal automations before the call.
A free, written diagnostic for up to three of your team members. We send back what we found, not a sales deck.
Your team starts on a private cohort calendar negotiated to fit your sprints — usually two evenings plus Saturday morning.
Four months in, we re-run the diagnostic and write you a one-page note on how the team has shifted. Yes, even when it has not shifted much.
No prep needed — we will ask for read access to three of your existing automations on the call itself.