Other / unclear
Senior React Native developer for AI-powered SaaS
Project evidence involving TypeScript, React, Node.js. First observed 7 Sept 2026; the response opens on upwork.com.
- Budget
- $100
- Work format
- Project
- Role family
- AI / ML engineer
- Seniority
- Senior
- Observed
- 7 Sept 202616 days old
- Response destination
- upwork.com
What this signal says
This is a delayed public reading of the demand behind “Senior React Native developer for AI-powered SaaS.” 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 TypeScript, React, Node.js, OpenAI API, Tool/function calling, AI-enabled SaaS and web products. 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
The current format label is Project, meaning a defined delivery outcome rather than an open-ended employment relationship. Leadiy uses this shared taxonomy so technology hubs can show whether demand arrives as delivery work, capacity, procurement or employment. Classification does not resolve contract law, worker status or platform terms, and it should not be read as an endorsement of eligibility. A timing signal is present as “Open; no closing date published,” but the source should be checked before treating it as a live deadline.
Reading the budget
The published budget field reads “$100.” Leadiy preserves that wording because a fixed amount, range, hourly rate, daily rate and salary cannot be safely collapsed into one comparable number. Taxes, platform fees, currency conversion, milestones, scope changes and payment terms are not inferred. It remains an opening constraint rather than a valuation of the work. Confirm the unit, currency, inclusions and payment schedule at the source before using it for a proposal.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, TypeScript appears in 279 of 1305 observed opportunities (21.4%). Counts are multi-label, so one opportunity may contribute to several technology buckets. The comparison is dated through 2026-09-23 and describes Leadiy’s observed sample, not the whole software market. It helps answer whether this record sits beside other visible signals, but it does not prove future demand, market share or buyer intent. The individual page and the aggregate Pulse use the same public-safe vacancy and project scope, while direct leads and personal data remain excluded from both.
Observation and publication timing
Timing here is explicit: observed by Leadiy on 7 Sept 2026, 10:33 UTC, 15 days old at the current request, then admitted to the public catalog after 35.30 hours. The system never recomputes a shorter delay because a page is requested frequently. This is an evidence timestamp, not a promise that the source remains open, and not a reconstruction of when the buyer first posted. Visitors who need the freshest matched records use the authenticated product; the public page is intentionally the later, indexable edition.
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: "CTO / Solution AI Architect for new AI product", "Full-stack JavaScript developer for production AI web platform", "Senior Full-Stack Developer for Gamified AI-Powered Learning Platform" 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
The response button on this page opens Upwork at upwork.com. It leaves Leadiy and goes to the original opportunity URL; Leadiy is not the application destination and does not relay a response from this public page. The source may require its own account, profile, proposal form, geographic eligibility or platform terms. Check the destination address before entering information, and use the source’s current instructions rather than any summary here. This disclosure is intentionally repeated beside the button so the action is clear before a visitor clicks.
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.