Contract
Senior AI Engineer — LLM / Agentic Systems
Hiring evidence involving TypeScript, JavaScript, Python. First observed 21 Sept 2026; the response opens on nofluffjobs.com.
- Technology
- TypeScriptJavaScriptPythonDockerAWSRAG+2 more in the evidence
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- AI / ML engineer
- Seniority
- Senior
- Observed
- 21 Sept 20267 days old
- Response destination
- nofluffjobs.com
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- Square One Resources / undisclosed healthcare analytics client
- Source reference
- OPP-20260921-1266
- Location evidence
- Remote Poland / CET–CEST
- Employment type
- contractor
- Required skills
- Python, TypeScript/JavaScript, LLM applications, prompt/tool/function calling, MCP, RAG, agentic workflows, Strands, LangChain, Pydantic, AWS API Gateway/Lambda, Terraform, Docker, evaluation-driven development
- Expected duration
- Full-time B2B; start ASAP; duration not published
What this signal says
Leadiy recorded “Senior AI Engineer — LLM / Agentic Systems” 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
For comparison across sources, Leadiy maps the visible stack to TypeScript, JavaScript, Python, Docker, AWS, RAG, AI agents and agentic workflows, Tool/function calling. Source marketplaces often mix frameworks, platforms, infrastructure and delivery language in one line, so a literal string would fragment the market view. The controlled catalog keeps stable concepts together while retaining the original stack as a concise fact below. Detection is multi-label: several technologies may be valid at once, and a stack combination is admitted only when its required components appear. Buyers and suppliers should still use the source page to confirm versions, depth and mandatory versus optional skills.
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 “2026-10-02,” 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 284 of 1216 observed opportunities (23.4%). Counts are multi-label, so one opportunity may contribute to several technology buckets. The comparison is dated through 2026-09-29 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 21 Sept 2026, 02:31 UTC, 7 days old at the current request, then admitted to the public catalog after 24.06 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: "AI Engineer — agents, AI Gateway and enterprise integrations", "Full-Stack AI & Automation Engineer — first product version", "Machine Learning Engineer — GenAI/LLM/RAG" 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
Applying means leaving Leadiy for nofluffjobs.com, identified here as No Fluff Jobs. 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 nofluffjobs.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.