Live data from Hacker News

Exercises to craft an employer brand that makes engineers want to work for you

blog.interviewing.io

11–20 of 62 posts

Re: Exercises to craft an employer brand that makes engineers want to work for you

#11
post #6

Honestly, I just want to work for a company that is honest, it does not have to be the most exciting work, as long as hours are flexible and at least some remote work is offered. I'm tired of recruiters try to hype up the company. If employer said, "Our product is not exciting but we offer great benefits, you just have to put in 30-35 hours a week, come to few meetings and meet reasonable deadlines that we agreed upo…

Im sorry but 30 to 35 hours a week, especially at a startup is just not tenable for any company except a small lifestyle company Also i have to laugh at the fact that you "just" want to work at a company thats honest and then you throw in the 30 to 35 hour work week requirement

It's quite a bit more tenable when you admit to yourself that anyone who is nominally putting in 60-hour weeks as a knowledge worker is only actually working for 35 of those hours anyway. Studies show reduced productivity after that point, so you're just going to burn out engineers, and all you'll have to show for it is a butt in a seat.

Re: Exercises to craft an employer brand that makes engineers want to work for you

#12
post #5

1) Remote. 2) Money. 3) Demonstrate that you have half a clue how to run a project. 4) BONUS ROUND: No hours-long puzzle-question-memorization interview bullshit if you're not paying FAANG money and providing FAANG levels of résumé prestige.

Does F still have resume prestige? I predicted more than 10 years ago that someday having worked at Facebook would be the resume stain that you wear for life. Has it not yet come to pass that having worked at Facebook is a red flag? Sure, you are probably smart. But anybody that lists Facebook on their resume is going to find a lot of their interview time with me going to probing their ethics.

Re: Exercises to craft an employer brand that makes engineers want to work for you

#13

Earlier quoted context omitted.

Im sorry but 30 to 35 hours a week, especially at a startup is just not tenable for any company except a small lifestyle company Also i have to laugh at the fact that you "just" want to work at a company thats honest and then you throw in the 30 to 35 hour work week requirement

It's quite a bit more tenable when you admit to yourself that anyone who is nominally putting in 60-hour weeks as a knowledge worker is only actually working for 35 of those hours anyway. Studies show reduced productivity after that point, so you're just going to burn out engineers, and all you'll have to show for it is a butt in a seat.

You go from 30 to 35 straight to 60 when im thinking 40 hours a week. I dont know about you all but if i work 5 to 10 fewer hours a week i would get a lot less done

Re: Exercises to craft an employer brand that makes engineers want to work for you

#14
post #6

Honestly, I just want to work for a company that is honest, it does not have to be the most exciting work, as long as hours are flexible and at least some remote work is offered. I'm tired of recruiters try to hype up the company. If employer said, "Our product is not exciting but we offer great benefits, you just have to put in 30-35 hours a week, come to few meetings and meet reasonable deadlines that we agreed upo…

Im sorry but 30 to 35 hours a week, especially at a startup is just not tenable for any company except a small lifestyle company Also i have to laugh at the fact that you "just" want to work at a company thats honest and then you throw in the 30 to 35 hour work week requirement

> Im sorry but 30 to 35 hours a week, especially at a startup is just not tenable for any company except a small lifestyle company

You're right, its still too much. If you want the best engineers to do their best work, I'd put 30 hours as the upper limit.

Re: Exercises to craft an employer brand that makes engineers want to work for you

#15

Earlier quoted context omitted.

It's quite a bit more tenable when you admit to yourself that anyone who is nominally putting in 60-hour weeks as a knowledge worker is only actually working for 35 of those hours anyway. Studies show reduced productivity after that point, so you're just going to burn out engineers, and all you'll have to show for it is a butt in a seat.

You go from 30 to 35 straight to 60 when im thinking 40 hours a week. I dont know about you all but if i work 5 to 10 fewer hours a week i would get a lot less done

[deleted]

Re: Exercises to craft an employer brand that makes engineers want to work for you

