Screens
Gallery
01 / 05
DevBench landing page: "Hire developers by what they can build", with Get started and Try the demo buttons
01
Overview
Companies build coding, MCQ, and written problems, invite candidates by email to timed assessments, and score the results. Candidates take exams in the browser with a code editor, autosave, and a countdown. Admins oversee the whole platform. Includes Stripe-based credits, role-based dashboards, and one-click demo logins.
02
Tech stack
Frontend
Backend
Database
Tools
03
Challenges faced
01
Role-based access before a page renders
What went wrong
Users should never see a flash of a dashboard they are not allowed to open.
02
Auth cookies across two origins
What went wrong
The frontend and backend live on different origins, so auth cookies would be third party.
03
A reliable timed exam experience
What went wrong
Candidates must not lose work during a timed exam, and authors must not lose long problem drafts.
04
How I used AI
The same workflow I use on every project: AI speeds me up, I own the decisions, the review and the security.
- 01AI + Me
Requirements
AI drafts the basic requirements; I check every point.
- 02Me
Project setup
I initialize the project myself. No AI.
- 03AI
Code generation
AI, mainly Claude, writes the feature code.
- 04Me
Line-by-line review
I review every generated line before it stays.
- 05Me
Security code
All security-related code is written by me, not AI.
- 06AI + Me
Bugs and errors
I debug with AI's help and verify every fix.
Written by me, not AI
- Role-based access before render in proxy.ts, with a client RoleGuard as a backup
- httpOnly JWT cookies kept first party through the /api/v1 rewrite
- Refresh-token retry in the ofetch client
- Stripe-based credits
05
Improvements and future plans
- Next
Automated test suite
Unit, API, and end-to-end tests, since the app is currently checked by a written manual walkthrough for every role.
