Problem
Learner drivers need structured practice, useful revision feedback and trustworthy progress signals without exposing premium answers or relying on unsupported exam-frequency claims.
Pre-launch EdTech product
End-to-end product delivery across UX, serverless architecture, data quality, payments, security, accessibility and release operations.

The problem, the decisions I owned and the boundary of my contribution.
Learner drivers need structured practice, useful revision feedback and trustworthy progress signals without exposing premium answers or relying on unsupported exam-frequency claims.
I built the learner experience, content pipeline, serverless APIs, payment and passwordless-account adapters, operator tooling, automated QA and release documentation.
A recruiter-readable map of the product path, followed by the implementation choices behind it.
How the build is checked, delivered and kept honest about what is production-ready.
The custom-domain public preview is active. It is an independent practice product and is not affiliated with RSA or Prometric; paid launch remains blocked pending real provider and commercial verification.
Premium sessions are selected server-side, correct answers are withheld until submission, payments use signed idempotent webhooks, and admin endpoints enforce server-side roles.
What remains incomplete is shown deliberately, because engineering judgment includes knowing what not to claim.
Commercial launch is deliberately gated on real Stripe/database evidence, suitable business identity details and legal/content review. The website does not claim official exam frequency or guaranteed outcomes.