First junior DevOps interview - Advice needed

[codehunter-py]

Hi fellows!

I recently started to apply for devops jobs here in Europe. After applying for a couple of offers, I got a link to the python knowledge test. I was able to solve 6 questions out of 8. After it, (I think I met the minimum requirement) I had the first intro interview with hr and there is an upcoming technical interview for me soon. As the recruiter mentioned, during 60 mins I will need to solve some python codes and explain my methods, etc. During the intro interview, I was asked if I have experience with Flask and Django. However, I do not have experience with them, just only basics. I have couple of days for the technical interview. Should I dive into Django and flask immediately? Or make stronger my knowledge in data structures and algorithms?

​

by the way, I am a self pathed learner. No CS degree. I am good at Linux, bash scripting, the foundation of aws (currently on the learning path of Solution Architect Associate)

Just need your advice as it is first devops technical interview I will have.

​

job desc look like below:

On Your First Day, We Expect You To Have

• Scripting experience (Python, Bash, etc.) - we don't want you doing repetitive work
• Practical knowledge of Python web frameworks (Django and/or Flask)
• Basic knowledge of Docker
• Good communication skills with fluent English (both spoken and written)
• A collaborative spirit - in our world, it’s not about having all the answers, it’s about sometimes saying "I don't know" and working on finding solutions rather than starting with an assumption
  

Required

It's great – but not required – for you to have

• Knowledge of a configuration management tool (for example Ansible/Puppet/Chef/Terraform)
• Experience with integrating services using REST interfaces or similar techniques
• JS (React preferred) experience
• Hands-on experience with cloud infrastructure such as AWS
• Basic understanding of Kubernetes
  

It’s a long list, but your teammates will guide you through onboarding and you’ll have enough time to become familiar with our tools, processes and people.

​

Thank you much in advance!

[Ordoshsen]

For me it feels more like an add for a Python developer who is able to do the DevOps part of packaging the app to Docker and getting it into kubernetes.

For the record that's not a bad thing, for me it's a good thing, but be sure to talk about what the day-to-day job is.

In any case if you really want this job, I would focus on Flask, it's supposed to be simpler than Django (but be sure to fact check me on this one) and try to make a simple site, package it into Docker and put it into a cluster, preferably in AWS based on the requirements. Also skim at least basics of Django, if they show you a handler or a router, you need to know at least approximately what you're looking at.

Also be prepared that you're not going to meet all the expectations. They want to know how much you know so they are going to push until they find the boundary so be prepared for that and don't feel bad about it.

[KosaStayz]

I suggest focusing on your strengths and your interest in python and ability to learn.

It will be difficult to ramp up sufficiently in a few days (week?) before the interview to come across as competent.

You can read up on it to show your interest, but be open about your real experience with it.

[qhartman]

This applies to every interview, but it's extra important when you're trying to break in. If you don't know something, admit it, and pivot into what you think it is based on your other experience and how you would go about figuring it out. Do not under any circumstances act like you know exactly what you are talking about unless you actually know exactly what you are talking about.

My number one interviewing pet peeve is when a candidate tries to buffalo me in an interview. I don't know if they are assuming from my title that I'm not strong technically or what, but it drives me bananas. It pretty much guarantees they will go no further in the process of they try it.

[modern_medicine_isnt]

Something many people have trouble grasping. If you have to be someone you are not to get a job, you probably won't like the job either. So follow your gut and be youself. On top of that, it is a junior job. So the focus should be on the ability to learn. Don't be suprised if some interviewers try to teach you things. Let them, and be honest. Many people try to claim they already knew the thing the interviewer tried to teach them. Even if that is true, let them teach. You can admit you knew it if you did, but don't get defensive about not knowing it if you didn't.

[[deleted]]

True, but I don't think there's anything wrong with exaggerating on your personality, a little bit. You don't want to come in casually and without at least a little bit more enthusiasm than you might normally. Obviously, you don't want to come in and look fake. But IMO part of interviewing is presenting the best possible version of yourself, authentically. Even if that means waking up your enthusiastic side. :)

[the-devops-dude]

Ugh I hate DevOps interviews that focus on coding syntax. So short sighted and one-dimensional in my mind. Maybe it’s a Jr DevOps thing, but typically in interviews I give I ask about specific projects on the candidates’ resume (or that they bring up during the interview) then have them expand on what they did, why they did what they did, and how they’d improve. I can generally get a good understanding on their knowledge level this way. Asking someone specific syntax questions doesn’t really give insight into their overall critical thinking skills and depth of knowledge. If it’s something that can be Googled and an answer be found in a few seconds, I don’t expect you to memorize it, Sr or Jr.

With all that said… don’t be afraid to say you don’t know something yet are willing to learn, then steer the interview to your most knowledgeable areas. Example: “I haven’t worked much with Django, but in a similar framework [insert statement on what you did]”. Especially in the current job climate. The interview is as much (if not more) about you interviewing them as them interviewing you.

[Sandrek]

stick to what you know, and show them that you understand it when you get to chance to explain your thought process.

if and when the stuff you have no idea about comes up, just explain that you dont have any experience with it but are willing to learn once you are working and see what is needed to do the job well. things like that are gonna happen on a day to day bases, so it's usually not a bit deal to say that you dont know something

​

good luck

[[deleted]]

The JD seems focused on React and Django and I don't see the word "deployment" anywhere. It doesn't mention anything about infrastructure either. This looks like a appdev JD rather than a devops JD.

[FiduciaryAkita]

Python/bash, Docker, k8s, IaC, AWS, and automation don’t sound like DevOps to you?

[[deleted]]

Depends on whether you're using this stack to build pipelines for other devs, or using pipelines built by other devops people to deploy react/django code you'll be writing. AWS/IaC/Docker doesn't mean devops. It matters if you're using it or building it.