π dev community,
There is often an ongoing debate about working in startups vs working in MNCs.
Most people prefer to go into MNCs like FAANG for the recognition, perks and the money.
However, there is a large number of people who prefer to work in a more fast paced environment like a startup with it is high risk and high reward.
I got a chance to intern in a startup when I was in college and since then have been part of an MNC post graduation. I like both for its perks and haven't found anything that I particularly dislike in either. π
Where do you stand on this debate?
What do you prefer and why?
What would you suggest someone to choose who is just starting out in their career? π
Top comments (9)
hmm, I have friends that did the bay area start up thing. It wasn't for me, more of a personal choice. I did contract work for them on the side, which got me enough 'start up' vibes, but no emotional attachment (just got paid and moved on).
I think the reasoning is that I don't particularly like to have a personal attachment to my professional work. With start-ups, I "feel" there is a tendency to have this personal attachment to the product...since, many times, developers have a vested financial interest in making sure the product sells. Having a personal attachment to a project doesn't equate to better code quality or professionalism. In fact, the face paced nature of startups can lead to the opposite.
For me, I prefer what you call "MNC" -> specially fin tech, though the term fintech is board and covers many things. I don't think I will ever join a start up, unless it's my startup :) I would join a start up as a contractor, but not as a employee.
I don't like companies that have overly complicated interview processes and many FAANG's are known for that. At my current experience level I can find a equally paying job without that hassle so I never go though it. I know some ppl are hooked in having "Facebook or Google" on their resume. I'm just not that kind of person.
I think a person should do what they enjoy. Start ups have a very different vibe then many MNC or other places. They shouldn't just get caught up in the hype either, joining a startup can take a huge emotional toll on a person.
Yes even I am vary of the whole DS/Algo interview process. Not only does it make many talented people not want to apply because they don't want to put themselves through preparing for such interviews, it also prevents companies from having a diverse group of talented individuals.
Also so many smart people end up getting demoralised after not clearing one of these rigorous interviews and thinking their skills are not good enough.
There has to be a bit better way of conducting interviews.
But these are the only kind of interviews I have given, the ones focused on DS/Also.. what are the kind of interviews you see happening elsewhere? Both for people with experience and those just starting out?
Unfortunately, I also go though the DS/Algo interview process too. But, its never a multi-day affair like some FAANGs. For me, I usually see 1 tech challenge (after a separate HR interview). Sometimes a take home assignment or coding challenge.
That way putting the skills to a test. Awesome!
Apologies for bombarding your answer with another question XD
I am just curious about what other skills you can focus on and showcase in an interview to get a job.
no problem!
I think if the interview is simply people just peppering the candidate with questions whom expect only answers, those are harsh.
Some interviews are more discussion type. Ie, "Lets have a discussion about Javascript closures" There is no right or wrong answers. You can showcase your communication and soft skills, yet still get across you know what a particular topic is about.
I also get asked to draw architectural designs on the whiteboard - this isn't the same as whiteboard coding questions. Drawing diagrams and presenting architectural concepts clearly is something very relevant to a senior position. As a lead, I do this all the time, so I don't really practice this myself, but explaining the design decisions of a particular system at a high level is another opportunity to impress the interviewers.
As for coding problems. I do practice some before an interview and I have a React + Springboot template app ready in case I get asked for some take home coding problem.
In very first development job interview, years ago, at a Java consulting company. I impressed my interviewers with a ad-hoc whiteboard presentation about one of my personal projects. It didn't write any code, etc. They asked me "oh, thats interesting, what was that about".... so I picked up a marker and talked about it.
This is quite insightful π
Thanks for sharing! ^^
I too was under the same delima.
Here is my two cents
Working at a startup can give you more insights at the real skill that is needed to solve real world problems. It is not only limited to coding but also exploring other solutions, efficient interactions, estimations etc.
In my opinion, in those ages of your life in which you have the minimal risk( just fresh out of college), invest time into improving skills hence work at a startup.
And when more rigidity is need of the hour, maybe goto a MNC.
Yes agreed, depends on one's situation and priorities. π―