DEV Community

Cover image for How to Pull Python Developer Jobs from Reed.co.uk with Reed Scraper
ReventaData
ReventaData

Posted on Originally published at apify.com

How to Pull Python Developer Jobs from Reed.co.uk with Reed Scraper

By the end of this tutorial you will have a Python script that pulls UK job listings from reed.co.uk into structured rows: job title, company, location, salary range with its period, employment type, workplace arrangement and posting dates.

Reed Scraper (reventadata/reed-scraper) is the Apify Actor built for this site. You give it a search, such as python, and it returns one row per job vacancy. This guide runs it from Python with the Apify client. The sample rows below are copied from a real run of 16 November 2026 that searched python with no location and collected 10 rows, not from an invented example.


Prerequisites

You need three things:

  1. Python 3.11 or newer, which the Apify client requires.
  2. A free Apify account.
  3. Your Apify API token, from your Apify account.

Install the client and export the token:

pip install -U "apify-client~=3.0"
export APIFY_API_TOKEN="your_apify_token_here"
Enter fullscreen mode Exit fullscreen mode

No scraping code is needed on your side. The Actor reads the public search pages for you.


What you'll achieve

You will search reed.co.uk for python, read the rows in Python and print two lines per job: the title, company, location and salary first, then the employment type, workplace and whether Easy Apply is on.

Each row carries 29 fields, so you can also sort the results by salary or workplace afterwards. The output is plain text, one job per pair of lines, so it reads well in a terminal and pastes cleanly into a spreadsheet. The same script works for a job seeker comparing pay across towns, or for an analyst building a table of contract rates. Only the input changes.


Step 1: Open Reed Scraper

Open the Reed Scraper page on Apify Store. This tutorial uses the Actor from Python, so you need only its name, reventadata/reed-scraper.


Step 2: Choose the search

The search is described by a few input fields:

  • searchQueries: a list of job titles, keywords or full reed.co.uk search URLs. Required.
  • location: an optional UK city, county or region, applied to keyword searches. Left empty, the search has no place filter.
  • maxItems: the most rows to collect. Left unset, it defaults to 100.
  • maxPages: an optional limit on result pages per query. Each page holds 25 jobs.

A full reed.co.uk search URL in searchQueries is read as that search, with its filters kept.

The run behind this guide used this input:

{
    "searchQueries": ["python"],
    "location": "",
    "maxItems": 10,
    "maxPages": 1
}
Enter fullscreen mode Exit fullscreen mode

Step 3: Run it from Python

This script starts the Actor, waits for it, reads the dataset and prints two lines per job:

import os
from apify_client import ApifyClient

# 1. Initialise the client with your token from the environment
client = ApifyClient(os.environ["APIFY_API_TOKEN"])

# 2. Describe the search: Python jobs, no place filter, 10 rows from one page
run_input = {
    "searchQueries": ["python"],
    "location": "",
    "maxItems": 10,
    "maxPages": 1,
}

# 3. Start the Actor and wait for it to finish
run = client.actor("reventadata/reed-scraper").call(run_input=run_input)
if run is None or run.status != "SUCCEEDED":
    status = run.status if run else "unknown"
    raise SystemExit(f"Run did not succeed (status: {status}).")

# 4. Read the rows from the run's default dataset
items = client.dataset(run.default_dataset_id).list_items().items
print(f"Retrieved {len(items)} jobs.\n")

# 5. Print two lines per job
for item in items:
    salary = f"{item.get('salaryFrom')} to {item.get('salaryTo')} GBP, {item.get('salaryType')}"
    print(f"{item['title']} at {item['companyName']}, {item['location']} | {salary}")
    print(f"  {item['jobType']}, {item['workingOption']}, Easy Apply: {item['isEasyApply']}")
Enter fullscreen mode Exit fullscreen mode

The run_input is the same input as above. Change it to search for something else.


Step 4: Read the output

The loop prints two lines per job. Here are the first two jobs of the 10 rows, cut from the full output:

Retrieved 10 jobs.

Python Developer at Salt Search, Cambridge | 55000 to 75000 GBP, annual
  permanent, hybrid, Easy Apply: False
Python Developer at Sustain Recruit, Essex | 500 to 500 GBP, daily
  contract, hybrid, Easy Apply: True
Enter fullscreen mode Exit fullscreen mode

Each row has 29 fields. The script prints nine of them: title, companyName, location, salaryFrom, salaryTo, salaryType, jobType, workingOption and isEasyApply.

