Hacker News new | ask | show | jobs
by gere 2560 days ago
This is a sensible advice, but how do you recognize an easy programming job?
3 comments

There are (at least) two ways in which a job can be "hard":

1) Technically. Having to constantly learn new things, new technologies, etc. Unable to rest on your laurels. Learning new things can be very rewarding from a career growth standpoint, but it can also leave you drained at the end of the day.

- Avoid a technically challenging job by choosing one which is in your skillset, and unlikely to change. For instance, if Java is your thing, find a back-end Java job at a big company (startups will often ask you to change roles and learn new things).

2) People. Dealing with shitty bosses / managers / coworkers can suck the "easy" out of a job and make it very challenging to get anything done.

- Try to get a feel for the leadership in your interview process. The interview should come off as warm, and inclusive, even you aren't doing well. Overly complex questions, riddles, or hide-the-ball interview tactics generally come from insecure interviewers.

It's hard to from the outside, but I would guess the biggest factor that correlates with easy is amount of red tape. The more bureaucratic, the more non-work is done in place of actual work, the easier the job.

So I'd say large corporations or government jobs would skew easier. Maybe work for a large government organization?

less then 5 days/week helps