Live data from Hacker News

Ask HN: DevOps Career Advice for an Oldy

news.ycombinator.com

21–30 of 50 posts

Re: Ask HN: DevOps Career Advice for an Oldy

#21

To me it seems like you've hit a point in your career where you need to learn some new skills. That doesn't mean your old skills are now worthless, it means you need to learn some new ones to go with them. I'm younger than you (25), but I already flip-flop between higher paid jobs that use the skills I already have, and slightly less well paid ones that give me the opportunity to learn new skills. I figure that's jus…

I'm almost 42: you never hit a point where you don't need to learn new skills. There will be periods of time when you can sit on your hands and just coast, but those periods ALWAYS come to an end. I've seen it happen multiple times.

Re: Ask HN: DevOps Career Advice for an Oldy

#22
Use your skills to your advantage. In an interview, don't settle for crappy coding challenges. Ask the company what version of linux they're running in their docker containers (and when it was updated/patched) If they can't even tell you, prove value by telling them why (security, perf) and how (either newer canonical images or custom) My point here is the game hasn't really changed, it's just gotten wrapped in two more layers of abstraction. My learning advice: - Skip python, unless you want to become a coder or get into data science - Learn how to launch a basic app using docker (think of a dockerfile like a shell script) - Learn the 4 basic things you need to launch a basic app on kube (pod, deployment, service, ingress)

Re: Ask HN: DevOps Career Advice for an Oldy

#23
I used to work in financial and it's pretty easy to get frozen in time technology-wise.

It would do some good to learn modern CICD. Take a look at CircleCI and see if you can wrap your head around it. These days the tolerance for a developer that can't build/deploy their own code is getting low.

Also while it's a good idea to learn Docker/Kubernetes, its primary use-case will become making older applications easier to manage on cloud providers. The demand for people who know Kubernetes is still increasing however the skillset is becoming a commodity.

The current trajectory for new development work is leaning towards solutions like App Engine and other cloud-specific solutions. As a python developer I'd pick up any python-centric offering from AWS and GCP and make a weekend project out of it.

Re: Ask HN: DevOps Career Advice for an Oldy

#24
Old? You're hardly even middle age! Someone who is actually on the later stage of their working life might take issue with you calling yourself old.

I'm sorry that the jobs you've hit up made you feel old, but please keep in mind that that is more a property of the places where you've interviewed rather than a property of you. Plenty of places will have interviewers in their 40s or 50s if that's what you're after. Maybe start looking at more established organizations rather than the nimble upstarts?

It's probably expected that any sysadmin style role knows their way around Python and the other stuff you mention, but nobody is an expert on everything. It's probably more likely that you are priced out rather than skilled out if you've done this for a while. That's not strange in itself. Experience breeds specialization, and the more specialized you are the longer you will have to look.

The answer is never to sell yourself cheap. Find out what your specialization looks like and find someone who might find it valuable.

Re: Ask HN: DevOps Career Advice for an Oldy

#25
Your question is how can you continue to be compensated highly in this fast changing industry that already compensates very well. It's a tough question and I don't think anyone has a magic bullet for you.

Here's some general tips from the business side:

- When you are struggling to compete, differentiate yourself and find a smaller, more specialized audience. Don't attempt to compete head on unless you believe you have an upper hand.

- There are skillset that are always subject to the whims of the day but there are also skillsets that do not: among them are (1) the ability to sell yourself and (2) the ability to manage and motivate others. These two skills have stood the test of time and if you commit yourself to at least getting better at them, so will you.

I'm a developer in my 30s who retrained after being a lawyer. I flat out tell people I'm not that great a developer. I have never gotten a job from having to prove my technical skill and have not yet needed to. I rely on my network, find a specialized niche market (startups that have just figured out how to make money but don't yet have a product orientated tech leader), and I impress upon them non-coding abilities (I ask them a load of questions about their business and operations and talk about strategy, product, organization challenges - things they don't get from a typical developer candidate). You should not adopt the same strategy but maybe think about what non-technical skills makes you differentiated and where those skills might be needed most.

Re: Ask HN: DevOps Career Advice for an Oldy

#26

I'm a systems engineer in WA state in my early 40s and this is exactly why I gave up trying to find a "real" DevOps job. I know Python, Puppet, Docker, Azure, etc. very well, have a liberal arts BA as well as a good chunk of a CS degree, but found that I couldn't get an offer no matter how well the interviews went. I eventually chalked it up to my age, especially after I was made fun of during a team lunch portion of…

that is depressing. early 40s isn't even that old. are your salary demands outrageous, or do you just think it's outright ageism?

Re: Ask HN: DevOps Career Advice for an Oldy

#27
post #3

I have a few questions to ask you, which will hopefully help you find a more satisfying answer to your conundrum. 1) What is motivating this change? Are you currently unemployed, looking for new work or rather concerned about ensuring your employability over time? Are you looking to earn a higher salary? 2) In an ideal world, would you want to learn this new technology or would you rather stick with building your exi…

Makes sense!

1 - Contract is ending soon and I'm scouring for a new one or FTE role while wading through strange interviews and lots of recruiters. This sort of gives me a sense.

2 - Outside of work is fine! I already spend 3-4 hours a week on personal tech reading. The issue is, you can read Docker all you want - companies want to see it in production. What do they ask?

"How many years of experience do you have in production with AWS/Docker/Kubernetes"

3 - A fair amount of risk

4 - Pay the bills! For the next 5-10 years.

No, it's helpful. Thank you.

Re: Ask HN: DevOps Career Advice for an Oldy

#28

I'm a systems engineer in WA state in my early 40s and this is exactly why I gave up trying to find a "real" DevOps job. I know Python, Puppet, Docker, Azure, etc. very well, have a liberal arts BA as well as a good chunk of a CS degree, but found that I couldn't get an offer no matter how well the interviews went. I eventually chalked it up to my age, especially after I was made fun of during a team lunch portion of…

that is depressing. early 40s isn't even that old. are your salary demands outrageous, or do you just think it's outright ageism?

I make at least 30% less than any systems related industry job out there, so no I don't think my salary demands are outrageous. I think it's a combination of ageism, having a family - hence not being willing to put in insane hours, and the idea that someone coming from the public sector cannot succeed anywhere else.

Re: Ask HN: DevOps Career Advice for an Oldy

#29
post #24

Old? You're hardly even middle age! Someone who is actually on the later stage of their working life might take issue with you calling yourself old. I'm sorry that the jobs you've hit up made you feel old, but please keep in mind that that is more a property of the places where you've interviewed rather than a property of you. Plenty of places will have interviewers in their 40s or 50s if that's what you're after. Ma…

Regarding it's a property of the places I'm interviewing at..

.. there's a startup boom in NYC. And I think startups prefer young, dynamic types on the cheap? A buddy of mine from California says this is the Silicon Valley mindset creeping in. I'm not so sure, but there is something about startups and not hiring too many older folks.

Re: Ask HN: DevOps Career Advice for an Oldy

#30

My path started as Systems Admin -> DevOps/SRE -> Management. Double down on your programming skills, cloud management and brush up on the infrastructure components. Your age / experience should actually add to your value. Subnetting, firewalls, routing, security baselines are things that are often overlooked by new people starting DevOps roles. This option also lends to doing consulting and contracting. You day job…

I was thinking about going back to management.

Do you find roles through old-fashioned recruiters or business networks?

Post reply on HN