How I Built Attempt Hire for Video-Based Interview Workflows

Attempt Hire came from thinking about how hiring processes often feel heavier than they need to. There is usually too much friction on one side or too little structure on the other. I wanted to build something that gave hiring teams control while keeping the candidate experience direct and easy to follow. The platform allows admins to create roles, build interview sets, manage questions, and send secure interview links to candidates. Candidates can complete their interviews directly in the browser without creating an account, and their recordings are stored securely for later review. I built it with Next.js App Router, React, Tailwind CSS, Supabase, Zod, and some Three.js-based animated touches to give the interface more personality. The biggest challenge was not the visuals. It was shaping two different experiences that had very different needs. On the admin side, the product needed structure, clarity, and the ability to manage interview flows confidently. On the candidate side, the platform had to feel calm, simple, and trustworthy. That difference pushed me to think more carefully about product design, not just UI design. I also liked how much this project taught me about workflow thinking. A good product is rarely just a collection of pages. It is a sequence of decisions, states, permissions, and expectations that need to fit together naturally. Attempt Hire made me think more deeply about how to build for real usage, where trust, clarity, and reduced friction matter just as much as the technology behind the scenes.