Interview questions for networking: 14 questions about building professional relationships before you need them
On this page
- Networking, defined as something you can observe
- Ten behavioral questions, with red flags and probes
- Four situational questions
- Testing a network claim without asking for names
- What strong and weak answers sound like
- A 1–4 anchored rating scale for networking
- Common interviewer mistakes with networking
- Questions people ask
Interview questions for networking usually go wrong in one of two ways. Either they ask, in effect, "who do you know?", which rewards background and can push candidates toward sharing information they should not, or they ask "are you good at networking?", which rewards confidence. What the job needs is a candidate who builds professional relationships deliberately, keeps them up when there is nothing to ask for, gives as much as they take and knows how to turn a relationship into an introduction or an answer when the work needs it. Below are fourteen questions, ten behavioral and four situational, each with what a strong answer contains, red flags and a follow-up probe, plus how to test a network claim without asking for names, illustrative sample answers, a 1–4 anchored scale and common mistakes.
Networking is close to the relationship building covered in interview questions for sales ability, but that is tied to specific deals and buyers. Networking is the wider, slower habit of building relationships across companies and communities with no transaction in view. Inside one organization, the related skill is cross-functional collaboration.
Networking, defined as something you can observe
Definition: networking is building and maintaining professional relationships beyond your immediate team and company, on a basis of mutual usefulness, so that information, introductions and help can flow in both directions when needed. Listen for four behaviors:
- Starting relationships deliberately. Reaches out with a reason, to people they did not already know.
- Giving first. Shares information, introductions or help with no immediate return.
- Keeping in touch. Has a light, real habit of staying in contact between needs.
- Using it well. Asks clearly and specifically when they do need help, and closes the loop afterward.
Ten behavioral questions, with red flags and probes
| Question | A strong answer contains | Red flags | Follow-up probe |
|---|---|---|---|
| 1. Tell me about a professional relationship you built from scratch that turned out to be valuable. | How they met, why they reached out, what kept it going and what came of it for both sides. | All their contacts came through school, family or an employer introduction, with nothing built. | "What did they get from knowing you?" |
| 2. Describe a time you helped someone in your network with nothing expected in return. | A specific introduction, piece of advice or favor, and why they did it. | Every example is transactional. | "Did anything come of it later?" |
| 3. Tell me about a time you needed information or an introduction you did not have. How did you get it? | Worked through second-degree contacts, made a clear ask, respected the other person's time. | Cold-messaged dozens of people with a generic request. | "What did your message actually say?" |
| 4. How do you keep in touch with people you do not work with day to day? | A real, light routine: sharing relevant articles, quick check-ins, meeting at events. | Only gets in touch when they need something. | "Who did you last contact without needing anything?" |
| 5. Describe a time you made an introduction between two people you knew. | Checked both sides wanted it, explained why they should talk, followed up. | Introduced people without asking first. | "How did you frame it?" |
| 6. Tell me about a time you joined a new industry, city or community and had to start from zero. | Specific steps: events, groups, volunteering, contributing, and early relationships that formed. | Waited for people to come to them. | "What did you do in the first month?" |
| 7. Describe a time something useful for your work came from your network. | A clear link from relationship to outcome: a hire, a partner, a solution, market information. | Vague ("it's always helpful to know people"). | "Could you have got that any other way?" |
| 8. Tell me about a time you asked for help and the answer was no. | Took it gracefully, kept the relationship, tried another route. | Resented it or pushed repeatedly. | "Are you still in touch?" |
| 9. Describe a time you had to decline a request from someone in your network. | Declined honestly and kindly, offered an alternative if they could. | Agreed to things they should not have, such as a reference they could not stand behind. | "How did you put it?" |
| 10. Tell me about an event, community or group where you contributed rather than just attended. | Spoke, organized, answered questions, mentored or wrote; and what relationships followed. | Attends many events, contributes to none. | "What did people come to you for?" |
Questions 2 and 4 do the most work. They separate people who maintain relationships from people who only activate them when they need something.
Four situational questions
-
"You join us next month and need to understand how three partner companies make buying decisions. You know nobody at any of them. What do you do?"
Probes: Who do you contact first? What would your first message say? -
"A former colleague you have not spoken to in two years asks you to introduce them to your current CEO. What do you do?"
Probes: What would you need to know? How would you say no, if you did? -
"You are at an industry conference for two days with no meetings booked. What is your plan?"
Probes: How do you decide who to talk to? What happens the week after? -
"A contact at a competitor offers to tell you about their pricing plans over coffee. What do you do?"
Probes: What do you say? Who would you tell?
Scenario 14 is a boundary check, closely linked to integrity. A strong answer declines to receive confidential competitor information and keeps the relationship to what is appropriate.
Testing a network claim without asking for names
If a role depends on an existing network, such as a partnerships lead or an agency recruiter, you still should not ask for a contact list or for clients the candidate would bring from their current employer. Doing so can put the candidate in breach of their obligations and rewards willingness to share what is not theirs. Test the behavior instead:
| Claim | Ask instead | What good evidence sounds like |
|---|---|---|
| "I know everyone in this space." | "Tell me how you met two people you would call this week." | Specific origins and a reason each relationship lasted |
| "I have a strong network of candidates." | "Describe how you built it and how you keep it current." | Repeatable methods: communities, referrals, contributions |
| "I can get meetings with decision-makers." | "Walk me through the last one you set up from a cold start." | A route through mutual contacts and a clear, respectful ask |
| "People come to me for advice." | "What was the last question someone brought you?" | A recent, specific example |
References can confirm the pattern. Ask former colleagues how the candidate built relationships outside the team and what came of them.
What strong and weak answers sound like
Illustrative answers to question 1, written to show the difference in structure.
Weak: "I'm a natural networker. I have over two thousand connections and I go to a lot of events. I know people at most of the big companies in our industry."
Connection counts and attendance show reach, not relationships. There is no example of a relationship built, kept or used.
Strong: "When I moved into payments I didn't know anyone, so I started answering questions in a practitioners' forum on reconciliation, which was what I knew best. One person kept replying with good counterpoints, so I suggested a call. We swapped notes every couple of months for a year. When my company needed someone who'd done a bank migration, I asked if she knew anyone. She introduced me to two people, and one became our contractor. Later I introduced her to a hiring manager when she was looking."
The strong answer shows a relationship started deliberately, built on contribution, kept up without an agenda, used with a clear ask and returned.
A 1–4 anchored rating scale for networking
| Score | Anchor |
|---|---|
| 1 — No evidence | Relationships are inherited or purely transactional. Gets in touch only when they need something. Measures network by size. |
| 2 — Limited | Some relationships built, but little upkeep. Asks are vague. Gives occasionally, mostly when asked. |
| 3 — Solid | Builds relationships deliberately, keeps in touch with a light routine, gives without immediate return, and makes clear, respectful asks. |
| 4 — Strong | Everything at 3, plus has built a network from zero in a new field, contributes to communities, connects other people often and can show concrete results from relationships for both sides. |
Common interviewer mistakes with networking
- Scoring network size or prestige. Big numbers and well-known names reflect background as much as skill. Score how relationships were built and kept.
- Asking for contacts or clients. Do not ask candidates to name contacts, share lists or promise to bring business. Test the behavior instead.
- Equating networking with extroversion. Some of the strongest networkers build relationships one at a time through careful, written contributions. Score behavior, not energy in the room.
- Ignoring ethics. A candidate who brags about inside information from a competitor contact is showing a risk, not a strength.
- Writing "well connected" in the notes. Record the behavior: "built payments network from zero via forum answers; kept up every two months; introduction led to contractor hire."
When a candidate uses relationships to change someone's position, score the persuasion under influence and the relationship itself here.
Questions people ask
How is networking different from the relationship building assessed in sales interviews?
Sales relationship building is tied to a pipeline: earning trust with specific buyers in order to win and keep deals. Networking is broader and slower. It is building and maintaining professional relationships across companies, functions and communities, usually with no immediate transaction in view, so that information, introductions and help can flow both ways later. A strong seller can be a weak networker outside their accounts, and the reverse.
Should I ask candidates who they know?
Ask how they build and use relationships, not for names. Asking a candidate to list contacts, share a client list or promise to bring business from their current employer can put them in breach of confidentiality or other obligations and rewards the wrong thing. If a role genuinely depends on an existing network, test it through examples of how relationships were built and what they produced.
Does networking favor candidates from privileged backgrounds?
It can, if you score the size or prestige of a network. Candidates from well-connected schools or families start with more contacts. Score the behaviors instead: how they built relationships from scratch, how they kept them up and what they gave. Those can be shown by anyone, at any career stage.
Which roles need networking skills?
Business development, partnerships, recruiting and agency roles, fundraising, investor relations, community and developer relations, journalism, and senior leaders who need peers outside the company. It also matters for internal roles that depend on knowing people across a large organization, such as program management.