Skip to answer guide
RockStarCV.com
Toggle Navigation

What do you know about us?

The interviewer wants to see preparation and judgement about what is relevant. Preparation shows in the connection you make between public facts and this vacancy.

Business Operations Manager workplace scene from Pexels for the interview guide “What do you know about us?”

Chapter 01

Introduction

The interviewer wants to see preparation and judgement about what is relevant.

Research should lead to interpretation, not recitation. Choose the professional starting point that makes this answer useful now. Name the work, responsibility, or transition before adding background, so the interviewer can understand why the detail belongs in your response.

Preparation shows in the connection you make between public facts and this vacancy. Research is not a memory test. The value lies in selecting the facts that affect this role and asking an informed question about the part you cannot see from outside. Test the evidence against the vacancy. Keep the facts you can explain in a follow-up, remove biography that does not help the decision, and make the final sentence point toward the role in front of you.

  1. 01
    Set the direction

    The interviewer wants to see preparation and judgement about what is relevant.

  2. 02
    Choose the proof

    Research should lead to interpretation, not recitation.

  3. 03
    Connect it to the role

    Choose the professional starting point that makes this answer useful now.

Chapter 02

Understanding the Question

They may ask this to see whether you can distinguish established facts from assumptions about the team.

Read the question as an assessment, not only a request for information. Decide which judgment, risk, working habit, or motivation the interviewer needs to see, then make that purpose visible through one concrete detail.

Expect a follow-up on where your information came from and what you still do not know. A hiring manager may correct your interpretation. Treat that as useful information, not a threat to your preparation. Prepare for the next question as well as this one. If you mention a result, transition, conflict, or constraint, keep the context and your exact contribution ready so the interviewer can test the claim without weakening it.

  1. 01
    What they are testing

    They may ask this to see whether you can distinguish established facts from assumptions about the team.

  2. 02
    Prepare the follow-up

    Read the question as an assessment, not only a request for information.

  3. 03
    Keep the evidence ready

    Decide which judgment, risk, working habit, or motivation the interviewer needs to see, then make that purpose visible through one concrete detail.

Chapter 03

Preparing Your Answer

Review the company's own material, then connect one fact to the role.

Prepare two verified facts and one intelligent question about their effect on this role. Build a small evidence bank before rehearsing. Write the setting, the decision you owned, the action you took, and the observable result. That gives you facts to select instead of forcing you to invent polished language under pressure.

Read the company's own description, a current product or service page, and the job posting side by side. Collect two reliable facts, write the source beside each, and note how each might shape a responsibility in the vacancy. Prepare one question to test that inference. Arrange the answer so the listener never has to guess why a detail matters. Put the strongest evidence near the claim it supports, keep your role precise, and finish with the lesson or relevance to this position.

  1. 01
    Build your evidence

    Review the company's own material, then connect one fact to the role.

  2. 02
    Shape the sequence

    Prepare two verified facts and one intelligent question about their effect on this role.

  3. 03
    Keep the evidence ready

    Build a small evidence bank before rehearsing.

Chapter 04

Dos and Don’ts

What to do: Distinguish what you know publicly from what you would like to learn.

Do

  • Distinguish what you know publicly from what you would like to learn.
  • Do distinguish the organization from the specific team you hope to join.

Don’t

  • Do not recite a website paragraph without interpretation.
  • Do not fill missing operational details with assumptions about culture or strategy.
  • Do not recite the company's About page.
  • The interviewer wrote or approved that copy; they want to know what you made of it.

Chapter 05

Example Answers

The examples connect public service information to onboarding, an annual-report priority to case notes, and expansion to training work.

Each also names a remaining unknown. Compare the examples by structure rather than memorizing their wording. Notice where each candidate sets the context, states personal ownership, and closes with a result, lesson, or reason the experience matters to the employer.

Example 1A concise route built around one clear fact

“I understand that you provide software for teams managing recurring customer requests and that the role supports adoption after the sale. My experience is in reducing friction during onboarding, so I would be interested in how you measure a successful first month.”

Why it works: Treat this first example as a model for sequence. Replace its workplace, task, people, and result with truthful details of your own while keeping the connection between the claim and the supporting evidence.

Example 2A second route using relevant experience

“From your annual report, I understand that service quality and retention are major priorities. The vacancy's emphasis on accurate case notes makes sense in that context. I would like to ask how the team currently checks whether handovers are working.”

Why it works: Use the second example to explore a different route to the same competency. Your version can come from paid work, study, volunteering, or a project, provided you state the context and do not overstate your responsibility.

Example 3A version that connects evidence to the role

“I have read about the markets you serve and the recent expansion of your training offer. I do not know how that has changed the team's day-to-day work, so I would be keen to learn where this role could help most.”

Why it works: Use the third example to test whether your answer sounds recognisably yours. Keep the useful structure, then change every borrowed fact.

Chapter 06

Fine-Tuning Your Answer

It is better to be accurate and curious than to sound encyclopedic.

State the source of an important claim if it is not obvious from the posting. Fine-tuning is mainly subtraction and precision. Move the strongest fact earlier, replace labels with actions, and check that the ending answers the question rather than drifting into a second example or an unrelated career summary.

If you have only a little reliable information, go deeper on one point instead of listing many shallow facts. If your answer sounds like a company briefing, move one step closer to the actual team: who uses this role's output, and what decisions does it support? Record one practice version and listen for the first useful fact. If it arrives late, shorten the setup. Then check every result, number, and claim so the final wording remains accurate when the interviewer asks for detail.

  1. 01
    Make it sharper

    It is better to be accurate and curious than to sound encyclopedic.

  2. 02
    Test the wording

    State the source of an important claim if it is not obvious from the posting.

  3. 03
    Keep the evidence ready

    Fine-tuning is mainly subtraction and precision.

Chapter 07

Additional Considerations

Public information may lag current priorities.

Invite the interviewer to correct your picture. A thoughtful question about how the role contributes may be more useful than another company statistic. Adapt the structure to your circumstances without hiding them. Career changes, gaps, early-career evidence, senior scope, confidentiality, and reasonable boundaries may change the example, but they do not remove the need for relevance and honest ownership.

For a small company with limited public material, a careful reading of the product and job description may be enough. Inventing facts to sound researched is worse than asking. Protect credibility where context is sensitive. Use the level of detail you can share, separate team results from your contribution, and explain constraints without disclosing private information or blaming people who are not present.

  1. 01
    Adapt the answer

    Public information may lag current priorities.

  2. 02
    Keep it credible

    Invite the interviewer to correct your picture.

  3. 03
    Keep the evidence ready

    A thoughtful question about how the role contributes may be more useful than another company statistic.

Chapter 08

Conclusion

Show curiosity about how the company works, not just memory for its homepage.

Bring the answer back to one clear message. The interviewer should be able to repeat your main claim, the evidence supporting it, and why it matters to the role without reconstructing the meaning from several disconnected points.

Verify what you know and ask about what you cannot see publicly. Finish with the question your research created. That keeps the discussion grounded in what the employer can confirm. End deliberately. Stop when the question has been answered, the evidence is credible, and the relevance is clear. A concise landing invites a useful follow-up and leaves the listener with the professional judgment you intended to show.

A concise landing invites a useful follow-up and leaves the listener with the professional judgment you intended to show.

Source & adaptation

Built from the RockStarCV interview-question library

Adapted from the RockStarCV guide 100 Most Popular Job Interview Questions and its long-form narration. The structure and examples have been edited for a practical web reading experience.

Book reference: Question 13

RockStarCV 100 Most Popular Job Interview Questions book, stacked copies, and an open spread

More from RockStarCV

Build your complete career toolkit