The Classic Recruiter Mix-up: Jason vs. JSON
Description
The image is a screenshot of a tweet from a user named Hamza (@oihamza). The tweet, set in white text against a black background, reads: 'Once I asked a recruiter “who’s Jason” when they were actually asking if I knew JSON'. The timestamp below the tweet says '10:06 AM · 25 Jul 21 · Twitter for iPhone'. The original post's caption adds context: 'Please, stop saying Jason instead of JSON, I swear'. This meme captures a classic and highly relatable moment of miscommunication between developers and non-technical or junior recruiters. The humor stems from the phonetic confusion between the common name 'Jason' and 'JSON' (JavaScript Object Notation), a ubiquitous data format. For experienced engineers, this is a painfully funny nod to the interview process, highlighting the disconnect that can occur when recruiters are unfamiliar with the very technologies they are hiring for
Comments
31Comment deleted
My resume lists expertise in JSON, YAML, and XML. A recruiter called to ask if I knew their cousin, Jason, and his two friends, Yammel and X-Mel
Told the recruiter my “Jason” skills were solid - right up until he grew past 5 MB and started nesting like Inception, at which point I introduce everyone to Protobuf and quietly deprecate Jason
The real JSON parsing error here is when recruiters try to deserialize '10 years of experience in a 5-year-old framework' into a valid candidate object - at least this one just had a pronunciation bug in their human speech API
This perfectly encapsulates the eternal struggle of technical recruiting: when your recruiter's understanding of JSON is so abstract, they might as well be asking about a person. It's the hiring equivalent of 'we need someone who knows Jason, jQuery, and that other Jason guy who does the backend stuff.' At least the candidate didn't respond with 'Jason Bourne? Great movie, but I'm more of a REST API guy.'
Recruiter's ultimate deserialization bug: JSON.parse('Do you know JSON?') → 'Who's Jason?' - no schema validation in HR pipelines
Recruiter: “Do you know JSON?” Me: “I keep five versions backward‑compatible with tolerant readers - Jason is the PM who calls it a simple rename.”
I told the recruiter I know Jason - picky guy: hates trailing commas and breaks your contract tests whenever Product says 'just add one more field'
am I missing something or letter J is pronounced exactly as "Jay"? Comment deleted
The creator of GIF still insist that it should be pronounced as “JIF” (which, imho, is totally wrong) Comment deleted
aye, I pronounce it GIF (not jif) as well. Dunno why people think jif is acceptable lol Comment deleted
That's so disgusting Comment deleted
And pronounce S as Z.... Comment deleted
JavaScript Object Notation. Maybe Douglas Crockdord wrong Comment deleted
Well, Comment deleted
He created it, Comment deleted
But does it mean he also should introduce pronouncation of JSON Comment deleted
Instead say Gay son Comment deleted
Ok, my beloved gay-son Comment deleted
how should i pronounce it then? Comment deleted
Thanks for the sticker Comment deleted
You are welcome! Comment deleted
Cool Comment deleted
dudes, im spanish speaker, the recruiters here's spell that like "JOTAson" its terrible Comment deleted
Lol Comment deleted
Why does everyone here speak English? I see your names Comment deleted
Because the rules specify to Comment deleted
Then want you tocall it Jison Comment deleted
that's Gson akshually Comment deleted
😂😂😂😂akshually its actually /s Comment deleted
Jason is Joe Mama's son Comment deleted
Jason is fine Comment deleted