Contract
Senior AI Engineer — SysML knowledge base, agents and RAG
Hiring evidence involving AWS, LLM integrations, RAG. First observed 15 Sept 2026; the response opens on justjoin.it.
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- AI / ML engineer
- Seniority
- Senior
- Observed
- 15 Sept 202612 days old
- Response destination
- justjoin.it
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- Sigma Software / confidential EdTech client
- Source reference
- OPP-20260915-1247
- Location evidence
- Remote across Europe, Ukraine and LATAM; Europe/Kyiv compatible
- Employment type
- contractor
- Required skills
- Golang, LLM integrations, AI agents, multi-agent systems, RAG, ETL, semantic search, entity resolution, vector databases, knowledge graphs, Apache Spark/Beam, Kubernetes, AWS/GCP/Azure, observability
- Expected duration
- Full-time; duration not published
What this signal says
This is a delayed public reading of the demand behind “Senior AI Engineer — SysML knowledge base, agents and RAG.” 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
For comparison across sources, Leadiy maps the visible stack to AWS, LLM integrations, RAG, AI agents and agentic workflows, Monitoring and alerting. 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 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 “Remote B2B; Ukraine is explicitly included. Agency nomination is not stated, so use a named engineer..” The stated duration context is “Full-time; duration not published.”
Reading the budget
No budget value was supplied in the imported source record. The page labels this plainly as “Budget not provided by source” so publication status cannot be confused with compensation coverage. An absent figure is not converted into zero and is not inferred from neighbouring opportunities. The original destination remains the authority for price, salary, rate unit, fees, milestones and any later updates.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, AWS appears in 215 of 1188 observed opportunities (18.1%). 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 15 Sept 2026, 08:29 UTC; at page render it is 12 days old. Its public eligibility time was calculated once from that observation using a deterministic 24.82-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. "Principal AI Automation Engineer", "AI Process Engineer / AI Scientist — agentic workflows and RAG", "Senior Agentic SDLC Engineer" 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 Just Join IT at justjoin.it. 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 justjoin.it. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.