Loading...
Loading...
A transparent breakdown of how HR Mapper constructs search queries, predicts email patterns, and processes natural language.
HR Mapper is primarily a formatting tool. It takes natural language inputs (Company Name, Location, Industry) and formats them into syntax-compliant Google search strings (Boolean queries).
The logic engine applies:
site: operators to limit searches to public profiles on specific domains (e.g., site:linkedin.com/in).OR operator (e.g., ("HR Manager" OR "HRBP" OR "Head of HR")).- (NOT) operator to remove false positives like job boards and directories (e.g., -jobs -dir).The "Find People" conversational search feature uses an external AI API to interpret user prompts.
When a user types "Find me TA leads at fast-growing fintech startups in Bangalore", the AI parses the intent into structural components:
The AI does not search the web or provide a list of people. It returns a structured JSON payload which HR Mapper uses to format the Boolean search queries described in Section 1.
The email generator tool does not hack, scrape, or verify email addresses against active mail servers. Instead, it generates statistical guesses based on common corporate IT naming conventions.
For example, given the name "Rahul Kumar" and the domain "company.com", the tool generates common patterns:
These are purely mathematical combinations. Users must verify these addresses using their own email clients or validation tools before sending outreach.
Users must be aware of the following technical limitations when using HR Mapper:
Dependence on Google's Index: HR Mapper relies entirely on what Google has currently indexed. If a professional recently changed jobs, or their profile is not indexed by Google, they will not appear in the search results.
Public Data Only: We cannot search private profiles, paywalled databases, or internal company directories. The tool only surfaces publicly available web pages.
False Positives:Search engines match text strings, not semantic employment status. A result may surface because someone wrote "I used to be an HR Manager at Company X" in a blog post, rather than an active profile.