06 · Behavioral

Your Intro + Delivery Mechanics

The 60-second "tell me about yourself", the delivery habits that matter more than content, and what each round is really testing.

01The 60-second "tell me about yourself"

Intro Timer 60s mode

"I'm a backend and AI engineer at Mira in Bengaluru — about two years in, including internships. Two things define my work. First, scale: I run our LLM-serving API layer — 2M+ requests a month behind Kong on Kubernetes, handling auth, rate limiting, and billing for 50+ enterprise clients, plus Kafka event pipelines serving 5,000+ concurrent users. Second, agents: I built Sentinel, a self-healing dev system that detects issues from GitHub webhooks, root-causes them from production logs over MCP, generates fixes with an LLM — about a hundred merged PRs a month — and gates everything behind an adversarial AI reviewer with human approval. It cut our incident resolution time roughly 70%. I studied CS at IIIT Sri City, graduated 2025. I'm looking for a role where I can go deeper on exactly this: production AI systems with real reliability constraints."

60s

Trim to 30s by cutting the second halves of each part. Practice until it's conversational, not recited.

02Delivery mechanics (matter more than content)

1 · Pause before answering.

2 seconds of thought reads as depth, not slowness.

2 · Numbers land only when said casually.

"About two million requests a month" — not proudly, just factually.

3 · Structure out loud.

"Two things here — first… second…" Interviewers remember structured answers.

4 · When you don't know: say so fast, then reason.

"I haven't used X in production — my mental model is Y; here's how I'd verify." This scores HIGHER than a bluff at every good company.

5 · End answers.

Land the result, stop talking. Silence after a strong finish is the interviewer's problem, not yours.

6 · Coding rounds.

Restate the problem → tiny example → brute force out loud → optimize → code → trace through the example → state complexity. Every time, same ritual.

03Delivery mechanics self-check

Tick each habit once it feels automatic in mock practice. Saved in your browser.

04Round-type cheat sheet

RoundWhat they're really testingYour play
DSA / codingCan you reason out loud + pattern-matchThe ritual above; patterns cheatsheet
CS fundamentalsDo you understand what you use dailyAnswer from production experience first, theory second
System designStructured thinking + tradeoffsThe framework; steer to LLM-gateway/Kafka designs you run
BehavioralOwnership + honesty + growthStory bank; never inflate
"Any questions?"Whether you think like an ownerAsk "what breaks most often?"