We are unable to offer you a job because your name doesn't work with db schema
twitter.com
twitter.com
Maybe they created a tool called Jeffrey, and it's too integrated with the DB...
Clueless intern: "So what about this guy Jeffrey"?
Mean/Pissed/Annoyed/thinks-he-has-a-sense-of-humor boss: "Tell him that we don't hire anyone with that name"
The most obvious one seems that someone decided to make first name the primary key and now they are stuck with the problem but still that doesn't feel right to me.
It means the company has just saved you time. You are free to pursue another company that is competent enough to store a name in a database record.
Please, leave them a thank you note on your way out, maybe link to one of reoccurring articles here on HN: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
Which I'll just take as true since the fact that they are actually more polite than most companies in replying to job applicants just adds to the humour.
Tech for Good careers page: http://www.techforgood.global/jobs/
A data scientist would be expected to understand how databases work. They want the applicant to respond back and say why that response doesn't make sense so they can weed out the 99% of people who apply to jobs on Indeed that are unqualified. It's also a good barometer of the applicants temperament. 300 IQ move.
The alternative explanation, that they're unable to hire people with the name 'Jeffrey' (and know exactly what the problem is but don't fix it), is just too absurd to actually be true. If one of their systems actually had this limitation they would have started naming people Jeffrey1, etc, by now.
>Jesus shit, you guys love my failure. follow me to see more of my unfortunate life and ily all