Clarify ratios are not absolute numbers

Author: john-kurkowski

src/content/posts/2025-04-03-still-measuring-devs-with-leetcode.mdx

@@ -89,7 +89,7 @@ Much to my chagrin, I didn't make it far in the interview process, because
 almost every company I've interviewed with this year still uses LeetCode-style
 interviews. If a company even gives the heads up of what to expect in an
 interview, don't necessary believe, "Our live code assessment uses real-world
-problems." In 9/10 of my interviews this year, the technical step was still
+problems." In 90% of my interviews this year, the technical step was still
 LeetCode in a trenchcoat.
 
 I was rusty at these live coding interviews, because in my 14 year career,
@@ -103,7 +103,8 @@ questions about the job. The interview for mutual fit turns out not to be a
 2-way street. It's dehumanizing for the experienced dev.
 
 When I'm rejected after an interview, in my spirit of continual improvement, I
-ask for feedback why. 9/10 companies are cagey, to cover their ass. So I'm not
+ask for feedback why. 90% of companies responded cagily with a non-answer or
+that it was not their policy to share feedback, to cover their ass. So I'm not
 fully certain all the reasons I was rejected over the last 12 months. I might
 have a worse personality than I think. Maybe a member of the hiring panel was
 underslept and cranky. All I know is, the interview process ending _correlated_