Related Posts
Following open position in Siemens Pune location:
1)C# .NET 3-5 YOE
2)Nodejs Developer(2-4 Years)
3)Azure DevOps Lead (Infra) 7-9 years
4)Software Developer Engineer(C#.Net) 3-5 Years
5)Java Backend Developer (2-4 Years)
6)C# Developer(2 to 5 Years)
7)Software Developer Engineer-Java 3-6 years
8)Angular Full stack Developer(2-5 Years)
9)UI Software Architect 10+years
10)Cybersecurity Professional 4-5 years & 7+
11) DevOps Engineer 2-5 years
12)Mobile App Developer 3-6 years
Who’s on their way to FAT FIRE?
New to Fishbowl?
unlock all discussions on Fishbowl.




I think most firms make you partner just before you are really ready, so give it time. If you were already doing all the other things and not a partner, you’d be gone.
It’s frightening at the beginning and overwhelming. In time one looks back and realizes that it was daunting but not insurmountable - you’ll learn the ropes with time and it’s part of the process.
First off, congratulations. It might seem that way at first but it does give you credibility in the market and help you develop your own book. It took me several years but able to make the jump to EP
I feel the same way two years in as a junior partner at a one-tier shop (mostly because I am super slow this week). I think everyone struggles for a while but when I take a step back, it seems more like imposter syndrome than a real desire to go back to counsel.
What’s the other stuff you’re talking about?
I would suggest giving it a go for 1 year and then re-evaluate whether you still feel the same. (I suspect you’ll grow into the job. )
We've had partners (I think choose to) move to a counsel position because they only want to bill, but even then, it took several years for them to make that move. I've also seen many partners just stick around as NEP and ignore the BD aspects. In short, agree with others to give it more time and allow yourself to mold your practice into what works for you and deal with title when it comes up.