Candidate management
Registration, documents, payments, progress, and exam readiness.
DirPermis
The digital platform connecting driving schools, instructors, and students.
DirPermis30-second spot
00:00 / 00:00
DirPermis modernizes the way driving schools operate and the way students learn.
Instead of managing registrations, instructors, lessons, schedules, payments, documents, and student communication across paper, spreadsheets, phone calls, and WhatsApp, DirPermis brings the entire experience into one connected platform.
Students connect directly with their driving school, discover available instructors, follow their training progress, and book lessons online. For schools, the same platform becomes the operational layer for managing candidates, teams, schedules, training, and daily activity.
- SaaS
- Dashboard
- Online Booking
- Student Experience
- Instructor Management
- Candidate Management
- UX/UI Design
- Full-Stack Development
Client
DirPermis
My role
Product Designer & Full-Stack Developer. End-to-end ownership across product thinking, UX/UI, technical architecture, frontend development, backend integration, deployment, and continuous iteration.
Product
A web platform connecting driving schools, instructors, and students throughout the driving licence journey.
Tools
- Next.js
- Figma
- React
- TypeScript
- Web APIs
- Cloud
001 · Overview
One journey. Three connected actors.
Getting a driving licence involves constant coordination between the student, instructor, and driving school. Traditionally, much of that coordination happens manually.
Students call or message the school. Staff check instructor schedules. Instructors communicate availability. The school confirms the appointment. Every change creates another round of calls and messages.
DirPermis turns that fragmented process into one connected digital experience. The goal was not simply to digitize a driving school—it was to connect everyone involved in learning to drive.
00:00 / 00:00
002 · Business context
A simple driving lesson can create an unnecessary amount of coordination.
Every student creates an operational journey involving registration, documents, payments, theoretical training, practical lessons, instructors, scheduling, progress, exam preparation, and communication.
Yet many interactions still happen through disconnected channels. The student contacts the school, staff check instructor availability, and everyone tries to find a suitable time before the booking can finally be confirmed.
3
Connected user roles
1
Shared operational platform
003 · Student experience
Booking a lesson becomes a self-serve experience.
Students access their school online, follow their licence journey, discover available instructors and time slots, and book practical lessons in a few clicks. Training progress and upcoming activity stay visible in the same place.
00:00 / 00:00
004 · School operations
The student experience and school operations share the same source of truth.
The dashboard brings candidates, instructors, availability, bookings, documents, payments, and training activity together. Staff can coordinate daily operations without rebuilding the same context across spreadsheets, calls, and message threads.
Instructor management
Availability, assignments, schedules, and practical training activity.
School dashboard
A clear operational view of the entire driving school.
00:00 / 00:00
005 · What I built
Designed, engineered, integrated, and deployed end to end.
I owned the product from early thinking through production: UX/UI, technical architecture, frontend development, backend integrations, cloud deployment, and continuous iteration. The result is not a prototype or a set of screens, but a working product connecting the full driving licence journey.
00:00 / 00:00