r/devops • Junior DevOps Engineer • 2d ago

Discussion Mid-Level DevOps Engineer expectations

I'm a Junior DevOps Engineer with 4 YOE straight out of uni and I would like to know from all the Leads/Managers/Seniors etc what do you guys expect from a mid-level engineer compared to junior.

I will list some of my responsibilities to paint a better picture:

- Maintain and update our internal site (Flask, SQL + MSSQL, Apache, nginx, JS)

- Create and maintain on-prem and in-cloud VMs (Azure and vSphere)

- Setup and maintain on-prem AI servers that we used to rollout to the rest of the engineering department (Nvidia DGX boxes with vLLM + load balancer + harness)

- Troubleshooting tickets from other departments within the engineering department and helping them out with their issues

- DevSecOps for CI/CD pipelines where we implement code analysis (SonarQube) and dependency/base-image analysis (Trivy)

- Containerization (docker and k8s)

- setup and configure and maintain internal repo servers via Nexus Sonatype

- Experience in Platform Engineering, built an in-house tool that allows the devs to push a list containing their dependencies which the tool will download and pushes those packages to the internal repos which then can be used by our Jenkins pipelines (all our pipelines are air-gapped)

- Networking (internal/external DNS, configuring network settings for servers/VMs)

- Issuing self-signed certs

- Maintaining a project that is integrated with Zoho which is used to create customer's sales orders and confirmation emails which I work closely with the support department

These are some of my responsibilities and the point of this post is that I am genuinely interested in what others who are above me look for a mid-level engineer. I have already asked the expectations of the company but I would like to know the expectations of the industry in general. Thanks in-advance

18 Upvotes

26 comments sorted by

11

u/Sea_Ad6592 2d ago

4 YOE and you’re still not a mid, despite taking on all those responsibilities? Honestly, it might be time to consider moving on.
I’d expect a mid-level engineer to demonstrate solid technical execution and some measurable business impact. But it seems like some companies are increasingly expecting junior engineers to deliver at a senior-level pace, without the title, recognition or compensation to match. At some point, that starts looking less like career development and more like exploitation.

3

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

Noted, thanks for the input

18

u/mralex215 2d ago

To me this sounds like sysadmin. Devops is writing code to glue things (tools) together to automate this stuff.

17

u/aquabarron 2d ago

Lots of it sounds in the ballpark though. Implementing SonarQube in a CI/CD pipeline (and I’m assuming that’s where the containerization comes in) and his platform engineering stuff and the networking, even automating the sales orders with zoho.

0

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

I can expand more on it if my point isnt making sense

1

u/aquabarron 2d ago

Ive got less experience in DevOps than you so by all means explain as much as you like

-1

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

So for example in relation to ur initial comment, we have 100s of pipelines running in Jenkins which us the DevOps maintain. Now these pipelines different from project to project but in relation to SonarQube, the point im trying to make is that any project where code is involved will have a stage within the Pipeline that runs a SonarQube scan.

Now the SQ scan itself is part of an automation pipeline which will trigger various procedures which involve scanning the code, summarising the analysis, emailing the analysis and sending the result of the analysis as a message.

In terms of containerization, its part of pipelines as well as sysadmin where we create containers via pipelines as well as on the servers to run certain services such as a syslogger or Grafana.

The platform engineering script has a UI which is used by the devs and once the dev uplands a file, it will trigger an Automation pipeline which to summarise, it will read the file, fetch the package names, pull the packages and then push the packages so that these packages can be used within our other cicd pipelines.

In regards to Zoho, the pipeline is along the lines of.... create order -> assign details (invoice, product id etc) -> create an email -> send the email. Thats the flow of the pipeline used for the Zoho side which is all controlled by pythin code that gets pushed to Zoho via a pipeline

0

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

most of these stuffs are automated together usually via bash scripts. For example to release a new release for the internal site, it runs through cicd pipeline to create the release which is then pushed live and part of that pipeline is calling other pipelines that automate other bits behind the scenes.

