Start a conversation
  1. Home
  2. Careers

Careers at Vandorq

Engineering work with actual depth.

If you want to own a system end to end — design it, build it, run it, and see what it does in production — this is that kind of company. Small teams, senior review, real infrastructure, no layer of people between you and the problem.

See open positions Send a general application
Hiring across
Cloud · Data · Software · Security · SRE
Work model
Hybrid and remote options by role
Interview process
Four stages, typically within two weeks
Review cycle
Twice yearly, against a published framework

01 / Why Vandorq

What is genuinely different here.

Every company claims growth and ownership. These are the specific mechanisms that make those words mean something in our day-to-day.

You see the whole system

Because we deliver across cloud, data, software and security, engineers here understand how their component behaves in the full stack — not just their slice of a ticket.

Senior review, every change

Your pull requests are read by people who have operated systems at scale. Feedback is technical, specific and written down — the fastest way anyone learns.

Ownership with authority

If you own a service you also make its architectural calls, within agreed guardrails. Accountability without authority is just blame, and we avoid it.

Time budgeted for depth

Learning, documentation and technical debt are line items in the sprint, not something you do at 10pm. Certification costs and exam time are supported.

Sane operations

On-call is paid, rotated fairly and measured. If a rotation is noisy, fixing the noise becomes the next sprint's priority — that is the deal.

Written culture

Decisions are recorded, designs are circulated before implementation, and good writing is treated as an engineering skill. It also makes remote work actually work.

02 / Culture

Direct, technical, unbothered by hierarchy.

We argue about designs and not about people. The most junior engineer in a review can challenge the most senior one, and is expected to — provided the argument is technical and specific.

We do not run a culture of visible busyness. Nobody is measured on hours online. Work is judged on whether the system behaves correctly, is understandable to the next engineer, and holds up under load and audit.

We are also honest about what this is not: we work with enterprise clients on production systems, which means change control, documentation and occasional unglamorous maintenance. If that sounds tedious rather than satisfying, we are probably not a fit.

Design before code

Non-trivial work starts with a short written design that anyone can comment on.

Blameless post-incident review

We analyse the system that allowed the failure, then fix it. Nobody is named as a cause.

Deep work protected

Meeting-light days by default; asynchronous updates preferred over status calls.

Client contact for engineers

You talk to the people using what you build. No permanent translation layer.

Feedback on a cadence

Short, direct, twice-yearly reviews against a published framework — no surprises.

Internal mobility

Engineers move between practices deliberately; cross-domain depth is rewarded.

E1

Engineer

Delivers well-scoped work with review. Learns the estate, the pipeline and the standards. Paired with a senior engineer for the first quarter.

E2

Engineer II

Owns components end to end, writes designs for review, participates in on-call and contributes to reference implementations.

E3

Senior Engineer

Owns a service or workstream, reviews others' designs, makes architectural calls within guardrails and mentors deliberately.

E4

Staff Engineer / Architect

Holds design authority across an engagement, sets standards, and is accountable for technical outcomes in front of the client.

E5

Principal / Practice Lead

Shapes a practice: capability roadmap, hiring bar, reference architecture and the technical reputation of the firm.

03 / Growth

A published ladder, reviewed twice a year.

Progression is written down: expected scope, expected influence and expected behaviours at each level. You can read the level above yours and know exactly what is missing.

There is no requirement to become a manager in order to progress. The senior technical track runs to principal level, with equivalent scope and compensation to the leadership track.

Certification & learning support

Exam fees and preparation time are funded for role-relevant certifications across cloud, data and security tracks, plus an annual budget for books, courses and conferences.

04 / Benefits

Practical support, not novelty perks.

We would rather fund health cover, learning and quiet working conditions than a games console nobody uses.

Hybrid & remote options

Role-dependent flexibility with clearly stated expectations, agreed before you join.

Paid, measured on-call

Compensated rotations with a hard rule: noisy rotations get engineering time to fix them.

Certification funding

Exam fees and preparation time for role-relevant cloud, data and security certifications.

Health cover

Medical insurance for you and your immediate family, plus an annual health check.

Parental leave

Meaningful paid leave for all parents, with a structured return-to-work plan.

Equipment you choose

A machine specified for your work, plus a home-office setup allowance.

Learning budget

Annual allowance for books, courses and one conference, with time to attend.

Internal tech forum

Fortnightly engineering sessions where teams present designs, incidents and findings.

Transparent reviews

Twice-yearly reviews against the published ladder, with compensation discussed openly.

05 / The environment you will work in

Engineering stack

Modern tooling, production systems, real constraints.

You will work on live enterprise platforms with actual availability requirements. That means good tooling and disciplined practice: everything as code, automated pipelines, observability by default, and designs reviewed before they are built.

See the full technology stack

AWSAzureGoogle Cloud KubernetesTerraformArgo CD SnowflakeDatabricksKafka .NETJavaPython ReactTypeScriptPostgreSQL OpenTelemetryGrafanaSIEM / SOAR

