Interview Q&A

Short answer: Use a Present-Past-Future structure in 60 to 90 seconds: who you are now, what shaped you, and why this role is the logical next step. Keep it role-specific and outcome-driven, not a full life story. End with one line that connects directly to the job description.

Why this matters in Interview Preparation

For this question, interviewers evaluate communication clarity, relevance, and confidence in the first impression.

Step-by-step approach

1. Start with your current role and core expertise in one concise sentence.
2. Add 1 to 2 major achievements from recent work with measurable impact.
3. Briefly mention background context that is relevant to this role only.
4. Explain why you are interviewing now and what scope you are targeting.
5. Close with a role-fit line tied to the company’s product or technical challenge.
6. Practice your version aloud until it sounds natural and under 90 seconds.

Real-world example

Priya, a backend engineer from TCS, kept giving long introductions in interviews and lost panel attention. Rahul from Razorpay helped her rewrite the answer into Present-Past-Future format with one metric-heavy project example. She used that script in a Flipkart interview and the panel moved quickly into deep technical questions. The improved opening changed her confidence and she cleared the round.

What to say / email template

Sample 1 (Fresher): "I am a final-year CS graduate focused on backend development using Java and Spring Boot. During my internship, I built an API monitoring tool that reduced debugging time for the team. I am now looking for an entry-level backend role where I can contribute to production systems and continue growing in distributed architecture."

Sample 2 (1-3 years): "I am currently an SDE at Infosys, working on payment APIs and reliability improvements. Over the last year, I helped reduce critical incident volume by 30% through better retry logic and observability. I am exploring this role because it offers deeper product ownership and larger scale challenges, which align with my next growth goal."

Sample 3 (Experienced): "I lead backend delivery for checkout services at a fintech team, with focus on scalability and release quality. Recently, I drove a migration that improved p95 latency by 22% and reduced rollback frequency. I am now looking for a role where I can combine architecture leadership with hands-on execution in a high-growth product environment."

Mistakes to avoid

• Starting from school history and spending 3+ minutes before role relevance.
• Using generic adjectives like "hardworking" without proof.
• Not tailoring the answer to the company or position.
• Memorizing a robotic script and sounding unnatural.

If your intro exceeds 90 seconds, trim it.

Short answer: Pick strengths that match the role and prove them with real examples. For weaknesses, choose a genuine but non-critical area and show an active improvement plan. Interviewers reward self-awareness plus execution, not fake perfection.

Step-by-step approach

1. Select 2 strengths directly relevant to the target role requirements.
2. Prepare mini-STAR examples for each strength with measurable outcomes.
3. Choose one weakness that is real but improvable and not core-role blocking.
4. Explain the specific actions you are taking to improve that weakness.
5. Close with current progress signal, such as feedback trend or output change.
6. Avoid over-sharing personal issues unrelated to job performance.

Real-world example

Karan at Razorpay used to say his weakness was "I am a perfectionist," which interviewers found generic. Isha from PhonePe helped him choose a real weakness: over-committing to too many tasks in parallel. He then added his improvement plan using weekly prioritization and stakeholder alignment notes. The answer became authentic and credible.

Mistakes to avoid

• Giving cliché weaknesses with no corrective action.
• Choosing strengths unrelated to role needs.
• Turning weakness answer into self-criticism spiral.
• Claiming strengths without measurable evidence.

Authenticity plus improvement trajectory wins here.

Short answer: Technical rounds are cleared through pattern recognition, fundamentals, and communication under pressure. You do not need to solve every hard problem; you need a repeatable process and clean reasoning. Interviewers evaluate approach quality as much as final code.

Step-by-step approach

1. Build a study plan across DSA, language fundamentals, and debugging.
2. Solve curated problem sets by pattern: arrays, trees, graphs, DP, and system basics.
3. Practice thinking aloud while coding to show interviewer your reasoning path.
4. Revise complexity analysis and edge-case handling for every solved problem.
5. Run timed mock interviews weekly and review weak patterns.
6. Prepare project deep-dives because many technical rounds include practical discussions.

Real-world example

Ananya was stuck at coding rounds despite solving problems daily. Vikram asked her to switch from random practice to pattern-based revision and mock interviews. She started verbalizing thought process and validating edge cases before coding. Her next set of interviews at Flipkart and Razorpay showed immediate improvement in round outcomes.

Mistakes to avoid

• Practicing only easy questions and avoiding timed pressure.
• Coding silently and leaving interviewer blind to your reasoning.
• Skipping revision of failed questions.
• Neglecting core CS fundamentals and focusing only on tricks.

Structure beats randomness in technical prep.

Short answer: Answer with a researched range, not a random number or hard anchor. Mention flexibility while signaling that your expectation is market-aligned and role-dependent. This keeps negotiation space open without weakening your position.

Step-by-step approach

1. Research compensation ranges for your role, city, and experience level before interviews.
2. Decide three values: target, acceptable, and minimum walk-away number.
3. Frame your answer as a range tied to role scope and market benchmark.
4. Ask for compensation structure details before final commitment.
5. Stay calm if interviewer asks current salary and redirect to expected value.
6. Confirm revised figures in writing once verbal alignment happens.

Real-world example

Meera used to panic when asked salary expectation and often gave low numbers. Rohit from Freshworks helped her prepare a benchmark sheet and a polished range-based response. In her next interview with Zoho, she gave a confident range and asked for fixed-variable split details. She avoided low anchoring and closed with a better package.

What to say / email template

Based on my experience and current market range for this role, I am targeting [X]-[Y] CTC, depending on final responsibilities and compensation structure. I am flexible and happy to discuss fixed, variable, and growth path to find a fair fit.

Numbers & benchmarks

• Keep range width around 10% to 15% for credible flexibility.
• For stability, many candidates prefer variable component below 20% to 25%.
• Always pre-decide minimum acceptable number before final HR round.

Mistakes to avoid

• Answering with a single number too early in process.
• Saying "any amount is fine" and losing negotiation leverage.
• Ignoring compensation structure and focusing only on CTC headline.
• Giving different expectations across rounds.

Range + rationale = confident salary answer.