Salary amounts are shown in the period named next to them: annual, daily or hourly. The Actor does not convert them to a yearly figure, so 500 to 500 GBP, daily stays a daily rate. A salary of zero comes through as null.

One complete row from the run, verbatim, the first of the 10:

{
  "id": "57421497",
  "url": "https://www.reed.co.uk/jobs/python-developer/57421497",
  "title": "Python Developer",
  "descriptionSnippet": "Mid-level (2 years min commercial Python coding experience) - Cambridge | Hybrid - 2 days a week in office | 55,000- 70,000 Python with C++, Rust o...",
  "companyName": "Salt Search",
  "companyProfileName": "Salt Search",
  "companyProfileUrl": "https://www.reed.co.uk/jobs/Salt-Search-70274",
  "location": "Cambridge",
  "county": "Cambridgeshire",
  "salaryFrom": 55000,
  "salaryTo": 75000,
  "salaryType": "annual",
  "currency": "GBP",
  "jobType": "permanent",
  "isFullTime": true,
  "isPartTime": false,
  "workingOption": "hybrid",
  "dateCreated": "2026-10-05T08:30:31.26",
  "dateUpdated": "2026-10-17T08:32:17.38",
  "displayDate": "2026-10-05T08:30:31.233",
  "expiryDate": "2026-11-16T23:55:00",
  "category": "Developer",
  "subCategory": "Python Developer",
  "isFeatured": false,
  "isPromoted": false,
  "isEasyApply": false,
  "logoUrl": "https://resources.reed.co.uk/profileimages/logos/thumbs/.",
  "searchQuery": "python",
  "searchUrl": "https://www.reed.co.uk/jobs/python-jobs"
}
Enter fullscreen mode Exit fullscreen mode

Understanding your results

Each row has the fields below.

  • title, companyName, companyProfileName, companyProfileUrl: the job title, the company name and the company's profile on Reed. The company name is the employer's name when Reed gives one, and the profile name otherwise.
  • location, county: the town or city, and the county.
  • salaryFrom, salaryTo, salaryType, currency: the range, its period (annual, daily or hourly) and the currency, GBP.
  • jobType, isFullTime, isPartTime, workingOption: permanent or contract, the hours, and the workplace (hybrid, remote or onSite).
  • dateCreated, dateUpdated, expiryDate: when the vacancy was posted, last updated and closes. The values carry no time zone.
  • category, subCategory: the sector and specialism. In this run, nine rows read Developer and Python Developer, and one reads Engineer and Principal Engineer.
  • isEasyApply: nine of the 10 rows are true in this run.
  • descriptionSnippet: a short extract of the description. In these rows it ends with ....
  • url, searchQuery, searchUrl: the vacancy link, the query and the search page it came from.

In this run every field has a value on all 10 rows, and both salary fields are set on every row.


Pro tips

  1. Narrow the search with a place. Enter a UK town or county in location. Left empty, the search has no place filter.
  2. Keep maxPages small while you test. The run above used maxPages 1, and maxItems 10 ended it at 10 rows.
  3. Convert rates yourself. The Actor returns the range and its period, not a yearly figure. Multiply a daily or hourly rate by your own working days or hours.
  4. Copy an exact Reed search. Paste the reed.co.uk address of a search, filters included, into searchQueries.
  5. Expect repeats to be dropped. A job found by two queries, or twice on the same search, is kept once. The Actor skips a repeat by job id and by URL.
  6. Read the sector fields for a split. category and subCategory name the sector and specialism of each vacancy, so a table grouped by them shows how a search divides.

Troubleshooting

  • Zero rows, status SUCCEEDED. The site answered and nothing matched. The status message says so and suggests broader keywords or looser filters.
  • Zero rows, status FAILED. Either the input cannot return anything (a search that does not exist on the site), or the site refused or could not be read in that run, so matches may have been missed. The status message says which: fix the input, or run again later.
  • Some rows, then a stop. If the run reaches its time limit, it keeps the rows already saved and logs a warning.
  • Fewer rows than maxItems. A page that fails is logged as a warning, and the run moves on to the next page. A repeat job is skipped and counted in the log. The log ends with Pushed N row(s).

Next steps

To repeat a search, save it as an Apify task and attach a schedule, which runs an Actor or task at times set by a cron expression. The dataset exports as JSON, CSV, XML, Excel, HTML table, RSS or JSONL (dataset docs).

For current pricing and details, see the Store page.

What are you planning to search for on Reed? Drop a comment below.

About the author: reventadata builds and publishes data extraction Actors on the Apify Store.

Top comments (0)