Live data from Hacker News

Reasons to Turn Down That Startup Job

deardesignstudent.com

11–20 of 48 posts

Re: Reasons to Turn Down That Startup Job

#11

This should really be "8 reasons to turn down that startup job as your first job" as most of the bullet points are really only geared towards someone in or leaving college. This should be obvious from the website's name but without context it took me a minute before I realized. That being said the #7 point of "The world needs fixing, not disrupting" seems to lose sight of what disruption really is and conflates it wi…

Thing is, #7 doesn't apply because he's referring to Amazon, and they are far, far away from startup territory. Sure, there are actual startups that have work/life balance issues that are as toxic (or more) as Amazon's, so I suppose it applies to them.

I liked his other reasons, though.

Re: Reasons to Turn Down That Startup Job

#12
While I agree with some of the author's points, such as considering your tolerance/appetite for working within a chaotic environment before joining a startup, the article seems less about deciding whether to take a startup job and more about why one should choose to work at an agency instead of in-house for their first role.

>4. You need to be going wider than deep right now.

The author's argument is roughly that working a at a startup is limiting because you will work only a single problem because a startup is focused on solving only a single problem.

I disagree.

1. A company that seeks to solve a single problem is a company that has focus; I would argue that many startups lack focus. Many startups do not know the specific problem that they are solving nor for whom. Much time is spent on product/market fit. So, I disagree with the premise that startups are solving for a single problem. Successful ones do, yes, and that brings me to (2).

2. The idea that you will work more broadly at a successful, time-tested company than you would at a startup does not seem accurate. Startups are known for allowing people to wear many hats for a reason (because they often require people to wear many hats). For individual contributors, roles at a Fortune 50 company will be far more specialized – and opportunities to join projects even slightly outside your domain of expertise will be far less prevalent.

This is why I think the argument is really about in-house vs. agency work. Agency work will teach you their methods and provide you with exposure to a range of clients and industries, sure.

3. The premise that because your startup is focused on solving a single problem, you will not get to work on a variety of problems or get to 'try different things' makes me scratch my head... If only solving a problem were that simple, that efficient!

Re: Reasons to Turn Down That Startup Job

#13
At a startup you'll have way more responsibility and be making decisions at a much higher level than at bigcorp. You'll learn way more, move much faster, wear more hats. It's not even close. That mentor will put you on some narrow meaningless tasks, especially if you have some talent because then he'll be afraid of you. I'd advise the opposite, go startup when you're young and have less to risk and more to prove. If you have the energy and the talent you can run circles around the big guys.

Re: Reasons to Turn Down That Startup Job

#14
I don't know, because I'm an engineer, but what I learned from Apple, was not the work I was doing, but it was from being surrounded by such brilliance. I would go to lunch (or dinner) with the guy who wrote the javascript engine. Or pop into the office, during a beer bash, of the engineer who wrote the original UIScrollView and pick his brain about why they did things a certain way.

The actual day to day work though, was pretty routine. I was mostly fixing bugs and rebuilding parts of features that had to ship in yearly timelines. Every project I worked on that wasn't canceled was spent in refactor mode for a good portion of the year. Let's rewrite this for 64-bit for example, or let's rework this for this new framework. The actual customer should never notice a change in the product, and usually the visual changes are subtle if any. Lucky few got to work on the shiny demo-able new features and even fewer lucky folks got to lead teams from their new products.

