behavioral/
Behavioural
This folder has no README. Everything inside it is listed below.
Notes
- What was the most challenging part of a recent project? 5 An open invitation to demonstrate depth.
- How do you work with AI tools? 5 Asked in nearly every 2026 interview. It is not a question about which tools you've tried — it's about whether you've thought about where you keep judgement…
- What AI tools do you use? 4 Day to day I mainly use Cursor as my primary coding agent environment, alongside general-purpose LLMs for research and explanation.
- How exactly do you apply AI in your work? 4 I apply AI throughout the development lifecycle: shaping designs, scaffolding code, writing and maintaining tests, refactoring, debugging, and documenting,…
- What are the benefits of TDD for a codebase when using coding agents? 4 With coding agents, TDD becomes even more valuable: tests act as an executable specification and safety net that lets you confidently accept or reject…
- How do you think application architecture has changed with the advent of coding agents? 4 Coding agents push architectures toward being more modular, well-documented, and automation-friendly, because clear boundaries and contracts dramatically…
- Joining an Existing Project: How to Read and Understand the Codebase 4 Every job starts here, and the question is really about whether you can become useful without breaking something.
- Describing your strongest project 4 The most predictable question in any interview, and the one most often answered as a tour of the stack.
- How do you work independently without close management? 4 Whether they can give you a problem on Monday and not think about it until you report back.
- How do you handle not knowing something in an interview or on the job? 4 Two things at once. In the interview itself: will you bluff?
- How do you approach working with new technologies? 4 Two different questions hide in this one, and it helps to notice which you are being asked.
- Disagreement With a Teammate or Manager The classic senior STAR question. Interviewers want to see: you can hold a position, listen, change your mind when wrong, escalate appropriately, and not…
- A Project That Failed, or a Mistake You Made The interviewer wants ownership, learning, and self-awareness.
- Working With Ambiguity / Unclear Requirements 4 Senior engineers don't wait for clarity — they create it.
- Advocating for Tech Debt / Engineering Investment Every senior engineer has been asked "why are we slowing down for tech debt when we could be shipping features?" The strong answer turns this into a…
- Mentoring, Feedback, and Helping Others Grow Senior engineers don't just write code — they multiply other engineers.
- The six signals an interviewer is actually reading 5 Every technical question is a proxy. The interviewer has a small number of things they are trying to decide, and the topic is the vehicle.
- The questions you ask, and the red flags in your answers 3 Two things get scored that most candidates never prepare: the questions you ask at the end, and the patterns your own answers fall into.
- Leading technical direction on R&D work 4 The question behind "have you led technical direction" is not whether you had the title.
- Working directly with clients 4 Consultancy and agency work asks for something product-team experience does not teach: the person you are negotiating scope with is paying, the relationship…
- Leading a team of five to ten 4 Tech lead is a different job from senior engineer, and the interview probes whether you know that.
- Presales and scoping AI work 4 "Presales or estimation experience" on an engineering job ad means the role sits next to the sales conversation: you will be in the room before the…