If I'm rolling the dice then we've moved from d00 to d20 and saved a ton of time. Here are a few general examples of things I'll look at:

- Can I tell what the actual point of the job is from the job description? Does it describe what their services are in service to?

- How many non-technical, non-domain experts will I speak with before I'm talking engineer to engineer?

- How jazzed are the interviewers about speaking with me, in the moment? Are they interested in the details of earlier projects? Are they curious about me, or just running down a list of questions?

- Do they use leetcode or similar? There are a lot of really good reasons for a company to use leetcode in their hiring process, but none of those reasons are particularly good for me, as an employee.

- Do their interview questions make sense, given their context? E.g are they quizzing me on recursion from an environment where recursion wouldn't be a particularly great idea?

By that definition, nothing is a choice because nothing is 100% certain in life.

Even for something as simple as deciding to "go shopping" tomorrow, there is some probability that it does not happen. But it is still my decision to do so.

The only way to never fail is to never try. But it means you will never win either.

There is always an aspect of luck in everything. Also, the kinds of social skills which help you weed out bad potential employers and bad potential employees (when hiring) are likely learnable.