There are so many questions to be asked. I often had to limit myself, since most of the interviewers are not prepared to be interviewed themselves. That's, however, a huge misconception. I am not the only one trying to present myself. The company needs to present itself to me.
Assuming that the product is clear to me, I often ask.
Company-wise
It boils down to just one question:
How long do devs stay with the company in general?
Team-wise
Here my goal is to get a sense of if the team actually works as a team. Some companies have strict hierarchies and the devs are working ants. Does the team have a say? Do they pursue a common goal? Is there a single point of failure in terms of knowledge distribution?
How big is the team and how many people are assigned to which role?
How is the team workflow? Self-organized? Top-Down? Scrum? Whatever.
When was your last retrospective?
How does your daily look?
If this goes well: Can I sneak a peak on your backlog (assuming that whatever is in there would be my work soon)?
Only after all that is done, I would get down to the real technical questions. Why? I don't care how awesome the tech stack is if the team members are miserable. That's a company where your salary is a compensation for pain and suffering.
Technical-wise
The usual tech things: What languages for what purpose.
Whats your code coverage?
Can you walk me >quickly< through a typical deployment?
Can you rollback if deploy fails?
That's pretty much it. Like I said in the beginning - there are so many questions to be asked. You need to be careful not to ask too many questions since you might be perceived as arrogant and or picky. In my experience, however, the companies that can answer those questions are self-reflected and conscious about their employees.
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.
There are so many questions to be asked. I often had to limit myself, since most of the interviewers are not prepared to be interviewed themselves. That's, however, a huge misconception. I am not the only one trying to present myself. The company needs to present itself to me.
Assuming that the product is clear to me, I often ask.
Company-wise
It boils down to just one question:
Team-wise
Here my goal is to get a sense of if the team actually works as a team. Some companies have strict hierarchies and the devs are working ants. Does the team have a say? Do they pursue a common goal? Is there a single point of failure in terms of knowledge distribution?
If this goes well: Can I sneak a peak on your backlog (assuming that whatever is in there would be my work soon)?
Only after all that is done, I would get down to the real technical questions. Why? I don't care how awesome the tech stack is if the team members are miserable. That's a company where your salary is a compensation for pain and suffering.
Technical-wise
That's pretty much it. Like I said in the beginning - there are so many questions to be asked. You need to be careful not to ask too many questions since you might be perceived as arrogant and or picky. In my experience, however, the companies that can answer those questions are self-reflected and conscious about their employees.