Skip to contentSkip to content
Verified credentials. On-chain. Forever.Learn more
Ewance
Sign in
Cover image for Design a Multi-Tenant Kubernetes Namespace-Provisioning Self-Service
Code

Design a Multi-Tenant Kubernetes Namespace-Provisioning Self-Service

FreeVerified credential4 weeksAdvanced

Overview

What this challenge is about.

Design a Multi-Tenant Kubernetes Namespace-Provisioning Self-Service. Advanced challenge in code. Writing production code that solves real engineering proble...

CredentialBlockchain-anchored
ShareableLinkedIn-ready
LanguageEnglish
PaceSelf-paced

The Brief

What you'll do, and what you'll demonstrate.

Replace ticket-based namespace provisioning with a self-service flow that respects HIPAA-class guardrails and cuts lead time from 4 days to under 1 hour.

This is not a coding exercise. It is the work a software engineer does between a Jira ticket and a merged PR. That distinction matters to every hiring manager who has seen candidates solve LeetCode problems and none who have shipped production code under real constraints.

When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."

Earning criteria — what you'll demonstrate

  • Build a self-service flow that respects policy guardrails by construction
  • Apply GitOps + policy-as-code to provisioning workflows
  • Measure lead-time and compliance honestly during a pilot
  • Sequence rollout to a 22-squad org without overwhelming on-call

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Platform Engineering

Master · Cloud And Devops

Strong alignment

This challenge maps to Platform Engineering at the Master level. It sharpens the same practical skills your coursework expects — but in a real industry context with actual constraints and deliverables.

One more thing

You can put a credential on your CV by Friday.