this post was submitted on 11 Jul 2023
56 points (98.3% liked)

Experienced Devs

3950 readers
1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

founded 1 year ago
MODERATORS
snowe@programming.dev
jmk1ng@programming.dev
drewsiferr@programming.dev
56
Questions to ask during an interview (programming.dev)
submitted 1 year ago by buxton@programming.dev to c/experienced_devs@programming.dev
48 comments fedilink hide all child comments
 

I was wondering if anyone else had any questions they always asked the interviewer in the "we'll give you five minutes at the end to ask us questions" bit in interviews.

Personally I always ask what the staff turnover rate is. Mainly because in my first dev job I was one of four people who started on the same day. One of the other guys left after two days, I left after six weeks, and another guy left after two months.

Another I'll be asking after my current job is if they have a mainframe. I've now worked at three companies with mainframes and they all were old corporations where they were outsourcing loads of stuff to unhelpful companies (often IBM) which generally meant lots of headaches.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] i_stole_ur_taco@lemmy.ca 5 points 1 year ago (1 children)

My secret weapon is "what questions do you think I should have asked?".

Not as a cop out, but something to follow your other questions with. A good interviewer will point you toward some of the company workings you wouldn't have thought to ask about. And if they're evasive it's a red flag you can use to consider their offer.

[โ€“] buxton@programming.dev 4 points 1 year ago

I like this kind of simple question. It often reveals a lot. Something I've done in the past is to ask "what's the best thing about working for this company?" and after they answer that I ask "what's the worst thing about working for this company?"

I've found being direct like that can often get some useful information.