Researching Your New Team Before Day One: What to Read

You signed the offer four weeks ago and your start date is Monday. Most new hires spend that gap on vacation, errands, or doom-scrolling. That is a wasted month. The candidates who show up already knowing the org chart, the product roadmap, and the three loudest debates in the codebase are the ones who hit quota, ship velocity, or promotion criteria six months faster than peers. This guide tells you exactly what to pull up between now and Monday — and who to look up on LinkedIn before you shake their hand.

Spend 8 to 12 hours, not 40

Do not turn your pre-start research into a second job. Eight to twelve hours across the final two weeks is the sweet spot — enough to arrive informed, not enough to arrive burned out or projecting anxiety. Block two 90-minute sessions per week, put them on your calendar, and stop when the timer ends. If you are still researching at hour 20, you are procrastinating your real life, not preparing for work.

The goal is not mastery. The goal is enough context that when your manager says "we are pivoting away from the Helios initiative," you know what Helios was and do not have to ask. You want to be the new hire who catches references, not the one who needs every acronym decoded.

Read these 12 artifacts in this order

Skip generic "about the company" pages. Those are for candidates, not employees. You are past that. Here is the ordered list of what to actually read:

1. The last two earnings calls or investor letters (public companies) or the last all-hands recap (private) — this tells you what leadership is actually measured on in 2026.
2. The CEO's most recent long-form post — Substack, LinkedIn essay, internal memo if leaked. You want their actual vocabulary.
3. The last three product launch announcements on the company blog.
4. Any Glassdoor reviews from the past 12 months, filtered to your department.
5. The team page on the company website — memorize faces and titles.
6. Your direct manager's last 20 LinkedIn posts and their last public talk or podcast.
7. Your skip-level's background and one public statement they have made in the past year.
8. The company's most recent funding announcement, acquisition, or org change — TechCrunch, Pitchbook, or a simple Google News search limited to the past six months.
9. Two competitor product pages — you should be able to explain the competitive differentiation.
10. The company's public API docs or engineering blog (if technical role) or case studies page (if GTM role).
11. Any press coverage from the past 90 days, good or bad.
12. The one internal document your recruiter or hiring manager offered to share — ask for it if they did not offer.

That is the stack. Do not add a thirteenth item.

Look up seven specific people, not the whole org chart

Do not LinkedIn-stalk 200 employees. Look up exactly seven people and take two minutes of notes on each:

• Your direct manager
• Your manager's manager (skip-level)
• The two people your manager mentioned you would work most closely with
• The most senior IC on your team (the person who has been there longest)
• The cross-functional partner your role depends on — PM if you are eng, eng lead if you are PM, AE lead if you are SE
• The executive two or three levels above you who owns your function — CRO, CTO, CPO, whoever

For each person, note three things: where they worked before, one thing they seem to care about publicly, and any mutual connections you have. That is it. You are not building a dossier. You are building enough hooks to hold a real conversation on day three when you are introduced.

The fastest-ramping new hires do not memorize org charts. They memorize what three or four key people care about, and they lead with that in their first one-on-ones.

Map the product before you touch it

If the product is public, use it. Sign up for a free trial, click through the whole onboarding, and submit at least one real piece of feedback to the support email on your last Friday before starting. You will be shocked how many new hires at SaaS companies have never completed their own product's signup flow.

If the product is internal or enterprise, read every customer case study on the site and note which customer logos appear most often. Those are the reference customers your team will talk about constantly. Knowing that Acme Corp is the flagship deployment before someone says "well, Acme does it this way" saves you six weeks of confusion.

For technical roles, pull the public GitHub org and skim the README of the three most-starred repos. You do not need to read code. You need to know what exists.

Understand the money before you understand the mission

Every company has a mission statement. Almost none of them tell you how decisions actually get made. What tells you that is the money: how the company makes it, who the biggest customers are, what the gross margin looks like, and how much runway or profitability cushion exists in 2026.

Here is a compact pre-start financial checklist:

• Revenue range — public filings, Pitchbook, or press estimates
• Last funding round size, date, and lead investor (private only)
• Approximate headcount trajectory over the past 18 months — LinkedIn Insights shows this free
• Whether the company is profitable, near profitable, or burning
• Top three customers or top three customer segments by revenue
• Biggest existential competitor