06 / Open positions

Roles we are actively hiring for.

If none of these match but your work is relevant, send a general application. We keep strong profiles on file and come back to them when a practice grows.

Senior Cloud Engineer — AWS & Azure Hybrid Full-time 5–9 years Cloud practice

What you will do

  • Design and build multi-account landing zones defined entirely in Terraform
  • Lead migration waves: dependency mapping, cutover planning, validation
  • Own platform reliability targets and the automation that maintains them
  • Review designs from other engineers and mentor within the practice

What we look for

  • Production experience across at least two major cloud providers
  • Strong infrastructure-as-code discipline and CI/CD fluency
  • Networking and identity fundamentals you can explain from first principles
  • Clear written communication — designs, decisions and runbooks

Reference VQ-CLD-001 · Immediate start

Apply for this role
DevOps / Site Reliability Engineer Remote Full-time 3–7 years Platform practice

What you will do

  • Build and operate Kubernetes platforms with GitOps delivery
  • Instrument services with OpenTelemetry and design low-noise alerting
  • Define SLOs with client teams and report against them honestly
  • Drive problem management: eliminate recurring incident causes

What we look for

  • Hands-on Kubernetes, container and pipeline experience in production
  • Comfort debugging distributed systems under time pressure
  • Scripting or programming ability beyond configuration templating
  • A low tolerance for alerts that nobody acts on

Reference VQ-SRE-004 · Immediate start

Apply for this role
Data Engineer — Lakehouse & Streaming Hybrid Full-time 3–7 years Data practice

What you will do

  • Build ingestion and transformation pipelines across batch and streaming
  • Model business domains into tested, documented, reusable datasets
  • Implement data quality gates, lineage capture and access controls
  • Work directly with analysts to turn questions into data products

What we look for

  • Strong SQL plus Python or Scala in production pipelines
  • Experience with a cloud warehouse or lakehouse platform at scale
  • Understanding of dimensional modelling and idempotent design
  • Care about data correctness over pipeline cleverness

Reference VQ-DAT-002 · Immediate start

Apply for this role
Senior Software Engineer — Backend Hybrid Full-time 5–10 years Software practice

What you will do

  • Design and build API-first services for enterprise platforms
  • Decompose legacy monoliths using incremental, reversible patterns
  • Own quality: tests, performance budgets and observability in your services
  • Write the designs and decision records the next engineer will rely on

What we look for

  • Depth in .NET, Java or Node.js and the ecosystem around it
  • Sound data modelling and transactional reasoning
  • Practical security knowledge: authn/authz, secrets, input handling
  • Willingness to work directly with client engineers

Reference VQ-SWE-003 · Immediate start

Apply for this role
Frontend Engineer — React & TypeScript Remote Full-time 2–6 years Software practice

What you will do

  • Build accessible, fast interfaces for enterprise portals and internal tools
  • Hold performance budgets and Core Web Vitals as delivery criteria
  • Contribute to a shared component library used across engagements
  • Work with designers and API engineers as one team, not in sequence

What we look for

  • Strong React and TypeScript fundamentals, plus solid CSS
  • Real understanding of accessibility beyond automated checks
  • Ability to profile and fix rendering and bundle-size problems
  • Interest in design quality, not just implementation

Reference VQ-SWE-006 · Immediate start

Apply for this role
Security Engineer — Detection & Response On-site rotation Full-time 3–8 years Security practice

What you will do

  • Engineer SIEM detections and SOAR playbooks that reduce manual triage
  • Run cloud posture reviews and drive prioritised remediation with clients
  • Lead incident response and produce evidence-based post-incident reports
  • Harden identity, pipelines and workloads alongside delivery teams

What we look for

  • Practical detection engineering, not only tool administration
  • Cloud security depth in at least one major provider
  • Scripting ability for automation and log analysis
  • Calm, structured communication during live incidents

Reference VQ-SEC-005 · Immediate start

Apply for this role

07 / How we hire

Four stages. No unpaid take-home marathons.

The whole process usually completes within two weeks. You will get a decision at every stage, and specific feedback if we say no.

Stage 01

Application review

A practising engineer reads your application — not a keyword filter. Response within three working days.

Stage 02

Technical conversation

45 minutes on work you have actually done: decisions, trade-offs, what broke and what you changed afterwards.

Stage 03

Practical session

90 minutes of collaborative problem solving or system design, scheduled at your convenience. No trick puzzles.

Stage 04

Team & offer

A conversation with the practice lead about ways of working, then a written offer with the level and its rationale explained.

Apply

Send us something you built and are proud of.

A repository, an architecture you designed, an incident you fixed properly. That tells us more than a formatted résumé ever will — though we will read that too.

Email info@vandorqcorp.com Read how we work

Decision at every stage Specific feedback if we decline Equal opportunity employer