Salary
Posted
Jul 26, 2026
Location
Last confirmed open
Jul 28, 2026

What this job asks for AI summary

A contract backend engineering role on a large-scale SaaS bikeshare platform, focused on designing and shipping new features, integrating legacy systems with modern services, and keeping a globally distributed platform stable. The work is primarily server-side Java and Python, with cloud infrastructure on AWS, and suits a mid-level developer comfortable owning features end-to-end in a cross-functional team.

Mid level · 3+ years · Contract

Must have (6)
JavaPythonMySQL, PostgreSQL, SQL Server or OracleAWS, Azure or GCPTerraform or PulumiDataDog or Dynatrace
Nice to have (1)
distributed systems

“or” means any one of them counts — you don't need all of them.

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

What won't set you apart
Python51%MySQL40%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $138,970 (middle half $107,524–$175,762).

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (7)

The posting explicitly states 'We're seeking talented contractors', so this is classified as a contract engagement.

AWS and infrastructure-as-code are listed under Required Skills but framed with 'familiarity with', which softens the gate slightly; they are retained as required given their placement in the required section. The infra-as-code requirement names no specific tool — Terraform, Pulumi, and CloudFormation are listed as common substitutes.

DataDog is listed under Required Skills with 'or similar observability tools', so well-known alternatives are captured.

MySQL is listed under Required Skills with 'or other RDBMS', so common relational database alternatives are captured.

Distributed systems experience is listed under Preferred Experience as 'a plus', so it is marked preferred.

The 3+ years figure comes from the Preferred Experience section rather than a hard-requirements block; however, it is the only experience signal in the posting and is treated as the role-level minimum.

Posting is for a contract engagement — the market benchmarks below price full-time roles, so read the comp comparison with that in mind.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