Nilay Baranwal
  • WorkSection
  • WritingSection
  • LabSection
  • Open sourceSection
  • GallerySection
  • AboutSection
  • ResumeSection
  • ContactSection
  • Hive MindProject
  • Pre-trade dashboardProject
  • Social LineProject
  • PartymakerProject
  • Orvio.aiProject
  • Agentic property managementProject
  • AI agents now outwork humans at Anthropic. Junior engineers are feeling it first.Article
  • Anthropic replaced git. Here's why you probably shouldn't.Article
  • Recruiters can now interview your AI twin. Here's what it actually checks.Article
  • Everyone's building a Jev rival. The independent numbers tell a different story.Article
  • Jev vs OpenAI Decisions API: which decision model should your agent use?Article
  • Top 10 Jev use cases in agentic appsArticle
  • Jev vs Laya: decision modelsArticle
  • LLMs or Jev: where each one actually fitsArticle
  • Everyone's talking about Jev. Here's a closer look at what the data shows.Article
  • Live agent with an approval gateLab
  • AI engineer interview, beginner pathLab
  • Behavioural interview coachLab
  • Interview drill, experiencedLab
  • AI adoption plannerLab
  • Discovery call simulatorLab
  • Scope a vague problemLab
  • MCP analyzerLab
  • MCP inspectorLab
  • Tool gate playgroundLab
  • Prompt-injection spotterLab
  • RAG chunking visualizerLab
  • Eval benchLab
  • Agent trace debuggerLab
  • Prompt caching simulatorLab
  • Context window budgetLab
  • textagentOpen source
  • Help EngineerOpen source
  • Email nilaybaranwal@gmail.comContact
  • Connect your agent to my MCP serverLab
  • LinkedInContact
  • GitHubContact
Lab

For interview prep

Behavioural interview coach

A question bank with what interviewers are really asking, a story bank, timed practice, conflict resolution with the LEAD method, and a weak-vs-strong example.

Ownership

They're really asking: Do you finish things and take responsibility when they go wrong?

Conflict

They're really asking: Can you disagree without damaging the relationship?

Failure

They're really asking: Are you honest about mistakes, and do you learn from them?

Ambiguity

They're really asking: Can you make progress when nobody tells you exactly what to do?

Customer focus

They're really asking: Do you understand users' real problems, not just their requests?

Influence

They're really asking: Can you move people you don't manage?

Learning

They're really asking: How fast can you get useful in something new?

Motivation

They're really asking: Why this role, and will you stay engaged?

Six rules that make answers stick

Prepare stories, not answers
Five or six strong stories cover almost every question. Map each story to the categories it proves.
Spend half the time on Action
Situation and Task set the scene in two sentences. Action is where you show how you think.
Say "I"
Interviewers are hiring you, not your team. Say what you did, and credit others briefly.
End with a number and a lesson
"Cut response time from 3 hours to 20 minutes" sticks. Then say what you'd do differently.
Keep it to one or two minutes
Roughly 150–300 spoken words. Let them ask follow-ups instead of telling everything.
Have a failure story ready
Pick a real one with a clear lesson. A fake weakness ("I work too hard") costs trust.