Project
AI-native e-commerce operating system — full-stack engineer
Hiring evidence involving TypeScript, React, Next.js. First observed 30 Aug 2026; the response opens on upwork.com.
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- Full-stack developer
- Seniority
- Level not stated
- Observed
- 30 Aug 202612 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 AI-commerce startup
- Source reference
- OPP-20260830-323
- Location evidence
- Worldwide; buyer profile in Lahore, Pakistan
- Employment type
- full time
- Required skills
- Node.js, TypeScript, React, Next.js, PostgreSQL, NestJS/Express/Fastify, React Flow/Puck/Craft.js/GrapesJS, Tailwind, Prisma/Drizzle, Redis, queues, Shopify/payments APIs, LLM APIs, Docker, CI/CD
- Expected duration
- More than 30 hours/week; 6+ months; full-time and long-term
What this signal says
Leadiy recorded “AI-native e-commerce operating system — full-stack engineer” as a hiring signal, not as a copied job-board article. The public page keeps only the facts needed to understand the commercial request: the role or outcome, normalized technologies, engagement format, stated budget, observation time and the exact destination for a response. Contact names, email addresses, outreach drafts, private notes and the imported source row stay outside this page. The useful question is therefore narrow: what kind of software demand is visible here, and what should a supplier verify before deciding to respond?
How the technology was normalized
The controlled technology reading for this record is TypeScript, React, Next.js, Node.js, Fastify, NestJS, PostgreSQL, Redis, Docker, Next.js + Supabase/PostgreSQL, Next.js + Node.js/NestJS, Node.js + Redis + queues. 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 “More than 30 hours/week; 6+ months; full-time and long-term.” Work-location context is recorded as “Worldwide remote contractor; agency not explicitly addressed, so apply only with one named engineer.”
Reading the budget
Budget data is unavailable from the source for this record. That is a statement about one missing field, not about whether the opportunity itself is public: this evidence page is published and indexable. Leadiy keeps the gap visible instead of inventing a midpoint or borrowing a number from another listing. Ask the source to confirm amount, currency, unit, inclusions and payment schedule before treating the opportunity as commercially qualified.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, TypeScript appears in 232 of 1124 observed opportunities (20.6%). 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 30 Aug 2026, 02:00 UTC, which makes this record 11 days old when this page is rendered. Public release waited 26.34 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
To build a useful neighbourhood around this record, Leadiy compares normalized technology IDs and favours the strongest overlap among pages that have already cleared the public delay. The current result is: "Gamified AI-powered learning platform for high-school students", "Custom Next.js ecommerce website and admin platform", "AI Sales Operations Employee — autonomous CRM and outreach platform" This method makes relationships inspectable and avoids copying descriptive text from the source. Similarity means shared technical vocabulary, nothing more. It does not assert shared ownership, equal scope, equivalent seniority or an identical application process, and it can evolve as later records become publicly eligible.
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
The product promise stays deliberately plain: the same opportunities, one day earlier. Public visitors can inspect this delayed record without an account, but the private product exists for earlier matching and action. Neither route changes the buyer’s requirements, the third-party application flow or the probability of winning work. The value difference is lead time and workflow. Keeping that claim next to a useful, self-contained public page avoids a teaser model in which essential provenance or the true destination is withheld.
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.