113 HR & Behavioral interview questions with detailed answers, sorted from basic to advanced. Free to practice, with progress saved automatically.
This section holds behavioral and career questions that look at how a candidate collaborates, communicates and plans growth rather than at technical knowledge. It covers situational questions, introducing yourself, culture fit, soft skills, code review etiquette, estimation, salary and compensation, career paths, changing direction, CV presentation and continuous learning.
and 10 more topics.
What they're assessing: a 60-90 second job-relevant summary, not your life story. Use the present → past → future formula: what you do now, a standout result, and why this role. Avoid: starting from university, or reciting your whole CV. Sample answer: "I'm a frontend…
What they're assessing: a genuine, specific motivation that signals long-term commitment, not just chasing salary. Avoid: generic reasons ("IT pays well", "it's trending"). Sample answer: "I love turning an idea into something real that people use every day. The first time I built a small…
What they're assessing: that you have direction, and it aligns with a path the company can offer. Split it into short-term (technical) and long-term (depth or leadership). Avoid: saying "I want to manage" for a purely technical role, or a vague "not sure yet". Sample…
What they're assessing: that you understand Senior is about growing scope and autonomy, not just "coding better". Give 3 milestones and what changes at each. Sample answer: "Junior (0-2 yrs): learn the fundamentals, code under review. Mid-level (2-5 yrs): work independently, own a module, review…
What they're assessing: that you actually researched the company, not mass-applied. Name 2-3 concrete things from the JD/product/team. Avoid: "because it's famous" or "for the pay" — and don't bash big companies to flatter this one. Sample answer: "I like the TypeScript/React stack and that…
What they're assessing: that you have a point of view with technical reasoning, while staying flexible to real needs. Avoid: "anything works". Sample answer: "I'm focusing on Backend because I enjoy database design, API optimization, and handling load. But I keep my frontend skills sharp…
What they're assessing: a balanced, honest answer that fits your career stage. Avoid: "I don't care about salary" (not credible) or "salary is everything" (no commitment). Sample answer: "Fair, livable pay is a baseline. But at this stage I prioritize an environment that lets me…
What they're assessing: a forward-looking reason (what you're moving toward), not an escape, and that any frustration is framed around process/tech, not people. Avoid: badmouthing your manager, colleagues, or former employer — the biggest red flag. Sample answer: "I learned a lot there, but they…
What they're assessing: that you can drop jargon and use familiar analogies — a core skill for working with PMs, sales, and clients. Avoid: explaining with more technical terms. Sample answer: "I start from the outcome they care about, then use a familiar analogy. To…
What they're assessing: your specific role in the shared result, not "the whole team tried hard". Answer with STAR. Sample answer (STAR): - Situation: a 5-person team, one-month deadline for the v2.0 release. - Task: I owned the payments module and helped coordinate overall progress.…
What they're assessing: that you handle disagreement professionally, putting the work above ego — not that you "won". Avoid: badmouthing the colleague, or "I never have conflicts" (sounds evasive). Sample answer (STAR): - Situation: a backend dev and I disagreed on whether to validate data…
What they're assessing: that you support first, judge later, and stay transparent when it affects the team. Avoid: jumping to criticism or escalating to the boss immediately. Sample answer: "First I check what's blocking them and how I can help — sometimes it's just missing…
What they're assessing: that you do both well and know when each fits. Avoid: picking an extreme — it sounds like you're hard to collaborate with, or can't work independently. Sample answer: "I need both. Working alone gives me deep focus for hard problems. Working…
What they're assessing: that you treat strict reviews as learning, separate feedback from ego, but still speak up when you disagree. Avoid: getting defensive, or silently changing things without understanding why. Sample answer: "I ask for the reasoning behind each comment — understanding the \"why\"…
What they're assessing: that you can lift others up, even informally. Teaching is a sign of deep understanding. Avoid: a flat "no". Sample answer: "Not formally, but I often pair with juniors when they're stuck — I don't fix it for them, I ask guiding…
What they're assessing: that you stay calm, prioritize, and communicate transparently instead of trying to absorb everything. Avoid: "I just work overtime until it's done" — it signals poor management. Sample answer (STAR): - Situation: before a release, we found extra critical bugs with not…
What they're assessing: your specific role, a real challenge, and a measurable result. Avoid: describing the tech generically without saying what you did. Sample answer (STAR): - Situation: an e-commerce platform slowed down as traffic grew. - Task: I owned redesigning the backend for load.…
What they're assessing: that you stay calm, restore service first, then find the root cause and learn. Avoid: rambling without saying what you did and in what order. Sample answer (STAR): - Situation: a slow DB query left users unable to load data at peak…
What they're assessing: that you distinguish temporary tech debt (acceptable) from quality/safety (never cut), and have a payback plan. Avoid: "I cut nothing" (unrealistic) or cutting testing/security. Sample answer: "The first thing I do is talk to the PM/PO about cutting scope: drop or postpone…
What they're assessing: that you raise risks with data and offer alternatives, not just say "no". Avoid: either nodding along, or rigidly refusing. Sample answer (STAR): - Situation: the PM wanted a feature in 5 days; I estimated 2 weeks to do it right. -…
What they're assessing: a safe strategy, not a reckless rewrite. The core principle: a safety net before you touch anything. Sample answer (STAR): - Situation: the old payments module was tangled and hard to extend. - Action: I wrote tests to capture current behavior first,…
What they're assessing: that you measure before fixing and find the real bottleneck instead of guessing. Avoid: a generic "I optimize the code" with no method. Sample answer (STAR): - Situation: a page loaded slowly and customers complained. - Action: I profiled with DevTools, found…
What they're assessing: that you can own failure, see the cause, and change how you work after. This doubles as "your most valuable lesson". Avoid: blaming circumstances, or a fake failure like "I worked too hard". Sample answer (STAR): - Situation: a project I was…
What they're assessing: that you're transparent, fix fast, and prevent recurrence — because hiding a bug is always worse. Avoid: pretending you never make mistakes. Sample answer: "I tell the team right away instead of hiding it, because hiding only makes the impact bigger. I…
What they're assessing: that your feedback is constructive — private, specific, with a solution — not vague or publicly embarrassing. Avoid: dodging feedback to avoid friction. Sample answer: "I give feedback in a 1-on-1, specific to the issue not the person, always with a path…
What they're assessing: that you take it without getting defensive, reflect, and turn it into action. Avoid: appearing hurt or pushing back immediately. Sample answer: "I thank the person and try to separate the emotion from the content. I ask clarifying questions if needed, then…
What they're assessing: that you decide on clear criteria (performance, maintainability, team skill, time), not vibes or trends. Avoid: calling one approach "always better". Sample answer (STAR): - Situation: choosing between microservices and a monolith for a new product. - Task: I was the one…
What they're assessing: a clear prioritization framework and that you communicate when you can't do it all. Avoid: "I'll try to finish everything" — unrealistic. Sample answer: "First I ask the PM which has the biggest business impact. If it's unclear, I use an urgent/important…
What they're assessing: that you researched the market and give a reasonable range, while tactfully asking the company's budget back. Avoid: anchoring yourself to a minimum too early, or "anything works". Sample answer: "Based on salary reports (ITviec Salary Report, VietnamWorks) and my 3 years…
What they're assessing: that you're flexible but know your limits, and can negotiate beyond base pay. Avoid: accepting unconditionally (undersells you) or refusing flatly (rigid). Sample answer: "If it's within about 10% and I genuinely like the opportunity, I'm open to discussing. If it's well…
What they're assessing: your real preference and whether it fits company policy. Hybrid is the most common now. Avoid: setting rigid conditions before understanding how the company operates. Sample answer: "I prefer a hybrid model — about 3 days in the office for collaboration and…
What they're assessing: a concrete description with examples, so they can picture whether you fit how the team works. Avoid: empty adjectives like "I'm hardworking". Sample answer: "I lean organized and proactive — I plan before diving in, break work into clear milestones, and update…
What they're assessing: whether your ideal environment matches reality here — a two-way fit check. Avoid: describing the opposite of what the company offers. Sample answer: "I work best in a collaborative environment that still has quiet time for deep focus. Ideally a short morning…
What they're assessing: that you know what you need from a manager to do well, and can adapt. Avoid: sounding like you need close supervision or can't take feedback. Sample answer: "I work well with a coaching style — a manager who sets clear direction…
What they're assessing: that you understand the differences and your choice matches the very company interviewing you. Avoid: praising the opposite of where you're applying. Sample answer: "I fit best with a scale-up — enough resources to build quality, but still small enough to see…
What they're assessing: that culture genuinely matters to you and you researched the company's values enough to name a specific fit. Avoid: a generic "I like the culture" with no specifics. Sample answer: "Very much — culture shapes how we work, collaborate, and grow. From…
What they're assessing: a positive but realistic answer, with the conditions that would make you stay. Avoid: promising "forever" (not credible) or sounding like you'll job-hop. Sample answer: "I don't like job-hopping and prefer to build depth in one place. I'd plan to stay 3-4…
What they're assessing: that you value sustainability but are realistic about the industry, and can professionally ask back about workload. Avoid: sounding unwilling to ever do extra, or conversely accepting burnout. Sample answer: "Important — sustainable pace is how you go far. I understand crunch…
What they're assessing: that you're balanced and have a life outside work that recharges you — an icebreaker. Avoid: "I just code" (sounds burnout-prone) or oversharing. Sample answer: "I play basketball on weekends, read engineering blogs, and occasionally go to developer meetups. Having activities away…
What they're assessing: a concrete learning process combining theory and practice, not just "reading for awareness". Avoid: a generic "I self-study online". Sample answer: "I read the official docs first to get the foundation, then build a small project to apply it — e.g. I…
What they're assessing: proactive learning and that you actually finished something. Side projects show self-learning better than certificates. Avoid: an unfinished idea with no result. Sample answer: "Most recently I built a personal expense-tracking app with React + Node, deployed for real and used daily.…
What they're assessing: that you proactively use mentoring and turn it into action, not passively wait to be taught. Avoid: "no one" without saying how you still seek people to learn from. Sample answer: "I have a senior dev mentor, with monthly 1-on-1s. I always…
What they're assessing: that you can match your skills to the specific need in the JD, with evidence rather than self-praise. Avoid: listing adjectives ("hardworking, passionate") with no proof. Sample answer: "The JD needs someone who can do performance work and also communicate with the…
What they're assessing: genuine interest and that you've thought about the role. Always prepare 2-3 sharp questions. Avoid: "no, you covered everything" — it reads as indifferent; and don't ask about salary/leave in an early round. Sample answer (questions to ask back): - "What does…
What they're assessing: a strength relevant to the job (with proof), and a real weakness plus how you're fixing it. Avoid: fake weaknesses like "I'm too much of a perfectionist" — everyone sees through it. Sample answer: "My strength is breaking big problems into clear…
What they're assessing: that you stay professional, understand the motive behind difficult behavior, and build trust. Avoid: painting the other person as a "villain" without saying what you did to improve things. Sample answer (STAR): - Situation: a stakeholder kept changing requirements and got sharp…
What they're assessing: that you don't silently absorb it all or decide alone, but clarify priorities transparently across the parties. Avoid: "I do whatever the loudest person wants" or trying to do everything and breaking. Sample answer: "I list the requests with the time each…
What they're assessing: your genuine values, and whether they align with how the company measures success. Avoid: defining success only by title or money. Sample answer: "To me, success is solving real problems for users and being better than I was a year ago. Concretely:…
Interviewers are not measuring who was right; they measure how you argue: whether you reason from evidence, whether you reach a decision, and whether the working relationship survives. STAR outline: - Situation — one line of context: "We had to pick how two services would…
This question checks when you raise the flag and the quality of the information you raise, not your ability to work nights. Four steps worth saying out loud: 1. Escalate as early as possible — the moment you know, not on the morning it is…
What is being judged is whether you can separate the substance from the tone. Blunt reviews are normal on teams with high standards. STAR shape: - Situation — a PR came back with many comments, some written curtly. - Action — three concrete moves: (1)…
This one shows up in nearly every interview. The interviewer wants self-awareness plus evidence you are acting on it, not a reason to reject you. Three-part formula: 1. A real, work-related weakness — but not a core competency of the role you are applying for.…
The interviewer checks two things: whether you can look at failure directly, and whether the lesson is applied or merely stated. How to build the answer: - Define the failure clearly — cancelled, shipped but unused, late enough to lose a client, or rewritten from…
Changing requirements are normal; what is assessed is whether you turn change into a controlled decision or just complain about it. Four things worth saying: 1. Record the change somewhere official — update the ticket, comment on it, or confirm by email. A verbal request…
The interviewer wants to know whether you can work with non-engineering roles, especially when both sides read the same ticket differently. Core principle: bring the argument back to the requirement text and acceptance criteria, not to who said what in which meeting. By counterpart: -…
Common from mid-level up, because the company wants to know whether you can scale capability or only do your own work well. A first-month plan worth describing: - Week 1 — running, with a small win. The goal is that they can set up the…
The interviewer wants a describable ordering scheme, and how you handle work that comes from different managers. Criteria, in order: 1. Blocking others or blocking users — production incidents, a task two people are waiting on. Do it first even if it is small. 2.…
The interviewer wants to know whether you go toward solving the problem or assigning blame, and whether you escalate at the right moment. Order of action: 1. Ask directly and early, in private. Find out the real status and cause: technically stuck, pulled onto other…
Common at outsourcing firms serving Japanese, US and European clients, and at product companies with distributed teams. What is assessed is whether you can work asynchronously. Habits worth naming: - Write first, meet second. Decisions and updates live somewhere searchable (ticket, doc, channel), not in…
Gross is total pay before deductions; net is what actually lands in your bank account. The gap consists of mandatory insurance (social 8% + health 1.5% + unemployment 1% = 10.5% employee share) and personal income tax after family deductions. A concise way to answer:…
You are not obliged to disclose your current salary, but in the Vietnamese market many recruiters still anchor offers on it, so a flat refusal can read as uncooperative. The balanced move is to shift focus from the old salary to the value of the…
The difference comes down to who owns the product and where the money comes from. Outsourcing — building software under contract for overseas clients or other businesses; revenue is per project or per hour. - Upside: exposure to many domains and stacks, well-defined process, onsite…
Under the 2019 Labour Code: - Duration (Art. 25): up to 60 days for roles requiring a college degree or above — which covers most developer positions; 180 days applies only to enterprise managers; 30 days for intermediate qualifications; 6 days for other work. Probation…
General rule: let the company state its band first, since they already have a budget. In Vietnam, though, HR usually asks for expectations during screening to filter fast, so dodging indefinitely just drags the process out. Handle it in this order: 1. Ask back first:…
The best moment to negotiate is after the offer and before signing — the company has already chosen you and does not want to restart hiring. A polite negotiation rarely costs you the offer. Sequence: 1. Thank them and confirm interest first: "I am genuinely…
A gap is not disqualifying; how you narrate it is what gets judged. Answer in three beats: a brief reason — what you did during it — why you are ready now. Template: - "After my previous project ended I took about eight months for…
What the interviewer really wants to know is not "why did you leave" but "will this time be different". Your answer must show the moves follow one consistent direction, not random reactions. Structure: 1. Tie the moves into one arc: "All three moves went the…
Do not overstate your level. Many companies test it on the spot with a few English questions or a client-facing round. Answer honestly, with specifics: - "I am solid at reading technical material and written communication — I read docs daily, write pull request descriptions…
Interviewers worry about two things: how long until you are productive, and whether you will quit halfway. Your answer must address exactly those. 1. Separate what transfers from what you must learn. - Transfers: HTTP, API design, SQL and query tuning, Git, testing, reading logs,…
Years are only a rough proxy. The real difference is the scope of problem you can own and how much supervision you need. - Junior: gets clearly specified tasks, needs careful review, and mostly asks "does this run yet". Value comes from learning speed and…
Core rule: comment on the code, not the person, and give the reason instead of an order. - Replace "you wrote this function wrong" with "this function doesn't handle an empty list; line 42 will throw". - Explain why, so the author learns the principle…
Do not read folder by folder top to bottom — you will drown in detail. Follow a real execution path. An order that usually works: 1. Get it running locally first. Without a working environment, all reading is guesswork. Write down the setup steps, since…
The most reliable method is to break the work down first, then estimate. Estimating a big task by gut feel is nearly always low, because the parts you have not thought of do not show up in the guess. Process: 1. Split until each piece…
Principle: raise it as soon as the signal appears, with options attached — do not grind silently and announce it on the due date. The value of slip information decays fast; three days of warning lets the team react, three hours does not. A structured…
A good small piece is independently runnable and mergeable, does not break main, and can be fully understood in about 30 minutes of review. Common ways to split: - Vertical slices: each piece goes from API down to database for one narrow case, instead of…
Technical debt is design or code knowingly left below standard to move faster now; the gap accrues "interest" in the form of every later change being slower and riskier. Debt is not inherently bad — deliberate debt with a repayment plan is a legitimate business…
The key is not more study hours but attaching learning to the work you already do, so you get repetition and real feedback. How to run it: - Learn with an application target. Pick what you will use in the next 1-3 months (the upcoming…
This question measures how you act when things stop going to plan: what you did yourself (not "what the team did"), how you prioritised and what you learned. How "hard" the story is matters less than how clear your actions are. Picking the story: -…
Unlike the generic "biggest challenge" question, this one will be drilled into technically: the interviewer wants to see how you reason from symptom to root cause and whether you truly understand what you fixed. Present it as an investigation: 1. Symptom and impact — what…
A good answer sits between two extremes: use AI for what it does well, but every line you commit is still your responsibility. The interviewer wants to hear your control process, not "I never use it" or "I let AI write everything". Where AI helps:…
Answer honestly and with conditions: willing to do OT when there is a clear reason (a release, a production incident, a final push), but sustained OT is a sign the plan has a problem that should be raised. The interviewer is probing two things: will…
A good answer is both, in order: learn enough not to break things, then contribute early through small tasks. Picking one side is risky: "contribute immediately" sounds like you will change what you do not yet understand, and "learn for three months" sounds like a…
Answer with specific things tied to this role and this company, in two directions: what you want to learn and what you want to contribute. The interviewer is checking whether you did your homework and whether your expectations match what they can actually offer. How…
The right order is listen and acknowledge → find the cause with data → offer a concrete plan with milestones → follow up on results. This comes up for account/partner management roles at e-commerce platforms, but developers who work directly with clients get similar versions.…
This measures your ability to make progress on your own without silently getting stuck: researching methodically, time-boxing, and when you do ask, asking in a way that costs others as little time as possible. What to say you would do: 1. Clarify the requirement first…
What the interviewer looks for is how you got parties with different goals moving in one direction — finding the shared goal, clarifying who owns what, and settling things in writing instead of letting each side understand it differently. What the story should contain: -…
This checks whether you did your homework and whether your picture of the job is realistic. A good answer restates the role in your own words, ties it to the company's actual product, then links it to your experience. Preparation: - Read the job description…
The most convincing answer is "it depends" backed by examples showing you know when to use which, rather than picking one fixed label. The interviewer wants to know whether you are aware of your strengths and weaknesses when guiding others. How the two differ: -…
The interviewer wants to see that you have a learning method, not just effort: you identify exactly what needs learning, learn by doing, and deliver a concrete result on time. The method your story should show: 1. Scope it: how much does the task actually…
Answer with one real, specific motivation backed by something you have done, then connect it to this role. Interviewers use this question to judge whether you will stay and do well in their environment. Motivations that sound convincing (pick the one that is true for…
This evaluates how you go from question to data to action, and whether you are careful enough not to trust the first number you see. "How you found the insight" is the core — do not just tell the outcome. The process to show: 1.…
Do not grade yourself "I communicate well" — let a concrete example prove it, and honestly name one thing you are improving. For a developer, good communication means others understand you correctly with as few follow-up questions as possible. Communication in IT work includes: -…
For a shared component, your users are other developers, so the most important step is gathering how they use it now and will use it later, before writing any code. Changing the API of a component with ten call sites costs far more than thinking…
The principle: respond quickly so the client knows someone has it, assess the impact, limit the damage before fixing the root cause, and keep updating until it is closed. Clients are often more upset by silence than by the bug itself. Steps: 1. Acknowledge receipt…
The interviewer evaluates your decision-making process, not just whether the outcome was good: did you consider several options, have clear criteria, consult the right people, and own the consequences. What to include: - The decision was yours, or you were the main proposer. Avoid telling…
Answer with concrete experience and the working habits you adjusted: clear written communication, confirming understanding to avoid mistakes, and understanding how the other side works. If you have no such experience, say so and give the closest one you have. Things that commonly come up…
The job is to list everything only that person knows, transfer it by having the receiver do the real work while the departing person is still there, and revoke access at the right time. Long term, a good answer also covers reducing the "bus factor"…
The right approach is to clarify the goal instead of demanding every detail, write down your assumptions, then deliver a small version early to get feedback. At startups or fast-moving product teams, waiting for complete requirements means never starting. Habits worth mentioning: - Ask "what…
The main principle: state your conclusion and what you need them to decide right at the start, in business terms, and only go into detail if asked. Senior leaders have little time and hear many topics a day; a presentation that walks through the technical…
An easy model: the PM/PO decides what to build and when, the BA clarifies what exactly, developers build it, QA checks it is built correctly, DevOps gets it to production and keeps it running. Real boundaries vary by company: on a small team one person…
Answer with your real reason, then show you understand the strengths and weaknesses of that choice. The interviewer does not need to hear that PHP is the best language; they want to know you chose thoughtfully and are not dogmatic about tools. Common real reasons,…
