Hi! Thank you for your interest in EstateSpace. Our evaluation process begins with an open-ended coding challenge that we will discuss during your interview. There is not one correct way to approach this challenge. Rather, we would like to see your approach and your creativity in solving the problem.
We appreciate that any coding challenge represents an investment of your time. We hope you see the value in having a code sample that is relatable to both of us for the interview. Should you be unsuccessful, you should feel free to use the code you developed for this challenge in any way that you would like.
If you are successful, then we will set up an in-person interview and use this code as the starting point in our conversation.
EstateSpace uses a containerized approach to its microservices. The challenge would be to write an NGINX reverse proxy to proxy the EstateSpace website and a site of your choosing and then wrap that proxy in a docker container, then use CircleCI to deploy to a cloud hosted kubernetes cluster.
Ideally, this would take a mid-level DevSecOps engineer, with experience with these technologies two-four hours to complete the minimum requirements.
We would like your submission to offer a minimum capability. The criteria are:
- A docker container containing an NGINX reverse proxy.
- A proxy of the EstateSpace website.
- A proxy of a website of your choosing.
- A CircleCI configuration for deployment
- A cloud hosted kubernetes cluster
In a DevOps environment, there are many areas that may be considered. Working software is always top priority, however, to meet the minimum requirements. Should you want to go above and beyond the minimum requirements, please feel free to add to your submittal either via code or via documentation in common mark compliant documentation.
- Creating a build, Test, Publish (to docker hub) pipeline using a CD tool such as (preferrably) CircleCI or Jenkins.
- deploying the continuous deployment tool to AWS (free tier) using kubernetes
- Container security
- Container size
- A basic understanding of source code control, git is required.
- You must make your code available via a GitHub account.
- All JavaScript shall be written using ES6 standards.
- A basic understanding of NGINX.
- A basic understanding of Docker.
- A basic understanding of Kubernetes.
- Fork this repository.
- Clone the fork to your personal machine.
- Start coding.
- Commit changes to your fork as you see fit.
When you are comfortable with your results, please email your fork to dev@estatespace.com. Please keep your emails short and to the point.
Any specific notes or further information you would like to add about your submittal, should be included in the GitHub project as additional Common Mark notes.
Do not feel as though you must create a public fork of this repository. You are free to create a throwaway GitHub account or private fork. In those cases, please let us know so that we may send you the GitHub IDs to add to the repository.
We realize there are many items to look at within the DevOps space. Please do not feel like you have to do everything. Use your strengths to your advantage. If you have more orchestration experience, feel free to showcase that. If you have more security experience, then wrap security in your containers. Give us a heads up by documenting your code to let us know where and why you concentrated on certain items.
As you develop your solution, you may have ideas on other avenues to pursue. Please feel free to include them inline as documented source or as additional Common Mark compliant notes in your fork.
We look for readability, good architectural decisions, modularity, and a solid approach to testing in your code.
This project is MIT licensed.