Minh Nguyen

Have you ever wondered why we still rely on resumes for hiring, even though research shows they aren't the best predictor of job performance?
I've spent my career in casting and matchmaking, which are all about finding and reading talented people. When I started exploring hiring, I expected a more thorough process. Instead, I noticed the industry mainly depends on keyword matching and job titles, despite decades of proof that behavioral and values-based assessments predict success and retention much better.
I'm really curious to hear your thoughts:
Is it just tradition? Do resumes seem more legally solid than structured interviews? Is it because they re quick to scan at scale, even if they don t say much? Or maybe we just haven t yet developed the tools to do it differently on a large scale?
I've been working on Rh yo, a SaaS platform that scores candidates and roles based on fit and values rather than keywords and titles. I don't think resumes will disappear overnight, but I'd love to know what it would take to change the way we do things.

I always assumed building the product would be the hardest part.

After launching my first app, I realised getting people to discover it is a completely different challenge.

For founders who've been through it, what was the biggest surprise after you launched?

I was looking through the newly released benchmark comparison, and one thing stood out immediately.
Opus 5 outperforms Fable 5 on many of the benchmarks that matter to me:
* Agentic terminal coding: 43.3% vs 33.7%
* Knowledge work: 1861 vs 1747
* ARC-AGI-3: 30.2% vs
* Computer use: 70.6% vs 66.1%
* Business workflows: 26.0% vs 17.4%

Yet from what I ve seen, the API pricing is also lower than Fable s.
As someone building AI products, that s a pretty interesting combination. Usually when a model takes the lead on benchmarks, it s also the most expensive option.
I m curious about real-world experience though.
Has anyone here already switched from Fable to Opus 5?
* How does it perform on long coding sessions?
* Is the benchmark advantage noticeable in production?
* Any hidden downsides (latency, tool use, context handling, reliability)?
Would love to hear from people who ve actually deployed both.