TL;DR
- The 48 hours between a verbal offer and signed contract is the single most underused tool in the tech job search.
- Use it to ask seven specific questions: team retention over the last two years, manager tenure, on-call burden, typical promotion timeline at your level, refresh equity policy, the biggest internal team tension, and a 20-minute informal call with two engineers on the team.
- Then run a back-channel reference with someone who left in the last 12 months.
- These questions consistently catch the team-fit and compensation issues that drive most regretted SWE job decisions.
Introduction
You got the offer. The natural impulse is to sign. Resist it for 48 hours. That window is when every experienced engineer does their final due diligence — and the signal quality is higher than at any other point in the process because the company now has budget invested in your yes. This guide is the seven questions that experienced engineers ask before signing, plus the back-channel reference process that flags most regretted decisions.
Table of Contents
- Why the 48-Hour Window Matters
- Question 1: What is the team's retention over the last 2 years?
- Question 2: How long has my manager been in role?
- Question 3: What is the on-call burden?
- Question 4: What does a typical promotion timeline look like at this level?
- Question 5: What is the refresh equity policy?
- Question 6: What is the biggest internal tension on this team right now?
- Question 7: Can I talk to two engineers on the team informally?
- Running a Back-Channel Reference
- Red Flags to Walk Away From
- FAQ
- Conclusion
Why the 48-Hour Window Matters
Most companies expect a 2-to-5-day turnaround on offers. Use the time. In that window:
- The recruiter is maximally responsive.
- You have leverage to negotiate both comp and team fit.
- You can ask questions that would have been awkward pre-offer.
- You can set up back-channel references with your network.
Candidates who skip this window rarely regret what they did. They often regret what they did not ask. Two years in, when the manager reorgs away and the team's tech debt buries them, the questions below would have caught it.
Question 1: What is the team's retention over the last 2 years?
Who to ask: hiring manager, then cross-check with a future peer.
Ask: "Of the engineers who were on this team 2 years ago, how many are still on it today?"
Healthy tenure: 60 to 80 percent retention over 2 years.
Yellow flag: 40 to 60 percent. Probably a rough patch; ask what happened and whether it has been addressed.
Red flag: below 40 percent. Either the manager churns people or the team is in crisis. Ask specifically: "Where did the people who left go, and why?"
Question 2: How long has my manager been in role?
Who to ask: the hiring manager directly.
Ask: "How long have you been managing this team? And how long at this company?"
Good: manager in role 12+ months, at the company 2+ years. Stable.
Yellow: manager in role 6 to 12 months. Probably recently promoted; acceptable if tenure at the company is longer.
Red flag: manager in role less than 6 months AND at the company less than 1 year. The manager is likely still figuring out the team, which means their commitments to you may not survive the next reorg.
Also ask: "What is the company's typical manager tenure on a team before rotation?" This tells you whether your manager is structurally likely to leave in 18 months.
Question 3: What is the on-call burden?
Who to ask: a peer engineer (not the manager — managers systematically underestimate).
Ask the specifics:
- How often are you on call (every N weeks)?
- How many pages per rotation, on average?
- How many of those are in sleeping hours (11 PM to 6 AM)?
- What is the typical severity of pages?
- What is the on-call compensation, if any?
Healthy: one rotation every 4+ weeks, fewer than 5 pages per rotation, fewer than 1 sleep-hour page per rotation.
Yellow: one rotation every 2 weeks, 5 to 15 pages per rotation, occasional sleep-hour pages.
Red flag: weekly rotations, 20+ pages per rotation, regular sleep-hour disruptions with no compensating comp or time-off.
This is the single most under-asked question and the single most common regret at the 12-month mark.
Question 4: What does a typical promotion timeline look like at this level?
Who to ask: hiring manager AND the recruiter (triangulate).
Ask: "At this level, how long does a solid performer typically take to reach the next level? And what percentage of engineers at my level got promoted in the last cycle?"
Healthy: 18 to 36 months to next level for solid performers; 40 to 70 percent promoted per cycle.
Yellow: 36+ months; 20 to 40 percent promoted.
Red flag: the manager cannot give a number OR the last promotion on the team was more than 2 years ago.
Also ask: "What would need to be true for me to be promoted in 18 months?" The specificity of the answer tells you whether the manager has calibrated promotion paths or is making it up.
Question 5: What is the refresh equity policy?
Who to ask: recruiter.
Most FAANG initial offers have a front-loaded 4-year RSU vest. Without a refresh, your total compensation drops sharply in year 3 and beyond.
Ask:
- Is there an annual RSU refresh?
- What is the typical refresh size at my level?
- Is the refresh tied to performance rating?
- When does the first refresh vest?
Healthy: yearly refresh, roughly 25 to 50 percent of the initial grant's annual value.
Yellow: refresh only at promotion or top performance rating.
Red flag: no refresh program OR discretionary with no target band.
This single question is worth tens of thousands of dollars per year of tenure. Never skip it.
Question 6: What is the biggest internal tension on this team right now?
Who to ask: the hiring manager.
Ask: "What is the biggest internal tension on this team right now, and how is it being addressed?"
Honest managers will name something specific. Dishonest or clueless managers will say "no real tensions". The former gives you real insight. The latter is itself a red flag.
Listen for:
- Tension between the team and its PM.
- Tension with a dependent team (infrastructure, platform, other business units).
- Tension about scope or charter.
- Tension between engineering quality and shipping speed.
A team without tensions is either new or not being honest.
Question 7: Can I talk to two engineers on the team informally?
Who to ask: recruiter or hiring manager.
This is the most powerful question. Ask for 20 minutes each with 2 engineers on the team you would be joining. Healthy teams say yes; unhealthy teams say no.
During those calls:
- Skip your prepared list. Ask "what is it really like?"
- Ask "what would you tell a friend considering this role?"
- Ask "what is the most frustrating thing on the team?"
- Ask "how is your manager specifically?" if you have not already talked to them.
Tenure-weighted signal: if the engineers you talk to are consistently 3+ years of tenure, the team retains people. If they are all 6-month hires, dig harder.
Running a Back-Channel Reference
Separate from the formal calls, use your LinkedIn network to find someone who WAS on the team but LEFT in the last 12 months. Reach out privately. Ask:
- Why did you leave?
- What would you have wanted to know before joining?
- How is the manager?
- How is the team's trajectory?
This is the most honest signal you will ever get. Use it.
Rules:
- Keep it to 15 minutes. Respect their time.
- Do not name the hiring manager as a mutual contact.
- Offer reciprocity — you will help them with their next job search.
If you do not have anyone 1 or 2 hops away, post on Blind or ask your closest engineering friends for warm intros.
Red Flags to Walk Away From
If any of these show up, seriously consider declining:
- The recruiter pressures you to decide in under 48 hours. No reputable company does this.
- The hiring manager cannot name a single engineer on the team for you to talk to.
- The team has lost 2 or more engineers in the last 6 months and the manager deflects.
- The offer has significantly below-market equity for the level (use levels.fyi).
- You ask about on-call and the answer is vague. The vagueness itself is the signal.
- The hiring manager has been in role less than 6 months AND was brought in externally. High risk of the team's existing norms being overthrown.
None of these is an automatic walk-away alone. Two or more together is.
Frequently Asked Questions
How do I ask these questions without sounding paranoid?
Frame as due diligence: "I want to make sure I can hit the ground running and stay engaged here for years. A few questions as I finalize my decision."
What if the company refuses to connect me with team members?
A hard no is a red flag. Most healthy teams are proud to connect candidates to 1 or 2 engineers. A "we do not typically do that" answer is either a bureaucratic company or a hiding one.
Can I negotiate the offer while asking these questions?
Yes, and it is efficient to do both in the same window. See our salary negotiation guide for the mechanics.
What if the due-diligence window expires before I am ready?
Ask the recruiter for an extension. "I am moving as fast as I can but I would like a few more days to do my diligence." Most recruiters will grant 2 to 5 extra days without fuss.
What if the answers are concerning but the offer is still the best option?
Take the concerns to the hiring manager directly. Most are solvable: team-switch offer, on-call rotation guarantee, explicit refresh commitment in writing. The offer letter is negotiable more often than candidates realise.
Conclusion
The 48-hour window between verbal offer and signed contract is the single most underused tool in the tech job search. Seven questions, a back-channel reference, and a candid hiring-manager conversation are enough to avoid 80 percent of the regretted job decisions experienced engineers describe. Do the work. It is the cheapest insurance you will buy this decade.
Frequently asked questions
What is the most under-asked question before accepting a SWE offer?On-call burden — frequency of rotations, pages per rotation, sleep-hour pages (11 p.m. to 6 a.m.), severity, and on-call compensation. Ask a peer engineer rather than the manager, because managers systematically underestimate. Healthy is one rotation every 4+ weeks with fewer than 5 pages. Weekly rotations with 20+ pages and regular sleep-hour disruption is a red flag, especially with no comp or time-off offset.
How do I check my future team's retention before joining?Ask the hiring manager 'of the engineers who were on this team 2 years ago, how many are still on it today?' and cross-check with a future peer. 60-80% retention over 2 years is healthy. 40-60% is yellow and needs explanation. Below 40% means either the manager churns people or the team is in crisis — ask specifically where the people who left went and why.
What is RSU refresh equity and why does it matter?Most FAANG initial offers have a front-loaded 4-year vest. Without an annual refresh, your total compensation drops sharply in year 3 and beyond. Ask whether there is an annual RSU refresh, the typical refresh size at your level (healthy is 25-50% of the initial grant's annual value), whether it is tied to performance rating, and when the first refresh vests. This single question is worth tens of thousands of dollars per year of tenure.
Should I ask to talk to engineers on the team before accepting?Yes — request 20 minutes each with two engineers on the target team. Healthy teams say yes; unhealthy teams say no, which is itself a strong red flag. On those calls, skip your prepared list and ask 'what is it really like', 'what would you tell a friend considering this role', and 'how is your manager specifically.' If the engineers are 3+ years tenured, the team retains people.
What is a back-channel reference and how do I run one?Use your LinkedIn network to find someone who was on the team but left in the last 12 months and have a private 15-minute call. Ask why they left, what they would have wanted to know before joining, how the manager is, and the team's trajectory. Do not name the hiring manager as a mutual contact and offer reciprocity for their next job search. This is the most honest signal you will ever get on a team's reality.