r/devops • u/Husseinnnnnnn 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
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.
18
u/mralex215 2d ago
To me this sounds like sysadmin. Devops is writing code to glue things (tools) together to automate this stuff.
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/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.
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/DhroovP 2d ago
How good is your Kubernetes knowledge? That matters a lot for future career goals
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/tanyadev4827 2d ago
valid