Hire developers · Back-end

Back-end

Hire Python engineers

Two largely separate candidate pools — web and API engineers, and data or ML engineers. Which one you need changes the search entirely.

Category
Back-end
Roles
4
Screening
By an engineer, with written evidence
Terms
Quoted per role, in writing

What they are hired to build

The work, before the CV.

A role written against the work gets a better shortlist than a role written against a stack. These are what Python engineers are usually brought in to do.

Roles we recruit: Python backend engineer · Django or FastAPI developer · Data engineer (Python) · ML engineer.

  • Django and FastAPI services
  • Data pipelines, ETL and automation
  • Backends for AI and ML features
  • Internal tooling and integration work

The technical screen

What the conversation actually covers.

Every candidate has a real technical conversation with an engineer who has done the job, and you get written evidence per competency. In Python, that conversation covers the following.

Usually assessed alongside: Django or FastAPI, PostgreSQL, Celery, pandas / SQL.

  • Which of the two pools they are actually in — asked directly, early
  • Async Python, and whether the role needs it at all
  • ORM behaviour, query counts and migrations under Django
  • Packaging, environments and dependency management on a real team
Worth saying up front

A job description that says only 'Python' will produce a shortlist split between two disciplines. We will ask you to pick one before we source.