Conrad DevOps

Train

Conrad DevOps

Preparation for the platform part of the Conrad interview, written from your Conrad DevOps note — Cloudflare at the edge, the GitLab to GKE pipeline, Docker and Kubernetes, monitoring and A/B testing, your Develit architecture to compare, and the questions to ask them.
Kubernetes conceptsCloudflare WAF

Written from your Conrad DevOps note for the interview on 14 October 2026. The questions are general ones about the technologies in the note, the kind an interviewer asks: how Cloudflare, CI/CD, Docker, Kubernetes, A/B testing and SEO for a server-rendered shop work and why you would use them. They are not about Conrad's own setup; the note is the map of what to know. Caching, monitoring and the Cloudflare platform have their own sections: Conrad caching, Conrad monitoring and Conrad Cloudflare.

Both Conrad notes are in Unfiled. Open one and pick a folder in the folder menu if you want them elsewhere; the questions link to the notes themselves, so they keep working wherever you file them.

Know

PageCoversQuestions
Cloudflare at the edgeWhat Cloudflare does in front of an app, WAF, Access, device detection with SSR, API gateways5
CI/CD pipelineThe pipeline from merge to production, tests in CI, staging versus production, building images, image tags, build once, Terraform and Helm, assets on a CDN, preview environments per merge request, Nx generators10
Docker and KubernetesImages and containers, a Nuxt Dockerfile, volumes and Compose, cluster to Ingress, probes, HPA and why Node fools it, KEDA, rolling updates, Istio, Secrets, StatefulSets, ServiceAccounts, managed Redis14
A/B testingA/B testing without flicker or cache leaks, feature flags1
SEO and crawlersSitemaps for a huge catalogue, robots.txt versus noindex, canonicals, crawl budget, and why bots must see the same page2
Your Develit architectureYour two-minute answer, gateway trade-offs, when to cache, a whole e-shop on Cloudflare4
  • Drill them: Train, press Only next to Conrad DevOps, Smart order. Or open the note and press Practise … from this note.
  • Rehearse: run a mock interview with Conrad DevOps, Conrad caching and Conrad monitoring selected and answer the open questions out loud.
  • This week: one page a day, then a mock, then the flashcards.

Questions to ask them

From your note, in English:

  • What do you use for CI/CD, and is moving off Kaniko on the roadmap?
  • Which tool do you use for tasks and planning?
  • Are there quarterly performance reviews or a similar feedback cycle?
  • What does a typical day look like: stand-ups, syncs, focus time?
  • How big is the team I would join, and who are its main consumers?
  • How does holiday work?

For a front-end platform role, worth adding:

  • How do product teams consume the platform: Nuxt layers, modules, shared packages? How are breaking changes rolled out?
  • Which Nuxt version is the storefront on, and what is the plan for Nuxt 5 and Nitro 3?
  • How is the HTML cache invalidated when prices or stock change, and which layer owns API caching?
  • How do you measure front-end performance in production, and who owns the budgets?
  • How often do you deploy, and how do rollbacks and canaries work?
  • Is there on-call for the storefront?

Be able to say

Be able to say· Summarise Conrad's storefront architecture in one minute.

"Every request goes through Cloudflare first, for bot protection, the WAF and the CDN for static assets. Behind it, a Google load balancer sends traffic to Nuxt pods on GKE. Each pod serves HTML from a shared Valkey cache, with a 60-second lifetime and stale-while-revalidate, and renders on a miss. JavaScript, CSS and images come from the CDN with year-long caching, and APIs sit behind Apigee. Deployments go from GitLab CI, where Kaniko builds the image and the assets go to Cloud Storage, through Terraform and Helm to Kubernetes, which rolls out and autoscales the pods."

Pages in this section

  1. 01Cloudflare at the edgeWhat Cloudflare does in front of Conrad's storefront and why the app runs on GKE rather than Workers, with answers to the open questions in your notes — WAF, Snippets, the CF-Device-Type header, Cloudflare Access, Apigee and the 512-character limit — and edge versus origin caching.
  2. 02CI/CD pipelineHow a change reaches Conrad's production — GitLab CI tests and lint, Kaniko builds the image, assets go to Cloud Storage behind the CDN, Terraform reads secrets and applies the Helm release, and GKE rolls out the pods — plus image tags, deploy ordering and build-once runtime configuration.
  3. 03Docker and KubernetesThe container and cluster basics from your Conrad notes — images and containers, a Nuxt multi-stage Dockerfile, what the image contains, .dockerignore, Compose and volumes, Deployment, Service, HPA and Istio VirtualService, probes, rolling updates and Service types.
  4. 04A/B testingA/B testing with a tool like Kameleoon on a site with server rendering and a page cache — assigning visitors, avoiding flicker, keeping variants out of the shared cache, and feature flags.
  5. 05Your Develit architectureHow to present the platform you worked on at Develit — isolated Cloudflare Workers services behind an orchestrating gateway, service bindings and Workers RPC, KV for exchange rates, Durable Objects for idempotency, Workflows and Queues, micro-frontends on shared Nuxt layers — and how it contrasts with Conrad's stack.
  6. 06SEO and crawlersSitemaps for a catalogue of hundreds of thousands of pages, robots.txt versus noindex, canonicals and crawl budget on a server-rendered shop, and why crawlers must get the same page as users.

Your notes

Open in Notes

Nothing yet. Notes filed here show up on every page of this section.

Nitro's cache

defineCachedEventHandler, cachedFunction and route-rule cache — every option, what swr does on the server and in the header, where entries live, sharing them through Redis or Valkey, and the headers the browser should get for cached HTML.

Cloudflare at the edge

What Cloudflare does in front of Conrad's storefront and why the app runs on GKE rather than Workers, with answers to the open questions in your notes — WAF, Snippets, the CF-Device-Type header, Cloudflare Access, Apigee and the 512-character limit — and edge versus origin caching.