Blog
Notes on interview preparation, hiring, and building Prepair.
Why a candidate who's practiced salary negotiation is easier to hire, not harder
Recruiters often brace for negotiation as friction. A candidate who's rehearsed the conversation tends to be faster to close, not slower — here's why that's not a contradiction.
Negotiating the Full Package in Singapore and Hong Kong — CPF, MPF, Housing, and Relocation
Base salary is only part of a Singapore or Hong Kong tech offer. Here's how to think about CPF/MPF, bonus structure, housing allowance, and relocation terms when negotiating.
How to Negotiate a Signing Bonus in Singapore and Hong Kong Tech
A practical guide to asking for a signing bonus in Singapore and Hong Kong tech hiring — when it works, realistic ranges, and how it differs from pushing on base salary.
Salary Negotiation FAQ for US Job Seekers
Straight answers to the questions that actually block people from negotiating — when to bring up pay, whether it's rude, what "final offer" really means, and what Prepair's practice tool does and doesn't do.
Salary Negotiation FAQ for Indian Job Seekers
Direct answers on sharing your current CTC, what hike is realistic, handling "the offer is final," and whether Prepair's negotiation practice covers CTC-structure math.
Salary Negotiation FAQ for Canadian Job Seekers
Direct answers to the questions Canadian job seekers actually ask about negotiating salary — is it rude, what's a fair counter, how much RRSP matching matters, and more.
Salary Negotiation FAQ for Singapore & Hong Kong Tech Job Seekers
Straight answers to common questions about negotiating tech job offers in Singapore and Hong Kong — is it culturally acceptable, what's a reasonable counter, and does salary disclosure matter.
Negotiating notice period buyout, joining date, and other non-salary terms in India
Notice period buyout is a real, distinct negotiation in Indian hiring that most other markets don't have. Here's how to negotiate it, plus joining date and relocation, without losing the offer.
How to Respond to a Lowball Offer in Singapore or Hong Kong Tech
Got a tech offer in Singapore or Hong Kong that's well below what you expected? Here's how to figure out if it's actually a lowball, and how to counter it without sounding offended.
How to respond to a lowball offer or a hike below expectations in India
A hike offer that's well under 20% isn't automatically an insult, but it isn't automatically fair either. Here's how to tell the difference and respond without burning the offer.
How to negotiate a joining bonus in India — when it works and when it doesn't
Joining bonuses in Indian offers come with clawback clauses and fine print most candidates skip. Here's how to actually ask for one, and what to check before you do.
How to Respond to a Lowball Job Offer
An offer came in well below what you expected. Here's how to respond without burning the relationship — and how to tell a real lowball apart from a fixed band you can't move.
How to Respond to a Lowball Job Offer in Canada
Got a Canadian offer that came in well under what you expected? Here's how to figure out if it's actually a lowball, and how to counter without burning the relationship.
How to Negotiate Remote Work and Relocation Terms
A verbal "sure, remote is fine" isn't a policy. Here's how to get flexibility in writing and negotiate a relocation package as its own line item, not an afterthought to salary.
How to Negotiate Equity and Stock Options at a Canadian Tech Company
Stock options at a Canadian startup work like their US counterparts on paper, but the numbers and market context are different. Here's how to evaluate and negotiate equity without over-anchoring on Silicon Valley figures.
How to Negotiate Equity and Stock Options in a Job Offer
RSUs at a public company and options at a startup are negotiated differently, and the number on the offer letter tells you less than it looks like. Here's what to actually ask.
How to Negotiate Total Compensation in Canada (Not Just Salary)
RRSP matching, extended health, vacation, and flexibility often move more easily than base salary in Canada. Here's how to evaluate and negotiate the whole package, not just the number on top.
How to Negotiate a Signing Bonus
A signing bonus is often the easiest number to move in a US job offer. Here's when to ask, how to justify it, and what a repayment clause actually means for you.
How to Negotiate a Signing Bonus in Canada
When a Canadian employer can't move on base salary, a signing bonus is often the easier ask. Here's when it works, how to frame it, and what to expect in dollars.
How to Negotiate a Counteroffer From Your Current Employer
Your current employer countered after you gave notice or mentioned another offer. Here's how to think about it clearly, before a bigger number talks you out of leaving for the wrong reasons.
How to Negotiate a Counteroffer From Your Current Employer (Canada)
You resigned and your Canadian employer countered. Here's how to think it through clearly — what counteroffers actually fix, what they don't, and how to respond either way.
How to negotiate ESOPs at an Indian startup — what to ask before you say yes
An ESOP grant number means very little without vesting terms, strike price, and a real answer on liquidity. Here's what to actually ask before treating equity as part of your compensation.
How to Negotiate Equity and Stock Options at a Singapore or Hong Kong Startup
Vesting, cliffs, strike price, and dilution — how to evaluate and negotiate an equity offer at a Singapore or Hong Kong tech startup, and why comp data here needs more legwork than the US.
How to handle a counteroffer from your current employer in India
Your manager just matched or beat the new offer to keep you. Here's the honest, India-specific pattern behind retention counteroffers, and how to decide without regretting it in six months.
How to Handle a Counteroffer From Your Current Employer (Singapore & Hong Kong Tech)
You resigned and your manager countered. Here's how to think through a retention counteroffer in Singapore and Hong Kong tech, and why the reasons you wanted to leave rarely disappear with a bigger number.
Salary negotiation tips for India — why the CTC number isn't the whole negotiation
In Indian hiring, the headline CTC hides most of what actually matters — fixed-variable split, retirals, joining bonus. Here's how to negotiate the package, not just the number.
How to negotiate a CTC offer — a step-by-step walkthrough
A practical, line-by-line way to read an Indian offer letter's CTC breakup, spot a badly structured variable-pay trap, and use it — plus a competing offer — to actually negotiate.
How to Negotiate a Job Offer (Without Blowing It)
You have an offer in hand. Here's how to counter it — anchoring, using competing offers, negotiating the full package, and the one situation where you shouldn't push at all.
How to Negotiate a Job Offer in the UK (Without It Feeling Like a Showdown)
A practical guide to countering a UK job offer — what to push on beyond base salary, how to use evidence without sounding aggressive, and why most UK employers already budgeted room to move.
How to Ask for a Raise (When You're Already Employed)
Asking your current manager for a raise runs on different rules than negotiating a new offer. Here's how to build the case, time it right, and understand what your manager actually controls.
How to Ask for a Pay Rise in the UK (Timing, Evidence, and What to Actually Say)
When to raise it, how to build a case your manager can actually act on, and what a realistic pay rise looks like in the UK — plus how to rehearse the actual conversation first.
UX/UI designer interview questions — why "walk me through your process" is the whole interview
Portfolio reviews look like a presentation, but they're graded like an interview. Here's what's actually being scored while you're clicking through your own case study, and where most designers lose points without noticing.
UX/UI designer interview questions for the Indian market — what product companies actually screen for
Design hiring at Indian product companies leans harder on measurable impact and localization thinking than global portfolio-review advice usually accounts for. Here's what shifts.
System design interview questions — what "design a URL shortener" is actually testing
The prompt is always vague on purpose. Here's what a system design round is really scoring, the questions that come up across every prompt, and why the diagram matters less than the trade-offs you say out loud.
Questions to ask the interviewer — the ones that actually tell you something
"Do you have any questions for us?" is graded too, and most people ask something that gets a rehearsed answer. Here's what to ask instead, and how to tell a real answer from a recruiting-brochure one.
Project manager interview questions — the ones that separate "ran meetings" from "ran a project"
Certifications and methodology names get you in the door. What actually gets scored is whether you can describe a specific moment a project went sideways, and what you did before it became a crisis.
Project manager interview questions for the Indian IT services market — what's weighted differently
PM hiring at Indian IT services firms and product companies asks the same core questions as anywhere, but client-facing pressure, distributed teams across time zones, and certification expectations shift what actually gets weighted.
Product manager interview questions — why "how would you improve this product" has no right answer
PM interviews look unstructured compared to engineering rounds, but they're scored just as precisely. Here's what the classic prompts are actually checking, and where most candidates lose points without realizing it.
Product manager interview questions for the Indian market — what changes at product-based companies
PM hiring at Indian product companies (and the product arms of IT services firms) leans on the same core questions as anywhere else, with a few local specifics — case studies grounded in Indian market context, and a heavier bar on execution over vision.
Marketing interview questions — why "grow this metric" answers are scored on what you'd measure, not what you'd try
Every marketing candidate has a list of growth tactics ready. The interview is decided by whether you can name what would prove the tactic actually worked, before you're asked to.
Marketing interview questions for the Indian market — what shifts at D2C and product-led companies
Marketing hiring in India — especially at D2C brands, edtech, and fintech — leans harder on budget efficiency and regional/language segmentation than generic global marketing interview advice accounts for.
iOS Swift interview questions — the follow-ups that expose whether you've shipped, not just studied
ARC, optionals, protocol-oriented programming — every iOS candidate can define them. The interview is decided by the follow-up that asks what breaks in production when you get it wrong.
HR round interview questions — what's actually being decided in the round everyone underrates
The HR round isn't a formality after the "real" technical interview. It's where salary expectations, notice period, and offer decisions actually get made — here's what each common question is really checking.
DBMS interview questions — the ones that separate "memorized the definition" from "used it"
Normalization, ACID, indexing, joins. Every fresher can define them. The interview is decided by the follow-up question that asks you to use the concept, not recite it.
Core Java interview questions — the follow-ups that catch people who only memorized syntax
Every candidate can define OOP, collections, and exception handling in Java. The interview is won or lost on the follow-up question that asks why the language works that way.
Coding interview questions — what changes once you stop treating it as a LeetCode problem
Most coding interview advice is about which algorithm to memorize. The actual differentiator is what you do in the five minutes before you write any code, and the sentence you say after you finish.
Is a Mock Interview App Actually Worth Using?
What a mock interview app solves that a friend or a mirror doesn't, what it can't solve at all, and a plain decision framework for when to use one.
AI Mock Interview — How It Actually Works, and When It's Worth Your Time
What happens mechanically when you use an AI mock interview, what it can and can't tell you, and when it's the right tool versus a waste of an evening.
AI Mock Interview FAQ for US Job Seekers
Does an AI mock interview cover FAANG-style loops, system design, and behavioral rounds? Honest answers on what it does and doesn't replace in a US tech hiring process.
AI Mock Interview FAQ for Indian Job Seekers
Straight answers on whether an AI mock interview tool actually helps with Indian hiring rounds — technical, HR, freshers, campus placements, accents, and pricing.
What an AI Interview Simulator Actually Simulates
The word "simulator" promises more realism than these tools deliver. Here's the specific, narrower thing that actually gets rehearsed — and the parts of a real interview that don't survive the simulation.
The technical interview — what actually differs from every other round
A technical interview isn't just "the hard round." It's testing a specific, narrower thing than the rest of the process — and prepping for it like a behavioral round is why strong engineers still stumble.
Spring Boot interview questions — the ones that check understanding, not vocabulary
"@Autowired, bean scopes, the difference between @Component and @Bean." Everyone can name these. The interview isn't over until you can explain what breaks if you get them wrong.
Situational interview questions — why "what would you do" is harder to fake than it looks
Situational questions feel easier than behavioral ones because you can just make up a reasonable-sounding answer. That's exactly what interviewers are trained to notice.
Selenium interview questions — the ones that separate "wrote a script" from "maintained a suite"
Anyone can find an element and click it. The interview is testing whether your tests still pass six months later, when the page has changed and the suite runs against real load.
React interview questions for experienced developers — past the "what is a hook" stage
For experienced React developers, interviews stop asking what useEffect does and start asking why your app re-renders three times when it shouldn't. Here's what that level of question actually looks like.
Power BI interview questions — where "I built a dashboard" gets tested for depth
Almost every analyst can build a dashboard. Power BI interviews are designed to check whether you understand the data model underneath it — because that's what breaks first at scale.
OS interview questions — why "explain a process vs a thread" still gets asked in 2026
Operating systems theory looks like the most irrelevant part of a coding interview. It isn't — it's a proxy for whether you understand what your code is actually doing underneath the framework.
OOPs interview questions — the four concepts everyone lists and almost nobody can defend
Encapsulation, inheritance, polymorphism, abstraction. Every candidate can define them. Almost none can answer the follow-up that actually decides the interview — why does it matter here.
Mock interview questions — why practicing alone doesn't train the skill you actually need
Reading a list of practice interview questions trains recall. A mock interview trains something reading can't — producing an answer out loud, in real time, while someone is listening and can ask a follow-up.
MERN stack interview questions — the ones that check if you understand the seams
A MERN interview isn't four separate quizzes on MongoDB, Express, React, and Node. The real questions live at the seams — where data crosses from database to API to client, and where things quietly break.
Interview questions for freshers — what the first round is actually testing
Freshers over-prepare for the wrong round. The first technical interview isn't testing what you know — it's testing whether you can think out loud about what you don't.
How to prepare for an interview — the checklist that actually matters, not the one that feels productive
Rereading your resume and researching the company feels like preparation. Most of it doesn't move the needle. Here's what actually predicts how an interview goes.
DSA interview questions — what's actually being measured behind the LeetCode grind
Data structures and algorithms interviews look like they're testing whether you know a hundred problems. They're actually testing three much smaller things. Here's what those are, and how to prepare for them instead of the problem count.
Django interview questions — where "it just works" stops being a good enough answer
Django hides a lot of complexity behind clean abstractions. The interview is testing whether you know what's happening underneath, especially in the ORM.
Computer networks interview questions — the layer where "it's slow" actually gets diagnosed
TCP vs UDP, the OSI model, DNS lookups — networking questions look academic until you're the one debugging why a service times out under load and nobody else on the team can explain what's happening at the socket level.
The most common interview questions — and the answer structure that actually works for each
The same dozen questions show up in almost every interview, in almost every industry. Here they are, with what a strong answer to each one actually contains — not just an example script to memorise.
Behavioral interview questions — why the STAR method isn't the point
"Tell me about a time you..." questions aren't testing whether you know the STAR method. They're testing whether the story you tell is actually yours. Here's what separates a memorised answer from a real one.
Angular interview questions — what change detection questions are actually checking
Everyone can define change detection. The interview is really testing whether you've ever had to fix a UI that stopped updating, and whether you know why it did.
Null is not a measurement
I shipped attribution, wrote tests for it, and ten days later every row was empty. I read that as "too early to tell". It meant the code had never run once — and the second bug in it was worse, because it would have produced an answer instead of a blank.
The interview is in a week and you cannot learn everything
With seven days left, most preparation advice is useless because it assumes you have a month. Here is what actually moves the outcome in a week, in the order that matters, and what to deliberately skip.
What an AI copilot costs you in a real interview
A whole category of tools now feeds you answers live during the interview. Having sat on the hiring side for ten years, here is what actually happens when someone uses one — and the narrower case where they are worth it.
Your job posting has 250 competitors. Here's what happens after you beat them.
The average job opening gets around 250 applications, and only 4-6 people ever get an interview. If you're one of them, that filter already did the hard part — the mistake is treating the interview like just one more step instead of the rare shot it is.
The SQL interview question that predicts who finds the bug
Most SQL questions for QA test whether you remember JOIN syntax. The ones that matter test whether you'd think to check the database at all. Ten years of interviewing, and here's what actually separates candidates.
QA automation is one of the hardest tech roles to hire for right now
Over 2,300 QA automation postings on Indeed alone, 9,000+ on LinkedIn counting adjacent titles — and companies still say they can't fill them. What the gap actually looks like from the interview side, and what closes it.
The weakness question is a trap, but not the one you think
Nobody is fooled by "I am a perfectionist". But the real risk is not sounding rehearsed — it is that this is the one question where an interviewer can find out whether you know yourself, and most answers prove that you do not.
A free mock interview with no signup, by role and level — here's what that costs us
Google's Interview Warmup proved people want to try before they register. We built the same idea, but scoped to a specific role and seniority level instead of generic questions — and here's what giving away the demo actually costs.
The API testing interview question that separates "I've read about it" from "I've done it"
Anyone can define a status code. The gap shows up the moment you ask what to do with one. Five questions from ten years of interviewing that tell the difference in under a minute.
Answering out loud is a different skill from knowing the answer
You can explain the theory perfectly in your head and still fall apart the moment you have to say it to another person. Why that gap exists, and the only way I've found to close it.
I priced every AI mock interview tool so you don't have to
interviewing.io, Final Round AI, Exponent, Yoodli — what each one actually costs, what it's actually for, and where our own tool loses. No invented ratings, no "trusted by" numbers.
Everything people actually ask about AI mock interviews
How AI mock interviews work, whether the scoring is accurate, how many you should do before the real thing, and the honest limits of what this kind of practice can tell you.
AI is mentioned in most tech job postings now — what that actually means in an interview
AI fluency now appears in the large majority of technical job postings, not just AI-specific roles. Here's what that shift actually turns into when you're sitting in the interview, role by role.
\"Tell me about yourself\" is not an icebreaker
It is the first question in almost every interview, and most candidates answer a different question than the one being asked. Here is what the interviewer is actually listening for, and how to build ninety seconds that earns you the rest of the hour.
Your idempotency test probably cannot fail
My test for "do not announce the same payment twice" passed. Production sent two identical messages 142 milliseconds apart. The test was not weak — it was structurally incapable of catching the bug, and it looked like proof of the opposite.
Five bugs AI wrote for me that never threw an error
None of them crashed. None of them appeared in the logs. Three were invisible in code review. What they were, why they survived, and the kind of test that actually catches them.
The junior QA bar keeps rising — and here is what each requirement is actually for
A decade ago one good question after a conference talk could get you the job. Now a junior is expected to know test design, HTTP, SQL and basic security. Which of those requirements are earned, and which are noise.
The DevOps interview question that predicts an outage
Most DevOps interviews test whether you can name tools. The good ones test whether you would make the call that takes production down. Five questions that tell the difference, and what interviewers are actually listening for.
Practice before the real thing
Cam asks real interview questions and scores every answer honestly.
Start a free interview →