If you cannot answer these six questions by Monday morning, you do not understand the environment you are walking into. You will be blindsided the first time someone says "we cannot hire for that headcount this quarter" and you do not know why.

Prepare your own 30-60-90 before they prepare one for you

Most companies will hand you a 30-60-90 plan in your first two weeks. Some will not hand you anything. Either way, draft your own before day one. Do not share it. Just write it down — one page, three columns.

For the 30-day column, list only learning goals: people you will meet, systems you will get access to, processes you will shadow. No deliverables yet. For the 60-day column, list the two or three contributions you think you could realistically make based on the job description. For the 90-day column, list one meaningful owned project.

This exercise does two things. First, it forces you to translate the job description into concrete actions, which exposes vague spots you should clarify with your manager in week one. Second, when HR or your manager asks "what are you hoping to accomplish in your first 90 days," you will have a real answer instead of reciting the job description back to them.

Do not over-index on Blind, Glassdoor, or Reddit

It is tempting to spend your last free weekend reading every anonymous review of the company on Blind, Glassdoor, and r/cscareerquestions. Do not. Here is the rule: read enough to notice patterns, then stop.

Anonymous reviews are dominated by two populations — the recently fired and the recently promoted. Both are unreliable narrators. If every recent review complains about the same specific thing (a bad VP, a failing product line, a 2025 layoff nobody talks about), that is signal. If the reviews are a mix of "best place I ever worked" and "toxic hellscape," that is noise and you should close the tab.

A reasonable cap: 30 minutes on Blind and Glassdoor combined. If you spend more, you are inoculating yourself with other people's anxiety, and you will walk in on day one expecting the worst. Do not do that to yourself.

Show up with three questions, not thirty

By the time Monday arrives you will have accumulated a pile of questions. Resist the urge to fire them all at your manager in the first one-on-one. Pick exactly three to bring to day one, and save the rest for week two or three when you have context to ask them well.

The three should be:

• One strategic question that shows you did the reading ("I saw the Q4 letter mentioned a shift toward self-serve — how is that landing on our team?")
• One tactical question about your role ("What does a successful first 30 days look like from your seat?")
• One cultural question ("How does this team prefer to disagree — in the meeting, in Slack, in a doc?")

Three good questions in your first one-on-one land better than thirty scattered ones. Your manager will remember the good ones. They will not remember the scattered ones, except to note that you seemed anxious.

Next steps

This week, block two 90-minute sessions on your calendar before your start date and label them "ramp research." Pull the 12 artifacts listed above into a single Notion page or Google Doc so you have them in one place. Look up the seven people and write two lines each. Draft your private 30-60-90. Cap Blind and Glassdoor at 30 minutes combined. Write down your three day-one questions and bring them in your notebook on Monday. If you do all of this, you will walk into your first all-hands meeting already knowing who is speaking, why they are speaking, and what they are measured on — which is more than 80 percent of your new colleagues can say about each other.

Related guides

• The 30-60-90 Day Plan Template for a New Job in 2026 — By Role and Seniority — A strong 30-60-90 plan turns a new job from vague onboarding into a visible operating plan. Use this role-by-role template to learn fast, build trust, ship early wins, and avoid overpromising in your first quarter.
• First-Day Questions to Ask Your Manager: The Year-One List — The specific questions to ask in your first one-on-one that set up year-one success. No filler, no soft-pedaling — a checklist you can bring into the meeting.
• Onboarding Checklist for a New Job in 2026 — What to Set Up in Week One — A strong first week is about access, expectations, relationships, and rhythm — not trying to prove everything at once. Use this 2026 onboarding checklist to set up tools, manager alignment, stakeholder context, and early wins without creating noise.
• Skills to Brush Up Before Starting a New Job — By Role and Seniority in 2026 — Before day one, focus on the few skills that will shorten ramp time: your core tools, stakeholder language, company context, and the behaviors expected at your level. This guide breaks down what to refresh by role, seniority, and first-week use case.
• Asking for a Promotion in Year One: When It's Reasonable — A direct read on when a year-one promotion is realistic in 2026, what evidence you need, and the script for asking without torching the relationship.