Earlier quoted context omitted.
My "never again" story was around a decade ago. Thoughtworks had me interview with roughly a dozen people over half a dozen or more interviews, lasting ~20 hours (if you include the proctored Wunderlic test they administered to me on premises). At the end of that lengthy process, they said they would have loved to bring me on but "didn't have any open positions that fit my set of skills". You know, that set of skills…
Thoughtworks also screwed me like that. They gave me a take-home assignment which took few hours. At the end, their feedback was - my code is not cloud scalable and their were some values that I used directly and not from a configuration :-). How can those people claim to be interviewers?
Tell HN: You can't hire because you don't post salary ranges
491–500 of 544 posts
Re: Tell HN: You can't hire because you don't post salary ranges
#492Earlier quoted context omitted.
> You only get 15-30 days of vacation per year. This is why I'm glad to have "unlimited" PTO (subject to manager approval + must be requested at least the duration in advance, e.g. 2 weeks notice for 2 weeks off), along with a few annual company-wide breaks and an earned month-long break every 3 years.
So really your PTO is subject to the discretion of your manager. Unlimited sounds good, but in practice, I think it is better to have ownership of your time off. I remember like 20 years ago having unlimited sick time, which in reality just meant your manager was rated on how much sick time their team burned through.
That said, I need to take more PTO so I don't burn out...
Re: Tell HN: You can't hire because you don't post salary ranges
#493Earlier quoted context omitted.
OK, but... some places think a "senior software developer" should make $70,000, and other think they should make $250,000 or more. And everything in between. I don't care how nice the a place it is to work, I'm not applying to the $70k place. If I can't quickly figure out where you fall on that spectrum, I'm not going to bother to contact you because job listings are not rare . If you somehow manage to present as exa…
Honestly I'm considering the $70k place where as right now I have the $500k total comp. I can't say I hate my job but I have zero interest in it. Where as I had lots of The biggest reason I haven't pulled the trigger is there's no guarntee that taking the $70k will actually be fun this time. I have my criteria for taking the jump though and if they're met I'd do it in a heartbeat.
Re: Tell HN: You can't hire because you don't post salary ranges
#494Earlier quoted context omitted.
It’s famously administered to all nfl quarterbacks. Tom Brady got a 33.
All NFL players, not just quarterbacks, right?
Apparently Frank Gore had one of the all time lowest scores with a 6. He is a borderline Hall of Fame caliber running back.
Re: Tell HN: You can't hire because you don't post salary ranges
#495We just went through a large hiring cycle. We posted two versions for every job posting- one with salary ranges and one without. The ads performed equally well in regard to total responses with the better candidates responding to the ones without salary ranges. And... before you say, perhaps your salary ranges were bad, they weren't. Our salary offerings are very aggressive to the developer's benefit. In my opinion,…
Re: Tell HN: You can't hire because you don't post salary ranges
#496Earlier quoted context omitted.
You never have the thought, "I'm not being payed enough for this shit?" Or, realized new hires with less experience are being payed more? Or that colleagues that are slacking are being payed the same or more? All these feel like concerns related to pay while working. I've certainly had those thoughts and was genuinely underplayed for half my career
> You never have the thought, "I'm not being payed enough for this shit?" More like "no amount of money is enough to make me happy doing this shit"
Re: Tell HN: You can't hire because you don't post salary ranges
#497Earlier quoted context omitted.
This is a difficult topic. We evolved to the 40h/week mentality. This is a big luck for us. I think things should be more based on goals than on time itself, honestly. What I mean is: if you work 40h but you do not deliver anything, how is that good compared to someone that in 32 delivers more? We have to put ourselves on the side of the employer also, even if some people hate them.
This is a management problem, not an employee problem. Figuring out if I can be outperformed by someone working less hours than me is irrelevant to my relationship to my employer. I'd go further to say that it's irrelevant barring frequency of the event having an impact on the broader job market. For any team, you will have a range of performance. For any individual, you will have different work styles. This is norma…
What I mean, all in all, is: we all should care. That's why it is called an organization.
I agree with job about the job of a manager. I am just telling you that each one has her responsibility. All of us.
Re: Tell HN: You can't hire because you don't post salary ranges
#498Earlier quoted context omitted.
OK, but... some places think a "senior software developer" should make $70,000, and other think they should make $250,000 or more. And everything in between. I don't care how nice the a place it is to work, I'm not applying to the $70k place. If I can't quickly figure out where you fall on that spectrum, I'm not going to bother to contact you because job listings are not rare . If you somehow manage to present as exa…
Honestly I'm considering the $70k place where as right now I have the $500k total comp. I can't say I hate my job but I have zero interest in it. Where as I had lots of The biggest reason I haven't pulled the trigger is there's no guarntee that taking the $70k will actually be fun this time. I have my criteria for taking the jump though and if they're met I'd do it in a heartbeat.
Re: Tell HN: You can't hire because you don't post salary ranges
#499Re: Tell HN: You can't hire because you don't post salary ranges
#500Earlier quoted context omitted.
This isn't how salaried position work though, not in the US anyways. You will get paid X if you work 10 hours a week or X if you work 50 hours a week. There is no difference in pay. Would you be open to losing pay? Do you want to be accountable for every single hour of work you do? Most don't.
I'm not in the US, but I work for a US based company. My contract specifically says I work 40h/week, have X days off/year (outside of statutory holidays) as PTO, etc. This means that 5 days a week, I am at my keyboard, available on Slack, etc for 8 hours per day. Hours are logged in a time tracking application (including time spent when there was nothing to do), and overages get added automatically to holiday time.