Skip to main content
Careers · Cloud & platform engineering

CAREERS

We hire engineers who love technology, solve hard problems, and go the extra mile. RFCs over slide decks, production systems over proof-of-concepts. Boutique team in Rijswijk, working with Dutch enterprises on AWS, Azure, Kubernetes, and the tooling around them.

View open roles Coffee first?
20+
Architects & platform engineers
Craft
Ambition, grit, and a love of automation
Hybrid
Home, hub, or client. Output counts
2019
Founded in the Netherlands
Why engineers join

Built for people who ship platforms, not decks

We love technology, innovate deliberately, and use AI where it belongs in delivery and platforms. We stay close to the customer business so their infrastructure stays ahead. If tough platform problems and room to grow sound like your week, you will fit here.

Real ownership

You stay on the architecture and delivery path: landing zones, cluster upgrades, pipeline hardening. Not ticket-chasing on someone else’s design.

Peers, not layers

Small teams, short lines. Reviews focus on systems and trade-offs. Pushback on scope or risk is expected when it is specific.

Modern stack

Terraform, Kubernetes, GitOps, observability, policy-as-code, and AI-assisted delivery where it speeds review and automation without weakening guardrails.

Calm pace

We reserve time for learning, internal sessions, and sensible on-call boundaries. Sustainable delivery beats heroics that do not survive handover.

Vacancies

Open roles

If you prefer Terraform in production over Terraform in slide decks, you are in the right place. Pick a role below to read the full brief, or send a short note if nothing matches yet.

Current openings

Select a role to open the full description and apply.

Recruitment process Recruiter FAQ
What we build

Platforms your client engineers can inherit

Cloud platforms and the integrations around them: landing zones, identity, guardrails, CI/CD, and glue between systems. Expressed as code; Terraform where it fits; AI where it makes delivery faster and safer.

Identity & access

Entra ID to AWS permissions

We needed group membership in Entra ID to drive temporary AWS permissions faster than the default directory sync cycle allowed. We designed a small, auditable automation path on a tighter cadence so developers could get short-lived access without weakening access-review trails.

Landing zone

Multi-account AWS foundation

Terraform modules, account vending, guardrails, and CI/CD plans that finance and security reviewers can follow. Built so the client platform team owns the baseline after handover.

Read the case study

Kubernetes

EKS cost-aware autoscaling

Karpenter migrations, node consolidation, and observability wired to the release path. The kind of work where small infrastructure choices show up clearly on the invoice and in the pager.

Kubernetes consultancy

Tools we use in anger

Platforms and tooling our engineers operate weekly, not a logo wall.

Cloud
  • AWS
  • Azure
  • Hybrid footprints
Platform
  • Kubernetes / EKS / AKS
  • Docker
  • Traefik / NGINX
IaC & GitOps
  • Terraform / OpenTofu
  • Ansible
  • Argo CD / Flux
Security
  • HashiCorp Vault
  • OPA / Checkov
  • Entra ID patterns
Observability
  • Datadog
  • Elastic Stack
  • SLO-driven alerting
AI infra
  • Secure inference paths
  • RAG platform plumbing
How we work

Specs before improvisation

We work alongside client teams on cloud platforms that carry revenue: landing zones, Kubernetes platforms, and CI/CD paths. We aim for deliverables they can extend once we step back.

RFCs, ADRs, and runnable docs beat hallway lore. When IAM boundaries, network paths, or blast radius are still fuzzy, we tighten them before merge, not during an incident call.

We document decisions in the same repositories as the code. Two years in, the platform should still make sense to the people running it. Read more about our engineering culture.

Engineering circle

How we grow as engineers

Experiment safely, improve with evidence, learn when telemetry contradicts assumptions, share artifacts someone else can rerun.

We experiment

We probe safely: limited blast radius, sandboxes, game days, and reviews that focus on systems, not individuals. Curiosity is welcome where it cannot take down customer workloads.

We learn

Training portals, meetups, and technical challenge: everyone keeps current on AWS, Azure, and Kubernetes at their own pace.

We improve

Short RFCs, paired delivery, and measurable reliability: we turn fuzzy asks into concrete controls and pipelines.

