Contract
Senior Site Reliability Engineer — AI/ML platform
Hiring evidence involving Python, Prometheus, Grafana. First observed 23 Sept 2026; the response opens on nofluffjobs.com.
- Technology
- PythonPrometheusGrafana
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- AI / ML engineer
- Seniority
- Senior
- Observed
- 23 Sept 20265 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
- Link Group / undisclosed AI-platform client
- Source reference
- OPP-20260923-1302
- Location evidence
- Poland-listed remote / CET–CEST
- Employment type
- full time
- Required skills
- Kubernetes, Prometheus, Grafana, distributed tracing, Python, Go, Terraform, CI/CD, AI/ML infrastructure, GPU workloads, SLO/SLI, incident response
- Expected duration
- Permanent full-time employment
What this signal says
The observed opportunity titled “Senior Site Reliability Engineer — AI/ML platform” enters this catalog as a market signal with a traceable source. Leadiy does not republish the original description. Instead, it separates a few decision-grade facts from the private operating record and adds context from the same demand dataset. That boundary matters: the public edition can help a developer or agency assess relevance, while the source remains responsible for complete requirements, eligibility, current status and the actual response flow. Any fact not shown here should be checked at that destination.
How the technology was normalized
The controlled technology reading for this record is Python, Prometheus, Grafana. 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
Leadiy reads the buying motion as Hiring. This matters because the response shape for a deliverable, contractor seat, formal proposal and employment application is not interchangeable. The category is a classifier output rather than a legal characterization, and the original post wins if its terms change. The available duration wording is “Permanent full-time employment.” Work-location context is recorded as “Fully remote, but compensation is explicitly gross employment salary rather than B2B/contract..”
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, Python appears in 421 of 1216 observed opportunities (34.6%). 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 23 Sept 2026, 02:34 UTC, 5 days old at the current request, then admitted to the public catalog after 41.92 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
Similarity is based on shared normalized technology tags and then recency, not on company identity or copied source prose. "DevOps Engineer", "Senior MLOps Engineer — AI Infrastructure & Pipelines", "Senior Full Stack Developer — Python/FastAPI and React/Next.js" 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 No Fluff Jobs at nofluffjobs.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 nofluffjobs.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.