HR, Behavioural & Salary Round — Interview Questions

In short: Use Present → Past → Future in 60–90 seconds.

• Example: "I'm a .NET developer with 5 years' experience in C#, ASP.NET Core, SQL Server and Azure.
• Currently I build payment reconciliation APIs at ABC, where I cut the nightly batch from 3 hours to 25 minutes by moving row-by-row processing to set-based T-SQL and parallel jobs.
• Earlier at XYZ I built SSIS/SSRS reporting for a banking client and set up Azure DevOps CI/CD.
• I'm looking for a role building cloud-native, high-scale services — which is why this Azure platform role interests me." Tailor the achievements to the job description.

In short: Connect three things: the role's needs, your proof, and your attitude.

• "You need someone who can build and run .NET services on Azure and improve performance.
• I've done exactly that — for example, I reduced API p95 latency by 60% with caching and query tuning, and I set up the CI/CD pipeline my team uses today.
• I also communicate well with business users, and I'm keen to keep learning, as my recent AZ-204 certification shows.
• I can contribute from the first month."

In short: Pick two or three that matter for the role and prove each with a short example.

• "First, problem-solving under pressure — I led the fix for a production payment outage within 40 minutes by isolating a failing dependency and switching to a fallback.
• Second, ownership — I don't stop at 'code complete'; I add monitoring and documentation.
• Third, learning quickly — I picked up Angular in a month to help our frontend team meet a release."

In short: Choose a real but manageable weakness and show improvement.

• "I used to find it hard to say no to extra requests, which once put a sprint commitment at risk.
• I've learned to make trade-offs visible: when a new request comes in, I ask my lead or product owner what should move out, and I track everything in Jira.
• Over the last three sprints we met all our commitments."

In short: Show research and fit: company → role → you.

• Mention the product/domain, something specific (tech stack, engineering culture, growth, customers), and how your experience matches.
• Avoid answers about salary only or "it's a big brand".
• Example: "Your platform serves banks across Asia, and I've spent three years on banking data systems.
• This role combines .NET microservices with Azure, which is where I want to grow, and your focus on automated testing matches how I work."

Stay positive and future-focused: "I've had a great learning experience and delivered X and Y, but the project has moved into maintenance, and I'm looking for larger-scale, cloud-native work and more ownership, which this role offers." Never criticise your employer, manager or colleagues, and keep it consistent with what's on LinkedIn and your resume.

In short: Show realistic ambition aligned with the company's path: "I see myself as a senior engineer or tech lead owning a product area's architecture, mentoring developers and working closely with business stakeholders, with deeper Azure architecture expertise.

• I'd like to grow into that here." Avoid "running my own startup" or "in your job".

In short: STAR, showing empathy and resolution — not blame.

• "S: A senior QA and I disagreed on releasing a hotfix — he wanted a full regression; I worried about the client's outage.
• T: We needed a decision within the hour.
• A: I spoke with him privately, understood his concern about a past incident, and proposed a targeted regression of affected modules plus a rollback plan, then we presented both options to the lead together.
• R: We released in 90 minutes with no new defects; since then we keep a 'hotfix test checklist' we built together, and we work well."

In short: Choose a genuine mistake with low-to-moderate impact, own it, and show learning.

• "I once deployed a database migration that locked a large table during business hours, causing 10 minutes of slow responses.
• I rolled back immediately, informed my manager and the client, and redid it off-hours in batches.
• I then added a pre-deployment checklist for migrations — size checks, off-peak scheduling and a tested rollback script — and we haven't had a repeat."

In short: Use STAR with planning and communication.

• "When a client moved a release forward by two weeks, I prioritised by risk, automated repetitive validation with scripts, split tasks with two teammates, and gave daily status updates highlighting risks early.
• We delivered three days early with zero UAT defects." Emphasise calm prioritisation, not heroic overtime.

In short: Pick a professional achievement relevant to the role, with a measurable result and your personal contribution.

• "Re-architecting our report generation: reports took up to 20 minutes and often timed out.
• I profiled the queries, introduced pre-aggregated tables refreshed by SSIS, moved generation to a background queue with email delivery, and added caching.
• Average time dropped to under 30 seconds, and support tickets on reports fell by 80%."

In short: "I treat feedback as information to improve.

• I listen without being defensive, ask for specific examples, and agree on what to change.
• For example, my lead said my PRs were too large to review; I started splitting work into smaller PRs with clear descriptions.
• Review time dropped from days to hours, and I now give feedback to others the same way."

