I currently work as a NOC operator, and am looking to make the transition to DevOps engineer.
"I'm one out of five DevOps engineers that work day and night for production operations at Playstation in San Francisco." - What's your typical schedule look like? How's the on-call rotation?
What was the interview process like? Did/do you need to have a portfolio?
That's awesome! We have a great relationship with NOC operators at Playstation. They are our eyes and ears 24/7 when our monitoring misses something :)
4 years ago, I went through their interview process and it was tough. I didn't need a portfolio. Keep in mind I interviewed before a lot of the things I had to learn about wasn't available for AWS at the time (AWS Secrets as an example).
Be sure to know Linux inside and out. Know how to troubleshoot random issues by utilizing lsof.
For example, how do you find the pid NAME of a file that's opened.
Knowing your linux is half the battle. Then you need to know about the SDLC, be prepared to be able to go into detail when you explain CI/CD, and they'll probably be knit picky and ask you what the difference is between Continuous delivery vs continuous deployments.
The link you sent me is pretty accurate. Understanding inside and out linux and the anatomy of a web server takes up most of the middle of the page, so you really should know that if you want to succeed.
Scripting languages: Know your Bash, Python, Ruby (If they're a Chef shop), and Node.js if you're supporting a web application.
Rust and Go are still in the experiment phases over at playstation, but we have built some custom K8s tooling with Go. Those two languages can wait for now. Stick with learning Python first.
Also, learn how to deploy an application using Jenkins. You're not limited to Jenkins, but that's almost the cultural norm around here. Circle CI is also cool, but it's tough adopting to it since a lot of "set in stone" tech stacks are heavily embedded with Jenkins.
Lastly, know your Log aggregation tool. Whether it's SPLUNK or Kibana. They love someone who can just get up and start searching complex searches in their stack.
How to build and use Data visualization tools like Grafana or DataDog will also very much help you.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Fernando! :)
I currently work as a NOC operator, and am looking to make the transition to DevOps engineer.
"I'm one out of five DevOps engineers that work day and night for production operations at Playstation in San Francisco." - What's your typical schedule look like? How's the on-call rotation?
What was the interview process like? Did/do you need to have a portfolio?
How accurate would you say this list of for becoming a DevOps engineer?
javarevisited.blogspot.com/2018/09...
Hi Xavier,
That's awesome! We have a great relationship with NOC operators at Playstation. They are our eyes and ears 24/7 when our monitoring misses something :)
4 years ago, I went through their interview process and it was tough. I didn't need a portfolio. Keep in mind I interviewed before a lot of the things I had to learn about wasn't available for AWS at the time (AWS Secrets as an example).
Be sure to know Linux inside and out. Know how to troubleshoot random issues by utilizing
lsof.For example, how do you find the
pidNAME of a file that's opened.Knowing your linux is half the battle. Then you need to know about the SDLC, be prepared to be able to go into detail when you explain CI/CD, and they'll probably be knit picky and ask you what the difference is between Continuous delivery vs continuous deployments.
The link you sent me is pretty accurate. Understanding inside and out linux and the anatomy of a web server takes up most of the middle of the page, so you really should know that if you want to succeed.
Scripting languages: Know your Bash, Python, Ruby (If they're a Chef shop), and Node.js if you're supporting a web application.
Rust and Go are still in the experiment phases over at playstation, but we have built some custom K8s tooling with Go. Those two languages can wait for now. Stick with learning Python first.
Also, learn how to deploy an application using Jenkins. You're not limited to Jenkins, but that's almost the cultural norm around here. Circle CI is also cool, but it's tough adopting to it since a lot of "set in stone" tech stacks are heavily embedded with Jenkins.
Lastly, know your Log aggregation tool. Whether it's SPLUNK or Kibana. They love someone who can just get up and start searching complex searches in their stack.
How to build and use Data visualization tools like Grafana or DataDog will also very much help you.