Backend Platform Engineer - Labrynth at Infinity
—
Jul 26, 2026
—
Jul 28, 2026
What this job asks for AI summary
A contract backend engineering role (60–90 day initial term, with extension options) building the greenfield B2C API layer for an AI-assisted patent intelligence platform. The work centers on a modular TypeScript BFF with Fastify and OpenAPI, PostgreSQL with forced row-level security, Cognito-based identity, durable async operations via SQS, and Python worker integration — all delivered as a forward-deployed, remote-first engagement serving US and Australian project hours.
Senior level · Remote · Contract
Quick apply — this platform usually takes a CV and a few fields.
Posted 2 times — it's one opening, so apply once.
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
Roughly 7,000 people nationally plausibly meet what this posting asks for (software developers). range 1,450–10,400
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
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 (8)
This is a fixed-term agency/Statement-of-Work contract with a 60–90 day initial term and an option to extend; it is not a permanent hire.
No explicit total years of experience are stated; seniority is inferred from the depth and breadth of the technical requirements (advanced PostgreSQL RLS, distributed systems patterns, identity/authorization architecture, AI trust boundaries).
Compensation is hourly but no rate range is disclosed in the posting; the hiring process is described as the venue where rates will be confirmed.
The role requires meaningful overlap with both US and Australian business hours, which may constrain eligible time zones even though the role is remote-first.
Fastify, JSON Schema/TypeBox, and generated OpenAPI tooling are listed as 'strongly preferred' within the requirements section rather than in a separate nice-to-have block — treated as hard gates accordingly.
S3 appears in the stated stack but is not called out explicitly in the requirements prose; included as required given its presence in the stack the engineer must own.
pgvector, Neo4j, and Stripe appear under the 'Nice to Have' section and are marked preferred.
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.