Public team research
Understand a team through public profiles.
Inspect a bounded sample of public profiles associated with a known company and see which roles appear in the returned data.
Connect and try this workflow
What you can inspect
- Public name and role when available
- Company and location fields
- Profile links and source provenance
- Returned sample size and warnings
Fields vary with what the source makes available. Missing values remain missing.
Try this prompt
Use Thirdwatch to inspect up to 10 public profiles associated with https://www.linkedin.com/company/stripe. Filter returned titles for engineer. Estimate the cost first, then show names, available titles, locations and profile URLs. Describe this as a sample, not a complete or verified current employee roster.
First call get_account_info to check your connection. Preview this request with estimate_cost, then run the selected data tool when you are ready. These inputs show an example request, not live results.
estimate_cost · preview input
{
"tool_name": "get_company_employees",
"query": "https://www.linkedin.com/company/stripe"
}get_company_employees · example tool input
{
"company_url": "https://www.linkedin.com/company/stripe",
"title_filter": [
"engineer"
],
"max_results": 10
}Know the coverage
Public profile coverage can be incomplete, outdated or unavailable. Title filters apply to the fetched sample, so empty results do not establish that a company has no matching employees. This does not verify current employment or provide contact permission.
A useful next question
Read the linked profiles to confirm context. Use search_jobs to compare public roles with advertised openings instead of inferring headcount from this sample.
Returned metadata includes the source coverage, credits used and any warnings. Additional data calls can use more credits.