Contract
Fractional CTO — Agentic AI EdTech/FinTech platform
Hiring evidence involving TypeScript, React, Next.js. First observed 29 Aug 2026; the response opens on upwork.com.
- Technology
- TypeScriptReactNext.jsPythonPostgreSQLRedis+4 more in the evidence
- Budget
- $5 fixed price
- Work format
- Hiring
- Role family
- Engineering manager
- Seniority
- Lead / principal
- Observed
- 29 Aug 202611 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 EdTech/FinTech platform
- Source reference
- OPP-20260829-300
- Location evidence
- Tampa, Florida, USA / America-New_York
- Employment type
- contractor
- Required skills
- Gemini 2.0 Flash, LangChain, Vertex AI Vector Search, Python, Django/DRF, Django Channels, Celery, Redis, PostgreSQL, Next.js 15, React 19, TypeScript, GCP Cloud Run, Docker, GitHub Actions, JWT, OAuth
- Expected duration
- 20 or 40 hours/month; ongoing; immediate start; monthly fixed compensation must be proposed
What this signal says
Leadiy recorded “Fractional CTO — Agentic AI EdTech/FinTech platform” 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, Python, PostgreSQL, Redis, Docker, GitHub Actions, Vector search and knowledge systems, 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
The engagement classifier places this record in Hiring: an employment-oriented search for an individual contributor or team member. That decision comes from the supplied opportunity-type language, using the same categories as Hiring Pulse—project, contract, RFP or procurement, hiring, and other or unclear. It does not convert an ambiguous request into a stronger claim. The imported public-safe work-format field also says “Worldwide remote, but the listing explicitly forbids dev shops and organizations and requires one independent CTO; incompatible with Zanzarra agency delivery..” The stated duration context is “20 or 40 hours/month; ongoing; immediate start; monthly fixed compensation must be proposed.”
Reading the budget
The financial signal is “$5 fixed price,” exactly at the level available in the normalized record. No midpoint is invented and no missing value is estimated. This restraint is important when similar technology work can be sold as fixed delivery, hourly capacity, a retainer or employment. The number is useful for triage only after its unit and scope are understood. The application destination should be used to verify what the amount includes, whether it is negotiable, and whether platform or payment conditions change the supplier’s effective return.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, TypeScript appears in 227 of 1093 observed opportunities (20.8%). Counts are multi-label, so one opportunity may contribute to several technology buckets. The comparison is dated through 2026-09-10 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
Leadiy first observed this signal on 29 Aug 2026, 21:00 UTC; at page render it is 11 days old. Its public eligibility time was calculated once from that observation using a deterministic 32.80-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
Similarity is based on shared normalized technology tags and then recency, not on company identity or copied source prose. "Gamified AI-powered learning platform for high-school students", "Production document-intelligence pipeline: OCR, LLM extraction and cited RAG", "Custom Next.js ecommerce website and admin platform" These neighbours are useful for comparing delivery shape, budget visibility and technology overlap. They are not duplicates and they do not imply that the same buyer, scope or qualification rules apply. When no suitable public neighbour exists, the page says so instead of padding the section with unrelated links. New public records can change this comparison set after their own delay and quality checks pass.
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
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.