Contract
Full-Stack AI Engineer — citation-backed RAG, agents and automation
Hiring evidence involving React, Next.js, Node.js. First observed 6 Sept 2026; the response opens on upwork.com.
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- AI / ML engineer
- Seniority
- Level not stated
- Observed
- 6 Sept 202613 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
- Undisclosed US travel & hospitality company
- Source reference
- OPP-20260906-751
- Location evidence
- Brooklyn, USA / America-New_York
- Employment type
- contractor
- Required skills
- Python, React, Next.js, Node.js, OpenAI/Claude, LangChain, Pinecone/FAISS, Firebase/Supabase, AWS, Docker, n8n
- Expected duration
- 3–6 months; more than 30 hrs/week; contract-to-hire
What this signal says
This is a delayed public reading of the demand behind “Full-Stack AI Engineer — citation-backed RAG, agents and automation.” It is deliberately smaller than the private workspace record and deliberately more interpretive than the source listing. The page identifies the work, translates its technology language into Leadiy’s controlled catalog, names the commercial format and preserves the original application destination. It does not publish personal contacts, internal qualification, prepared outreach or hidden source fields. Read it as an evidence note about one observed opportunity, with the source link retained for the current authoritative details.
How the technology was normalized
This record contributes to the normalized topic set React, Next.js, Node.js, Python, Docker, AWS, OpenAI API, RAG, n8n, Next.js + Supabase/PostgreSQL, Next.js + Node.js/NestJS. The mapping is evidence-based and intentionally conservative. It looks for named technology terms in the public-safe opportunity fields, resolves aliases, then checks any combination as a set of requirements rather than a loose keyword. This makes the page discoverable under stable technology hubs without pretending that a tag replaces technical due diligence. The source may contain additional context, but no unpublished contact or outreach field is used to create the public classification.
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 “3–6 months; more than 30 hrs/week; contract-to-hire.” Work-location context is recorded as “Worldwide remote; agency/B2B route not stated — nominate one engineer and verify.”
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, React appears in 333 of 1254 observed opportunities (26.6%). Counts are multi-label, so one opportunity may contribute to several technology buckets. This aggregate context is intentionally bounded. The denominator is the current observed sample, technology counting overlaps, and small buckets may be suppressed. A single listing cannot establish a trend, and a technology’s share in Leadiy’s feed is not market share. The useful comparison is operational: it shows whether the normalized topic recurs among recently observed opportunities and gives the individual signal a dated reference point. Direct leads, contact data, raw source rows and private qualification notes do not enter that public calculation.
Observation and publication timing
Leadiy first observed this signal on 6 Sept 2026, 03:33 UTC; at page render it is 12 days old. Its public eligibility time was calculated once from that observation using a deterministic 39.88-hour delay inside the promised 24–48 hour window. The delay is not the source publication age and should not be presented as one. It creates a clear product boundary: authenticated customers can work from the live matched feed, while search engines and unauthenticated visitors receive a later evidence edition. The stored eligibility timestamp prevents an early publish after restarts or repeated syncs.
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: "Senior AI Full Stack Engineer — enterprise agents and workflow automation", "Full-stack Next.js developer for RAG chatbot and API integrations", "AI Engineer & Automation Developer — LLM agents and flow optimization" 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
This page’s action route is explicit: it opens Upwork on upwork.com. Leadiy provides context and provenance, not an application proxy. A click can therefore lead to a third-party login or proposal workflow governed by that service’s own privacy, eligibility and payment rules. The public catalog never replaces those instructions and never publishes a hidden email address as an alternate route. Review the destination hostname, confirm that the opportunity is still active, and respond only through a path you trust.
Public evidence versus earlier access
The commercial distinction is one sentence: the same opportunities, one day earlier. The paid workspace is for acting on newly matched signals with private workflow tools; this public edition is for later discovery, citation and market context. Paying does not improve the source’s terms or guarantee a response. It changes when the Leadiy record becomes available and adds the operating context needed to triage it. That boundary keeps the open catalog genuinely useful while preserving a simple reason to subscribe without hiding where the original response must be submitted.
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.