The best hiring manager intake meeting questions for a developer role are the ones that force a trade-off: "Which of these skills would you give up to start two weeks sooner?" gets you further than "What skills do you need?" Below are 14 questions for a 30-minute intake meeting, grouped by what they decide, each with the follow-up to use when the first answer is vague. The form version of this lives in our intake form template; this post is about the conversation.
Key Takeaways
- An intake meeting exists to turn a wish list into a short list of real requirements.
- Ask for outcomes, trade-offs and deal-breakers; skills alone produce a wish list.
- Bring market data; recruiters who do are taken more seriously by hiring managers.
- Sol covers the first five minutes of this meeting in chat, so the human conversation can go deeper.
The Intake Meeting Questions, Grouped by What They Decide
The work
1. What does this person need to have shipped 90 days from their start? Follow-up if vague: "If they shipped only one thing, which one?"
2. Why is this role open now? Follow-up: "What happens if it stays open another month?" The answer tells you how urgent the role really is.
3. What is the hardest technical problem they will face in year one? Follow-up: "Has anyone on the team solved something like it before?"
The profile
4. Which three skills are deal-breakers? Follow-up: "Would you reject a great candidate who has two of the three?"
5. What seniority, and why? Follow-up: "What would a mid-level engineer get wrong in this role?" If there is no clear answer, the role may not need a senior.
6. What does this person do on a normal Tuesday? This exposes meeting load, on-call and how much code they will actually write.
The team and setup
7. Who do they report to, and who reviews their code?
8. How many hours of overlap with your team's time zone do you need? Follow-up: "Which hours exactly, and for which meetings?"
9. Employee, contractor or staff augmentation? Follow-up: "Would you consider converting a contractor later?"
The process
10. Who makes the final decision? One name.
11. What are the interview steps, and who runs each one? Follow-up: "Can we finish them within a week?"
12. What made past hires in this team succeed or fail?
The sell and the money
13. Why would a strong engineer choose this role over two other offers?
14. What is the budget, and how firm is it? Follow-up: "If the right person costs 15% more, who approves it?"
How to Run the 30 Minutes
| Minutes | Topic | Questions |
|---|---|---|
| 0-5 | Why now, what success looks like | 1, 2 |
| 5-15 | Must-haves and seniority | 3, 4, 5, 6 |
| 15-22 | Team, overlap, engagement type | 7, 8, 9 |
| 22-27 | Process and decision maker | 10, 11, 12 |
| 27-30 | Pitch and budget, agree next step | 13, 14 |
Come with data. In SHRM's Recruiting 101 guidance, recruiter Katrina Collier says: "You will immediately gain the respect of the hiring manager if they see that you're armed with data about the industry, competitors, geographies and salaries." For engineering roles, that means a rough sense of how many candidates match the must-haves and what they cost.
Write the answers into one shared doc during the call and read them back at minute 28. Most misunderstandings surface right there.
Where Sol Fits
When a CTO comes to Ruzora, the first part of this meeting happens in a chat. You describe the role to Sol on our homepage, and Sol asks at most a couple of short questions: role or stack, how many, seniority, timeline and US-hours overlap. That covers questions 4, 5 and 8 in rough form. If engineers on our vetted bench fit, you see anonymized profiles in the chat right away, and your shortlist follows within 72 hours of giving a work email.
Sol does not ask the deeper questions here, like 90-day outcomes, the decision maker or why past hires failed. Those come up on the founder call, which happens before any agreement is signed. The whole flow is in Meet Sol.
A Concrete Version
A recruiter at a 90-person logistics startup runs an intake meeting for a "senior full-stack engineer." The hiring manager's draft lists: React, TypeScript, Node, Go, Kubernetes, 8+ years, logistics experience, Spanish, startup background.
Question 4 cuts it fast. Asked which three are deal-breakers, the manager picks React, TypeScript and Node. Go turns out to be for a service another team owns. Kubernetes is handled by a platform engineer. Logistics experience and a startup background are "nice." Spanish was for one stakeholder who also works in English, so it goes. Question 5 lowers the bar from 8+ years to 5+, because the manager admits a strong 5-year engineer would be fine.
The result: nine requirements become three must-haves, two nice-to-haves and a seniority floor of 5+ years. Question 11 compresses the interview plan from four rounds to two. With a median time to fill of 39 days for nonexecutive roles in SHRM's 2026 benchmarking, cutting two interview rounds is a real share of the calendar.
The Honest Counterpoint
Intake meetings can turn into wish-list sessions where the hiring manager talks for 30 minutes and nothing gets cut. If that happens, stop asking open questions and switch to forced choices: "Pick three." "Which one goes?"
Sometimes the right outcome is not opening the role. If question 1 gets no clear answer after two tries, the team does not yet know what it needs. Pushing ahead creates a hire who struggles because the job was never defined. We wrote about that in signs you are not ready to hire a developer yet.
And a recruiter can over-steer. Market data should inform the requirements, but the hiring manager owns them.
Frequently Asked Questions
What are the most important hiring manager intake meeting questions?
What the person must ship in 90 days, which three skills are deal-breakers, how many hours of time-zone overlap you need, and who makes the final decision. Those four drive most of the search.
How long should a hiring manager intake meeting be?
Thirty minutes is enough if the hiring manager has filled in an intake form beforehand. Without one, plan for 45.
What should a recruiter bring to an intake meeting?
Rough market data: how many candidates match the must-haves, typical compensation, and how long similar roles took to fill. Then a one-page hiring brief after the meeting.
The Bottom Line
Good intake meeting questions force choices, and forced choices make the search shorter. If you want the first round done in a few minutes, describe the role to Sol and use the meeting time for the hard questions. Or request a shortlist and we will cover them on the founder call.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
