Unit 706 · restricted
Developers and integrations, L2
A restricted role in the developers and integrations family. Restricted roles are advertised by unit number, role family and level only; you will hear more at interview, on a need-to-know basis.
- Level
- L2 Practitioner
- Owns small outcomes end-to-end.
- Industry equivalent
- Mid-level, professional (no prefix)
- Typically 2 to 5 years
- NATO equivalent
- OR-5
- Sergeant, lieutenant. Indicative, not a rank.
- Hiring window
- Depth
- Q4 2029 to Q3 2030 · Register interest
What we expect at L2: Owns small outcomes end-to-end.
Independently delivers a feature slice, workflow improvement, or analysis with minimal supervision.
Impact and scope
What you own and how far your decisions reach.
- Owns a small outcome from definition to delivery.
- Understands users and constraints well enough to propose options.
- Flags trade-offs and risks with sensible recommendations.
Execution and delivery
How you plan, execute, and ship.
- Plans work, sets expectations, and meets commitments.
- Uses instrumentation, logs, QA, or operational checks to validate outcomes.
- Coordinates small changes across systems when needed.
Craft and quality
Correctness, maintainability, and professionalism.
- Writes maintainable work with tests, SOP updates, and clear documentation.
- Improves existing systems instead of only adding new ones.
- Uses standards and shared components to reduce bespoke complexity.
Collaboration
How you communicate, align, and work with others.
- Works effectively across functions and time zones.
- Writes clear updates: what changed, why, and how to operate it.
- Contributes to constructive reviews and decisions.
Security and trust
How you protect data, users, and the organization.
- Applies secure defaults and least privilege consistently.
- Understands how work affects privacy and compliance.
- Treats observability data as potentially sensitive.
Growth and leadership
How you learn, mentor, and raise the bar.
- Mentors peers informally through pairing, shadowing, or reviews.
- Builds reusable knowledge: templates, runbooks, and playbooks.
- Owns a skill area and keeps it current.
Developers and integrations
Platform builders: product engineering, data, SRE, integration engineering.
Typical titles at L2
Software engineer | Integration engineer | SRE (mid)
Examples of the work
- API and data integrations
- Reliability and incident response
- Observability and auditability
- Automation and deployment safety
Service lens
- APIs and data contracts are part of evidence integrity.
- Every integration must be observable, auditable, and secure-by-default.
- Operational users need calm workflows and safe failure modes.
About restricted roles
Restricted units build and protect our platform. Their roles are advertised by unit number, role family and level only, with no programme, customer or capability detail. Unit numbers are random and carry no meaning.
Before you start there is enhanced screening (identity, right to work, five years of verified history, references), an interview with the unit and a separate security interview. We say "restricted", not "cleared": Ireland has no statutory clearance for private-sector staff.
NATO grade equivalents follow STANAG 2116 and are indicative, to help people who have served read a role. They are not ranks.
Register interest
It takes about five minutes. You need your CV. We do not ask for your nationality, date of birth or a photo.
We have your application.
A confirmation is on its way to your inbox. A person on our People team reads every application, and we will email you if we would like to talk.