Lastly, most of the tooling that I got really good at and used to great advantage was proprietary except for Xcode and Instruments. :(

So leaving to go to a startup I literally had to learn a whole new set of tools and APIs. Then again, I learned so much more about how to build a product from the ground up at a small 11 person startup than I ever did at Apple.

At a company like Apple, I gained skills adding a feature to an existing product. At a startup, I gained skills building a product from nothing but an idea.

Re: Reasons to Turn Down That Startup Job

#15

This should really be "8 reasons to turn down that startup job as your first job" as most of the bullet points are really only geared towards someone in or leaving college. This should be obvious from the website's name but without context it took me a minute before I realized. That being said the #7 point of "The world needs fixing, not disrupting" seems to lose sight of what disruption really is and conflates it wi…

Honest question: have you ever worked a job in that service economy and fallen seriously ill? Things turn in to a shitshow really quickly when six-figure bills start raining in from oncology, your for-profit insurer starts denying claims after you've cleared the massive $5,000 deductible and $6,250 out-of-pocket maximum, you're technically "self-employed" and have no access to employee protections like paid sick time or FMLA, every bad health day you have is another couple hundred dollars foregone that could have gone to medical bills, and then the IRS piles on with self-employment tax to add insult to (literal) injury.

Disruption in the US health care system would be great; until that happens, my excitement over having cat litter delivered to my door in an hour or less will, sadly, be dampened by the fact that some Americans are literally doing their own minor surgeries over a bathroom sink right now. Wart removal is a really common one, presumably because it routinely bills out $250-$350 per visit in larger practices, and the typical visit count is high.

Re: Reasons to Turn Down That Startup Job

#16

I don't know, because I'm an engineer, but what I learned from Apple, was not the work I was doing, but it was from being surrounded by such brilliance. I would go to lunch (or dinner) with the guy who wrote the javascript engine. Or pop into the office, during a beer bash, of the engineer who wrote the original UIScrollView and pick his brain about why they did things a certain way. The actual day to day work though…

At a company like Apple, I gained skills adding a feature to an existing product. At a startup, I gained skills building a product from nothing but an idea.

Being able to take an idea and turn it in to a product is a brilliant skill that startups absolutely need, but equally, once the product is out there being used, you need the other skill set to maintain the product and add new things without annoying the users. Having people around who can do both is exceptionally useful because it means the team continues to do productive work for much longer without having to bring new people in.

To that end, I always recommend people get at least a few years experience at an established company before joining a startup.

Re: Reasons to Turn Down That Startup Job

#17
I hate to tell you this, but right now the startup world, or at least the ones making the majority of the noise, have their heads up their own ass and don’t realize it stinks. They’re solving problems for the top 5% of the population. How can I get poor people to do my chores? How can I get people to drive me around without having to pay them health insurance? How can a drone deliver my toilet paper within 15 minutes while the person who fulfilled my order sits at her desk crying because she’s working a 15-hour day and can’t take time off to get that lump in her chest looked at. This is known as the service economy. Where entitled white boys figure out how to replicate their private school dorm experience for life.

------

so. fucking. real.

Re: Reasons to Turn Down That Startup Job

#18

While I agree with some of the author's points, such as considering your tolerance/appetite for working within a chaotic environment before joining a startup, the article seems less about deciding whether to take a startup job and more about why one should choose to work at an agency instead of in-house for their first role. >4. You need to be going wider than deep right now. The author's argument is roughly that wor…

I think your criticisms of the explanation given are valid, but there is something to be said for breath vs depth.

Programing and design are both hard in their own way, but fundamentally they are a skill you can hone. Once you have mastered those skills the rest of it becomes understanding your companies domain.

As an example from a programers perspective it is fair to say that every system that deals with money interfaces with accounting. I have been in enough places and exposed to enough systems, that I understand that these things will need to happen, and how they need to happen. I also understand how to speak with the accountants to make sure the data they are getting is what they wanted or expected. It was only by seeing this repeatedly that the patterns and language became clear to me.

I think it takes time to become a proficient coder in a professional setting, as well as understanding the language and needs that are common to almost every business. If your busy learning how to do your job, and how to deal with the person in accounting, and trying to focus on your startups domain it might get a bit overwhelming.

Re: Reasons to Turn Down That Startup Job

#19
post #16

I don't know, because I'm an engineer, but what I learned from Apple, was not the work I was doing, but it was from being surrounded by such brilliance. I would go to lunch (or dinner) with the guy who wrote the javascript engine. Or pop into the office, during a beer bash, of the engineer who wrote the original UIScrollView and pick his brain about why they did things a certain way. The actual day to day work though…

At a company like Apple, I gained skills adding a feature to an existing product. At a startup, I gained skills building a product from nothing but an idea. Being able to take an idea and turn it in to a product is a brilliant skill that startups absolutely need, but equally, once the product is out there being used, you need the other skill set to maintain the product and add new things without annoying the users. H…

> Being able to take an idea and turn it in to a product is a brilliant skill that startups absolutely need, but equally, once the product is out there being used, you need the other skill set to maintain the product and add new things without annoying the users.

But guess who gets the glory? :(

Re: Reasons to Turn Down That Startup Job

#20
From the article: "I hate to tell you this, but right now the startup world, or at least the ones making the majority of the noise, have their heads up their own ass and don’t realize it stinks. They’re solving problems for the top 5% of the population. How can I get poor people to do my chores? How can I get people to drive me around without having to pay them health insurance? How can a drone deliver my toilet paper within 15 minutes while the person who fulfilled my order sits at her desk crying because she’s working a 15-hour day and can’t take time off to get that lump in her chest looked at. This is known as the service economy. Where entitled white boys figure out how to replicate their private school dorm experience for life."

YCombinator company list: http://yclist.com/

How many of those fit the above criteria?

Post reply on HN