I have to say that I can't disagree with this more. I've been a developer for around 25 years (16 as a web developer), and have worked at many different sizes of company at different points in their growth. I've found that by far the best places to work are the small places, ideally with a product or project that is in its early stages.
If you join a company where the product already has a lot of users, then it's extremely likely that the project is already fairly mature and all that you will be mostly doing is effectively just tending someone else's baby to keep it happy and healthy. There will be little opportunity to be truly creative, have a real say in the direction of the product, feel truly invested in the project etc. It can ultimately become soul destroying.
Sure, it's nice to be associated with a large, very successful product - but it feels way better to know you played or are playing a key role in the creation of something, rather than just knowing about / dealing with a small part of a larger system and just being a cog in a machine. Looks better on your CV too. If the interviewer is doing their job properly, name-dropping should mean very little indeed.
At a small place you can feel much more a part of something, with a real chance to show what you can do and actually feel like you're making a difference... it's infinitely more rewarding, and makes your job feel like something you actually want to do - rather than just something to pay the bills, and use as a stepping stone to the next salary bracket.
I have to say that I can't disagree with this more. I've been a developer for around 25 years (16 as a web developer), and have worked at many different sizes of company at different points in their growth. I've found that by far the best places to work are the small places, ideally with a product or project that is in its early stages.
If you join a company where the product already has a lot of users, then it's extremely likely that the project is already fairly mature and all that you will be mostly doing is effectively just tending someone else's baby to keep it happy and healthy. There will be little opportunity to be truly creative, have a real say in the direction of the product, feel truly invested in the project etc. It can ultimately become soul destroying.
Sure, it's nice to be associated with a large, very successful product - but it feels way better to know you played or are playing a key role in the creation of something, rather than just knowing about / dealing with a small part of a larger system and just being a cog in a machine. Looks better on your CV too. If the interviewer is doing their job properly, name-dropping should mean very little indeed.
At a small place you can feel much more a part of something, with a real chance to show what you can do and actually feel like you're making a difference... it's infinitely more rewarding, and makes your job feel like something you actually want to do - rather than just something to pay the bills, and use as a stepping stone to the next salary bracket.
Just my two pence...
Thanks for sharing Jon!
Really appreciate your input and agree with you.
My point of view isnt dogmatic, I was just sharing something that helped my career trajectory and hopefully someone finds value in it.
I agree, you should be apart of something you're passionate about.
Thats always the goal. But through a high user base comes impact (given the size of the company/seniority etc)
again thanks for reading and sharing :)