I frequently don't see the organizational support for a proper CICD process. The people that hold the purse strings just don't understand the value. There's an

I frequently don't see the organizational support for a proper CICD process. The people that hold the purse strings just don't understand the value. There's an obvious set of prerequisite here: 1. what's your code coverage? 2. what's the branching strategy like (this is a long winded way of asking: are PR branches built automatically?) 3. how frequently do you release? I guess this could be your "smoke test", without a reasonable code coverage you cannot have the PRs build automatically or a frequent release schedule. If you ask an HR person about the frequency and get anything less than "frequently" you're likely dealing with an org that doesn't have 1/2/3. It seems unlikely that something like this would make it into a job posting though.