Questions are totally based off of your experience and work history. Make sure to revisit fundamentals for your Key area of expertise. You'll be surprised to hear questions about simple basics such as protocols, networking fundamentals or even troubleshooting (any tools ), no need to worry about 3rd party tools (other than Microsoft products).
There was nothing difficult as such they really are not doing any rocket science, but if they are picky on some technology they will grill you on it, ex. f5 load balancers, if its on your resume better know it in and out and i dont mean load balancing methods, much beyond that. Questions such as application slowness issues through F5.
Basic about Linux, Scripting and Apache/Tomcat Load Balancing architecture
They asked about my previous careers and history
What is something that sets me apart from other people interviewing for the same position?
Find errors in a Jenkins pipeline script Do a customer-oriented presentation
They asked all different type of questions
Looking at a component determine likely failure modes and possible ways to prevent them.
Under new contract, but was slow getting the time codes out to users. I realize that the government had much to do with the delay.
Behavioral questions like 1 example where you failed and how did you solve it. Challenges you have faced convincing your leaders for an idea.
Viewing 71 - 80 interview questions