This makes me wonder how many people are okay with being underpaid. Like my title is officially VP of Engineering. But because of the circumstances of my position and what I was hired to do, I am probably making less than what someone in my position gets in sign on bonuses. $30,000/yr This is because I am not only the first employee but the only employee (if you don't count CEO) and only technical person. I was hired…
Why not just a simple spreadsheet of salaries?
111–120 of 384 posts
Re: Why not just a simple spreadsheet of salaries?
#112It's strange to me that these salary discussions are so narrowly focused on just pay/bonus and don't seem to care about benefits and work/life balance. Here's stuff I track in my own career spreadsheet and compare new jobs against these metrics when considering a new one: * Vacation, sick, and holiday time off * Distance to work and traffic considerations * Relative cost of living * Health insurance cost and coverage…
Re: Why not just a simple spreadsheet of salaries?
#113This makes me wonder how many people are okay with being underpaid. Like my title is officially VP of Engineering. But because of the circumstances of my position and what I was hired to do, I am probably making less than what someone in my position gets in sign on bonuses. $30,000/yr This is because I am not only the first employee but the only employee (if you don't count CEO) and only technical person. I was hired…
Re: Why not just a simple spreadsheet of salaries?
#114Re: Why not just a simple spreadsheet of salaries?
#115Re: Why not just a simple spreadsheet of salaries?
#116Earlier quoted context omitted.
Good comment. What are your thoughts on including: - "jump ship literally tomorrow salary requirement" (base, equity, signing bonus) regardless of whether you're looking, and an anonymized means of contact. It literally can't hurt. I don't think it even gives off any signal. I mean if you saw "$130K/undisclosed options/Bay Area/ Jump ship literally tomorrow: $180K + $15k signing bonus" it's next to no information. Th…
Looking to jump ship?
Re: Why not just a simple spreadsheet of salaries?
#117It's strange to me that these salary discussions are so narrowly focused on just pay/bonus and don't seem to care about benefits and work/life balance. Here's stuff I track in my own career spreadsheet and compare new jobs against these metrics when considering a new one: * Vacation, sick, and holiday time off * Distance to work and traffic considerations * Relative cost of living * Health insurance cost and coverage…
Re: Why not just a simple spreadsheet of salaries?
#118Re: Why not just a simple spreadsheet of salaries?
#119Earlier quoted context omitted.
I'm pretty positive I'm in full control of this company. I've taken reigns and made all the decisions. CEO has pitched in his requests, but ultimately has put me in full control, that being said I'm sure while my title says VP of Engineering (for his parent company by the way) I will become the CTO and co-founder of this company when it launches.
Get equity or get out - make the promises binding.
On top of that, being the only technical person and have full control over everything, including domains, hosting, code, etc. It's not really like I can be forced out.
Re: Why not just a simple spreadsheet of salaries?
#120Entering locations is notoriously difficult. Country + City is probably the best you could do, where country could be re-used for US States.
Eh, I think in cases of ambiguity you might be better off just sticking the state into the name of the city. Like "USA - New York City" vs "USA - Springfield (IL)".
If you don't have a db of cities to choose from you likely end up with cleaner data by sticking state to country since you could make a db for that with just some 100-200 entries.
Country/State: US/Illinois, City: Springfield
The original point is still there though, having a single location field breaks down quickly.