Hiring
Senior Front-End Drupal Developer JP055112 — Central Bank of Luxembourg eShop
Hiring evidence involving Drupal, Drupal Commerce, JavaScript. First observed 6 Sept 2026; the response opens on lu.linkedin.com.
- Technology
- DrupalDrupal CommerceJavaScript
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- CMS developer
- Seniority
- Senior
- Observed
- 6 Sept 202612 days old
- Response destination
- lu.linkedin.com
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- ITproposal / NTek for Banque centrale du Luxembourg
- Source reference
- OPP-20260906-782
- Location evidence
- Luxembourg / Europe-Luxembourg
- Employment type
- contractor
- Required skills
- Drupal 11, PHP 8.3, Pantheon, Drupal Commerce/e-commerce, Tailwind CSS, vanilla JavaScript, Figma, ERP, online payments, multilingual FR/EN/DE, WCAG 2.2, Core Web Vitals
- Expected duration
- Initial assignment through 13 October 2026, about two months; possible extension; ASAP start
What this signal says
This is a delayed public reading of the demand behind “Senior Front-End Drupal Developer JP055112 — Central Bank of Luxembourg eShop.” 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 Drupal, Drupal Commerce, JavaScript. 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
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 “Initial assignment through 13 October 2026, about two months; possible extension; ASAP start.” Work-location context is recorded as “Hard blocker: the assignment is onsite at Boulevard Royal 2, Luxembourg; no remote option is stated..”
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, Drupal appears in 115 of 1254 observed opportunities (9.2%). Counts are multi-label, so one opportunity may contribute to several technology buckets. Hiring Pulse is the contextual layer Leadiy adds beyond aggregation. It places the record against a verified observation window while keeping counting rules visible: technologies can overlap, the feed is not a census, and sparse groups are not disclosed as exact numbers. This evidence can support prioritization, not a forecast. The record still needs source-level verification, and the aggregate view deliberately omits direct leads, personal information, private outreach content and arbitrary micro-segments that could reveal too much.
Observation and publication timing
Timing here is explicit: observed by Leadiy on 6 Sept 2026, 07:29 UTC, 12 days old at the current request, then admitted to the public catalog after 42.21 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: "Senior Drupal Developer — European Institution", "Senior Drupal Engineer (AWS)", "Freelance Senior Drupal Developer — German-speaking remote" 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
This page’s action route is explicit: it opens LinkedIn (ITproposal; duplicate NTek cross-post) on lu.linkedin.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 lu.linkedin.com. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.