3 ms·
I have a slight problem with your 'open salaries': You don't define the ranks. Obviously if I took a job with RethinkDB I would be an "Engineer" rather than an
by cperciva 17y ago
I have a slight problem with your 'open salaries': You don't define the ranks. Obviously if I took a job with RethinkDB I would be an "Engineer" rather than an "Intern"; but would I be an "Engineer I", an "Engineer II", or an "Engineer III"? Between them, the salary ranges stretch from 65k to 105k.
Presumably everybody inside the company knows what rank everybody else has, so to that extend the salaries are indeed open; but from the applicant's perspective, all you seem to have done is renamed "negotiate salary" to "negotiate rank".
- coffeemug 17y agoThe reason we didn't define it is that it's incredibly tricky. There are some people with no education and no track record with incredible skills, drive, and professionalism. There are others with long track records who are less skillful in some areas. After trying to write up clear definitions for a while, we realized that we can't do it right without writing fifty pages of legaleze, so we decided not to waste time on it. In practice, when you have only three levels, most people have a good intuitive feel for where they fall, and it's usually in tune with our evaluation. I agree that this system has its problems, and we'll try to work out the kinks over time. It will be interesting to see how it evolves.
- cperciva 17y agoHave you considered defining the ranks based on the job responsibilities rather than the backgrounds of the applicants? e.g., "will need to do X without supervision" / "will need to supervise more junior people" / etc?
- lief79 17y agoAlong the sames line, if there is a variation, then write it down as the norms or minimums, at a minimum, they will be able to do 3 out of this 6 things, etc.
- deleted 17y ago[deleted]