u/g8rojas wrote (the comment Michael replied to):
Sir, if you want to say it is "hard to explain" I would normally ask you to explain it b/c I am a smart guy and i am sure there are other smart people here able to understand it. BUT this is not what I am asking. i am not asking you to justify why people missed work nor the comp
u/michaelnovati replied ·
Ok I'll try to answer!
"If a student does **not** do the work you ask them to do" => then nothing really happens. They'll be given other things to do or perhaps asked to do those things again, we'll try to get them to do it later.
People can still apply for and get jobs because it's not binary. They might be 75% ready for an interview and not do a task and it's 74% ready and it doesn't matter, they can still get the job.
We work with people on interviewing for specific companies when they are ready for that company. So you might do a task to get ready for Google, and not do it because you have a Meta interview you don't need that task for and get a job at Meta.
If people fail an interview then we look at how they prepared. They might have failed practice interviews and chose to do the real one for personal reasons. There might have been factors outside their control. They might have practice the wrong thing because they misunderstood the loop coming up.
We review and try to improve any gaps and improve the product to get better signal and then we repeat.
We work with people for however long it takes to get a job, so if you fail fail fail we keep working with you until you pass, so there isn't really a failure state.
I don't know what our failure state is. We certainly aren't perfect and have a lot of things to improve, so it's not that their isn't one, it's just not directly related to doing work = get job, it's probably more related to day to day experience, like a mentor cancelling last minute or not submitting feedback promptly, and those rarer events that cause a bad experience.