The Short Version

Set a 30-minute timer before you apply to any company you actually care about. Spend it in five places: the careers page, the engineering blog (if one exists), the company's last 18 months on LinkedIn, Glassdoor and similar review sources, and the news/funding feed.

You're not doing due diligence. You're building enough context to (a) decide whether this company belongs on your shortlist, and (b) walk into the first recruiter call with informed questions.

Most people skip this step. They scroll a job board on a Tuesday evening, see something that looks interesting, and one-click apply. Then three weeks later they're on a fourth-round interview with a company they still couldn't explain in one sentence.

The cost of that pattern is real. Bad fits show up as offers you regret accepting, interviews you regret sitting through, and energy spent in the wrong rooms. Thirty minutes of research up front buys you the right to be picky later. It's the highest-leverage chunk of time in the entire job search.

What follows is a playbook for that 30 minutes. It's organized as a sequence because order matters — some signals only make sense in the context of the ones you found earlier.

The 30-minute research sequence

Step 1 · 5 minutes

Read the careers page like it's a homepage

This is the company telling you who they think they are. Skip the marketing — read the team pages, the role descriptions, and the benefits section. Look for whether they name specific teams, name specific engineering problems, mention on-call, mention compensation philosophy, and link to the engineering blog.

Companies whose careers pages are stock photos and a "We're hiring rockstars!" headline are companies that don't know how to talk about themselves to engineers. That's a tell.

Step 2 · 5 minutes

