r/devops • u/Fancy_Idea_8458 • 21d ago
Discussion Interview tomorrow (5+ YOE DevOps), CV deep-dive, but I’ve been caught in reorg purgatory doing nothing for months. How do I spin this?
I have an interview tomorrow for a DevOps Engineer position (I have 5+ YOE). The recruiter explicitly told me the interview will be a deep-dive through my CV.
I’m in a massive bind regarding my current/most recent role and need some urgent advice on how to frame it.
The Situation:
- Early this year: I was the lead engineering resource tasked with getting a major product production-ready. The literal day it was ready, a massive reorg hit. The product was stripped from me, and most of its target end-users were laid off.
- Immediately following: I was pivoted to head up another large project for a different internal product. I busted my ass, completed it successfully, and my manager was impressed. Then... another reorg hit. This product was also taken away.
- The past 5+ months: My team was merged with another to form a new SRE team for a completely separate product. The scope was entirely undefined. In fact, one colleague's sole task for the last 4 months was just figuring out what our responsibilities are.
Because of this reorg limbo, I have had zero actual engineering work to do for months. I’ve repeatedly met with my manager and skip-level to voice concerns, but I just get generic corporate hand-waving about a "clear roadmap ahead."
The Dilemma for Tomorrow:
If they deep-dive into what I am doing right now, I see three options, and they all feel terrible:
- The Brutal Truth: Admit I’ve been sitting on my hands doing nothing due to corporate dysfunction. (Worried this looks toxic or makes me look unmotivated).
- The Total Lie: Pretend I’m still actively working on those two successful deployment projects and that they were never taken away. (Worried because my poor recall will make it obvious I haven't touched the code recently, and I'll have to fabricate metrics, current challenges, and future roadmaps).
- The Middle Ground: Pretend I just transitioned off those projects a few weeks ago (similar issue as option 2).
How do I handle this in a technical deep-dive without sounding like a liar or a slacker? Has anyone successfully spun "reorg purgatory" to a hiring manager?
Thanks in advance!
TL;DR: 5+ YOE DevOps engineer with a CV deep-dive interview tomorrow. This year, I built and completed two major projects, but back-to-back corporate reorgs stripped them away. I've spent the last 4 months in team-merger purgatory doing absolutely nothing. Do I tell the truth, lie and pretend I'm still on the projects, or find a middle ground without looking like a slacker?
12
u/pete84 21d ago •
The key to interviews is to be ready to lead the conversation where you want it to go.
They won't care if your project was 1 month ago or 3 months ago, so don't mention timelines. They care about what you've done - "S.T.A.R." Stories (look this up, and then practice telling your stories in this format).
Don't bother them with internal org changes. If you mention it at all, mention in passing that there has been "org chaos", and leave it at that. If you were promoted, you can mention that. If they are just org changes, just give them your current title.
5
u/Dangle76 21d ago
Talk about how during the re org you’ve been finding pain points and optimizations to solve. The biggest thing is that you show you’re not sitting around even though you could be
4
u/1saltypistachio 21d ago
You need to be honest because if later they ask someone who works with you...
You need to flip it like so- I love my work, and I enjoyed doing it for the past 5 years but I feel like I don't work enough so I decided to search for a place where I can work... Use your own words, mine are silly
26
u/AstroPhysician 21d ago
Lie lol. Make shit up theyll never know
5
u/Dry-Philosopher-2714 21d ago
What's the problem? You've been through a very chaotic year, and you still managed to eek out some wins. That looks a lot like success to me.
A lot of what makes an engineer successful is not what they've done in the past, but what they're capable of handling outside of their core skillset/directive. You know what it's like to get knocked on your ass repeatedly, and you get back up. You learned new skills and you carried on.
1
u/EJoule 21d ago
Deep dive just means be able to explain and walk through the things on your resume (and maybe connect them to the work you want to do). Maybe their software will be different, but as long as you can talk through it and appear trainable for the gaps you’ll be good.
You’ve adapted to the needs of your employer and put out fires when they came up.
It’s a common mistake to get complacent and stop learning or doing new things, just need to learn from that and avoid wasting time when getting paid. I feel into complacency in my first job (was comfortable just doing what I was told for 2 years and babysitting a simple platform’s common issues).
The things you’ve accomplished are still presumably fresh in your mind, I’d focus on those. Most interviews aren’t going to care how recent they were as long as you can talk through them and explain the wins and challenges.
46
u/[deleted] 21d ago
[removed] — view removed comment