Most of these roles want someone who has produced engineering deliverables themselves. Remote-first, published compensation bands, paid practical exercises, and a hiring process that tells you where you stand.
Every role lists its band on the role page. If a requirement reads as a hard gate and you are close but not exact, apply and say so in a sentence.
Own the discipline, specialisation, deliverable, software and standards vocabularies that everything else on the platform reasons over. This is a practising-engineer role, not a data role: you will be arguing about whether pressure-equipment design is a specialisation of mechanical or a discipline in its own right, and the answer changes how thousands of projects get matched.
Detect and disrupt credential falsification, portfolio plagiarism, stolen design submissions and payment fraud. You will build the detection systems and also work the hard cases by hand, including high-risk project review where an unqualified engineer taking on life-safety work is the actual harm being prevented.
Own matching, intake and proposal comparison. The central tension in this role is that every field you add to the intake improves match quality and reduces completion rate, and you will be the person who has to decide where that line sits, with data.
Build the workroom, escrow and enterprise procurement surfaces. Dense, data-heavy interfaces where correctness matters more than novelty: a revision history that loses a transmittal, or an acceptance that releases funds against the wrong milestone, is not a cosmetic bug.
Run the verification ladder end to end: identity, education, professional registration, certification, portfolio ownership, references and discipline expert review. Build relationships with issuing authorities across jurisdictions and keep turnaround under 48 hours without loosening the checks.
Own the guides, briefs library and standards explainers. The quality bar is that a practising engineer reads a page and finds it precise rather than promotional. Most of what exists on the internet about writing an engineering brief is marketing copy, and that is the gap.
Assess contested engineering engagements against what was actually contracted. You will read the brief, the proposal, the acceptance criteria and the delivered files, then write a reasoned determination that both parties can understand even when one of them dislikes it.
Take a client requirement, write the technical brief with their engineers, assemble a multidisciplinary team, and chair the interface between disciplines through delivery. Part sourcing, part engineering programme management, entirely dependent on being credible in a technical room.
Listed specifically rather than as adjectives, because vague benefit copy usually means the benefit is vague.
No headquarters that decisions quietly route through. Written-first communication, meetings recorded and summarised, and a four-hour overlap window rather than a fixed timezone.
Every role has a published band, mapped to level rather than negotiation skill. Location adjustment uses three broad tiers, published, rather than a per-city formula nobody can audit.
Professional registration fees, chartership costs, institution memberships and CPD hours are covered for anyone pursuing or maintaining engineering registration. The taxonomy team is expected to stay registered.
Thirty-two days plus public holidays, with a ten-day minimum that is enforced rather than encouraged. Sabbatical of one paid month after four years.
Private medical cover including mental health provision, in every country we employ in. Twenty-six weeks primary and sixteen weeks secondary parental leave at full pay, with no distinction by gender or route to parenthood.
The machine you need, the software licences your discipline requires, a home-office budget, and access to standards subscriptions — including the paid standards bodies, which is not cheap and is not optional for this work.
You will know the compensation band in the first conversation and your status at every stage without having to chase us.
Read by a human on the hiring team, not filtered by keyword. You will hear either way within five working days. No cover letter required; a short note on why this specific problem interests you is more useful.
With the hiring manager. Mutual scoping: what the role actually involves, what you are looking for, compensation band confirmed up front so nobody's time is wasted on a mismatch.
For engineering roles, a discussion of real problems from the domain — no algorithmic puzzles, no live coding under observation. For taxonomy and content roles, we will disagree about a classification or a document structure and see how that goes.
A four-hour exercise drawn from real work, paid at your day rate, with a hard timebox we hold you to. You keep the work. If a take-home would be unreasonable for your circumstances, we run a paired session instead.
With people you would work alongside, including at least one person outside your function. These are two-way; they are also where you should ask the questions you would rather not ask the hiring manager.
Offer with the band position explained, then references at your convenience. From first conversation to offer is typically under three weeks, and we will tell you where you stand at every stage without being chased.
Discipline expert review is deliberately part-time contract work for practising engineers. Paid per review, roughly two to five hours a month, and the strongest reviewers are people with no intention of leaving their day job.