Read the engineering blog (or note that there isn't one)

If there's an engineering blog with substantive posts — not just product launch announcements — read the most recent two posts. You'll learn the team's actual tech stack, the kinds of problems they're proud of solving, and how they communicate. Look for names of engineers on each post; that tells you who's actually shipping.

If there's no engineering blog at a company of more than 200 people, that's not necessarily disqualifying but it's information. It usually means engineering doesn't have a strong external voice inside the company. That can be fine. It can also mean engineering is a service org for product/sales.

Step 3 · 7 minutes

Trace the last 18 months on LinkedIn

Open the company's LinkedIn page and scroll the activity feed back about 18 months. You're looking for: hiring announcements (are they hiring in your function?), leadership transitions (is the CEO/CTO/VPE the same person who was there a year ago?), product launches (are they shipping?), and the tone of their posts (defensive? promotional? thoughtful?).

Then check the People tab. Sort by "joined recently." How many people joined in the last 6 months? How many left? You can't see who left directly, but if headcount on the company page is flat or declining for 6+ months, that's a real signal.

Finally: look up the CEO, CTO, and any executive you'd report to. Read their last 5 posts. You're trying to see whether they sound like someone you want to learn from.

Step 4 · 7 minutes

Read employee reviews — but discount the extremes

Glassdoor, Comparably, and similar review sites are useful if you read them well. Skip the 1-star and 5-star reviews; they're usually the loudest voices, not the most informative ones. The 3-star reviews are where the most honest signal lives — people listing both real positives and real frictions.

Look for patterns across many reviews, not single anecdotes. If twelve reviews mention "siloed teams" and seven mention "low transparency from leadership," that's a pattern. If one review complains about a specific manager, that's one bad relationship.

Pay extra attention to the work-life balance score and the comments about it. WLB is the one thing that's hard to reverse once you're inside the company. A low score with specific reasons is a red flag worth taking seriously.

Step 5 · 6 minutes

Check the news and funding feed

Google "[company name] news" sorted by recent. Look for: recent funding rounds (and the amount), recent layoffs (yes, even quiet ones), executive transitions, product launches that landed well or poorly, and any controversy or lawsuit.

For startups specifically, find the last funding round on Crunchbase or the company's own press releases. Calculate: when was the round, how much did they raise, what's the implied burn? If the round was more than 18-24 months ago and there's been no announced extension, ask in the recruiter call about runway.

For public companies, glance at recent earnings coverage. You don't need to read the 10-K. You need to know: is the business growing, flat, or shrinking? Is the company in cost-cutting mode?

What you're looking for in each signal

Each of those steps surfaces signals. Some are green flags. Some are red. Here's what experienced researchers actually weight:

Green Flags

  • Engineering blog with recent, technical, named-author posts
  • Salary bands published on job postings
  • Long-tenured employees praising the team in reviews
  • Stable leadership for 2+ years
  • Hiring across multiple functions, not just one team
  • Specific named teams with specific problems on careers page
  • CEO/CTO posting thoughtfully about the work, not just hype
  • Recent funding round closed within the last 12 months

Red Flags

  • Unannounced layoffs in the last 6 months
  • VP-level departures with no replacement named
  • Repeated reviews citing the same specific friction
  • Careers page that's all stock photos and platitudes
  • No engineering blog at a 300+ person company
  • Defensive or evasive answers in reviews about WLB
  • Headcount flat or declining for 6+ months
  • Recruiter pressures you to skip culture questions

One red flag is rarely a deal-breaker. Two or three together usually justify either passing or asking very pointed questions in the first call.

What to ignore

The signals that get a lot of attention but don't actually correlate with job satisfaction:

JobsByCulture compiles this for you

For each company we cover, the profile page surfaces the signals above in one place — current open roles, employee-reported culture data, recent news, and verified leadership info. Browse the company directory to start your research with the homework already done.

Turning research into interview questions

The real payoff of this 30 minutes isn't a yes/no decision. It's the quality of questions you bring to the first recruiter call. A few patterns that work well:

Reference something specific. "I noticed your engineering blog had a post on the platform migration to Rust — is the team I'd be joining part of that work, or downstream of it?" This signals you did your homework and gets you a real answer about scope.

Ask about transitions, not present state. "Your CTO joined about ten months ago — what's changed since then, and what's still in flight?" Companies in transition are often the best opportunities (more impact) or the worst (more chaos). The answer tells you which.

Ask about the previous person in the role. If you're interviewing for a backfill, ask why the previous person left and how long they were in the role. If it's a new role, ask what the team did without it before. Either answer is useful.

Ask about decision-making. "How does an engineer here go from noticing a problem to shipping a fix?" The shape of that answer tells you everything about the culture — how empowered ICs are, how heavy the process is, who actually gets to ship.

How to know when 30 minutes is enough

The research is enough when you can answer three questions in a sentence each:

  1. What does this company actually do, and who pays them?
  2. What's the company's current trajectory — growing, flat, recovering, or struggling?
  3. What would make me happy or unhappy here based on what I learned?

If you can answer all three, you have enough to apply intentionally and to walk into the first call with a point of view. If you can't answer one of them after 30 minutes, give it another 10. If you still can't, the company is either being deliberately opaque (a signal) or it's a target you don't actually care that much about (also a signal).

One more thing. Save what you learn. A short note — three bullets per company — pays off later when you're juggling four interview loops and trying to remember which company had the better engineering blog. The research compounds when you write it down.

Frequently Asked Questions

How long should I spend researching a company before applying?+
30 to 45 minutes for a serious target. Less than that and you'll miss the signals that matter. More than that and you're procrastinating. The goal isn't due diligence — it's enough context to know whether you want a 30-minute call with the recruiter and what questions to ask them.
What should I look for on a company's careers page?+
Look for substance over polish. Specific team names, real engineering problems, named interviewers, transparent salary bands, and a sense of who actually works there. A careers page that's just stock photos and "we're hiring rockstars" is a tell. A careers page with engineering blog links, on-call rotation language, and named team leads tells you a lot about how the company actually operates.
Should I trust Glassdoor reviews?+
Read them but discount the extremes. The 1-star and 5-star reviews are usually the loudest voices in a small sample. The 3-star reviews are where the most useful signal lives — what people actually like and dislike. Look for patterns across many reviews, not single anecdotes. And cross-reference with employee posts on LinkedIn or community forums for a more grounded picture.
How do I tell if a startup is about to fail?+
Three signals in combination are usually a yellow flag: (1) last fundraise was more than 18-24 months ago with no announced extension, (2) headcount on LinkedIn is flat or declining for 6+ months, and (3) leadership has been quietly leaving — especially the CFO or VP of Engineering. None of these are conclusive alone, but two or three together justify asking pointed questions in the interview about runway and the next funding milestone.
What are the biggest red flags when researching a company?+
Recent unannounced layoffs, founder departures, repeated CEO changes, lawsuits over IP or compensation, evasive answers on Glassdoor about work-life balance, multiple negative reviews mentioning the same specific manager by initial, and recruiter responses that pressure you to skip culture questions. Any single one is worth asking about. Two or more together is usually a signal to walk.
How do I find out a company's salary range before applying?+
Start with the job posting itself — around a third of US states now require salary disclosure on listings, and many companies post bands voluntarily. If the band isn't published, search the same role title at competitor companies on JobsByCulture, look up the company's Series stage (which roughly predicts comp), and ask the recruiter directly on the first screening call. Reputable recruiters will share the band before they ask you about expectations.
Should I research a company before applying or after the recruiter reaches out?+
Before. Doing the research up front means you only spend interview time on companies you actually want to work at, and you go into every conversation with informed questions. The pattern of "apply broadly and figure it out later" wastes both your time and the recruiter's. A 30-minute research block before applying typically saves 5+ hours of mismatched interviews.

Start with the research already done

JobsByCulture profiles surface the signals above in one place — open roles, employee-reported culture data, and verified leadership info for every company we cover.

Browse Company Directory → Browse All Jobs →