> The latter is a bit easier to verify by talking to other engineers, but in general I find it extremely difficult to foresee what you are running into with a n

> The latter is a bit easier to verify by talking to other engineers, but in general I find it extremely difficult to foresee what you are running into with a new job. Ask the hiring manager what will your typical tasks be, and then try to detect if/how much is he lying I guess? Look out for usual red flags, like being ambigious or avoiding difficult subjects (such as - how bad the codebase is, how much maintenance vs greenfield work will you be doing, will you be able to influence the direction of the work, or are you just someone they need to implement their ideas).