Article summary
- You do not need to know how Vamo search works to get a good list from your agent.
- Tell your agent what you are starting from and how many people you want.
- A Vamo search can start from a technology, a role, a company, a school, a project, a person or a place.
- A firm requirement removes people from a Vamo search. A preference only changes the order.
- Ask your agent to show the repository behind each person, so you can check the match yourself.
Start from what you have
You do not need to know how search works to get a good list. Tell your agent what you are starting from, and how many people you want. The examples below are things you can say as written, with your own details in place of ours.
A technology or a role
- A niche or trending technology: "Find 30 developers building real-time voice agents who have pushed code in the last three months."
- People who code under another title: "Find designers and product managers who ship real code on GitHub."
- A credibility bar: "Only people with serious open-source work of their own. Skip the famous names who will not reply."
- A job description: "Here is the role. Find 50 people who fit, and tell me why for each one."
A company, a school or a project
- The strongest people at one organization: "Who are the strongest engineers in this GitHub organization?"
- Named companies: "Find engineers who work at these companies now, and a second list of people who used to."
- A school: "Find strong builders who studied at these universities."
- A project you admire: "Find the people who really build this repository, and others who build things like it."
People you already rate
- Your own team: "This is our GitHub organization. Find everyone in it, then find people like them."
- One great person: "Find more developers like this one."
A place
- A location: "Find Rust engineers in Austin, and show me where each location came from."
- A talent map: "Compare five cities for people building this kind of system, so we know where to hire."
Getting a better list
Describe what the person has built, and let your agent turn that into searches. "Someone who has written their own database" finds different people from "a senior backend engineer", and usually better ones.
Say which requirements are firm and which are preferences. A firm requirement removes people. A preference only changes the order.
- Ask for a number. Without one you get a short first page.
- Ask your agent to show the repository behind each person, so you can check the match yourself.
- If a list looks thin, ask for a different angle on the same role before changing the requirements.
Still stuck? Tell us.