Locations shouldn't be limited to numbers. Also, now that the salary field is limited to numbers, it should be clear which currency everything should be converted to, since people can't put their currencies in the column anymore.
Why not just a simple spreadsheet of salaries?
21–30 of 384 posts
Re: Why not just a simple spreadsheet of salaries?
#22Re: Why not just a simple spreadsheet of salaries?
#23Pretty crappy that "Gender" is a two-choice radio button. Literally gender binary.
Re: Why not just a simple spreadsheet of salaries?
#24Re: Why not just a simple spreadsheet of salaries?
#25>Location: Must be a number greater than 0 Locations shouldn't be limited to numbers. Also, now that the salary field is limited to numbers, it should be clear which currency everything should be converted to, since people can't put their currencies in the column anymore.
Re: Why not just a simple spreadsheet of salaries?
#26Re: Why not just a simple spreadsheet of salaries?
#27Pretty crappy that "Gender" is a two-choice radio button. Literally gender binary.
Sorry, I should have started with a trigger warning.
Re: Why not just a simple spreadsheet of salaries?
#28Re: Why not just a simple spreadsheet of salaries?
#29$122K in RDU seems very high for a developer/engineer, strange.
Source: live in RDU, was an engineering director until last summer, hired lots of people here over the years and know a bunch more. What's disturbing is the number of companies only hiring contractors or contract-to-hire engineers around here.
Re: Why not just a simple spreadsheet of salaries?
#30$122K in RDU seems very high for a developer/engineer, strange.