I think it's certainly incorrect (having known lots of people on both sides of that number, there are far far more below). Another comment thread suggested that startup equity is being taken at face value, which might justify the number but is totally ridiculous
Sentry.io (http://sentry.io) | Senior Software Engineer, Storage | ONSITE (San Francisco or Seattle, 3:2) | Full-time
Sentry.io builds a suite of application monitoring tools that developers love. The Search and Storage team builds out high-volume ingestion (hundreds of thousands of records per second) for our near-real-time event and metric storage built on top of the columnar data store ClickHouse. We’re looking for a seasoned engineer who has dealt with high-volume, production-traffic serving systems who’s searching for a new challenge.
The vast majority of our work is source-available; come take a look at what our team is working on at https://github.com/getsentry/snuba. Note that this position does have an on-call component.
If you have the budget, hire a personal trainer for 1-2 hours/week. It's not cheap, but having to make the appointment or lose the money you spent is a huge motivator. They'll probably work you harder than you would work alone as well as enforce good form. I got started lifting weights this way.
Then you'll be motivated to work out on your own to save money.
Not an employee, but I'm pretty sure that the interview is the same for all engineering roles, unless you're very senior/specialized. I doubt that your interviewers will even know that you're up for a ML position specifically.
I think the point the parent was trying to make is that responding to a recruiter isn't likely to get you ANY job, because they don't understand the job reqs they're recruiting for nor the people they're trying to place.
If you work as an engineer in the US you're probably an "exempt" employee by status, meaning that your employer doesn't have to compensate you for extra time. If you're sufficiently underpaid as an engineer that you're non-exempt, then you should be paid 1.5x for any time beyond 9-5/40 hours, or you should get to trade in those unscheduled hours to work less on following days.
EDIT:
Realized I didn't address the question of whether it is "standard". I've heard that DevOps engineers have a bit of a compensation consideration (maybe $10-20k/year in the Bay Area where I live) for the on-call nature of their jobs, but I am sure that they are mostly paid enough to be exempt employees. This is totally anecdotal/second-hand and it would not surprise me if their pay is at parity or even worse than other software engineers.
I happen to be an acquaintance of Rachel Myers, and while she does do not-for-profit stuff outside of work, do you have some evidence that she's a "social impact employee" there? It's not obvious on her Twitter/Github profiles.
I don't want to assume any motive to your comment, but I think it would be a cause for concern if the world at large assumes that women/minorities are hired strictly for their "social impact".
This is the Columbia Journalism Review. It's not saying science is stupid, it's saying that reporters are too quick to publish study results, when not enough research has been done on the subject topic.
Very often state machines are the best representation for domain objects which have a life cycle. If you have a lot of user submitted content shared among other users, a common set of states could be:
You probably won't handle every HTTP edge case as well as nginx defaults, and you don't really need the control at that level to implement a functional, high performance web app.