A mock interview is a simulated interview that mirrors the format, questions, and pressure of a real job interview, conducted by a mentor, coach, peer, or even an AI tool. Its purpose is to let you practise answering out loud, get honest feedback on your communication and structure, and fix gaps before the actual interview. For freshers it builds confidence before campus placements, while for experienced professionals it fine-tunes role-specific storytelling and reduces anxiety in the real room.

Start by studying the job description and shortlisting the likely questions — technical, behavioural, and role-specific. Prepare STAR-format answers for your key projects, revise your fundamentals, and pick a quiet, on-camera setting that mirrors a real interview. Practise with a peer, a mentor, or a structured mock interview session with an experienced professional, and record yourself so you can review your tone, pace, and filler words. Treat every mock like the real thing — no reading from notes.

You can practise through peer communities, AI-based interview tools, or 1:1 mock sessions with industry mentors on platforms like Topmate. The most effective way is to share the exact job description with your mock interviewer so the questions match the role you're targeting. Do at least two or three rounds, note the feedback from each round, and work on one weakness at a time — structure, depth, or communication.

Paste a job description into an AI tool, ask it to act as the interviewer, and answer every question aloud just as you would in the real interview. AI is excellent for building fluency, generating likely questions, and rehearsing at any hour. The limitation is that it cannot fully judge nuance, presence, and domain depth the way an experienced human interviewer can, so the best approach is to warm up with AI drills and then take at least one or two human mock interviews for realistic feedback.

Free options are a good starting point — they help freshers get comfortable speaking about projects and answering common HR questions before placements. The gap is that free and AI-only practice rarely reproduces the pressure and probing follow-ups of a real interviewer. For high-stakes roles, combining free practice with one or two mock interviews taken by an experienced industry mentor usually gives much sharper, role-specific feedback.

Job interview preparation is the end-to-end process of getting ready — researching the company and role, revising technical or domain fundamentals, building structured answers for behavioural questions, and planning how you'll present your resume. Two to four weeks works well for most roles, while competitive FAANG-style loops often need two to three months of consistent preparation. The goal is to walk in with rehearsed stories and fundamentals, not memorised scripts.

Begin with a clear plan: revise DSA or your core domain fundamentals, add system design if you're targeting senior roles, and build behavioural stories around your actual projects. Use company-specific material — Leadership Principles for Amazon, Googleyness-style prep for Google — and practise mock interviews with people who have cleared those loops. Since most candidates in India prepare alongside a full-time job, scheduling two to three months of steady preparation works far better than last-minute cramming.

A practical roadmap spans roughly eight to twelve weeks: the first four weeks on data structures, algorithms, or core technical fundamentals; the next four on system design and role-specific depth; and the final two on behavioural stories mapped to the company's values plus full-length timed mocks. Track progress weekly and adjust the split based on your target company and experience level. Taking a mock interview early in the roadmap helps you benchmark where you actually stand.

For most experienced professionals, two to three months of focused preparation alongside a job is realistic — especially if you're returning to coding fundamentals after years in delivery or management roles. Senior candidates should weight their time towards system design, leadership and behavioural rounds, and role-specific depth rather than only problem-solving drills. Taking an early mock with a mentor from a FAANG background gives you an honest benchmark before you start applying.

First research market benchmarks for the role and your experience level, and where possible let HR state the first number. Respond to the offer positively, then present a justified range anchored to your current compensation, skills, and market data — never an unexplained demand. Once agreed, get the final figures, including bonus, stocks, and notice-period terms, in writing before accepting. A calm, data-backed conversation almost always lands better than aggressive bargaining.

A good example follows a simple structure — thank HR for the offer, show genuine interest in the role, then anchor with data: "Based on my current package and market benchmarks for this role, I was expecting something in the range of X to Y. Is there flexibility on the fixed component?" Strong examples always ask about the total compensation, including variable pay, joining bonus, and stock, and close by asking what is possible rather than issuing an ultimatum. Practising this conversation out loud beforehand helps you sound confident instead of rehearsed.

Research the pay band for the role before the discussion, never reveal the minimum you'll accept, and negotiate the total CTC rather than only the fixed pay. Use market data or a competing offer as leverage without making empty threats, and ask for improvement in one or two specific components — fixed pay, joining bonus, or stocks — instead of vaguely asking for "more". Always negotiate after the offer is in writing, not during early screening rounds.

Offers are almost never withdrawn for polite, well-reasoned negotiation — recruiters build negotiation room into most offers and expect the conversation. This is exactly why you should always negotiate salary: accepting the first number often locks in a lower base, and future increments are calculated on that base for years. Handled professionally, the worst realistic outcome is HR saying the number is fixed, and you've lost nothing by asking.

In India, most salary negotiations wrap up within three to seven working days once an offer is on the table, though approvals for senior roles or out-of-band requests can stretch to two weeks or more. The delay is usually internal — hiring manager sign-off or compensation-team approval — and is not a signal that the offer is gone. If there's no update for over a week, follow up politely and set a decision deadline that protects your other offers.

A salary negotiation letter is a short, formal email sent after receiving a job offer, in which you make a counteroffer with a specific range and the reasons behind it — market benchmarks, your current compensation, or specialised skills. The tone should stay appreciative and the ask should be precise, covering components like fixed pay, bonus, and equity. It is best sent by email right after the offer call, and always before the acceptance deadline mentioned in the offer letter.