Live data from Hacker News

No management needed: anti-patterns in early-stage engineering teams

ablg.io

11–20 of 361 posts

Re: No management needed: anti-patterns in early-stage engineering teams

#11

I'd like to add to this, only because it is an early stage item but maybe a little unrelated: If you are an early stage startup and your founders have a habit of talking about "competitors", run like hell.

> If you are an early stage startup and your founders have a habit of talking about "competitors", run like hell. Why? Comparing what the competitors are doing can be a great way to come up with new ideas

[deleted]

Re: No management needed: anti-patterns in early-stage engineering teams

#12

When I read about 996-style culture I am happy to be European. That would not work here. 40 hours per week max and most engineers prefer to not work more than 32 hours a week. So you have a good work/life balance. I currently work 4 hours a week.

You don't have to work at an early stage startup - in fact most people don't. But some people do wish to participate in an early stage startup, and plenty do in Europe as well.

> So you have a good work/life balance. I currently work 4 hours a week.

And this is why when I was a PM, we shut down our Amsterdam office and shifted it to Praha, Bucharest, and Warsaw. You won't find as many people who will complain about a 40 hour workweek while earning €80k TCs

Re: No management needed: anti-patterns in early-stage engineering teams

#13
I wonder how universal these stages are. All I can say is when I worked at a 15 person company, it was extremely clear to me that we needed more structure than "everyone reports to the CEO". We struggled to prioritize between different projects, milestones weren't clearly defined or owned, at times there would be long debates on product direction without a clear decisionmaker, etc etc.

Not to say the article is so wrong. I think their advice to consider elevating a few engineers into informal tech leads is a great answer. We went with the path of hiring one dedicated "manager" of all engineers and that worked pretty well too.

Re: No management needed: anti-patterns in early-stage engineering teams

#14
post #13

I wonder how universal these stages are. All I can say is when I worked at a 15 person company, it was extremely clear to me that we needed more structure than "everyone reports to the CEO". We struggled to prioritize between different projects, milestones weren't clearly defined or owned, at times there would be long debates on product direction without a clear decisionmaker, etc etc. Not to say the article is so wr…

Depends team to team and founder to founder. I've seen early stage startups where most ICs were able to self manage, but others where some form of structure was needed. At the stage that you mentioned, it's natural for founders to end up hiring an Engineering Lead.

> consider elevating a few engineers into informal tech leads

It is potentially risky - I've seen plenty of talented engineers flounder because they were thrust into an ill-suited management role too soon, but I think if someone is motivated and eased into the role they tend to be superior to an outside hire.

Re: No management needed: anti-patterns in early-stage engineering teams

#16

lol. "don't motivate engineers." dude can't motivate engineers with money so he thinks you can't motivate engineers. that's actually funny. and a little depressing.

why don't you criticize the arguments his making instead of the person, he is basically saying hire people with autonomy not people who need motivation.

Re: No management needed: anti-patterns in early-stage engineering teams

#17

When I read about 996-style culture I am happy to be European. That would not work here. 40 hours per week max and most engineers prefer to not work more than 32 hours a week. So you have a good work/life balance. I currently work 4 hours a week.

You don't have to work at an early stage startup - in fact most people don't. But some people do wish to participate in an early stage startup, and plenty do in Europe as well. > So you have a good work/life balance. I currently work 4 hours a week. And this is why when I was a PM, we shut down our Amsterdam office and shifted it to Praha, Bucharest, and Warsaw. You won't find as many people who will complain about a…

Working more hours however =/= getting more done. In fact, some experiments show the opposite (within boundaries of course).

Re: No management needed: anti-patterns in early-stage engineering teams

#19

When I read about 996-style culture I am happy to be European. That would not work here. 40 hours per week max and most engineers prefer to not work more than 32 hours a week. So you have a good work/life balance. I currently work 4 hours a week.

Which is why fewer and fewer companies are hiring in Europe.

Re: No management needed: anti-patterns in early-stage engineering teams

#20

Earlier quoted context omitted.

You don't have to work at an early stage startup - in fact most people don't. But some people do wish to participate in an early stage startup, and plenty do in Europe as well. > So you have a good work/life balance. I currently work 4 hours a week. And this is why when I was a PM, we shut down our Amsterdam office and shifted it to Praha, Bucharest, and Warsaw. You won't find as many people who will complain about a…

Working more hours however =/= getting more done. In fact, some experiments show the opposite (within boundaries of course).

I agree, but the issue is the impetus behind the statement. The tone which that poster took and the default negative assumption is a negative trait to most hiring managers - especially at the early stage. At an early stage organization, you want your employees to be self-motivated but also open to pull crunchtime if needed (eg. customer escalation, rolled up product launch, pivot)
Post reply on HN