This is a big deal the longer you stay in the profession. I think looking at glassdoor is great, but they recently started censoring poor reviews.
So there are two other ways I use to find out the scoop.
Find someone who works there through your network and ask
Build a list of questions to ask when you are interviewing
For two I like to ask things like
Tell me about the last time you had a production issue
Let say we need to learn more about blue-green deployments, how does this company support people learning to do that?
What's one thing you wish you could change today?
There are more you can come up with, but the idea is keep the questions open and put them to thinking of actual experiences they've had. You'll learn a lot about the place, but it is always a gamble.
One good thing though is that in our profession you can bounce to another job pretty quick once you know how. You don't have to suffer a toxic workplace for long at all.
Hmm, I've never really given that too much thought.
I ask these questions to the dev managers and the peer developers who interview me. That cross-section helps me identify consistent messages or things that are way out of sync.
Also, most companies don't do any real preparation before they interview candidates, so when I ask these questions they don't have canned answers ready. They may not be completely forthright, but each person will expose parts of the whole truth. Especially the peer developers. They are usually thrown into an interview and don't have too much reason to cover things up.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a big deal the longer you stay in the profession. I think looking at glassdoor is great, but they recently started censoring poor reviews.
So there are two other ways I use to find out the scoop.
For two I like to ask things like
There are more you can come up with, but the idea is keep the questions open and put them to thinking of actual experiences they've had. You'll learn a lot about the place, but it is always a gamble.
One good thing though is that in our profession you can bounce to another job pretty quick once you know how. You don't have to suffer a toxic workplace for long at all.
Those are great questions, thanks
Any tips to spot lying in the answer?
Hmm, I've never really given that too much thought.
I ask these questions to the dev managers and the peer developers who interview me. That cross-section helps me identify consistent messages or things that are way out of sync.
Also, most companies don't do any real preparation before they interview candidates, so when I ask these questions they don't have canned answers ready. They may not be completely forthright, but each person will expose parts of the whole truth. Especially the peer developers. They are usually thrown into an interview and don't have too much reason to cover things up.