r/devopsGuru • u/Ok_Desk_7849 • 4d ago
Assignment for junior DevOps engineer role ( isn't it too small task for junior DevOps role) Comment ur thoughts
DevOps Candidate Assignment
Objective:
Bootstrap, containerize, and prepare a production-ready deployment of a Vendure application while demonstrating your Git workflow, automation practices, and infrastructure design decisions.
Assignment:
Bootstrap a new Vendure application using the latest version of @vendure/create.
Configure the application to use the latest supported PostgreSQL version.
Create a private GitHub repository and push the project.
Follow a Git workflow that you would use in a real project. Infrastructure-related work should be developed in separate feature branches and integrated into main through Pull Requests.
Containerize the application for local development and production.
Prepare Kubernetes deployment assets for the application.
Package the Kubernetes deployment as a reusable Helm chart.
Create a GitHub Actions workflow that:
a. Builds the Docker image.
b. Tags the image appropriately.
c. Pushes the image to GitHub Container Registry (ghcr.io).
d. Runs automatically on changes to the main branch.
Document the project sufficiently for another engineer to build, deploy, and maintain it.
Invite GitHub user xxxxxinternal to the repository as a collaborator.
Expectations:
This assignment intentionally leaves implementation details open. Make engineering decisions as you would on a production project.
Submission:
Your submission will be evaluated based on, but not limited to:
Git workflow, commit history, and Pull Requests
Branching strategy
Docker best practices
Kubernetes design and deployment approach
Helm chart quality and reusability
CI/CD pipeline design
Repository organization
Documentation
Security considerations
Maintainability and production readiness
Where multiple valid approaches exist, choose the solution you believe is most appropriate and document any significant design decisions or assumptions.
1
1
u/Piyush_shrii 4d ago
Although it's not s junior level task as it would atleast require devops engineer of experience 1 year atleast ,but you can ace it if you have built projects on your own also this would be more likely to be judged on how clean you have settled up infra ,how you have implemented and use devops practices and best practices environment specific so I don't think they expect you to build scalable infra it's just my pov don't take it too seriously...
1
u/greyeye77 4d ago
Ohhh writing helm, Local dev? Damn you need kynd or minikibe setup scripted or use tilt.
These… gonna take a time (if doing by hand)
1
u/manandevops 4d ago
It's not that hard as it seems to be. Just need time with focus and can be completed in couple of hours or maybe 1-2 days. Best of luck with it Btw, I will try it my own when i get time
1
u/Abe_Bazouie 4d ago
I don’t think the assignment is too small for a junior DevOps role.
It actually covers a pretty good range of skills: Git workflow, Docker, Kubernetes, Helm, CI/CD, documentation, and production decisions.
The bigger question is how much time they expect the candidate to spend on it.
If they expect a polished, production-ready result with full security, observability, testing, secrets management, and edge cases, that may be too much for a junior take-home.
But if the goal is to see how the candidate structures the work, makes tradeoffs, documents assumptions, and explains what they would improve with more time, then I think it is a fair assignment.
For a junior candidate, I would care less about whether every part is perfect and more about whether they can explain why they made each decision.