Big company or small company? They want different things
I've recruited for large corporates and for small businesses. The requirements can look similar on paper. They aren't.
One thing I can say after recruiting for both: a job title doesn't mean the same thing in each.
In a big company
- The process tends to be structured: set stages, set questions, several people involved.
- The requirements are usually written down, and they matter. If the job description says [X] years in a particular area, someone will check.
- Scope is defined. They want to know the size of what you've handled: team, budget, sites, customers.
- Decisions go through more people, so things take longer.
What to show: evidence against each listed requirement, with the scale.
In a small company
- The role is often looser, and it can change after you join.
- One or two people often decide, and they decide quickly.
- They tend to want range: someone who picks up what needs doing, not only what's listed.
- Fit carries more weight, because in a small team there's nowhere to hide.
What to show: ownership, speed, and examples of you solving a problem nobody handed you.
The mistake I see most
Sending the same CV to both. A CV built for a corporate shortlist can read as rigid to a founder. A CV built for a founder can look thin on scale to a corporate hiring team.
Here's how it plays out. This is an illustration, not a real candidate. Picture someone with a strong operations background applying to a large corporate and to a 40-person company in the same week. For the corporate, the CV that works lists the team size, the budget and the sites, matched to each requirement. For the small company, the stronger version leads with the problems they fixed themselves, and how fast. Same person, same experience, two different CVs.
Before you apply
Read the job description twice and ask: was this written by a process or by a person? Then decide what to lead with.
| Topic | Large company | Small company |
|---|---|---|
| Process | Structured: set stages, set questions, several people involved. | One or two people often decide, and they decide quickly. |
| Requirements | Usually written down, and they matter. | The role is often looser, and it can change after you join. |
| What they look for | The size of what you've handled: team, budget, sites, customers. | Range: someone who picks up what needs doing, not only what's listed. |
| What to show | Evidence against each listed requirement, with the scale. | Ownership, speed, and examples of you solving a problem nobody handed you. |