Contract
AI Developer & Consultant — LLM, automation and API integration
Hiring evidence involving TypeScript, JavaScript, Python. First observed 29 Aug 2026; the response opens on upwork.com.
- Technology
- TypeScriptJavaScriptPythonPostgreSQLAWSOpenAI API+2 more in the evidence
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- AI / ML engineer
- Seniority
- Level not stated
- Observed
- 29 Aug 202610 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 Ukraine-based software buyer
- Source reference
- OPP-20260829-247
- Location evidence
- Ukraine / Europe-Kyiv
- Employment type
- contractor
- Required skills
- Python, JavaScript/TypeScript, OpenAI, Anthropic, Gemini, REST APIs, RAG, embeddings, vector search, LangChain/LlamaIndex, PostgreSQL/Supabase/Firebase, AWS/GCP/Azure
- Expected duration
- Approximately 10 h/week initially; 6+ months; flexible hourly or fixed-price; contract-to-hire
What this signal says
Leadiy recorded “AI Developer & Consultant — LLM, automation and API integration” 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
This record contributes to the normalized topic set TypeScript, JavaScript, Python, PostgreSQL, AWS, OpenAI API, RAG, Vector search and knowledge systems. 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 Hiring, meaning an employment-oriented search for an individual contributor or team member. 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 “Budget not provided by source (open while active),” but the source should be checked before treating it as a live deadline.
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. 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 29 Aug 2026, 11:02 UTC; at page render it is 10 days old. Its public eligibility time was calculated once from that observation using a deterministic 25.30-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", "AI full-stack engineer for scalable AI applications", "Production document-intelligence pipeline: OCR, LLM extraction and cited RAG" 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
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.