gaspersic/devops-exercises
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

600 questions milestone

Browse Source 
yay
This commit is contained in:
abregman
2019-12-08 17:14:30 +02:00
parent b9a0f3c42b
commit d0a768915a
3 changed files with 86 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
prepare_for_interview.md
View File

@ -4,8 +4,8 @@ Note: the following suggestions are opinionated
### Coding
Some (if not most) DevOps interviews include coding tasks/questions. Be prepared for those by doing actual coding before the interview.
Also, when given the chance to choose any language, choose the one you have experience with and not the one the company is using or you think it's using.
Some (if not most) DevOps interviews include coding tasks/questions. Be prepared for those by doing actual coding.
Also, the following probably clear to most people but still, when given the chance to choose any language for answering questions or coding tasks, choose the one you have experience with and not the one the company is using or you think it's using.
### Prepare by answering interview questions
@ -27,3 +27,13 @@ Be familiar with the company you are interviewing at. Some ideas:
### Books
From my experience this is not done by many candidates but it's one of the best ways to deep dive into topics like operating system, virtualization, scale, distributed systems, ...
### Scenarios
This is a very common way to interview today for DevOps roles. The candidate is given a task which represents a common task of DevOps Engineers or common knowledge and the candidate has several hours or days to accomplish the task.<br>
This is a great way to prepare to interviews and I recommend to try it out before actually interviewing. How? take requirements from job posts and convert them to scenarios. Let's see an example:
"Knowledge in CI/CD" -> Scenario: create a CI/CD pipeline for a project.
At this point some people ask: "but what project? I'm not working right now" and the answer is: what about GitHub? it has only 9125912851285192 projects...and a free way to set up CI to any of them.