HR questions

The HR round (the interview with the human resources team, about you rather than technical skills) feels easier than the technical ones, yet candidates lose offers here by being vague, negative or untruthful. Most HR questions check one thing: that your expectations, your reasons for moving and your situation fit the job. Everything you say can be checked later, through payslips (your monthly salary documents), background checks (the employer's checks of your past jobs and details) and the technical rounds, so honest answers that you have prepared work best.

Why are you changing jobs?

Give a true reason that points towards the new role: more automation or API work (testing by sending requests to a server), a product you care about, a more mature engineering team, growth you cannot get where you are, or a move to another city. Leave out criticism of your current manager or company; the interviewer will assume you would talk about them the same way. If pay is part of it, you can say it is one factor, but lead with the work.

Example to adapt: "I have learned a lot testing our billing module, but there is little automation work left there. I want automation and API testing to be my main work, which is what this role offers."

Why this company?

Spend fifteen minutes on research before each interview: what the company sells and to whom, recent news, its engineering blog or careers page, and the job description in detail. Then connect what they do, what the role needs and what you bring. One specific detail beats general praise such as "big brand" or "good culture".

Salary, notice period and joining date

Research the market range for the role, the city and your experience, using job sites, salary surveys and people in similar roles. Give a range whose lower end you would accept, and say what it is based on. If asked for your current salary, state it truthfully; many companies verify it. In some places, such as several US states, employers may not ask about pay history, and there you can give your expected range instead.

State your notice period (how long you must keep working after you resign) exactly as your contract says, and mention ways to shorten it only if they are really possible. Give a realistic joining date; promising an early date and then missing it damages trust before you start. If you hold another offer, you can say so honestly without using it as a threat.

Strengths, weaknesses and achievements

Choose strengths that matter for testing and prove each with a short example. For a weakness, pick a real one that does not stop you doing the job, and say what you are doing about it. "I work too hard" is a strength in disguise, and interviewers recognise it. For an achievement, tell one measured result in STAR form (situation, task, action, result).

Five-year plans, relocation and gaps

For "where do you see yourself in five years?", give a direction rather than a job title, such as designing test strategy and helping newer testers, and name the skills you are building now.

For client sites (the offices of the customer you work for), relocation (moving to another city) and shifts (working hours such as nights or weekends), decide your real limits before the interview. If you are open, say so. If you have limits, state them and offer what you can, such as travel for a few weeks or three office days a week. You do not have to explain private reasons in detail.

For a career gap, give a short, honest reason (private details are optional), show how you kept your skills current, such as a course or a practice project, and say why you are ready now. Never hide a gap with false dates; background checks usually find it.

Your questions for them

Always ask two or three. Good ones for a testing role: how testers are involved before development starts, what the automation set-up (the tools and tests they already have) looks like and what the team wants to improve, how release decisions are made, and what success looks like after three months. Avoid questions about leave and salary in early technical rounds, and questions the company website already answers.

How to answer in an interview

Keep each answer under a minute, true, and pointed at the job you are interviewing for. Prepare short answers to each question in this topic, put in your own facts, and say them aloud a few times before the day.

Common mistakes

• Complaining about your current employer.
• A salary figure with no research behind it.
• A joining date you cannot meet.
• Saying yes to relocation now and refusing after the offer.

Recap

Every HR answer can be checked, so a plain, true answer with a positive angle is always safer than an impressive one you cannot support.