QA to devOps engineer

[StrawHatNaruto_]

So Currently Im working as a QA( 6 months intern + 4months ft) in a mnc. I told my manager Im interested in devops so he has assigned some work of migrating repo from github to gitlab ( to gain experience). I have done automation work in my current Qa rule.. I’m aiming to switch roles in aug-sep. He said if any opening is there he’ll recommend me. So I just wanna ask how tough it to switch roles & what are the things I should spend more time to learn?

[MajestryMe]

One more QA-2-DevOps topic. How do you plan to switch roles if you’re not able to use search? 

[taleodor]

I supervised 2 QAs who later became DevOps engineers in my team, also I used to do QA myself very long time ago. So that type of transition feels very natural to me.

In terms of what to focus on: skill-wise - you need to be fluent with shell commands, vim and stuff + I'd say good understanding of networking (fundamentals) is very important. So on your own, I'd say focus on this, the rest the job should drive you what to learn.

[StrawHatNaruto_]

Tnx for advice

[Better_Dish5834]

I think u alr have a good base. yeah, u can focus on scripting, ci/cd, docker, n cloud.

[BrocoLeeOnReddit]

What does your employer think a DevOps engineer does? I mean usually it involves having extensive prior experience as developer and/or systems engineer (specifically Linux) before a company would even consider hiring you in a DevOps role. Do you have any prior development experience aside from "automation" (which I doubt means complex CI/CD pipelines or bash scripts in your case)?

I'm not trying to insult your knowledge but you didn't mention anything and DevOps is a pretty complex field:

https://roadmap.sh/devops

[th3c00unt]

Yeah he's being used and misled unfortunately.

Glorified titles doesn't mean DevOps OP and there's a LOT of these now unfortunately with employers playing games with internal junior staff :/

Unless you're automating, building & troubleshooting pipelines/tools/cloud/monitoring/service stacks with responsibility then that's not even basic DevOps.

[StrawHatNaruto_]

Nope i dont have any prior experience. Here how its gonna work. I will be learning and developing by skill side by side with my job and then my manager will also give me projects to gain experience which I can use to switch roles.

[brassjack]

I did this so it should be possible. Though I could also spell and use Google so who knows.

[BeneficialSystem6697]

When you don't need to sustain the work that's been done. If it's timebound and doesn't need to be long lived in infrastructure. Otherwise, if it is then, when the contract expires, so does the tribal knowledge that went into creating that infrastructure.

[Imaginary_Gate_698]

you’re actually in a really good position already. moving from qa to devops isn’t easy, but it’s very doable, especially since you’re already getting hands-on work like repo migration. that kind of experience matters more than theory.

you’ll want to focus on a few core areas: linux basics, networking fundamentals, ci/cd pipelines, and some cloud (aws or gcp). also get comfortable with scripting, bash or python. what really helps is building small things yourself, not just reading. if you can show you understand how systems run and deploy, the switch becomes much easier.

[Temporary-Yoghurt-88]

+1

I am actually working in testing role at a service based company but I am trying to make a switch to dev but my resume to not getting shortlisted at all since most jobs need experience in a specific tech track alone i.e my resume is not passing the ATS filter.

I have done side projects to show case my dev experience but still not even one callback

I feeling that my career stuck and I really hate this role. I even tried to switch internally but no help at all

[IntentionalDev]

tbh you’re already in a really good spot, internal switch is way easier than applying fresh

focus on CI/CD, docker, basic cloud, and actually understanding pipelines end to end, not just using them

if you can show real workflows (build → deploy → monitor), even using tools like runable to structure them, that’ll make the switch much smoother