Source: A 40-year old who has no interest in marriage and only saw it as an "antiquated social construct" when I was younger. I learned there's more to it.
74 karma · joined October 4, 2021
Source: A 40-year old who has no interest in marriage and only saw it as an "antiquated social construct" when I was younger. I learned there's more to it.
The transparency is great and is clearly a value-add for candidates, IMO.
But the salary simply does not compete with HCOL Startup Senior+ Engineers (around 20- 40% lower than Staff level).
That said, Oxide is in a unique class of startups that can still hire strong talent despite this pay deficit (whether due to an exceptional product, team, technical challenge, or other rare attribute). I know a Software Engineer who just took a 25% pay cut to join a construction analytics SaaS startup because he has heard his brother (a Surveyor) complain specifically about problems this company's solving!
I'm just an HN user who was browsing jobs, found this one that listed the exact salary (with this link to their philosophy) - I had never seen this approach before and wanted to hear what HN felt about it.
Staff-level or higher starts at around $230K and occasionally reaches $275K.
The salary data comes from researching roughly 250 Bay Area startups. I'm personally defining startups as some combination of: Series A - D, founded post-2015, less than 100 Engineers.
>You're somewhat stuck anyway for companies that don't post jobs.
Good news on this front. I have manually compiled a limited tech stack DB for roughly 5,000 US startups over the last decade (limited because it only has Frontend and Backend languages/frameworks for each company). Much of this data is current too, thanks to the 2021 boom in jobs. And the majority of startups either share their technologies in job descriptions by simply listing them or alluding to them, with fun statements like "we welcome skills in Python, Ruby, or JavaScript/Node.js (but Ruby would be ideal)." It's big tech companies that are more likely to be vague, because you could end up being hired into one of a multitude of product groups using different technologies.
On a side note: the second Ruby example is one reason scraping will be insufficient, and why language-specific job seekers pull their hair out using most job boards. If you search for Python positions, that Ruby company will pop up because it has the word Python.
If this was a viable idea, then I'd really need to get deeper into the stack (i.e. "preferred" experience with technologies like AWS, RabbitMQ, Spark, etc). This is crucial, allowing a hiring manager or recruiter not just the data to hit the basic requirements in candidate sourcing, but exceed them by delivering those "pluses." But I digress. Perhaps I would wait to see if this idea even has legs before committing to the time investment of digging for these "secondary" technologies.
It's limited to cloud providers, as you mentioned, and just a few other tools (only one or two being tangentially related to the tech stack data needed for the idea presented it my post).
It's a bummer, because I would like this product to already exist!
How do you use this to find a company's tech stack?
Do you have experience working with these products and seeing its capabilities in finding the technologies companies are using?
Thanks.
Question: how would tech sales people use it? I'm not familiar enough with the field to know their use case.
Yes, keeping it updated is a hard job, but it needs to be done regularly.
Can you elaborate on the sense of proportion problem?
And as far as enough companies, can you give me an example of a specific search you might conduct and how many results you'd expect?
Thanks!
I think a job board like startup.jobs would solve this by creating a job archive - then it would be prime scraping material. But it's only a job board with (mainly) current jobs.
Thoughts?
You're super fortunate in that you at least have those short-term "best programmer" phases (especially in an industry with high pay and high demand for your skills).
My advice: use your ability to make yourself indispensable. Then you can lay out the terms and call the shots.
I use excuses for my long term absences because the stigma of my severe mental illness is too high. But if you perform well and deliver as promised, it doesn't even have to come up...
As far as explaining away the need for long absences, I personally keep it simple and vague, and Positive: that experience has taught you that you're happiest and most productive working on this bizarre schedule. It can even create a little "eccentric genius" aura and the illusion of confidence. Just be careful not to take this too far and enter jerk territory. They're still going out of their way for you, so gratitude & humility are important.
I'm very sorry to hear what you're going through. I understand it and it's incredibly difficult, but really admire that you're looking for ways to fight and work throughout it.
Psychotherapy requires a relationship; relationships are built on trust. The psychologist simply cannot complete against the will of the patient's reality (their untreated persona/thoughts). Not even their loved ones can, and doctors are complete strangers (and when it comes to those whose symptoms include paranoia, doctors are in fact the enemy). It's a fool's errand until an effective medication regimen is underway.
For example; yes, Rails or Django is common to rapidly whip things up at an early-stage startup.
Data Science and ML companies will lean towards Python because it's the main building block of their product. No hard and fast rules, of course; you'll often see Scala at these companies too, given it's relationship with Spark.
Anyways, I'm always trying to understand and seek out the answers to the exact questions you have.
When I was finally able to get past that noise and create a decent-sized list, Omicron hit and remote/office/hybrid policies blew up, yet again.
While it has improved, it's still in flux and I still can't get straight answers from many HR leaders.
I would love to provide this service when things stabilize a bit more.