# Find Software Engineers Working at a Specific Company

**Use case:** 

Recruiting and talent mapping: list the engineers and developers working at a company today, found by its website domain, with title, time in role, email flags and LinkedIn URL. Sales and solutions engineers are excluded by title, and low-signal profiles dropped. Swap the domain to map another team, or change the title words to data, platform or security.

## Input

```json
{
  "companies": [
    "datadoghq.com"
  ],
  "roles": [
    "cxo"
  ],
  "profileDetail": "roster",
  "compact": false,
  "titleContains": [
    "engineer",
    "developer"
  ],
  "titleExcludes": [
    "sales engineer",
    "solutions engineer"
  ],
  "excludeLowSignal": true,
  "maxRows": 500
}
```

## Output

```json
{
  "fullName": {
    "label": "Name",
    "format": "string"
  },
  "title": {
    "label": "Title",
    "format": "string"
  },
  "hasPersonalEmail": {
    "label": "Personal email",
    "format": "boolean"
  },
  "hasWorkEmail": {
    "label": "Work email",
    "format": "boolean"
  },
  "lowSignal": {
    "label": "Low signal",
    "format": "boolean"
  },
  "positionStartYear": {
    "label": "In role since",
    "format": "number"
  },
  "personUpdatedAt": {
    "label": "Profile re-checked",
    "format": "string"
  },
  "positionUpdatedAt": {
    "label": "Position re-checked",
    "format": "string"
  },
  "profileUrl": {
    "label": "Profile",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The LinkedIn Company Employees Scraper — Emails, Phones, by Domain Actor is ready to run with the inputs already set for "Find Software Engineers Working at a Specific Company". [Sign up or log in](https://console.apify.com/create-task-from-example/dQyThPswS6aAKFxTe) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Find Software Engineers Working at a Specific Company" task

The LinkedIn Company Employees Scraper — Emails, Phones, by Domain Actor will start running based on the input automatically. You can also change all the input fields, like companies, seniority roles (optional), and more, to match your specific use case.

### 3. Receive the "Find Software Engineers Working at a Specific Company" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as name, title, personal email, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Find Software Engineers Working at a Specific Company" task via API](https://apify.com/b2bsearch/company-employees.md).

## FAQ

### What does the engineers at a company task return?

The engineers at a company task returns everyone at the company whose title contains engineer or developer, minus sales and solutions engineers, with title, start date in the role, email flags and LinkedIn URL.

### How do I find one team, such as data or security?

Replace the words in Title contains, for example data engineer, security or platform. The engineers at a company task keeps a person when the title contains any of the words, up to 10 of them.

### Why does time in role matter for recruiting?

Tenure helps you prioritise: the engineers at a company task shows when each person started the current role, so you can reach people two or more years into a job first.

### Can I get personal emails for the engineers?

Set Profile detail to contacts in the engineers at a company task and Must have to personal email: only engineers with a personal mailbox on record are delivered and charged.

## About this Actor

This example demonstrates how to use [LinkedIn Company Employees Scraper — Emails, Phones, by Domain](https://apify.com/b2bsearch/company-employees.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/b2bsearch/company-employees.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/b2bsearch/company-employees.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).