u/Parky-Park wrote (the comment Michael replied to):
Very curious to see what the results for the second half of the year look like. **Edit:** There were some figures I posted here that, in retrospect, I regret posting. I think that the figures came across as more "authoritative" than I meant for them to. All of this data was gat
u/michaelnovati replied · · edited ★ FEATURED
Yeah I think Codesmith for the most part treats the fellow job reasonably with CIRR, but the loophole to watch out for is that they can "delay the clock indefinitely" by 1) extending contracts, and 2) hiring more Fellows. e.g. hiring 20% of a cohort back (7 people) is a MASSING clock delaying event for CIRR results. It pushes back 20% of people who might have otherwise not gotten a job, into the next report.
Thanks for sharing details as well, I suspect many programs have similar results and it's expected, but it should help people in navigating the tough market!
Again, I think they handle this reasonably, but they should disclose in a footnote on their reports how many people are fellows in each cohort as it manipulates the data.