• 0 Posts
  • 300 Comments
Joined 3 years ago
cake
Cake day: July 2nd, 2023

help-circle
  • So oddly tier iii is just tier 2. Most places don’t have a tier 2.

    1 years experience as sysadmin is great. Here’s the neat little trick no one tells you: what you say your job is on your resume should reflect WHAT YOU DO. Not the title of what you were hired for

    Are you doing dev ops at a small outfit as a support engineer? Your resume should not say “support engineer.” It should say what your tasks reflect to the market. Not what some dude said your position is.



  • I’m sure the job postings will say, but many dev ops roles are looking for someone with senior experience. Like 8-10 years or the resume is ignored.

    Id say the way to beat this is look for tier iii roles for folks that don’t know what they need is dev ops. Explain the value of what you want to do as a sysadmin to bring value. Then just write dev ops on your resume when you wind up doing dev ops.



  • 100% building a home lab and being able to talk about it openly, from memory, in your own words, from experience, is invaluable for interviews.

    I might update this. I might not. I have a lot to say but In out drinking.

    All I will say now is save this list. You’ll look back at it in 5 years and wonder what half of those things are.

    Okay a bit more from the bar:

    If you want dev sec ops, grafana, elk, build dashboards, get your agents setup in your fleet, get it all secure locally. That alone will impress any interviewer who knows anything.

    Dev ops specifically? Focus on building a local GitLab instance. Use grafana to monitor it. Run some app that has a busy db. Grafana dashboards on that. Oh my goodness, what a HOG you are GitLab! Tune it for your env. Purposely misconfigure something to watch, idk, the RAM keep growing because you didn’t setup redis or some shit.

    The sea is vast. You’re hungry. Employers will see that once you land interviews.

    If you want a ton of dev sec ops ideas, I am a good sounding board. Regular dev ops isn’t my daily grind so I know a bit less. What I do know is if you’re not ready to rebuild a multi node cluster some night after hours, you’re not quite a boss (doesn’t mean you’re not ready). So, emulate that nightmare.

    Back to drinking 🍻

    Edit: double check your *arr ideas bc afaik most of those were abandoned after a few major vulns were uncovered. That was months ago so that may be old hat.




  • Just here to brag that when my dad upgraded to windows 11, he was tricked into making a microsoft365 acct which was promptly compromised.

    So I walked him through the process of downloading a Linux mint iso, checking the hash in powershell, downloading rufus, prepping install media, and getting him off windows for the remainder of his life.

    I had no eyes on the situation. All over the phone. His browser was giving malware results for everything so no downloads could be trusted.

    2 years on his only complaint is occasional printer problems. He’s in his 70s.




  • lol how do you want your tech team’s security lead to explain to Bill from management in the ohio office that his new hire will continue to be isolated from the network if he downloads isos from his browser to make a VM on his desktop and also tell Shirley in the Texas office that one of her developers sftp users PW has been expired for a week and it’s setting off brute force triggers in your siem?

    You ready to hire a fuck ton more IT workers?

    Nah just have AI do it. Like a competitor won’t poison that shit to leak company data. 🤙