It may not sound like it, but 90% of the points listed above is part of an automation pipeline.

3

u/Antique-Stand-4920 2d ago

Since it is DevOps I'd want to know a candidate's experience around:

-working with devs to maintain dependencies and staying on top of security

- working with developers to build, maintain, enhance CI/CD pipelines

- making reusable components (e.g. IaC components, CI/CD components) that can b reused on multiple teams and projects

- working with dev teams with major migrations (e.g. helping them go from one architecture to another)

- introducing an initiative to help dev teams work more effectively

Of course I wouldn't expect a mid-level to lead these activities, but I'd be interested in what expose they did have

2

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

Im exposed to all of these. Point 1-3 is almost a daily thing for me.

For point 4 I was the lead in migrating some of our projects from docker to k8s for example. In addition to that I am part of a massive migration where we will be migrating our entire infrastructure from Perforce to Gitlab.

Last point, is almost a weekly thing i would say. A lot of devs from other depts do come for my advice when it comes to workflow and how we could improve it etc

2

u/Antique-Stand-4920 2d ago

Cool, it sounds like you have a pretty solid foundation.

2

u/yeahdj 2d ago

Good list of skills! The jump from junior to mid level, then to senior and then to principal is determined by behaviours and impact.

For a mid level engineer, how much of this did you set up? Vs how much what taught to you. In what ways did you automate processes, how did you land that within the team and what impact did it have. Etc etc

A mid-level engineer should be consistently closing projects they’ve been given, identifying problems and owning their solutions, automating the boring stuff, cost optimizing and adding observability.

A senior should be doing those things at a high level, guiding their teams and making broader architecture decisions, tooling decisions and delivering demonstrable value to the wider business.

1

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

In other words, the difference comes down to value and ownership? Junior does something because he's been told while mid level identifies an issue and resolves it himself?

3

u/yeahdj 2d ago

Yeah, that’s one part of it. Even if it’s a project you’ve been delegated, but you’ve worked with stakeholders to overcome issues, you’ve wrote all this documentation and you’ve created runbooks, and went above and beyond to provide a seamless cutover.

A good promo doc will be 90% behaviours and impact, showing that you’re owned the problem end to end and delivered value to the business.

Some tips from me - when I have a DR looking to get promoted I try to use the promo doc as the base for our 1:1s, we go through it every fortnight, go over each section see if it’s strong enough, try to compare it to an example if that’s possible - something to ask your manager?

1

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

Thanks a lot

3

u/anslly 2d ago

I digress, but Junior with 4YOE - shouldn't you be promoted to Mid already?

And out of curiosity - where are you based, and what do they pay you for doing all this (I have a similar scope of responsibilities)?

1

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

London 38k

2

u/Shadoweee 2d ago

GBP a year? 

2

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

Yep

1

u/DhroovP 2d ago

How good is your Kubernetes knowledge? That matters a lot for future career goals

1

u/Husseinnnnnnn Junior DevOps Engineer 2d ago

Its not as good as my docker knowledge but ive experience with creating pods, secrets, services as well setting up ingresses and externals DNS managers to allow traffic over the internet to these pods.

In my current work, not much kubernets is being assigned but we are slowly converting most of our services from docker to k8s.

1

u/SideMost3148 1d ago

your list is fine, it's a lot of stuff. but the jump to mid usually isn't more tools, it's what you do after the fix.

junior fixes the ticket. mid fixes it, then asks why it keeps coming back and kills the cause, and writes the runbook so the next person doesn't need to ping you.

the other one is owning things end to end. take the DGX/vllm box. if it falls over at 2am, do you know what breaks, who to tell, and how to bring it back without asking anyone? if yes you're closer to mid than your title says.

also 4 yoe and still "junior" sounds more like a company titles thing than a you thing

1

u/Husseinnnnnnn Junior DevOps Engineer 1d ago

Understood, thanks a lot