In short: "I first clarify impact and deadlines with stakeholders, then sort by urgency and importance (production issues and blockers first, then committed sprint work, then improvements).

• I break tasks into smaller pieces, track them in Jira, communicate early if something will slip, and ask my lead to arbitrate real conflicts rather than silently missing a deadline."

In short: Be honest and professional: thank the first company, express genuine interest, and ask for a reasonable timeline to decide ("Could I confirm by next Friday?").

• Inform the second company that you have an offer and a deadline to see if they can speed up.
• Compare on role, learning, team, stability, compensation and location — not just salary.
• Once you accept, honour it; reneging after accepting damages your reputation (and in India some companies share data on offer drop-outs).

In short: Raise the concern immediately with facts: explain the risk, likely impact and evidence, and propose alternatives (a safer approach, a feature flag, a staged rollout, more testing).

• Put it in writing (email/ticket) so the decision is documented.
• If the manager still decides to proceed and it isn't unethical or illegal, execute it as safely as possible with monitoring and a rollback plan.
• If it's unethical or illegal (e.g. data privacy violation), escalate through proper channels.

In short: Answer in three parts: reason, activity, readiness.

• Example: "My role was affected by a restructuring in early 2025.
• I used the time to deepen my skills — I completed the AZ-204 certification and built a full-stack project with ASP.NET Core, React and Azure that's on my GitHub — and I also did a three-month freelance contract building APIs for a logistics client.
• I'm now fully ready and looking for a long-term role where I can contribute from day one." Keep it calm, factual and short, then move on.

In short: Give a researched range tied to the role: "For a senior .NET developer role with Azure responsibilities in Pune, market data and my experience put my expectation at ₹22–25 lakhs fixed.

• I'm open to discussing the full package, including variable pay and growth." If it's very early, you can ask to learn more about the role first, but don't avoid answering entirely if they insist.

In short: State your current CTC honestly with its breakup (fixed vs variable).

• Justify the expectation with market value, expanded responsibilities in the new role, skills you bring (e.g. cloud, leadership), and competing offers if real.
• Example: "My current CTC is ₹12 LPA, of which ₹10.5 is fixed.
• My current salary is below the market median because I've been with the company since joining as a fresher, while my responsibilities have grown to leading a module and owning CI/CD.
• The market range for this role is ₹18–22 LPA, which is the basis for my expectation."

In short: "No — it was part of a company-wide restructuring that affected about 20% of the engineering team after a client contract ended.

• My last review rated me 'exceeds expectations', and my manager is happy to give a reference.
• I've stayed active since — I completed a certification and built a project with the latest .NET." Only say this if it's true; offer references.

In short: Show evidence, not just interest: "In my support role I wrote C# tools and SQL scripts that automated incident triage, saving about 10 hours a week.

• Over the last year I built two applications with ASP.NET Core and React (on GitHub), completed a .NET certification, and contributed bug fixes to our internal product with my lead's approval.
• My production-support background helps me write more reliable, debuggable code."

In short: Respond politely and with data: "Thank you.

• I'm keen on this role.
• However, a 15% increase puts the offer below the market range for this position, and below another offer I'm considering.
• Would there be flexibility to reach ₹X fixed, or to add a joining bonus and a salary review after six months?" If they can't move and you still want the job, decide based on the whole picture;
• if not, decline gracefully.

In short: Express enthusiasm and ask for time to review.

• Calculate the in-hand amount and compare with market data and your walk-away number.
• Then make one well-justified request covering the specific gap, and offer alternatives (joining bonus, earlier appraisal, a higher designation, a relocation allowance, remote days).
• If they can't move, decide consciously: accept if the role's learning, brand or stability is worth it, or politely decline.
• Either way, get the final terms in writing.

In short: Contact HR immediately and explain transparently — for example, the resume used the project start date while the official joining date was a month later, or a notice period was shortened.

• Provide documents (offer and relieving letters, payslips, PF/UAN service history).
• Small honest discrepancies can usually be resolved; deliberate misrepresentation usually leads to offer withdrawal.
• Prevent it by using official dates on your resume.

In short: Structure: business context → architecture → your role → tech stack → one challenge with a measurable result → process.

• Example: "I work on a loan-origination system for a European bank.
• It's an Angular frontend calling ASP.NET Core Web APIs, with SQL Server and Azure Service Bus for integration with the credit-scoring service, hosted on Azure App Service.
• I own the document-verification module and the reporting APIs.
• A key challenge was slow PDF generation timing out under load;
• I moved it to a background worker with Service Bus and blob storage, cutting API response time from 25 seconds to under 1 second.
• We work in two-week sprints with Azure DevOps pipelines and mandatory code reviews."

