Contract
Lead Engineer — Drupal / Web Platforms
Hiring evidence involving Drupal, WordPress, JavaScript. First observed 14 Sept 2026; the response opens on job-boards.greenhouse.io.
- Budget
- Not provided by source
- Work format
- Hiring
- Role family
- Software engineer
- Seniority
- Lead / principal
- Observed
- 14 Sept 202613 days old
- Response destination
- job-boards.greenhouse.io
Source job details
Structured facts are published only when supplied by the source; missing values are never invented.
- Hiring organization
- Current
- Source reference
- OPP-20260914-1232
- Location evidence
- United States remote
- Employment type
- full time
- Required skills
- Drupal, WordPress, PHP, JavaScript, React, Vue, Angular, Node.js, LAMP, AWS, Acquia, Pantheon, Azure, GCP, Docker, Kubernetes, CI/CD
- Expected duration
- Full-time permanent employment
What this signal says
This is a delayed public reading of the demand behind “Lead Engineer — Drupal / Web Platforms.” 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
This record contributes to the normalized topic set Drupal, WordPress, JavaScript, React, Node.js, Docker, AWS. The mapping is evidence-based and intentionally conservative. It looks for named technology terms in the public-safe opportunity fields, resolves aliases, then checks any combination as a set of requirements rather than a loose keyword. This makes the page discoverable under stable technology hubs without pretending that a tag replaces technical due diligence. The source may contain additional context, but no unpublished contact or outreach field is used to create the public classification.
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 “Hard blocker: remote work is limited to the United States; the application asks for US work authorisation and sponsorship status..” The stated duration context is “Full-time permanent employment.”
Reading the budget
Budget data is unavailable from the source for this record. That is a statement about one missing field, not about whether the opportunity itself is public: this evidence page is published and indexable. Leadiy keeps the gap visible instead of inventing a midpoint or borrowing a number from another listing. Ask the source to confirm amount, currency, unit, inclusions and payment schedule before treating the opportunity as commercially qualified.
Demand context from Hiring Pulse
In the current 30-day Hiring Pulse, Drupal appears in 116 of 1188 observed opportunities (9.8%). 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 14 Sept 2026, 20:38 UTC; at page render it is 13 days old. Its public eligibility time was calculated once from that observation using a deterministic 37.77-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
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 Software Engineer — FastAPI/React/Node and AI-assisted delivery", "Senior Fullstack Engineer — AI", "Software Engineer (PHP / Drupal / JavaScript)" 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 Current Greenhouse / We Work Remotely on job-boards.greenhouse.io. 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 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 job-boards.greenhouse.io. That third-party page controls login, eligibility, proposal fields, privacy and the current status of the opportunity.