TH-cam Chapters @DevOps-Cloud 0:00 - Introduction 0:23 - Early Career: Software Engineer Trainee at Infosys 1:06 - Senior Systems Engineer in IAM Domain 2:01 - Transition to DevOps and Cloud 2:41 - Cloud Support Engineer at Accenture 3:40 - Cloud DevOps Consultant at a Startup 4:37 - Overview of Professional Journey 4:44 - Kubernetes and Container Orchestration 6:06 - Components of Kubernetes 7:05 - Size of Managed Kubernetes Infrastructure 7:48 - Steps to Deploy a Service in Kubernetes 9:43 - Types of Services in Kubernetes 10:08 - Managing a Team of Six 11:21 - Infrastructure Management for Front-end and Back-end 12:00 - Understanding of Site Reliability Engineering (SRE) 13:19 - SLI, SLO, and SLA 15:26 - Measuring SLI, SLO, and SLA 16:35 - RTO and RPO 17:55 - Highly Available Application Considerations 19:04 - Cost-Effective Features for AWS 21:29 - High Availability: Region vs. Zone 23:24 - Crisis Management: Application Downtime 26:07 - Leadership and Crisis Communication 29:01 - Team Distribution and Prioritization in a Crisis 30:55 - Influencing Team for Innovation and Process Improvement 32:43 - Conclusion and Thanks
This was really good interaction and really a good reference point how to answer the interview questions. Amazing work! my biggest problem was even though I have the concept clear I would not be able to explain it in interview but after seeing this I really gave some guide points to improve myself. cheers and thank you!
I think this was a good interview, the main goal for the interviewee is to explain the concepts as it is to be explained to a person who has no knowledge about these concepts, and also to keep it brief. So this is a good interview when compared.
IMPOSTER. in it's purest form. Other than intro, she didn't prepared for anything else. I have interviewed many candidates in my career, whenever a candidate gives long intro with weird english accent, I quickly get a picture that, he/she gonna bluf a lot in the tech questions/answers. so keep your intro short, let the real talk begin as quick as possible. it will save the time for almost all of us.
Accent is perfectly fine. And intro isn’t that bad either. Looks like you need some interview training. So much bias and BS. If you feel it’s long, cut it short.
She has a very normal Indian accent for someone who is fluent in English. The only things she did wrong was that the intro was long so the interviewer will have lot more topics to ask questions on and expect proper answers. Also when you don't know something be free to admit it. I particularly don't like interviews that are more focused on technical questions. Most of the interviews that went well for me mainly focused on my work and gave the interviewee an idea of all the things I was exposed to. I also can particularly focus on parts where i can show how I solved a problem. Answering technical questions is not a perfect representation of a candidate. In a job scenario you have access to much more resources than in a face to face interview. The difference shows when a candidate can show that when they have access to resources they are able to find good solutions to problems and consider different options.
Should we consider as Excellent? As Team lead, Deploying application on Kubernetes cluster and not knowing about Kube Scheduler on Master node of Kubernetes which are responsible for scheduling the pods on workers nodes , not knowing main three services, Cluster IP, Node port, Load balancer, so what she has used as type in service.yaml if not knowing about three services,
Don't be so harsh on her...While she was not able to answer what are the three services. Having said that i am sure that she just blanked out at that moment. If the interviewer would have asked tell me something about nodePort, cluster IP, i am sure she would have been able to answer it given the fact she mentioned that she has worked on developing yaml files pertaining to services etc.
@@nvasudevafor antansolanki comment. Bro you can tell me she is clearly telling us we are using service.yaml file for connecting the other containers and nodes so she should know the types right because in service.yaml the main purpose is type only know.
It's a disastrous interview. Would never select her with these answers! No hands on, also very confused with the theory also! Microservices are not that straightforward, and it requires some system level experience, not necessarily Kubernetes experience. But having Linux administration experience would help alot.
Don't be a bad critic. What is the bad thing about reading it from somewhere? Having a script in front of you only makes you more organized with your responses
Intro-Good K8s- Just for the sake of the interview, she studied Kubernetes. No Practical work. 6. SRE?- Site HA, self heal, Disaster recovery mechanism.- Answer is not clear. SLI- SLO SLA? How do we measure each of them? Running the application for 6 months - how to measure the SLO?
Is it bad? She atleast studied. People who got into devops from beginning will have work experience, what about the people who wants to get in? With 8 years of experience she says i am fresher and new to devops will anyone hire her?
TH-cam Chapters @DevOps-Cloud
0:00 - Introduction
0:23 - Early Career: Software Engineer Trainee at Infosys
1:06 - Senior Systems Engineer in IAM Domain
2:01 - Transition to DevOps and Cloud
2:41 - Cloud Support Engineer at Accenture
3:40 - Cloud DevOps Consultant at a Startup
4:37 - Overview of Professional Journey
4:44 - Kubernetes and Container Orchestration
6:06 - Components of Kubernetes
7:05 - Size of Managed Kubernetes Infrastructure
7:48 - Steps to Deploy a Service in Kubernetes
9:43 - Types of Services in Kubernetes
10:08 - Managing a Team of Six
11:21 - Infrastructure Management for Front-end and Back-end
12:00 - Understanding of Site Reliability Engineering (SRE)
13:19 - SLI, SLO, and SLA
15:26 - Measuring SLI, SLO, and SLA
16:35 - RTO and RPO
17:55 - Highly Available Application Considerations
19:04 - Cost-Effective Features for AWS
21:29 - High Availability: Region vs. Zone
23:24 - Crisis Management: Application Downtime
26:07 - Leadership and Crisis Communication
29:01 - Team Distribution and Prioritization in a Crisis
30:55 - Influencing Team for Innovation and Process Improvement
32:43 - Conclusion and Thanks
Someone answering those questions at the end would be much helpfull for us to crack interviews or learn.
This was really good interaction and really a good reference point how to answer the interview questions. Amazing work! my biggest problem was even though I have the concept clear I would not be able to explain it in interview but after seeing this I really gave some guide points to improve myself. cheers and thank you!
I like your confidence sir you are ROCKING 🎉
I think this was a good interview, the main goal for the interviewee is to explain the concepts as it is to be explained to a person who has no knowledge about these concepts, and also to keep it brief. So this is a good interview when compared.
Follow up video with proper answers would have been great sir.
IMPOSTER. in it's purest form. Other than intro, she didn't prepared for anything else. I have interviewed many candidates in my career, whenever a candidate gives long intro with weird english accent, I quickly get a picture that, he/she gonna bluf a lot in the tech questions/answers. so keep your intro short, let the real talk begin as quick as possible. it will save the time for almost all of us.
lol
thanks...good point
Why does she have to worry about saving your time when she’s trying to get a job?
Accent is perfectly fine. And intro isn’t that bad either. Looks like you need some interview training. So much bias and BS. If you feel it’s long, cut it short.
She has a very normal Indian accent for someone who is fluent in English. The only things she did wrong was that the intro was long so the interviewer will have lot more topics to ask questions on and expect proper answers. Also when you don't know something be free to admit it. I particularly don't like interviews that are more focused on technical questions. Most of the interviews that went well for me mainly focused on my work and gave the interviewee an idea of all the things I was exposed to. I also can particularly focus on parts where i can show how I solved a problem.
Answering technical questions is not a perfect representation of a candidate. In a job scenario you have access to much more resources than in a face to face interview. The difference shows when a candidate can show that when they have access to resources they are able to find good solutions to problems and consider different options.
thank you for this type of content, it's very useful for me, I'm trying to gain more experience for english interviews
Happy to hear that!
Earlier its master slave in kubernetes its now master and worker nodes architecture
at 21:15 does she looking to ans and responding?
she listed the question and requirements and referencing it to answer the question
ssl is different from tls, in initial days ssl is used as security protocols, around early 2000 we started using tls
Kubernetes components are not explained correctly . SLI, SLA, SLO require more clarification in brief
kubernetes is not anymore considered as container orchestration tools, it provides more thn that
So what is it considered as now
Will we have any interview videos on azure devops or azure Admin
edge location for content delivery throughout the regions
Three K8 Services? There are Four:: ClusterIP, NodePort, LoadBalancer, ExternalName
There is also Headless service
thank you very much..
You are welcome
Should we consider as Excellent? As Team lead, Deploying application on Kubernetes cluster and not knowing about Kube Scheduler on Master node of Kubernetes which are responsible for scheduling the pods on workers nodes , not knowing main three services, Cluster IP, Node port, Load balancer, so what she has used as type in service.yaml if not knowing about three services,
Don't be so harsh on her...While she was not able to answer what are the three services.
Having said that i am sure that she just blanked out at that moment. If the interviewer would have asked tell me something about nodePort, cluster IP, i am sure she would have been able to answer it given the fact she mentioned that she has worked on developing yaml files pertaining to services etc.
Bro well explained what in my mind to comment it kudos bro 🤜
@@VinothKumar-ik1fc your response is against whose comment ?
@@nvasudevafor antansolanki comment. Bro you can tell me she is clearly telling us we are using service.yaml file for connecting the other containers and nodes so she should know the types right because in service.yaml the main purpose is type only know.
yup. it was a pretty basic question. @@VinothKumar-ik1fc
It's a disastrous interview. Would never select her with these answers!
No hands on, also very confused with the theory also!
Microservices are not that straightforward, and it requires some system level experience, not necessarily Kubernetes experience. But having Linux administration experience would help alot.
Hopefully you have better answers. Everyone is invited for a free mock interview.
if i'm just a regular joe developer without any experience in devops, can i land a job as as SRE lol
Sir your WhatsApp group is full?
there is always a new group because of high demand
Let me know when you create a new group.
we have new group
@@DevOps-Cloud please where is the link?
check video description@@danielessiet4063
Devops training instructors are more now than the devops job openings...
haha, most of them are looking for a job themselves ...
Agree
My guys is in Dagons domain, hahaha
Hi Bro,
How can i get Realtime experience in DevOps. Please Explain?
By building complex project. Our next project start’s mid January
how can i get the details..@@DevOps-Cloud
same question ,how can we attend the next project start mid january? @@DevOps-Cloud
topmate.io/cloud/649977
I think she is reading somewhere
Don't be a bad critic. What is the bad thing about reading it from somewhere? Having a script in front of you only makes you more organized with your responses
Not reading. These are spontaneous unprepared questions. Like actual interview.
Was she selected ?
What do you think ?
@@DevOps-Cloud probably no
these are mock interviews to check your readiness you can book for free with us@@shivamshekhar5423
@@DevOps-Cloud pls let me know how to book these interviews ?
do some look around our channel to find link@@shivamshekhar5423
How much experience does she have ?
overall 10+ years
his background 😭😭😭
😂
Intro-Good
K8s- Just for the sake of the interview, she studied Kubernetes. No Practical work.
6. SRE?- Site HA, self heal, Disaster recovery mechanism.- Answer is not clear.
SLI- SLO SLA? How do we measure each of them?
Running the application for 6 months - how to measure the SLO?
Is it bad? She atleast studied. People who got into devops from beginning will have work experience, what about the people who wants to get in? With 8 years of experience she says i am fresher and new to devops will anyone hire her?
Not "Excellent" very hollow answers and basics
toooo long introduction ...it shud be short...rest is good
sorry to say this .. but acording to you if it is excellent then que raised about excellency .....
it takes courage. you can try too..
She is good