This is the repository for the System Initiative Infrastructure Engineer III - Ecosystem take-home assessment. It is designed to verify that:
- You have proficiency in designing cloud architecture and implementing infrastructure automation
- You have proficiency with multiple cloud providers
We use a take-home assessment so that you can have your most productive environment at hand. Use whatever editor, operating system, etc. you like. Google to your heart's content.
Please spend no more than 4 hours on this assessment.
We created a fake company called Taskly, and you’ve been hired as an Infrastructure Engineer! Taskly is a new company reinventing the task list, and the engineering team has been busy working toward a beta launch. They’re ready to get this product into the world and start getting feedback! We need to decide which cloud provider and subsequent infrastructure architecture we will use for production. We want you to implement a few different options so we can choose what production will look like for Taskly!
Taskly is split into two components - a frontend and a backend. Each component has its own README with information about the components, including full instructions on how to run it (including link checks and automated tests).
To get started, fork this repository. If you prefer, you can make your fork private and add britmyerss,
fnichol, stack72, and mahirl as collaborators. When you've finished, let us know via email with a link to your fork. We'll review it and get back to you!
Have fun!
Your submission should include 3 implementations for a cloud architecture to run Taskly, including at least 2 cloud providers. For example, you could show 2 implementations of what Taskly might look like in AWS, and 1 in GCP, or one implementation in each of AWS, GCP, and Azure, etc. Also, while there is no pipeline built yet for Taskly in the repo, for this assessment, you can assume that there is a CD pipeline that will run your automation.
We want you to use whatever infrastructure automation tooling and cloud providers you’re most comfortable with. Please don't worry about actually standing up infrastructure and deploying Taskly, as we don't want you paying out of pocket for this assessment, and we don't want you to restrict your design to using the free\inexpensive tiers.
We also want you to include a README, that helps us understand your decisions, why you made them, which implementation is your preferred one and why, and any additional context that you think would help give insight into your decision-making process.
Thank you so much for taking the time to do the assessment. We're looking forward to reviewing your work!