How to Reverse-Engineer a Company's Interview Loop Before You Apply

Most candidates apply, get a recruiter screen, then panic-prep based on what the recruiter says.

The recruiter's description is wrong. Not maliciously - just incompletely. Recruiters describe the loop the way it appears in their internal handbook. The loop you actually face has been customized by the hiring manager, refined by the panel, and is shaped by what the team is currently obsessed with (a recent outage, a new framework migration, a leadership emphasis on "ownership").

The candidates who do best are the ones who walk into the loop knowing more than the recruiter told them. They prep for the actual round, not the generic round.

This post is how I do that research, and the templates that get real responses.

What You Are Trying to Find Out

Before you apply, try to learn:

1. The shape of the loop. How many rounds, what kind, in what order, with what pass bar.
2. The team's current obsessions. What technologies, problems, or projects keep coming up in their interviews and writing.
3. The hiring manager. Who they are, what they have shipped, how they evaluate.
4. The bar. Is this a "Senior" that is really a Senior, or a "Senior" that is really a Staff in disguise?
5. The recent vibe. Layoffs? Hiring spree? PIP-happy? Last 90 days of glassdoor reviews tell you a lot.
6. The actual questions. Yes, sometimes you can find them.

You will not always get all six. Three out of six is enough to prep with significantly more precision than the average candidate.

The Five Channels That Actually Work

1. The company's engineering blog

Underused. Companies tell on themselves all the time.

Reading their last 10 engineering posts, you can usually identify:

• The architecture they are most proud of (will likely come up in system design)
• The pain points they are still working through (will come up as "tell me about a hard problem you solved")
• The vocabulary they use (use it back to them, naturally)
• The technologies they actually use day-to-day (vs the resume keywords)

If they wrote a deep post on "how we migrated to CRDB last year," you should have a CRDB-relevant story ready to go. If they wrote about a foundation-models latency push, reach for a latency-optimization story.

This is free, public, and 90% of candidates skip it.

2. Glassdoor + Levels.fyi

Glassdoor's interview tab is unreliable on individual reports - lots of bitterness, lots of cope - but the aggregate is useful. Read 30+ reviews. Patterns emerge:

• "Three rounds in one day" → that is the loop shape
• "Asked behavioral first" → ordering signal
• "System design felt rushed" → time-budget signal
• "Senior engineer pushed back hard on every answer" → adversarial style signal

Levels.fyi has the comp data, but also has interview experiences from candidates who actually got offers (better signal than rejected ones).

Take it with a grain of salt - 30% of glassdoor reviews are venting. But the aggregate gets you 70% of the way to a clear picture of the loop.

3. LinkedIn outreach to current engineers

This is the highest-signal channel, and the one most candidates are too shy to use.

Find 3-5 engineers on the team you are applying to. Not the hiring manager. Not the most senior person. Mid-level engineers who joined in the last 6-12 months.

The reason: they remember the loop, they are not too important to reply, and they know what their team actually values.

A working template:

Hi Sara, I am exploring a Senior Backend role at Linear and noticed you joined the platform team last year. I would love to ask two quick questions about how you decided Linear was the right place. No pitch, just trying to be precise about my own search. 15 minutes if you have it - happy to make it 5 if 15 is a stretch.

That gets a meaningful response rate, especially with engineers in the first year of a role - they are still in the "hey I just had this experience" headspace and want to talk about it.

In the call, ask:

• "What did the loop actually look like? How many rounds, what kind?"
• "What surprised you about it?"
• "If you were prepping again, what would you focus on?"
• "What are you working on right now? What is the team obsessed with?"

The third question is the gold. Direct candidates skip it; you should not.

4. The job description, read like a lawyer

Job descriptions are written by recruiters, but they are briefed by hiring managers. The brief leaks signal.

Read with these questions in mind:

• Which technologies are mentioned by name? Those are the ones currently in heavy use, not just on the resume keyword list.
• Which soft skills are highlighted - and where in the JD? "Strong communicator" buried in the requirements is filler. "Strong communicator who can explain technical decisions to non-technical stakeholders" near the top is a hint that the loop has a stakeholder-communication round.
• What does the "you will be doing" section say? That is a preview of the system design problem space.
• What does the "nice to have" section say? Often a signal of where the team wants to grow but does not have expertise yet.
• What does the JD not say? If a role is for "Senior Backend Engineer" and there is no mention of leadership, mentoring, or cross-team work, this is a builder role, not a leadership role.

If a JD mentions Postgres and Kafka, your system design prep should bias toward write-heavy, queue-driven architectures. If it mentions React and tRPC, the bias is toward frontend system design and API contracts.

5. The hiring manager's recent talks, posts, and PRs

Once you know who the hiring manager is, search:

• Their recent conference talks (YouTube)
• Their last 10 LinkedIn posts
• Their open-source contributions (GitHub)
• Articles or interviews they appear in

You are looking for two things: what they are obsessed with, and how they communicate.

If the hiring manager gave a talk last month on "writing for engineers," your behavioral round will probably have a "tell me about a doc you wrote" question.

If they are active in the observability community, expect operability questions in system design.

If they retweet a lot of Hillel Wayne content, expect formal-methods curiosity in a round somewhere.

What to Do With What You Learn

You are not trying to game the loop. You are trying to prep with precision.

For example, you start the research thinking "I need to study system design." Three hours of research later, you know:

• The team works on a payments engine
• They blogged about CDC last month
• The hiring manager is obsessed with idempotency and ordering guarantees
• The JD highlights "comfortable owning on-call"
• A current engineer told you the loop has two design rounds, one deep and one cross-team

Now your prep has direction:

• Deep design: build a strong "design a payments system" story that includes idempotency keys, exactly-once-ish semantics, retries, dead-letter queues
• Cross-team design: have a story for "merging two payment-handling systems"
• Behavioral: have a strong on-call ownership story
• Vocabulary: use "ledger," "settlement," "double-entry," not "DB rows"

That candidate is going to outperform someone who just generally prepped for "Senior Backend interviews."

The Outreach Templates

For LinkedIn cold messages to engineers on the team:

Hi {first}, I am evaluating a {role} at {company} and noticed you have been on the {team} for {time}. I am trying to be precise about whether the team is a fit before I apply - would you be open to a 15-minute call this week or next? No pitch, just two or three honest questions about the team. Happy to send them in advance if it helps.

For an email to an alum or weak contact who works there:

Hi {first}, hope you are doing well. Quick favor - I am thinking about applying to {team} at {company}, and want to be honest with myself about whether the loop is one I should walk into now or later. If you have 15 minutes, I would love to ask you a few questions about the team. If not, completely understand. Thanks either way.

For a follow-up after the call (this is the one most people skip):

Thanks for the time today, {first}. Two quick follow-ups: 1) {specific thing they mentioned that I want to confirm}; 2) if you ever want a sounding board on {something they mentioned about their work}, I am happy to be that. Either way, really appreciated the conversation.

The follow-up creates a relationship. If you eventually apply and get an interview, this person now has a reason to mention you positively in the loop.

The Time Investment

This whole research process is 3-5 hours per company you are seriously considering. That is a lot. It is also less than the time you will spend prepping for the loop, and it makes the prep dramatically more effective.

If you are spraying applications, do not bother. If you are picking 5-10 companies you actually want to land, this is one of the highest-leverage things you can do.

gitGood helps you go from "I researched the company" to "I am ready for the actual rounds" with focused mock interviews. $5/month.