Promoted to Senior last year, now I’m suddenly the tech lead on a high-visibility project and I’m not sure if this is growth or a setup
Posted by cosmicCounterpart@reddit | ExperiencedDevs | View on Reddit | 40 comments
Been at my company 5 years.
Got promoted to Senior last year. My assumption was I’d now spend some time actually growing into the role properly. Not coasting, just gradually taking on more scope and moving from “new senior” to a more established senior over time.
Earlier this year I joined what was meant to be a one-week discovery sprint for a new internal initiative. I thought it would just be a short-term thing with product/design/engineering people from a few different areas.
Instead it turned into a much bigger initiative, pretty visible internally, with actual deadlines attached to it. Work got split into smaller streams and I ended up being assigned as the technical lead / lead engineer for one of them.
Since then I’ve been doing a lot more than I expected: architecture, scoping, estimation, phasing, cross-team coordination, stakeholder discussions, dependency stuff, figuring out ownership boundaries, all of that.
Part of me actually likes it. I do want stretch. I do want bigger responsibility. I can feel that it’s pushing me.
But the other part of me feels like I’ve been thrown into the deep end way too fast, and pretty much alone.
That’s the bit I’m struggling with. It’s not just “this is hard.” It’s more that there doesn’t seem to be much support structure around me while I’m doing it. No real lead-engineer-level backing on my side of the org, not much clarity on who the actual engineering owner is overall, not much clarity on whether I’m just temporarily filling a gap or whether I’m now expected to keep carrying this through launch and beyond.
I’ve already asked for more resourcing. My manager said he’s trying to pause other work and move people onto this initiative. That’s helpful, but to me that solves the capacity problem more than the leadership problem.
At my year-end review, my manager said:
- I’ve done strong work
- the discovery / groundwork / early shaping all looks good
- but since I was only promoted to Senior last year, I shouldn’t expect anything major recognition-wise this cycle
- and because nothing is in production yet, the real measurable impact is more likely next year
I’m not even mad at that, to be honest. I’m not sitting here saying “promote me again already.” I’m actually not in a rush to become a Lead. I’d be completely fine just continuing to grow within Senior.
What’s bothering me is more this feeling that I’m kind of speedrunning through a huge chunk of the senior-to-lead progression because the company needs someone to do it, and I don’t really have the support around me that would normally help you grow into that kind of responsibility.
And I’m also worried that if I raise this too much, I’ll just look like I’m overthinking things, talking too much, or “making it difficult” before I’ve actually shipped outcomes.
So I guess my question is:
Has anyone been in this kind of situation where a stretch opportunity was also kind of a lonely / under-supported one?
How did you figure out whether it was:
- a genuine growth opportunity or
- a leadership vacuum landing on you because you were the nearest capable person?
And how do you ask for clarity/support without sounding like you’re trying to dodge responsibility?
Would genuinely appreciate advice from people who’ve been through this.
justaguy1020@reddit
Welcome to being a Senior/Lead. What you described is literally the job. You’re the one providing direction/structure. They probably won’t give you adequate resourcing. They will still have the same expectations. You will have to navigate which corners to cut in order to meet those expectations without creating a technical shitshow.
Skid_gates_99@reddit
this is good luck coated as opportunity, but can be a setup if you dont look hard enough.
OverOnTheRock@reddit
Aren't there other seniors with whom you can compare notes? Based upon what you said, you were assigned a part of the project. Are there seniors on those other parts? Get all the seniors of the project together and talk shop. That way there is a coordinated effort across the board. The other more experienced ones can offer guidance as to how to make progress.
chikamakaleyley@reddit
dawg, they promote you because you are performing like a Senior
there's no reason for them to set you up. That's akin to burning money. They're putting you in a position where they need you, and if you crush it, they guessed correctly. If someone were more capable (and available) they would have had them Lead
it's your job to communicate what you need, and justify why you need it because, you can only take on so much, and your managers are there to support you. They don't know the finer details of the effort it will take, so if you determine you need backend support, they'll look for backend support
endurbro420@reddit
While I agree this doesn’t sound like a setup, I have 100% seen a company promote someone just to set them up. Dude got promoted to manager and project lead, then had to lay off people on his team, then they demoted him and put him on a pip, then fired him. All within 6 months.
chikamakaleyley@reddit
okay but, that says nothing about why the setup was required in order to fire him
i'm sure i don't know the finer details, it just sounds like a product failed and there was cuts. His team was trimmed, which messes with his output (velocity), his manager is compelled to act on it so they give him chance with a pip, which is more like writing on the wall, and he's out
aka whats with the whole charade
chikamakaleyley@reddit
cuz when you say 'had' to lay off people on his team it sounds like some outer financial situation is the first domino to fall
if it was the case where they intentionally lay them off to understaff his team - that looks like a setup to me, like just fire the damn guy LOL
FantasySymphony@reddit
I've seen the above situation happen too. Less of a "fuck you in particular" kind of thing, more that there was a project that was already failing, for example, because the previous lead massively oversold management on a promise they couldn't possibly deliver, but managed to keep the illusion going just long enough to find an offramp. So previous lead moves up or out, the poor sucker who gets brought in to fill the opening and sees the state of things is going to be feeling awfully setup.
endurbro420@reddit
I think it was somewhere between this and a full setup. The project was definitely in rough shape but everyone knew that. I really think part of it was using him as a fall guy as once the layoffs and his eventual firing happened all those roles were offshored.
chikamakaleyley@reddit
yeah this one makes more sense
supyonamesjosh@reddit
I would flee a company that did that so fast if there isn't more to the story, though there usally is.
endurbro420@reddit
I was one of the people laid off after he became my manager. Our positions were then offshored. I assume chaos ensued after that leading to his eventual firing.
igharios@reddit
Whoever put you in that position believe in you, so don't be shy to talk to them.
The tone you are using here is good, approach it with curiosity and interest of learning.
These promotions are better than nagging and getting one, or being promoted without the need. Throughout the years I built 3 rules for promotions
Does the company need the role? - if you are filling the void, that is a big YES
Can the person do the job? - likely a YES since you were picked to
Does the team support it? - anyone complaining about you doing this role? or stepping into this leadership? if NO, then that is a YES
MoistConsequence9338@reddit
What you're describing is real and it has a name — it's called a leadership vacuum, and capable people get pulled into them precisely because they're capable. The system finds its own solution and that solution is usually you.
The honest answer to your question is that it can be both things at once. A genuine growth opportunity and an under-supported mess handed to the nearest person who wouldn't drop it. Those two things aren't mutually exclusive and I think part of your discomfort comes from trying to figure out which one it is, when the answer is probably yes to both.
What I'd pay attention to is how you feel in your body after a full week of this, not just mentally but physically. Are you sleeping? Do you wake up actually rested or just less tired? Is there still something that excites you about Monday or has it started to feel like weight? Because there's a meaningful difference between stretch that builds you and stretch that slowly drains you, and your nervous system knows the difference before your brain does.
The support gap you're naming is the real issue here, not the scope, not the visibility, not even the ambiguity around your title. You're being asked to operate at a level that normally comes with scaffolding around it and that scaffolding is missing. That's not you being difficult, that's just an accurate read of the situation.
On asking for clarity without sounding like you're dodging, I'd reframe the conversation entirely. Don't ask for less responsibility, ask for explicit ownership definition. There's a big difference between "this is too much" and "I want to make sure we're aligned on what I actually own here so I can protect the outcome." One sounds like retreat, the other sounds like someone who's thinking about delivery seriously. You're not overthinking this. You're just thinking, which is apparently rarer than it should be.
heart-give@reddit
I’m going through basically the same thing. An EM role became available and they threw me into a manager role from senior. You need support. Product and staff. Otherwise you’ll be completely buried.
Gunny2862@reddit
"How did you figure out whether it was:
These are the SAME thing. Companies rarely, if ever, provide you with opportunities if it's not in their interest/solving a problem.
MoreHuman_ThanHuman@reddit
the lead thing isn't something you ever slowly roll into. you're ready or not. either way, you'll make mistakes. how you handle those mistakes will determine your future at this company.
flerchin@reddit
Impostor syndrome hitting hard. Fake it til you make it. You know how much money they'd be wasting to set you up to fail? They're taking a gamble on you, and you should take a gamble on you too.
nkondratyk93@reddit
nah, it's not a setup. this is just how tech leads get made - nobody is ready the first time. the discomfort is the point. if you were comfortable you'd probably still just be a senior.
rupayanc@reddit
it's both, and that's the part nobody tells you. every tech lead role on a visible project is simultaneously an opportunity and a test with real consequences. the skill shift that matters most isn't writing better code, it's communicating tradeoffs clearly to people two levels up who don't have your context. if you can explain why you chose approach A over B without jargon, you're already ahead of most first-time leads.
barndawe@reddit
IMO it doesn't matter if it started as a genuine growth opportunity or due to a management vacuum, you've delivered and are being recognised for it in your review. If it was a setup you'd have seen warning signs in your review etc by now.
Don't overthink it, take the W, and keep delivering like you've done
Alternative-Wafer123@reddit
If you're happy spending your time to deal with people (stakeholder, junior), you should ask for the "Lead" promotion. However, if you were the type of person who is willing to work individually while having big impact on technical side, you should ask for staff SWE. Remember the Peter principle.
smutje187@reddit
Where are you located/did you grow up in the same country? My experience with genuine European companies is that you’re expected to be much more independent and proactive even as senior whilst there’s enough stories on Reddit how a Senior in other countries is treated as an experienced developer without responsibilities.
AintNoNeedForYa@reddit
Two things can be true at the same time
LittleLordFuckleroy1@reddit
Embrace the chaos. This is where principals are forged. Push on, good sir.
telewebb@reddit
Congratulations on becoming senior / tech lead. From the sounds of it, you're doing the job well. I wouldn't worry about speed running things and missing stuff. This all sounds normal. My only advice is to do some reading around the tech lead role to help you define the boundaries of the role. You're not the engineering manager, you're not the project manager, and you're not the product owner. But for some reason, the industry has decided you are partly responsible for all those jobs. Remember to be easy on yourself. You're going to make more mistakes than you'd like, but it comes with being a new tech lead. Communicate early and often. And most importantly, write down everything with dates and where to find what was said. People have a funny way of forgetting things promised or said after things go live in prod.
And most importantly, remember to have fun. It's why we do it. Because it sure as shit ain't for the fucking non-existent pay bump for all this extra work.
Chewlies-gum@reddit
The company I work for, there is a very loose association between grade. Outside of principal engineer, we just generally don't make these distinctions. Generally when I look at something like this is you either have formal authority in reporting structure or you don't. Getting promoted in grade has little to do with hierarchy, authority, responsibility, and budgeting.
You either have people formal HC reporting to you, and budget authority along with the responsibility or you don't. You either have formal deliverables or a charter or you don't.
What is difficult is where you allow yourself to get roped into something where you have neither HC or budget, but you do have responsibility for group output.
I honestly don't know what to tell you since only you really know what's going on in your company.
In my career, I am either an IC or management, but not somewhere in the middle. I refuse to take responsibility without resourcing.
There is a point here. Ultimately, you own the course of your career, and there is a learning curve to doing it. If you are not comfortable with the situation you find yourself, this is where the hard part comes navigating the error. I think what most of us eventually learn is to avoid these traps by recognizing this laid out up front, and stating what you needing in resourcing and actual authority. This is not about your promotion. This is functionally about management, resourcing, and budgets. Don't equate the two. I would never let management trap me like this, and don't think "trap" in the perjorative.
diablo1128@reddit
I worked for a company that wanted a very flat hierarchy, so titles where you were a SWE or Lead SWE. Anyways I got roped in to being a Software Team Lead where I was responsible for all software activities on the project with 20 SWEs under me.
It all sounded great until I realized I had no budget or performances review authority and was not the one to set team priorities. They were all done by the project manager. So if I wanted to hire I had to convince the project manager why.
The project manager was not a SWE, so while I gave him input for performance reviews he really said whatever he wanted to say. I was not in those meetings and was not privy to the information relayed.
At the end of the day the role was shit and not worth the the bump in pay. I only got bailed out because one of the project managers golden child finished up a project and he wanted them to be the Software Team lead. I happily went back to being a SWE with no change in pay.
Relevant-Ordinary169@reddit
Are you guys hiring?
kylebutler07@reddit
Sounds like it's a testament to you. I can be paranoid about these things as well, and I have to remind myself that an opportunity is an opportunity, and generally you won't be given something like this if they dont think you are capable. I was brought over to a new team as a mid level and they handed me a big project right of the bat. Me and a junior did 95% of the thing. It was largely successful, and we were both promoted the next year. Do your best, and if there are obstacles, make sure to clearly express that to your manager.
That being said, seems like your company is missing a product owner in this scenario. In my opinion a good product owner makes things WAY easier, especially in this type of situation.
Last_Magazine2542@reddit
I’m in a very similar position, and have been for over a year. Just own it. Talk to your boss and just be clear about what is going on, when, and why. Talk about what other people are doing.
Not having the leadership around you might actually be a good thing, and you will naturally fill the gap. You will absolutely get recognition if that is the case.
Southern_Orange3744@reddit
Sometimes opportunity is just luck. Growth rarely comes how we want it , or expect it.
You've got a mixed bag here ,but it's the hand you've been dealt.
You're choices are to lean in and be honest with your boss about where you need help, fail quietly , or leave.
When I was a young senior I leaned into a similar experience. personally I felt like 15 years later it was one of those experience growing things that prepared me for the everything that came after.
Bricktop72@reddit
Own it and have fun.
Zhughes3@reddit
I would love to be in this position. It doesn’t even sound like you have to kiss any ass to level up and there’s no one blocking your path towards more and more seniority and leadership.
I have 8.5 years of experience. 4.5 at current (senior e4) role. Manager and I worked to get promoted to next level (E5 principal). His manager told him to downgrade my performance review.
I’m the youngest eng on my team of 3. Two other engineers are consultants with 27 and 35 years of experience, respectively.
We basically just all own our own services and review each other PRs. Definitely have learned a ton and always have been delivering but in terms of promotions - nada. I have to go out of my way to get the visibility and “VIPs” to care about the work I deliver.
notmyxbltag@reddit
Okay, few thoughts here:
> Has anyone been in this kind of situation where a stretch opportunity was also kind of a lonely / under-supported one?
Yup, multiple times. I distinctly remember a time where I messaged a more senior friend of mine and got told "man, does it always feel this _lonely_" and he basically responded "yup, you get used to it though". The first time I encountered a situation like this I totally flailed and had to do a "reset" before jumping back into a similar role 12 -> 18 months later.
I think a lot of people have this idealized notion of linear growth in their heads and sometimes it happens that way. Other times you just find yourself in next to vacuum and get carried along for the ride. This is most common when you stumble into areas of high business growth, which it sounds like you did. I also suspect that as you become more senior the loneliness just becomes... standard. Like, big decisions which would've stressed me out due to lack of support are no longer stressful, they're just... the day job.
As for getting support here a few tools in your toolkit:
Make specific asks. "I need support" is vague and hard for your manager to help with. "Here is a stack ranked list of my priorities this week. Do they make sense to you?" is much better. You'll find that "support" here is "do they actively engage with the question and help me problem solve"
Have a default course of action which you make clear. "If I don't get X estimates by Y team, we're going to do Z." This will at least give people the chance to tell you that you're doing something wrong.
Have you setup regular 1:1s with a peer mentor? I assume there's like... an overall project lead who you should be talking with regularly. If not, have you tried finding time with a lead you worked with in the past who you really like and respect?
Those are just a few things. These situations are hard, and you'll probably screw up a bunch. The good news is that if you're in a healthy environment, your screw-ups will be seen as "this person stretched and struggled; that's fine and expected when you stretch". If you're in an unhealthy environment, well then that's a whole other conversation >_<.
PolyglotTV@reddit
It almost never is
rhd_live@reddit
At my year-end review, my manager said:
\^ this is all good. Don't overthink it
Wonderful-Habit-139@reddit
I think the issue is that he did just get promoted. So he's going to have to endure an artificial year or two of working longer as a tech lead while having a senior title (and compensation).
mllv1@reddit
Yeah you’re overthinking. Just own it and have fun. Very often people see things in us we don’t see ourselves. You’re in a very fortunate situation.
Otherwise_Source_842@reddit
I was put in almost the exact same position but minus the promotion. I was put on a small discovery project of me a data engineer product and design and after the first planning a week into the team forming I was slapped with build a full prototype with actual production data for our market analysis product we were doing the discovery on. I got us to the finish line but barely for having a beta with customers using the prototype only for the project to become the big ticket item for the company and for it to no longer be an engineering project but a data one so I was removed as lead and now I’m back to IC with some senior responsibilities while they brought in a lead data engineer to be the tech lead for the project. I would say if you feel like this project is setup to fail communicate it up and engage management consistently but if you don’t get support and still believe it’ll fail then ask for a transfer and get your resume cleaned up just in case