# remote-tech-jobs-hiring-signals (`aetheronix-lab/remote-tech-jobs-hiring-signals`) Actor

Aggregate live remote tech job postings, company names, categories, tags, and salary signals from public remote job feeds to power job boards, recruitment workflows, and B2B sales hiring triggers.

- **URL**: https://apify.com/aetheronix-lab/remote-tech-jobs-hiring-signals.md
- **Developed by:** [Zaigham Abbas](https://apify.com/aetheronix-lab) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

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 examples already wired to this Actor's own input schema, see the [API](#api) section below.

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`).

# README

## Remote Tech Jobs, Salary & B2B Hiring Intent Signal Scraper

Extract live remote tech job openings, hiring company names, required locations, disclosed salary ranges, and tech stack tags in seconds. Built for recruitment agencies, job board aggregators, and B2B sales teams tracking active hiring intent.

### Key Enterprise Features

- **B2B Hiring Intent Signals**: Identify companies actively spending budget on engineering, AI, data, DevOps, and marketing roles.
- **Structured Skill & Salary Tags**: Outputs normalized columns for salary disclosure, tech stack tags, and remote geography.
- **MCP & AI Agent Ready**: Built with strict schemas and Limited Permissions for Claude, Cursor, n8n, Make, and Apify MCP Server.

# Actor input Schema

## `searchKeyword` (type: `string`):

Keyword to filter remote jobs (e.g., engineer, react, python, ai, marketing).

## `category` (type: `string`):

Category filter (e.g., software-dev, data, devops, product, marketing, design).

## `maxJobs` (type: `integer`):

Maximum number of remote job listings to return (Free plan runs cap gracefully at 50).

## Actor input object example

```json
{
  "searchKeyword": "engineer",
  "category": "software-dev",
  "maxJobs": 50
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchKeyword": "engineer",
    "category": "software-dev"
};

// Run the Actor and wait for it to finish
const run = await client.actor("aetheronix-lab/remote-tech-jobs-hiring-signals").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchKeyword": "engineer",
    "category": "software-dev",
}

# Run the Actor and wait for it to finish
run = client.actor("aetheronix-lab/remote-tech-jobs-hiring-signals").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchKeyword": "engineer",
  "category": "software-dev"
}' |
apify call aetheronix-lab/remote-tech-jobs-hiring-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aetheronix-lab/remote-tech-jobs-hiring-signals"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/25UscxLpvh4Rj9tsn/builds/IZ20tqz8oasQ7NHlq/openapi.json