Research a company by spending one focused hour on the sources that actually predict the job: the product itself, the exact job description, the team and interviewers, and the last few months of company news. Skip the marketing gloss and the decade-old history. Then convert what you learned into two things: sharper answers that connect your experience to their needs, and a short list of questions only someone who did the work could ask.
The reframe
Why company research is really interview preparation
Candidates treat company research as a box to tick, a few facts memorized so they are not caught flat by the question about what they know about the company. That framing wastes the whole exercise. Research is not trivia insurance; it is the raw material for almost everything that makes you look like the obvious hire: answers that speak to their actual problems, questions that prove you are already thinking like an employee, and the judgment to tell whether you even want the job.
The interviewer is trying to answer one question through everything they ask: will this person understand our situation and make it better. A candidate who has grasped what the company sells, who it sells to, and what is hard about that right now can connect every answer back to that situation. A candidate who has only skimmed the homepage gives generic answers that could apply to any employer, and generic is the thing that does not get hired.
Done well, research also protects you. An hour spent understanding the business, the stage, and the recent news often surfaces the reasons to walk away as clearly as the reasons to lean in. The layoffs last quarter, the product being quietly wound down, the leadership churn: these are worth knowing before you accept, not after. Research cuts both ways, and both ways are in your interest.
The pass
A repeatable research pass in under an hour
Do these four things in this order and you will have more useful signal than most candidates gather in a whole weekend of anxious browsing.
Use the product for ten minutes first.
If you can sign up, download, or browse what they sell, do it before anything else. Ten minutes as an actual user teaches you more about the company than any About page, and it gives you specific, credible observations no other candidate will have. If you cannot use it, watch a demo.
Read the job description like it is the answer key.
It is. Every requirement is a problem the team has right now, written in their own words. Mark the responsibilities that repeat and the phrases that sound like pain. Those are exactly the points your answers should hit, so mine the description before you look anywhere else.
Look up the people who will interview you.
Ask your recruiter who you will meet, then read their public profiles. Knowing someone runs infrastructure, or came from a company you admire, lets you pitch your answers to the room and ask each person something relevant to what they actually do.
Scan the last three to six months of news.
Search recent coverage, the company blog, and any funding or product announcements. You want the present tense: what shipped lately, what they are hiring for, what changed. Old history is trivia; recent movement is what shapes the conversation you are about to have.
Signal vs noise
What to read, and what to skip
Half of fast research is knowing what to ignore. These sources reward the hour; those below waste it.
Read
The product and its pricing
What they sell, who buys it, and what it costs tells you the shape of the business in minutes. Pricing pages in particular are honest: they reveal who the real customer is and how the company actually makes money, stripped of the marketing.
Read
The job description, twice
The single richest source, because it is the team describing its own needs. Read it once for the role and once for the subtext: which requirements are non-negotiable, which repeat, and what problem the hire is clearly meant to solve.
Read
Recent news and announcements
The last few months of coverage, funding, and product news put you in the present. This is what lets you say something current in the interview instead of reciting the founding story everyone else also read.
Skip
The polished origin myth
The founding story on the About page is written to sound inspiring and tells you little about the job. Know it exists; do not spend your hour there. Nobody was ever hired for reciting the year the company was founded.
Skip
Anonymous review-site noise
Employer review sites are worth a glance for patterns, not verdicts. A few furious anonymous posts are not data, and the extremes on both ends are the least reliable. Look for repeated, specific themes and ignore the rest.
Skip
Vanity metrics and buzzwords
Award badges, generic mission statements, and press-release adjectives are noise. They are designed to impress, not to inform, and repeating them back signals that you mistook the brochure for the business.
Answers
Turning what you found into answers
Research that stays in your head as facts is wasted. The work is converting it into answers, so that when the interviewer asks a standard question, your reply is quietly wired to their situation. The generic answer to why you want this role is enthusiasm; the researched answer names the specific problem the job description keeps circling and connects it to something you have actually done. Same question, completely different weight.
The mechanism is simple: for each thing you learned, ask what it lets you say. If the product has an obvious weak spot you noticed as a user, that becomes a tactful observation about where you could contribute. If a recent announcement signals a new direction, that becomes a reason your background is timely. If the job description repeats a requirement three times, that becomes the story you make sure to tell whether or not they ask for it directly.
Do not overdo it. The goal is not to prove you memorized the website, and reciting facts unprompted reads as anxious, not prepared. The research should be invisible, showing up only as the specificity of your answers. When the interviewer notices that everything you say seems to fit their situation, that is the research working exactly as intended, without a single fact recited on its own. The difference is subtle but decisive: a prepared candidate sounds like they already understand the job, while an over-prepared one sounds like they are reading a report about the company back to the people who wrote it.
Questions
Turning what you found into questions
The questions you ask are half of the impression you leave. Research is what turns them from filler into proof that you did the work.
Product
A question only a user could ask
Because you actually used the product, you can ask something concrete: why a feature works the way it does, how they think about an obvious gap, what a certain choice was trading off. This instantly separates you from candidates who read the homepage and stopped.
Role
A question about what success looks like
Ask what the person in this role needs to have accomplished in six months for it to be going well. It is grounded in the job description, genuinely useful to you, and it signals you are already thinking about delivering, not just being hired.
News
A question tied to something recent
Reference the recent announcement or change you found and ask how it affects the team you would join. It proves you did current homework and turns your research into a live, two-way conversation instead of a quiz.
Interviewer
A question aimed at this specific person
Because you looked them up, you can ask something only they can answer: what drew them here, what has surprised them, what the hard part of their work is. People answer these warmly, and the conversation stops feeling like an interrogation.
Team
A question about how the work happens
Ask how decisions get made, how the team is structured, or how this role fits the ones around it. Grounded, practical questions about the day-to-day tell you whether you want the job and show that you take the work seriously.
Caution
A question that surfaces a real risk
Tactfully probe something your research flagged: recent churn, a crowded market, a bet that has not paid off yet. Asked with respect, it shows maturity and gives you the honest read you need before saying yes.
The bigger picture
Research the company, then show your own work, and where Folio fits
The pattern under all of this is symmetry. You spend an hour understanding the company so you can speak to its situation with specificity, and the interviewer spends their time trying to understand you. The candidates who do best close that loop from both sides: they research the company thoroughly, and they make their own work just as easy to research in return. Preparation that only runs one direction leaves half the impression on the table.
That second half is often the neglected one. An interviewer who leaves the room interested will look you up, and what they find should be as clear and current as the research you did on them. A scattered trail across half-abandoned profiles undoes some of the good work you just did in the room. A single, coherent place that shows what you have done finishes the job.
Folio is a hosted home for exactly that: a portfolio and a resume kept current in one account, so the person who researches you finds a clear answer instead of a scavenger hunt. To be straight about the free plan: it puts you on portfolio.wrxstack.com/yourname rather than a custom domain, it shows a Made with Folio badge, and the full theme gallery is on the paid tier. The resume export is not gated; it downloads as PDF and DOCX at no cost and with no watermark. Research the company as thoroughly as you can, then make sure the work that answers their questions about you is just as easy to find.
Frequently asked questions
How long should I spend researching a company before an interview?
About an hour is enough for most interviews. The aim is signal, not a dossier: use the product, read the job description closely, look up your interviewers, and scan the last few months of news. Spending a whole weekend memorizing history produces anxiety, not better answers.
What should I research about a company before an interview?
Focus on four things: what the company sells and to whom, the exact job description and the problems it implies, the people who will interview you, and recent news or announcements. Those four predict the conversation far better than the founding story or the mission statement.
How do I use company research in the interview itself?
Convert it into tailored answers and specific questions rather than reciting facts. Let your research show up as answers that fit their actual problems, and as questions only someone who did the work could ask. Reciting trivia unprompted reads as anxious, not prepared.
What should I ignore when researching a company?
Skip the polished origin story, anonymous review-site extremes, and press-release buzzwords. They are designed to impress rather than inform. Glance at review sites only for repeated, specific themes, and spend your time on the product, the role, and recent developments instead.
How do I research a private company with little public information?
Lean harder on the product, the job description, and the people. Try the product or watch a demo, read the role for the problems it implies, and look up your interviewers and recent hiring. Even a quiet company leaves signals in what it builds and who it is bringing on.