Manish
A DevOps/SRE instructor at GeeksforGeeks. He previously worked at Cognizant and Amazon, and later joined Zoom as a Site Reliability Engineer. He shares his experience of career transitions.
Timeline (last 90 days)
Manish worked at Amazon for two years in an SRE-related position, then left to join Zoom as a Site Reliability Engineer.
Manish's career started at Cognizant as an Advanced Java Developer, assigned to the supply chain management domain, and later, by self-studying data engineering technologies such as Python, Scala, Kafka, Airflow, and SQL/NoSQL and preparing for AWS certification, he obtained an internal transfer opportunity into the DevOps direction.
After working at Cognizant for about a year and a half, Manish began sending out resumes, but due to the 90-day notice period, most HR personnel were deterred and interview opportunities were very few.
One CGI interview of Manish's ended after only five minutes, because he knew almost nothing when the interviewer asked about Kubernetes architecture.
Manish's core insight is: interviewers do not require that you have used a certain technology in real work; what they assess is whether you truly understand the principles and whether you have hands-on ability.
Manish received an offer from Amazon in 2024.
During Manish's job search after leaving Amazon, he was rejected by companies such as media.net, Warner Bros, PhonePe, eBay, and Goldman Sachs.
Manish ultimately received several offers including Zoom's, and chose to join Zoom as a Site Reliability Engineer, stating that his current work content and technical direction align highly with his career plan for the next five years.
Manish believes AI cannot be avoided and should be treated as a tool for improving delivery speed and quality rather than as a competitor, and that DevOps and SRE are still currently directions with high demand and high pay.
Manish advises people transitioning into DevOps/SRE to tie together knowledge points such as Linux, Shell, AWS, Terraform, Docker, Kubernetes, CI/CD, Prometheus, Grafana, and Python through one complete end-to-end project, and the project can take three to six months to complete.
All Facts (9)
Manish advises people transitioning into DevOps/SRE to tie together knowledge points such as Linux, Shell, AWS, Terraform, Docker, Kubernetes, CI/CD, Prometheus, Grafana, and Python through one complete end-to-end project, and the project can take three to six months to complete.
50%UnverifiedManish's career started at Cognizant as an Advanced Java Developer, assigned to the supply chain management domain, and later, by self-studying data engineering technologies such as Python, Scala, Kafka, Airflow, and SQL/NoSQL and preparing for AWS certification, he obtained an internal transfer opportunity into the DevOps direction.
50%UnverifiedAfter working at Cognizant for about a year and a half, Manish began sending out resumes, but due to the 90-day notice period, most HR personnel were deterred and interview opportunities were very few.
50%UnverifiedManish worked at Amazon for two years in an SRE-related position, then left to join Zoom as a Site Reliability Engineer.
50%UnverifiedManish's core insight is: interviewers do not require that you have used a certain technology in real work; what they assess is whether you truly understand the principles and whether you have hands-on ability.
50%UnverifiedDuring Manish's job search after leaving Amazon, he was rejected by companies such as media.net, Warner Bros, PhonePe, eBay, and Goldman Sachs.
50%UnverifiedManish ultimately received several offers including Zoom's, and chose to join Zoom as a Site Reliability Engineer, stating that his current work content and technical direction align highly with his career plan for the next five years.
50%UnverifiedManish believes AI cannot be avoided and should be treated as a tool for improving delivery speed and quality rather than as a competitor, and that DevOps and SRE are still currently directions with high demand and high pay.
50%UnverifiedOne CGI interview of Manish's ended after only five minutes, because he knew almost nothing when the interviewer asked about Kubernetes architecture.
50%