Operating system tutorial series - th-cam.com/video/0UvZ2BPIPX0/w-d-xo.html Computer networking tutorial series - th-cam.com/video/krC08BwZctc/w-d-xo.html Python tutorial series - th-cam.com/video/mHtjvDEdlas/w-d-xo.html
The GitHub material suggested by you is amazing and encapsulates a lot of topics that is very usesful for any candidate attempting an interview for SRE role or learn more about this role for a beginner. Thank you so much!
Regarding the CI/CD - Just want to correct you. SREs don't care about the faster code deployment. That's devOps scope. Not ours. We care about the risk and reliability of the code push. Even the CI/CD tools should be managed by the DevOps Tools team. Not SREs. Also DevOps and SREs are different in the different companys. A good DevOps may not be a good SRE. As he does not work with the SLO/SLIs/SLAs/NFRs etc. They dont understand the Product/Project integration/End to End data flow outside the fast code push/configuration push etc.
SRE is an implementation of DevOps and SRE's do care about faster code deployment. Even as a DevOps engineer, one has to care about reliability. What's the use of a CI/CD pipeline if its not reliable ? Different organizations have different way of working - some have just DevOps team, some have infra team, some have SRE team, some may have a combination of these.
@@ahsanraza2930 i dont remember now, but in my SRE interview experience linux and networking questions are quite important. Plus questions like how do you troubleshoot when a website is down. Similar questions like this.
Hello Codophobia, I have a question, do network engineering, traffic management(BGP,MPLS) are also part of the same SRE role? If not then why? @codophobia
There can be a SRE team handling traffic management. The skills required for them too are same as I have mentioned. There can be another networking team that manages the networking hardware.
But why would we need another SRE team who manages hardware networking and complex hybrid cloud networking? Is it ideal for a organization to have different SREs for different technologies? Do you think datacenter networking, cloud networking, hybrid networking should also be part of the same SRE team. I mean the guy who works with software engineering department should also manage effectively how traffic flows through different point of presence and networks/datacenters? Why core networking team is always a different team in most of the organization, not part of SRE( as far as I have seen)?
@@anandns05 No, there is no requirement of SRE team for hardware networking. Traffic management also requires software like load balancer and many others. These team will have a SRE.
@@practicalcsjourney Networking is also part of Site, Networking should be reliable as well. Any changes roled out in networking could affect organizational SLA, if current SRE(which you have described in the session) doesnt have visibilty or control over network architecture, quality of service(video streaming application such as youtube, zoom, Microsoft Teams requires proper QoS implementation, reliability at core network level to provide high quality service apart from the system and software reliability which SRE manages) I think for an organization to be a complete SRE, core networking, network architecture, network planning, network automation, network monitoring etc. should come under SRE umbrella), right now I feel only system, and software is part of SRE, large complex networking is still managed by different team. Network is a major piece which provides seemless user experience across the globe. I still feel, SRE has to evolve to bring core networking under its umbrella. Thoughts?
@@anandns05 I do not have much context on hardware side of things. For every service which involves pushing new changes to code, we do have have a SRE team. I agree with you each critical service requires a SRE type of mindset. We should have a SLA defined for each critical service.
Hi Shivam, it was a good session, but just wanted to ask, to talk on a broader perspective, its very hard a single person will manage all these stuffs, big companies make specialized teams for everything and as we dive down, the individual contribution may not be around all of the things mentioned.. whats your take on this ?
@@practicalcsjourney Like from engineering work to writing scripts to managing alerts to being on call to Debugging crashing things, like SRE also has a wide variety of things under its umbrella.. So either a person has to do it in rotation of all the stuffs, which at least I think is very difficult to get in Big companies as they usually define your area of work as I think... and when working on something very large.. which is a product used by many I think getting to know about stuffs and how they are connected becomes very time consuming maybe... for example I would state... I have been working in the cdn domain for past 1 year.. so knowing each and every stuff about the configurations on router, how they are deployed from router level to multiple services architecture and maybe building something on top of it.... I found it a bit difficult... Like solving a simple high partition usage problem on a live production server might become troublesome... with so many components involved with so many service owners around it
@@umanga312 Yes, I agree with you on that. We as SRE do not have to know everything. We should good with the basics of linux, networking, programming and system design. Depending on the team you are in (database, traffic, hadoop etc), you should learn about the the things you need to. But as a SRE, we have to be oncall once a week, do engineering work 50% of the time, debug issues during oncall when they arrive through alerts.
No. Both are very different roles. Software testing is concerned with testing. A SRE is concerned about the issues that may arise after the code is pushed to production and is live.
Hey Shivam, Could you suggest how to prepare for the "Code Review Round"? Your Video is very helpful for other Rounds. I have an upcoming interview in 1 week.
@Shivm does some experience matter for SRE role because I have 1 year experience in CICD but I don't know how much experience they want for SRE role in networking,system design, Linux. This book is enough to get knowledge & hand on experience in all SRE areas.
Some experience is good in getting interviews. 1 year experience in CI/CD should be good. You should focus on the core areas and apply. Which book you are talking about ?
Operating system tutorial series - th-cam.com/video/0UvZ2BPIPX0/w-d-xo.html
Computer networking tutorial series - th-cam.com/video/krC08BwZctc/w-d-xo.html
Python tutorial series - th-cam.com/video/mHtjvDEdlas/w-d-xo.html
Got selected as a SRE intern and TH-cam suggest this video, amazing explanation shivam bhaiya.... Great work you are doing ✌️✌️
Hi Mehul, I have an interview scheduled soon. Do you mind sharing your email where I can contact you and ask some questions.
Congratulations Mehul and all the best for your future :)
@@aayushupadhyay5890 Glad to help you buddy ... This is my email mehulanshumali.ma@gmail.com
@@practicalcsjourney thanks 😁
@@mehulanshumali which company?
tnk u so much bhai..........i think this kind of videos should get more visibility than tik-tok kind of videos
very amazong bhai
The GitHub material suggested by you is amazing and encapsulates a lot of topics that is very usesful for any candidate attempting an interview for SRE role or learn more about this role for a beginner. Thank you so much!
Hey where is the GitHub link ...can you please share
Great job bro. It was insightful
Can you please make some videos on Troubleshooting and approach for various scenarios
+1
Hello I am fresher I got my first job as SRE. So how will be my future growth compared to software developers?
You will learn a lot and. grow very fast.
Excellent, Very clear explanations with simple examples. And the Q&A session was more effective too.
Thank for this excellent video. SRE is crystal clear now.
Regarding the CI/CD - Just want to correct you. SREs don't care about the faster code deployment. That's devOps scope. Not ours. We care about the risk and reliability of the code push. Even the CI/CD tools should be managed by the DevOps Tools team. Not SREs. Also DevOps and SREs are different in the different companys. A good DevOps may not be a good SRE. As he does not work with the SLO/SLIs/SLAs/NFRs etc. They dont understand the Product/Project integration/End to End data flow outside the fast code push/configuration push etc.
SRE is an implementation of DevOps and SRE's do care about faster code deployment. Even as a DevOps engineer, one has to care about reliability. What's the use of a CI/CD pipeline if its not reliable ? Different organizations have different way of working - some have just DevOps team, some have infra team, some have SRE team, some may have a combination of these.
I have cleared 2 technical rounds of SRE interview,
Now what could be asked in the techno/managerial round?
Hi Shivam,
what questions they asked in second round of sre?
@@ahsanraza2930 i dont remember now, but in my SRE interview experience linux and networking questions are quite important. Plus questions like how do you troubleshoot when a website is down. Similar questions like this.
@@shivammalhotra3219 Thank you bro
Very Informative. Thank you Shivam
Hello Codophobia, I have a question, do network engineering, traffic management(BGP,MPLS) are also part of the same SRE role? If not then why? @codophobia
There can be a SRE team handling traffic management. The skills required for them too are same as I have mentioned. There can be another networking team that manages the networking hardware.
But why would we need another SRE team who manages hardware networking and complex hybrid cloud networking? Is it ideal for a organization to have different SREs for different technologies? Do you think datacenter networking, cloud networking, hybrid networking should also be part of the same SRE team. I mean the guy who works with software engineering department should also manage effectively how traffic flows through different point of presence and networks/datacenters? Why core networking team is always a different team in most of the organization, not part of SRE( as far as I have seen)?
@@anandns05 No, there is no requirement of SRE team for hardware networking. Traffic management also requires software like load balancer and many others. These team will have a SRE.
@@practicalcsjourney Networking is also part of Site, Networking should be reliable as well. Any changes roled out in networking could affect organizational SLA, if current SRE(which you have described in the session) doesnt have visibilty or control over network architecture, quality of service(video streaming application such as youtube, zoom, Microsoft Teams requires proper QoS implementation, reliability at core network level to provide high quality service apart from the system and software reliability which SRE manages) I think for an organization to be a complete SRE, core networking, network architecture, network planning, network automation, network monitoring etc. should come under SRE umbrella), right now I feel only system, and software is part of SRE, large complex networking is still managed by different team. Network is a major piece which provides seemless user experience across the globe. I still feel, SRE has to evolve to bring core networking under its umbrella. Thoughts?
@@anandns05 I do not have much context on hardware side of things. For every service which involves pushing new changes to code, we do have have a SRE team. I agree with you each critical service requires a SRE type of mindset. We should have a SLA defined for each critical service.
DO you issue a training certificate for your webinars?
Great Content Shivam (y)
Hi Shivam, it was a good session, but just wanted to ask, to talk on a broader perspective, its very hard a single person will manage all these stuffs, big companies make specialized teams for everything and as we dive down, the individual contribution may not be around all of the things mentioned..
whats your take on this ?
What are "all of the things mentioned" ? Can you explain this?
@@practicalcsjourney Like from engineering work to writing scripts to managing alerts to being on call to Debugging crashing things,
like SRE also has a wide variety of things under its umbrella..
So either a person has to do it in rotation of all the stuffs, which at least I think is very difficult to get in Big companies as they usually define your area of work as I think...
and when working on something very large.. which is a product used by many I think getting to know about stuffs and how they are connected becomes very time consuming maybe...
for example I would state... I have been working in the cdn domain for past 1 year.. so knowing each and every stuff about the configurations on router, how they are deployed from router level to multiple services architecture and maybe building something on top of it.... I found it a bit difficult... Like solving a simple high partition usage problem on a live production server might become troublesome... with so many components involved with so many service owners around it
@@umanga312 Yes, I agree with you on that. We as SRE do not have to know everything. We should good with the basics of linux, networking, programming and system design. Depending on the team you are in (database, traffic, hadoop etc), you should learn about the the things you need to. But as a SRE, we have to be oncall once a week, do engineering work 50% of the time, debug issues during oncall when they arrive through alerts.
Do I need to know ansible like a master who is writing custom module in python?
It depends on the jobs requirement.
Amazing session Shivam.. 👏🏻👏🏻👏🏻
Is it possible to switch senior SDET to senior SRE.
Is SRE role similar to as Software Testing / Quality assurance role?
No. Both are very different roles. Software testing is concerned with testing. A SRE is concerned about the issues that may arise after the code is pushed to production and is live.
@@practicalcsjourney Thanks 👍
Very nicely explained, Thanks for sharing 👍
Hey Shivam, Could you suggest how to prepare for the "Code Review Round"? Your Video is very helpful for other Rounds. I have an upcoming interview in 1 week.
Great work Chap!!!
Thank you!!
I have 5 years of experience in networking
Is this good to switch my career into SRE ?
yes could becomee Network SRE and upgrade yourself to application SRE
Keep it up Shivam!! your videos are really good with detailed explanation
shivvam the audio is not good
One person for few service!! , I am managing whole enterprise application 😳
It all depends on how big the service is. A single person handling a big service is not great. If the service is small, it can be handled.
@Shivm does some experience matter for SRE role because I have 1 year experience in CICD but I don't know how much experience they want for SRE role in networking,system design, Linux.
This book is enough to get knowledge & hand on experience in all SRE areas.
Some experience is good in getting interviews. 1 year experience in CI/CD should be good. You should focus on the core areas and apply. Which book you are talking about ?
@@practicalcsjourney thanks for answering
hi Shivam
Watch with 0.76 speed.
Nice
Hi,
hi
Hi
Hi
Hello
Hi
hi
Hi
Hi
Hi