How does Vamo Search work?
Step 1 Hard Filters
These narrow the pool before we look at projects.
e.g. Austin, Remote, San Francisco
e.g. TypeScript, Python, C++
This gives you a base group of engineers.
Step 2 Project Search (README Search)
Then we search what they've actually built using README + embeddings.
You choose one of three search types:
Example Searches
Choose the search type that best matches what you're looking for.
A) Archetype Search
You just want a general type of engineer. No README search needed — return everyone that matches hard filters.
"TypeScript dev in Austin"
Hard Filter: TypeScript, Austin
README Search: none
Result: All TypeScript devs in Austin
"iOS engineers who use Flutter"
Hard Filter: Swift, Dart
README Search: none
Result: All iOS/Flutter-capable devs
B) Platform Search
You want someone who has built on top of a specific platform like Shopify, Salesforce, Roblox, AWS, Cloudflare, Vercel, or Supabase.
"TypeScript dev who has done Shopify in Austin"
Hard Filter: TypeScript, Austin
README Search: Shopify
"Python dev who deployed on AWS"
Hard Filter: Python
README Search: AWS, EC2, Lambda, S3, etc.
C) Domain Search
You want someone who has built a specific type of product or used a specific technology — like scraping, CRM, Fintech, chat apps, AI tools, LLM apps, or data pipelines.
"TypeScript dev who has done scraping in Austin"
Hard Filter: TypeScript, Austin
README Search: scraping, crawling, data collection
"TypeScript dev who used Firecrawl"
Hard Filter: TypeScript, Austin
README Search: Firecrawl, Exa, web scraping tools
"Engineers who built sports betting platforms"
Hard Filter: none
README Search: sports betting, odds engine, wagering
"Frontend engineers working on AI products"
Hard Filter: TypeScript, JavaScript
README Search: AI, LLM, inference, agents, chat UI