Engineering culture

How the bar stays high

WTF sessions, learning budget, and community involvement: practices we run on purpose so depth compounds instead of decays.

  • WTF sessions

    Monthly What The Faqtory! (WTF) sessions: engineers walking through real customer work, technical deep-dives, demos, home experiments, and what did not work.

  • Time and tools to learn

    Pluralsight and A Cloud Guru access, a real budget for certifications, and study agreements where the topic justifies it.

  • In the community

    We attend and speak at meetups, follow the AWS, Azure, and Kubernetes communities, and back engineering events that keep the field honest.

Recent internal session topics include landing-zone patterns, Karpenter migrations, GitOps trade-offs, cost-aware EKS, and AI in platform delivery.

Team stories

Engineers in their own words

Not stock recruitment portraits. Colleagues on what they build, how they got here, and what they do when the laptop closes.

All personal stories
Lars Nonnekes
Lars Nonnekes

From software to platform engineering

Pipelines, reliability, and the same stamina he brings to long mountain trails.

Read the story
Jordy de Rooij and Richard Blaauw
Jordy & Richard

Mission-critical platforms, 24/7

Ownership that shows up in incidents and architecture reviews alike.

Read the story
Max van der Meij
Max van der Meij

Deep automation, patient iteration

Client platforms by day; growing food in the garden on weekends.

Read the story
Work style

Autonomy with clear interfaces

Hybrid by default: home, our hub in Rijswijk, or with clients when the programme needs it. Output over desk time.

Staff augmentation, project work, and managed services sit side by side. All paths stay technical.

Hiring process

Short, transparent, engineer-led

Usually two conversations, sometimes three, then a written offer if there is a match. Bring questions; the decision matters to both sides.

  1. 1. Get-to-know conversation

    Who you are, what you are looking for, and an honest picture of how we work.

  2. 2. Technical conversation

    Walk us through a design you have shipped or demo something you are proud of. We ask about trade-offs; you should ask the same of us.

  3. 3. Meet in person (optional)

    Coffee at our office or a location that works for you.

  4. Offer & onboarding

    Written offer, screening where client requirements demand it, then paired onboarding.

Full recruitment procedure

Questions candidates ask

I'm early in my career or switching into cloud, DevOps, or AI. Is that OK?

We are not a graduate programme, but we do hire ambitious engineers who learn fast and take ownership. Our focus lies on public cloud, yet we also hire people without years of public-cloud delivery behind them. We endorse hybrid cloud in practice; with sovereignty requirements on the agenda for many Dutch organisations, that blend is more relevant than it has been in years. Our work spans DevOps, cloud-native development, AI infrastructure, and platform engineering. Client work asks for credible judgement, curiosity, and follow-through. If you love automation, seek out hard problems, and go the extra mile, we would like to hear from you. Mentorship, pairing, and real project responsibility are how many of us grew here.

Remote, hybrid, or on-site?

Hybrid is the norm: home, our hub in Rijswijk, or on site with a client when the engagement needs it. We agree travel and location expectations up front, and we judge the work on output, not desk time.

Staff augmentation, projects, or managed services?

Our delivery spans staff augmentation, project work, and managed service assignments. Some roles focus on architecture-led programmes; others include operational responsibility for platforms we run with clients. We discuss which path fits during the first conversation.

Can I apply without going through a recruiter?

Yes. Direct applications are welcome via the listings above or a short note to recruitment@thefactory.nl. See our Recruiter FAQ if you are an agency.

What should I prepare for the technical conversation?

Pick something you have actually built or operated. Be ready to explain constraints, trade-offs, what you would do differently, and how the system behaved under failure. Whiteboard sketches and demos both work.

How long does the process take?

Typically two to four weeks from first call to offer, depending on calendars and whether an on-site meeting makes sense. We do not run endless panel rounds.

AWS Select Tier Consulting Partner
Microsoft Solutions Partner
ISO 27001 Information security
75+ Customers since 2019

Certifications · Case studies

Next step

Ready to join, or just curious?

Pick a role above, book a 30-minute coffee chat with an engineer, or send a short note about what you want to work on next. No CV required for the first conversation.

View open roles Coffee first
goToTop