#16

Earlier quoted context omitted.

Im sorry but 30 to 35 hours a week, especially at a startup is just not tenable for any company except a small lifestyle company Also i have to laugh at the fact that you "just" want to work at a company thats honest and then you throw in the 30 to 35 hour work week requirement

I work at an enterprise less than 40 hours a week. I hear from recruiters 3-4 times a week. I don't care about your mission or your culture, just pay me, I do the work, and then go home. If someone is of the opinion these sorts of orgs don't exist, I put forth that they might not have looked hard enough, and would encourage further exploration to better understand the employment landscape. If you're a startup and exp…

No not under market rate, if your goal is to work 30 to 35 hours a week under market rate all power to you but if you expect to be getting paid $400k total compensation or more you better be giving me at least 40 hours of work that i expect from a senior engineer. 5 to 10 hours is a full day of work.

Re: Exercises to craft an employer brand that makes engineers want to work for you

#17
post #5

1) Remote. 2) Money. 3) Demonstrate that you have half a clue how to run a project. 4) BONUS ROUND: No hours-long puzzle-question-memorization interview bullshit if you're not paying FAANG money and providing FAANG levels of résumé prestige.

Does F still have resume prestige? I predicted more than 10 years ago that someday having worked at Facebook would be the resume stain that you wear for life. Has it not yet come to pass that having worked at Facebook is a red flag? Sure, you are probably smart. But anybody that lists Facebook on their resume is going to find a lot of their interview time with me going to probing their ethics.

Big tech companies still use very valuable process, usually high amounts of tech (some in house but there is a lot to learn from even that).

The prestige is that they are hard to get into so if you made it you passed their bar and you probably had some impact there and learned good process that you can bring to a usually less disciplined startup.

Re: Exercises to craft an employer brand that makes engineers want to work for you

#18

Earlier quoted context omitted.

It's quite a bit more tenable when you admit to yourself that anyone who is nominally putting in 60-hour weeks as a knowledge worker is only actually working for 35 of those hours anyway. Studies show reduced productivity after that point, so you're just going to burn out engineers, and all you'll have to show for it is a butt in a seat.

You go from 30 to 35 straight to 60 when im thinking 40 hours a week. I dont know about you all but if i work 5 to 10 fewer hours a week i would get a lot less done

I find that my productivity, when I am specifically constrained to 30 or 35 hours a week, doesn't really change--because it puts a clear value on my time to other people.

Or, put more simply: I end up in way fewer meetings.

Re: Exercises to craft an employer brand that makes engineers want to work for you

#19

Earlier quoted context omitted.

I work at an enterprise less than 40 hours a week. I hear from recruiters 3-4 times a week. I don't care about your mission or your culture, just pay me, I do the work, and then go home. If someone is of the opinion these sorts of orgs don't exist, I put forth that they might not have looked hard enough, and would encourage further exploration to better understand the employment landscape. If you're a startup and exp…

No not under market rate, if your goal is to work 30 to 35 hours a week under market rate all power to you but if you expect to be getting paid $400k total compensation or more you better be giving me at least 40 hours of work that i expect from a senior engineer. 5 to 10 hours is a full day of work.

[deleted]

Re: Exercises to craft an employer brand that makes engineers want to work for you

#20

Earlier quoted context omitted.

It's quite a bit more tenable when you admit to yourself that anyone who is nominally putting in 60-hour weeks as a knowledge worker is only actually working for 35 of those hours anyway. Studies show reduced productivity after that point, so you're just going to burn out engineers, and all you'll have to show for it is a butt in a seat.

You go from 30 to 35 straight to 60 when im thinking 40 hours a week. I dont know about you all but if i work 5 to 10 fewer hours a week i would get a lot less done

Have you tried it? I am definitely tired and have generally hit a wall after about 6 hours or so. If I call it and stop, I’m fresh for the next day.

If I instead stay at my desk consistently, my week is over by Friday morning.

Post reply on HN