Ask HN: Which job criteria is important you when searching a new job? When you search a new job, apart from the regular job description (position, technology, Joel test) which criteria are important for you? What makes a good job for you? I feel that a lot of companies still underestimate softer criteria like "remote possible", "deep work possible" or "development plan from day". |
- How long does it take to stick a debugger into a particular place in the codebase and run a single automated test to trigger it?
- How long does it take to get a diagram of the schema (or implicit schema) of the relationships among data entities in their main applications?
- How long does it take to find out who the business stakeholders are for my team or projects?
- How long does it take to find out what the goals are for the engineering and product team are overall?
- Can the product manager explain the relationship between technical debt and engineering velocity?
——————
Is it weird that I find myself utterly distressed that these can be so uncertain?
Are you having a hard time finding this?
My current company uses MongoDB and I _really_ wish there was a schema I could read.
I am not joining a new place unless I can discuss work with my possible peers. They need to be deserving of me just as I need to be deserving of them.
There's ways to identify such companies. One of the more obvious ones tends to be having a strict dress code (i.e. must wear biz casual).