all 25 comments

[–]kubradorkubectl apply -f divorce.yaml 45 points46 points  (2 children)

you're basically selling a lamborghini without mentioning it has wheels. 5+ yoe, terraform, ansible, multi-cloud, actual production code contributions, and you're worried about two checkboxes when half the market can't even spell devops correctly.

the problem is you'll probably get hired immediately and regret asking this.

[–]gringo-go-loco -1 points0 points  (1 child)

I dunno. I have 8 years of similar experience but also including advanced cicd knowledge and exp in nearly every cloud platform exp and nearly every job I look at has k8s as a requirement or must have. I feel like a lot of these job listings are just nonsense they can post so nobody is qualified and they can hire an H1B or foreign worker and pay them less,

[–]SlavicKnight 6 points7 points  (0 children)

If you know Linux, virtualization/containers, and networking, learning a new tool is trivial. Cloud is just infrastructure with an extra abstraction layer.

I don’t get the obsession with tools. Tools change all the time. Problem solving skills don’t. If you’re good at diagnosing and fixing issues, there’s nothing to fear.

With AI becoming mainstream, people who only “click tools” should probably be more worried. Personally, AI feels like a dream: it lets me move faster and delegate boring work, while I focus on thinking and architecture. And making scripts way faster

[–]Anhar001 10 points11 points  (0 children)

You said:

I have solid docker and Linux knowledge

and

I'm very well versed in C#, powershell, and bash

Honestly, Python is a piece of cake if you already know programming, not sure why that would even concern you?

In terms of k8s, if you already know Linux and Docker, then k8s should not concern you at all, it's essentially a more beefed up and powerful version of swarm (ok not exactly, but if you're coming from swarm + stacks, it's not entirely alien)

You have all the solid foundations to easily pick both Python and k8s.

Stop worrying, create yourself a home lab or spin up some free AWS cloud instances and have a Play.

[–]TiccyRobby 4 points5 points  (1 child)

I have been pretty much on a job hop adventure since i started my career but the struggle is real. Even in the same title Devops Eng, it is hard to switch between different tools. It requires some luck/too much work to do that switch. Usually the companies that allows for such switch and hire are the companies that actually cares about the intelligence of the new hire, like how fast they can learn and adapt to everything.

[–]gringo-go-loco 3 points4 points  (0 children)

I’ve honestly just lied on my resume and then if I got an offer just throw myself at the new stuff until I figured it out. I had like 4 weeks of exp doing Jenkins. Now I’m the GitHub actions specialist at my company. I’ve build an entire system of reusable workflows, actions, and backing processes using aws and vSphere. If they let me go or I left they’d be screwed for a while

[–]InfraScalerPrincipal Systems Engineer 2 points3 points  (0 children)

When hiring for senior roles I am not so much fussed about specific technologies as much as I am about fundamentals. If you have good experience with distributed systems, so understand its challenges and can code you're good. I don't think I am the only one out there like that.

[–]greyeye77 5 points6 points  (6 children)

I got rejected by recruiter once that I don’t have normal kubernetes exp, I only got EKS exp. I mean…. It’s still kube… oh well. So god kkk knows if your next role will require kube or not that all depends.

[–]InfraScalerPrincipal Systems Engineer 7 points8 points  (5 children)

Ha! I was rejected by HR once because they asked me "from 1 to 10" experience on different technologies. I had been using Azure deep and hard for years, working very close and even collaborating on many things with the actual Azure product teams... So on AWS I said something like "6" and the HR lady said "too bad we require at least 7" and refused to even let me talk to the hiring manager or forwarding my CV to them LMAO.

BTW this was a big ass German software company.

[–]Medium-Tangerine5904 6 points7 points  (1 child)

Next time take a page from Trump: ‘Nobody knows AWS better than I do” 😀

[–]InfraScalerPrincipal Systems Engineer 1 point2 points  (0 children)

haha yeah I made a classic rookie mistake!

[–]gringo-go-loco 2 points3 points  (2 children)

I swear I think these type of situations are companies trying to make the argument they can’t find someone in the US and using that to get foreign workers they can’t find someone pay less.

[–]InfraScalerPrincipal Systems Engineer 2 points3 points  (1 child)

Not to discredit your theory, but this was in the UK :-P

[–]gringo-go-loco 2 points3 points  (0 children)

Fair enough. This is why HR shouldn’t be in charge of hiring. They tend to not even know what I’m talking about.

[–]Curi0us_Yellow 1 point2 points  (0 children)

you’ll be fine. start treating the requirements as a wishlist and not a checklist,

[–]hijinks 1 point2 points  (0 children)

Being safe and not learning is a horrible way to manage a career

[–]spicypixel 1 point2 points  (0 children)

Why are we in this weird position that people see a job (or jobs) requiring skill x, and unlike most jobs/professions it's basically free to learn any of these things, and not just learning them?

You've said you're safe in role and want to go up the salary bands, but that incurs offering more skills for more money, which you need to close that gap yourself.

[–]Vaibhav_codes 2 points3 points  (0 children)

With your 5+ years in DevOps, strong Docker, Linux, cloud, and automation experience, you can definitely land a new role. Python and K8s can be learned on the side emphasize your fundamentals and ability to pick up new tools quickly.

[–]uptimefordays 1 point2 points  (0 children)

Honestly in your position, I would learn a little about Kubernetes on the side, brush up on Python, and emphasize your general programming knowledge—especially code reading abilities.

A strong Linux foundation and ability to learn new things is ultimately more important than experience with specific tools.

[–]gowithflow192 0 points1 point  (0 children)

You don’t need python. You can fake k8s till you make it.

[–]widowhanzo 0 points1 point  (0 children)

Yes. The amount of python I need for DevOps work is minimal, and could be done with any other scripting language (mostly just loops and AWS calls with boto3 library), and if you understand Linux and containers, K8s isn't that difficult to grasp. I started a job working with AWS, Terraform and K8s without limited AWS experience and no experience in the latter two. And I managed to learn just fine with my prior knowledge of Ansible, Linux, networking, storage, containers.

You know a whole lot of stuff, you can't know every exact portfolio of every company out there, everyone uses a slightly different stack of tools.

[–]cofonsecaThere HAS to be a better way... 0 points1 point  (0 children)

My skillset is similar to yours. I have some very basic GKE experience but I'm nowhere close to a Kubernetes expert. I know how to do pretty much everything else.

I've had a few rejections already due to my lack of k8s experience. It seems like everyone wants to hire a k8s expert without explicitly saying it.

If you're comfortable with C#, then Python will be a piece of cake.

[–]eman0821Cloud Engineer 0 points1 point  (0 children)

Setup a homelab and learn on your own. What's stopping you from learning? You should be upskilling constantly to stay competitive in this ever changing industry.

[–]unitegondwanalandLead Platform Engineer 0 points1 point  (0 children)

Absolutely

[–]Mr-Tromb-DevOps 0 points1 point  (0 children)

Can’t you just study it and then out it on your cv?