Project
Cloud Infrastructure Lead / Senior DevOps — ERP migration to AWS
Hiring evidence involving Docker, GitHub Actions, Cloudflare. First observed 3 Sept 2026; the response opens on upwork.com.
- Technology
- DockerGitHub ActionsCloudflareAWSOpenTelemetryPrometheus+2 more in the evidence
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- DevOps / SRE engineer
- Seniority
- Senior
- Observed
- 3 Sept 20269 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 European software company
- Source reference
- OPP-20260903-448
- Location evidence
- Andorra; Spain preferred / Europe-Central
- Employment type
- full time
- Required skills
- AWS, Terraform/IaC, Docker Compose, GitHub Actions, Cloudflare, HAProxy, Nginx, SQL Server, Windows, Prometheus, Grafana, Loki, Alertmanager, OpenTelemetry, Zabbix, .NET/Blazor
- Expected duration
- Full-time; 6+ months; expected conversion to permanent employment
What this signal says
Leadiy recorded “Cloud Infrastructure Lead / Senior DevOps — ERP migration to AWS” 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 Docker, GitHub Actions, Cloudflare, AWS, OpenTelemetry, Prometheus, Grafana, AWS + Docker + GitHub Actions. 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 “Worldwide listing, but Spain preferred; other Europe considered only with compatible hours and professional Spanish.” The stated duration context is “Full-time; 6+ months; expected conversion to permanent employment.”
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, Docker appears in 138 of 1177 observed opportunities (11.7%). Counts are multi-label, so one opportunity may contribute to several technology buckets. The comparison is dated through 2026-09-13 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
The first-observed timestamp is 3 Sept 2026, 05:33 UTC, which makes this record 9 days old when this page is rendered. Public release waited 31.85 hours, selected deterministically between 24 and 48 hours from the record identifier. That rule survives process restarts and does not drift with each request. It also separates two clocks that are easy to confuse: the source may have published earlier, whereas Leadiy records when its own system first saw the opportunity. Paid access is to the earlier matched feed, not to a claim about the source’s original posting time.
What looks similar
Similarity is based on shared normalized technology tags and then recency, not on company identity or copied source prose. "Legacy investment platform rebuild", "Python backend / AI platform engineer for data pipelines, RAG, agents and AWS", "Python Backend / AI Platform Engineer — data pipelines, RAG, agents and AWS" 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 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 upwork.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.