Contract
Senior Full-Stack Developer (AI + Supabase, Cursor) — Full-Time, Remote
Hiring evidence involving TypeScript, JavaScript, React. First observed 29 Aug 2026; the response opens on upwork.com.
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- AI / ML engineer
- Seniority
- Senior
- Observed
- 29 Aug 20269 days old
- Response destination
- upwork.com
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- Cloud29
- Source reference
- OPP-20260829-200
- Location evidence
- Manchester, UK / Europe-London
- Employment type
- full time
- Required skills
- Cursor, JavaScript/TypeScript, React/Next.js-style frontend, Supabase/Postgres, REST APIs, webhooks, AI prompt/rules engine, Git/GitHub, Loom, Slack
- Expected duration
- Full-time, long-term; Monday–Friday 09:00–18:00 UK time
What this signal says
The observed opportunity titled “Senior Full-Stack Developer (AI + Supabase, Cursor) — Full-Time, Remote” enters this catalog as a market signal with a traceable source. Leadiy does not republish the original description. Instead, it separates a few decision-grade facts from the private operating record and adds context from the same demand dataset. That boundary matters: the public edition can help a developer or agency assess relevance, while the source remains responsible for complete requirements, eligibility, current status and the actual response flow. Any fact not shown here should be checked at that destination.
How the technology was normalized
The controlled technology reading for this record is TypeScript, JavaScript, React, Next.js, PostgreSQL, Next.js + Supabase/PostgreSQL. That label is derived from explicit terms in the role, primary technology and stack fields; it is not inferred from the buyer’s identity or from private contact context. Normalization folds common spelling and naming variants into one catalog so this page can be compared with other records. A combination tag appears only when every required part of that combination is detected. The result is a search aid, not a guarantee that every named tool is equally central to the delivery scope.
Commercial format
Leadiy reads the buying motion as Hiring. This matters because the response shape for a deliverable, contractor seat, formal proposal and employment application is not interchangeable. The category is a classifier output rather than a legal characterization, and the original post wins if its terms change. The available duration wording is “Full-time, long-term; Monday–Friday 09:00–18:00 UK time.” Work-location context is recorded as “Worldwide remote, but explicitly no agencies and no multiple main clients; exclusive full-time individual only.”
Reading the budget
The source did not provide a budget for this opportunity. “Budget not provided by source” describes that missing commercial field; it does not mean the opportunity page is unpublished or unavailable. Leadiy does not estimate a range from similar records because fixed projects, hourly work, contracts and salaries are not safely interchangeable. Confirm compensation, currency, rate unit, scope and payment terms at the response destination before deciding whether to proceed.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, TypeScript appears in 217 of 1038 observed opportunities (20.9%). Counts are multi-label, so one opportunity may contribute to several technology buckets. Hiring Pulse is the contextual layer Leadiy adds beyond aggregation. It places the record against a verified observation window while keeping counting rules visible: technologies can overlap, the feed is not a census, and sparse groups are not disclosed as exact numbers. This evidence can support prioritization, not a forecast. The record still needs source-level verification, and the aggregate view deliberately omits direct leads, personal information, private outreach content and arbitrary micro-segments that could reveal too much.
Observation and publication timing
The first-observed timestamp is 29 Aug 2026, 05:59 UTC, which makes this record 9 days old when this page is rendered. Public release waited 32.54 hours, selected deterministically between 24 and 48 hours from the record identifier. That rule survives process restarts and does not drift with each request. It also separates two clocks that are easy to confuse: the source may have published earlier, whereas Leadiy records when its own system first saw the opportunity. Paid access is to the earlier matched feed, not to a claim about the source’s original posting time.
What looks similar
The related-record layer searches already published pages for overlap in the controlled technology catalog. It does not inspect private contacts and it does not use a buyer name as a recommendation signal. The closest current titles are: "Fractional Next.js internal workflow apps", "React/Next.js drag-and-drop wedding floor-plan editor", "Next.js and Supabase application development" Treat them as adjacent demand signals, not substitutes for reading the original post. Their engagement format, budget unit, eligibility and delivery expectations may differ even when a framework or platform matches. This page keeps that uncertainty visible rather than manufacturing a single “typical” opportunity from unlike records.
Where the response goes
Applying means leaving Leadiy for upwork.com, identified here as Upwork. The link is the normalized direct source URL stored with the opportunity. No public form on Leadiy submits an application, and no contact detail is exposed as a shortcut. The destination can impose login, marketplace credits, identity checks, location limits or other terms that are outside this catalog. Verify the hostname and the current post before sharing information. If the source has closed or changed the opportunity, its live state is authoritative.
Public evidence versus earlier access
Leadiy sells timing, not a different truth: the same opportunities, one day earlier. Subscribers receive the fresh matched feed and private workflow before a record crosses its public time fence. The later page remains complete enough to stand alone, with provenance, classification, budget reading, aggregate context and related records. Subscription is not preferential treatment from the buyer, and it cannot guarantee availability or success. It is earlier awareness plus an operational workspace; the public catalog is the delayed evidence layer.
The same opportunities, one day earlier.
See the $39 / 30-day plan →Your response leaves Leadiy.
The button opens upwork.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.