# Interviewing at a Startup vs a Large Company: Adjust Your Approach

The same candidate can do brilliantly at a 20-person startup and stumble at a 20,000-person company, or the reverse. The questions overlap, but what interviewers listen for is different.

## What startups listen for

- **Range.** Can you handle work outside your job title? Stories where you picked up an unfamiliar task land well.
- **Speed and judgment.** "We had two weeks, so I shipped the simple version and measured it" is often a better answer than a perfect design.
- **Comfort with ambiguity.** Expect questions like "What would you do in your first month with no roadmap?"
- **Genuine interest in the product.** Use it before the interview and have opinions.

## What large companies listen for

- **Depth in your area.** Structured, rigorous answers, often scored against a rubric.
- **Collaboration at scale.** Stories about aligning several teams, handling dependencies, and influencing without authority.
- **Process awareness.** Code review, testing, documentation, launch reviews and on-call.
- **Consistency across rounds.** Several interviewers may probe the same competency; your stories should hold up.

## Adjust your stories, not the facts

Take one project and tell it two ways. For a startup, emphasise how quickly you scoped it and what you learned from users. For a big company, emphasise how you coordinated with other teams and ensured quality.

## Ask different questions

At a startup: runway, how decisions get made, what the founders do day to day. At a large company: team stability, how performance is evaluated, and how often priorities change.

## Practise both modes

Rehearse your main project in both versions until each feels natural. A mock session with an [AI interview copilot](https://www.linkjob.ai/) set to a startup or enterprise context is a quick way to hear the difference.

*Disclosure: I work on Linkjob AI.*