docs

Signed-off-by: Jonathan Pulsifer <jonathan@moonpay.com>

Author: jonpulsifer

README.md

@@ -2,12 +2,10 @@
 
 :wave: Hello and welcome to the DevOps Challenge! https://github.com/moonpay/devops-challenge
 
-We're excited to see you in action! This is your time to **show off your technical skills and aptitude**. We want to understand how you think, how you solve problems, and how you apply DevOps principles to real-world scenarios.
+We're excited to see what you can do! This take-home exercise is your time to **show off your technical skills and aptitude**. We want to understand how you think, how you solve problems, and how you apply DevOps principles to real-world scenarios.
 
 This exercise uses a simple Next.js application, but our focus is on your DevOps expertise—working with Containers, CI/CD, and Infrastructure as Code (IaC).
 
-**Relax and enjoy the process.** We know live coding can be stressful. We're more interested in your decision-making and approach than a perfect, finished product in the first few minutes. Please think aloud and walk us through your thought process.
-
 > **Note:** For development setup, scripts, and project structure details, see [DEVELOPMENT.md](DEVELOPMENT.md).
 
 ## :dart: Goal
@@ -19,7 +17,7 @@ Deploy the provided Next.js application in a **production-ready** manner.
 You should be comfortable with:
 1.  **Docker**: Building and running containers.
 2.  **CI/CD & IaC**: Tools like GitHub Actions, Terraform, etc.
-3.  **Orchestration**: Kubernetes, ECS, Cloud Run, or similar.
+3.  **Orchestration**: Kubernetes (GKE or local).
 4.  **Git**: Version control.
 
 ## :wrench: Tasks
@@ -32,7 +30,7 @@ You should be comfortable with:
 
 ### Task 2: Deploy the Application :rocket:
 
-1.  Deploy the application. We **strongly prefer deploying to Kubernetes** (local or cloud), but we are open to other cloud-based solutions (Cloudflare, AWS ECS, GCP Cloud Run, Fly.io, etc.) if that's what you're most comfortable with.
+1.  Deploy the application to **Kubernetes** (GKE or a local cluster such as kind, minikube, or Docker Desktop).
 2.  Ensure the solution is **as close to production-ready as possible**. Consider aspects like:
     *   Security
     *   Scalability
@@ -41,9 +39,7 @@ You should be comfortable with:
 
 ## :hourglass_flowing_sand: Time & Expectations
 
-You have **60 minutes** for this live session.
-
-**However, if you feel you cannot complete a solution you are proud of in this time, you are welcome to treat this as a take-home assignment.** You can finish it on your own time and submit it later. We want to see your best work!
+This is a take-home exercise — complete it on your own time and submit when you're ready. We want to see your best work! Be prepared to walk us through your solution and decision-making during the interview.
 
 ## :robot: AI Usage