Front End Developer - Labrynth at Infinity
—
Jul 26, 2026
—
Jul 28, 2026
What this job asks for AI summary
A contract front-end engineering role (60–90 days, with extension option) building a greenfield B2C platform in the patent/IP space. The engineer will own the full client-facing experience — invited-account onboarding, account and membership UX, a guided exploration interface, durable-operation progress via resumable SSE, and billing UI — all consumed through a generated TypeScript BFF client against a Next.js App Router architecture.
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,100 people nationally plausibly meet what this posting asks for (software developers). range 1,450–10,600
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 explicitly a contract engagement (Agency / Statement of Work) with an initial term of 60–90 days and an option to extend.
No overall years-of-experience figure is stated; seniority is inferred from the breadth and depth of the technical requirements (App Router SSR, SSE reconnect logic, idempotency/ETag concurrency, design-system ownership, E2E coverage).
Compensation is hourly but no rate range is disclosed in the posting; the hiring manager is told a range will be confirmed during the interview process.
The role is remote-first and requires meaningful overlap with both US and Australian business hours.
Neo4j, PostgreSQL, S3, and Stripe appear in the architecture description as systems the frontend does NOT directly access — they are listed as preferred/context skills because familiarity aids understanding of the system boundaries, not because the engineer will work with them directly.
'Graph visualization' and 'data virtualization' are listed under Nice to Have and carry no specific library name in the posting; they are captured as preferred with no canonical tool name available.
The title 'Front End Engineer' carries no seniority modifier, so the title states no level.
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.