I've been thinking about low-friction options for getting a sense of the engineering quality. I don't think I'm alone in thinking that technical debt and bad software development practices are a top concern.
Being quite senior now, I'd feel comfortable asking:
1 - To see their CI dashboard
2 - To see a sample of their production systems stdout & stderr
3 - Asking to review a recent non-trivial commit (with the person/people who wrote it)
4 - If you're interviewing remotely for an on-site position, finding out if they have an open office
Being quite senior now, I'd feel comfortable asking:
1 - To see their CI dashboard
2 - To see a sample of their production systems stdout & stderr
3 - Asking to review a recent non-trivial commit (with the person/people who wrote it)
4 - If you're interviewing remotely for an on-site position, finding out if they have an open office
5 - Finding out how they do deploys / devops