I usually ask for the team structure/geolocation , day to day activities, scope of responsibility/ownership. I think you need experience to figure out what you really do not want in a job, your red flags, and ask if they are present, better if you have a list of must haves for your success, ask if they can provide them. Forgot to mention the most important, be prepared. Interviews are not sth we experience too often in our careers, so no matter what, its exciting. You are on the podium, but if you do this preparation beforehand after you did it couple of times and you have confidence in your skills interviews really becomes two way conversations. At the very least you can always approach it systematically and ask for what you dont know already and what you are curious about the role/company/interviewer. Good luck.
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.
I usually ask for the team structure/geolocation , day to day activities, scope of responsibility/ownership. I think you need experience to figure out what you really do not want in a job, your red flags, and ask if they are present, better if you have a list of must haves for your success, ask if they can provide them. Forgot to mention the most important, be prepared. Interviews are not sth we experience too often in our careers, so no matter what, its exciting. You are on the podium, but if you do this preparation beforehand after you did it couple of times and you have confidence in your skills interviews really becomes two way conversations. At the very least you can always approach it systematically and ask for what you dont know already and what you are curious about the role/company/interviewer. Good luck.