In short: Mention exposure to multiple clients, domains and technologies;

• structured training and certifications;
• global delivery experience;
• career paths (technical or managerial);
• and the company's specific strengths (a major client in your domain, a cloud or AI practice, a location).
• Example: "Working with global clients across banking and retail would broaden my domain knowledge.
• Your Microsoft cloud practice is strong, and your certification programmes would help me move towards solution architecture."

In short: Answer honestly with any constraints: "Yes, I'm comfortable with overlap with UK or US hours and occasional on-call support.

• I'm primarily a .NET developer but I've also worked on Angular and SSIS, and I'm open to learning what the project needs.
• I'd prefer Pune or Bengaluru, but I'm open to discussing other locations." Ask how often shifts rotate.

In short: These tests typically cover quantitative aptitude, logical reasoning, verbal ability, programming fundamentals and one or two coding problems, all under time pressure, with proctoring.

• Prepare with timed practice (aptitude books/sites, previous-year style questions), master one language for coding (input/output handling, strings, arrays), revise OOP, DBMS/SQL and OS basics, and read the official registration page for the current pattern, since sections change between years.

In short: "S: My manager wanted to ship a reporting feature by computing aggregates on every request.

• T: I believed it would overload the database at month-end.
• A: I gathered data — query costs and expected month-end traffic — and proposed pre-aggregating nightly with a fallback for today's data.
• He disagreed because of the timeline, so we agreed on a quick load test; the on-request version exceeded our latency target by 4×.
• R: We implemented my approach in 2 extra days; month-end reports stayed under 2 seconds.
• Had the test gone the other way, I'd have committed fully to his design." Show data, respect and commitment.

In short: Pick a story where you went beyond the ticket to understand the user's real problem: "Customers kept calling support about failed payments.

• Instead of just fixing the error message, I analysed 3 months of logs and found 40% of failures came from one bank's timeout.
• I added retries with idempotency keys and a clear status page for pending payments.
• Support calls on payments dropped by 60%." Quantify customer impact.

In short: "Our API had random 5-second spikes.

• Dashboards showed nothing obvious, so I collected traces and found the spikes coincided with Gen 2 garbage collections caused by large JSON payloads (over 85 KB) landing on the Large Object Heap.
• I switched to streaming serialisation and paginated the responses.
• P99 latency dropped from 5.2 s to 300 ms." Show detailed investigation and data.

In short: Clarify requirements and constraints (input size, edge cases), talk through examples, state a brute-force solution with its complexity, optimise (hash map, two pointers, sorting, BFS/DFS, DP), write clean code while explaining, test with examples and edge cases, and state time and space complexity.

• Communicate throughout — interviewers evaluate problem solving and communication, not just the final answer.

In short: Requirements: shorten URLs, redirect fast, custom aliases, expiry, analytics; read-heavy (say 100:1).

• API: POST /urls → short code; GET /{code} → 301/302 redirect.
• ID generation: base62 encoding of a unique ID (from a distributed ID generator or a pre-allocated range per server) to avoid collisions, or random codes with collision checks.
• Storage: key-value or SQL table (code PK → long URL, created, expiry, owner); cache hot codes in Redis; CDN/edge for redirects.
• Scale: stateless app servers behind a load balancer, DB replication/sharding by code, async analytics via a queue.
• Discuss 301 vs 302 (caching vs analytics), abuse/malware checks and rate limiting.

In short: Common base: strong project explanation, C#/.NET/SQL fundamentals, behavioural stories.

• Services company: emphasise breadth (C#, ASP.NET Core, EF, SQL, Azure basics), client communication, flexibility, and classic coding programs.
• Product company: practise DSA problems by pattern (timed), system design for your level, and values-based behavioural stories (e.g. Amazon LPs), and write code without IDE help.
• Schedule the harder one later if possible, and use one as practice for the other.

In short: Ask the recruiter politely for feedback (not always shared).

• Write down every question you were asked the same day and identify gaps.
• Create a focused plan (e.g. 4 weeks of DSA patterns or system design) and practise with mock interviews.
• Many companies allow re-applying after a cooling-off period (commonly around 6–12 months, depending on the company) — check the policy and re-apply stronger.
• Meanwhile, keep interviewing elsewhere for practice.