511–520 of 544 posts
Earlier quoted context omitted.
> You think this is true, and might even be willing to go through the motions A good pun. The money stops being enough after a surprisingly short time. It would be interesting to see how long people could stomach terrible work for great pay.
wouldn't it have to be "go through the movements" to count as a pun on bowel movements? Or is there another sense I'm missing?
Earlier quoted context omitted.
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…
There is always a feedback cycle also I think. You can tell your manager why something could work or not. The manager is the responsible from the direction POV but it is also true that we are responsible to some extent of how we perform. Maybe not from an executive or strategic POV but yes from a deliver-what-you-are-asked for POV. What I mean, all in all, is: we all should care. That's why it is called an organizati…
Even then, expectations of what a role does vary from one org to another. I don't think it's realistic to have someone outside of an organization say "I'm a senior/staff engineer" and for that person to have consistent expectations on what that statement means from for a potential employer from one interview to the next.
> I agree with job about the job of a manager. I am just telling you that each one has her responsibility. All of us.
No disagreement there. My intended point is what appropriate expectations are at various points of a potential employees tenure at an organization. A interviewee has no responsibilities: they have no employment contract and no expectations on them other than those a hiring team or manager brings into the room. The responsibilities come after the interviewee agrees to their job responsibilities and signs an employment contract.
Earlier quoted context omitted.
> 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"
I would be thrilled to take some pretty "miserable" programming work for 7 digit compensation.
It's also not just the programming itself. I would turn down 7 digit compensation if it was going to mean intense burn out, depression and/or anxiety due to toxic management and impossible demands. The toll that shit takes on my personal life, my families lives and the way it removes my ability to even enjoy having that money for years afterwards isn't worth it.
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?
They must be leaking so many great makers arbitrarily. I assume that this helps the kind of work they do in some mysterious way?
We 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,…
Earlier quoted context omitted.
This is also why you should not agree to do coding interviews.
I feel like in the last years the level of arrogance of developers has reached a peak - somehow the market being full of opportunities, people seem to forget that there are others out there getting paid way less, doing critical things for society and going through way more stressful situations than the pain of not knowing what new shiny language to chose for your next microservice. As having a developer background th…
> how do you expect companies to hire?
At least in my case, if I have 25+ years of employment history on my resume doing the same thing that I'm interviewing for (and this can be verified), the interview process should be a lot simpler.
Earlier quoted context omitted.
Sorry but that's not how it works. $500k/year would mean roughly $250k base+bonus and $1 million of stocks vested over four years. And at most companies, the vesting starts after 1 year. So at the end of year one, you would have made $500k in base+bonus+stocks. And after that you would usually get the stocks every quarter so $62.5k worth of stocks every quarter. I am not sure where is your figure of 200-250k Total Co…
When someone says $500k/year, they usually mean a package like $150k base + $350k stocks with yearly grants. For the standard 4-year vesting schedule, and assuming a new $350k grant every year, this means actual earnings are: Year 1: $150k + $0 $150k Year 2: $150k + $87.5k $237.5k Year 3: $150k + $87.5k*2 $325k Year 4: $150k + $87.5k*3 $412k If you leave here, at year 4, and lose all unvested options (expected), your…
Earlier quoted context omitted.
When someone says $500k/year, they usually mean a package like $150k base + $350k stocks with yearly grants. For the standard 4-year vesting schedule, and assuming a new $350k grant every year, this means actual earnings are: Year 1: $150k + $0 $150k Year 2: $150k + $87.5k $237.5k Year 3: $150k + $87.5k*2 $325k Year 4: $150k + $87.5k*3 $412k If you leave here, at year 4, and lose all unvested options (expected), your…
$500K / year at year four is something entirely different than $500K / year. And that's what the OP said they were making.
Earlier 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.
500k requires you to live in San Francisco, commute to the office every day at strict hours and is at a soul crushing, bureaucratic big corp.
70k allows you to work from anywhere in the world, async an on your own schedule. Also, you get more vacation. 6k USD per month is a lot in many countries.
If you want to live now not later, I can see why you'd choose the 70k job.