3 ms·
+1. I had a similar crisis when I was a “big fish in a smallish company”, I wasn’t learning, I wasn’t being stretched and felt like I was going to get stuck in
by hellisothers 4y ago
+1. I had a similar crisis when I was a “big fish in a smallish company”, I wasn’t learning, I wasn’t being stretched and felt like I was going to get stuck in this eddy. Move to a bigger company, be challenged again.
- biomcgary 4y agoI mostly agree, but I don't think the company necessarily has to be bigger, just more competent and ambitious(?).
- mooreds 4y agoI agree. It depends on what you want to do. I've been challenged technically at 2 person startups and 100k person companies. Advice for OP: what companies do you admire? Either globally or locally? Have conversations with folks at that company (LinkedIn is your friend in accomplishing this) and see what people actually working at these companies think about challenges and accomplishments at their employer.
- 100011_100001 4y agoThis is an interesting idea.
- drewcoo 4y agoThe parent meant to communicate "big fish in small pond" but tossed in the word company instead of pond. Ignore that bit. Big fish in small pond still describes the need for room to grow accurately enough.
- QuercusMax 4y agoSame with me. I was the most senior dev still writing code ~every day, and there was literally no place to grow. Moved to Google and learned a ton, now I'm one of a number of big fishes in my org, and I also feel like I can potentially move on more easily if I want to.
- dosethree 4y agoIMO people who describe themselves as big fish in a small pond come off as extremely arrogant
- QuercusMax 4y agoWas just a statement of fact. 11 years at one company with only 20 engineers runs into limits of your scope pretty fast.
- lostlogin 4y agoHow about ‘largest fish in a small pond’?