Technological interviews are stressful. Even senior developers get anxious when asked to "design a scalable system" or "explain the event loop" on the spot. The best way to prepare is practice—mock interviews. But finding a peer who can give you objective, deep technical feedback at 11 PM on a Sunday is nearly impossible.
That's why I built AI Tech Interview—a voice-first platform that acts as your always-available technical interviewer. In this article, I'll walk you through how I leveraged Next.js 16, Azure OpenAI, and Azure Speech Services to create a realistic interview simulation that talks to you, listens to your answers, and grades you like a hiring manager.

(For for setting up a session with a target role and job description)
The Problem: "It's Not Just What You Know, It's How You Say It"
Most interview prep platforms are text-based. You read a LeetCode problem, type a solution, and pass a test case. But real engineering roles require communication. You need to explain trade-offs, discuss architecture, and articulate your thoughts clearly.
I wanted to solve three specific problems:
Lack of Verbal Practice: Writing code is different from explaining it.
Generic Feedback: "Correct/Incorrect" isn't enough; we need nuance (e.g., "Your solution works, but you missed the scalability concern").
Role Mismatch: A Junior Developer shouldn't be asked the same system design questions as a Principal Architect.
The Solution: A Voice-First Simulator
AI Tech Interview isn't just a quiz app. It simulates the flow of a real video interview:
Context Aware: You paste the Job Description and the Role Title (e.g., "Senior .NET Developer").
The Interviewer Speaks: The AI generates relevant questions and reads them aloud using a neural voice.
You Speak: You answer via microphone. No typing.
Real-time Analysis: The system records, transcribes, and evaluates your answer using strict hiring criteria.

(The active interview room with the question being read aloud)
Under the Hood: The Tech Stack

(The hybrid architecture: A local Next.js app connecting to Azure AI services)
To build a seamless, real-time experience, I chose a modern stack focusing on performance and type safety. Critically, this project is designed to run locally. You don't need a complex cloud deployment to get started; you just need your Azure API keys.
1. The Core: Next.js 16 & Local Database
I used the latest Next.js 16 with the App Router. The new Server Actions feature was a game-changer for this project. Instead of building a separate API layer for handling interview sessions, I could execute database logic and AI calls directly from my components securely.
Database Flexibility: By using Prisma, the app defaults to a local PostgreSQL database, but it can easily be swapped for SQLite or a cloud managed database. The app itself is platform-agnostic and can be hosted anywhere (Vercel, Azure Container Apps, or your laptop), as long as it can reach the Azure AI endpoints.
2. The Brain: Azure OpenAI (GPT-4o-mini)
The intelligence comes from GPT-4o-mini. I chose this model because it balances speed and intelligence perfectly. It handles two key jobs:
Question Generation: It analyzes the "seniority" in your role title (e.g., detecting "Senior" vs "Junior") and dynamically adjusts the difficulty.
Evaluation: It acts as the hiring manager, scoring your answers on 6 dimensions: Relevance, Technical Accuracy, Clarity, Depth, Structure, and Confidence.
3. The Voice: Azure Speech Services
This is what makes the app feel "alive."
Text-to-Speech (TTS): I used Azure's Neural voices to give the interviewer a natural, non-robotic tone.
Speech-to-Text (STT): Real-time transcription converts your spoken voice into text for the LLM to analyze.
4. Deep Dive: Building for Resilience
Real interviews don't stop if your WiFi flickers, and neither should this app. I implemented a robust Offline-First architecture using IndexedDB.
If your connection drops mid-interview:
The app continues recording and saves your audio blob locally.
It queues the synchronization task in
IndexedDB.A background hook (
useOfflineSupport) monitors the network status.As soon as you're online, it automatically retries the upload without losing your answer.
// Simplified logic from useOfflineSupport.ts
useEffect(() => {
const unsubscribe = onNetworkChange((online) => {
if (online && state.pendingCount > 0) {
triggerSync(); // Auto-upload queued answers
}
});
return unsubscribe;
}, [triggerSync]);







Join the conversation! Your thoughts help the community grow.