Cute but I mean… You just copy paste it into postman and fill in the blanks. It doesn’t really show anything, it’s just novel.
I’m not gonna be as cynical as the other people on here saying that it’s because they just want to have a machine/AI process your application.
But at the same time I’m gonna be even more cynical, because if they think that machines/AI aren’t already processing your PDF resumes, then you’re crazy lol
Not because it’s hard to fire up curl or something, but because any company that thinks this is a better solution than a human reviewing a resume needs to be smacked. Because you know what the very next step is? They’re going to ask for a resume, and then make you sit through that bullshit where you type your resume into a hundred different boxes into their candidate management system / workday / talento / etc., and promise to “get back to you soon.”
You know how you can check if a candidate can interact with an API? Send them a coding test. Ask questions. Do some whiteboarding with them. This sort of shit is just some HR lackey ninja thinking they’re clever and edgy.
Because you know what the very next step is? They’re going to ask for a resume, and then make you sit through that bullshit where you type your resume into a hundred different boxes into their candidate management system / workday / talento / etc., and promise to “get back to you soon.”
That’s a lot of assumptions. What I see here is “Do fizzbuzz before we look at your resumee, will you”.
I mean an API call isn’t hard, it cuts down in the amount of resumes probably meaning your resume will be more likely to be looked at. And it let’s then know you know the very basics, I’ve seen some shit on recruiting hell forums and I’m ok with this one. You don’t even have to retype anything since the resume field is just a link.
The cringy stuff is “rockstar developer” and ninja, etc. Those are always red flags to me
I really like this for technical roles. Or tech companies in general. That said, they don’t have any job descriptions or requirements beyond the API request so it’s not easy to tell what they’re looking for or how qualified you are. Plus there’s no posted salary range
Hey, I’m a senior developer with 25+ years’ experience and more languages and tools and stacks and environments and so on that is reasonable to list in a comment. In my decades of experience, finding someone who is legitimately good at Excel is a rarity.
Cuz you either graduate to real programming and databases, or languish in some kind of hell where you work in excel all day and have to get good at it to save your sanity
“blockchain” tends to be rather iffy too, especially since it’s seemingly inevitably tied with cryptocurrency or something like it in some form or another.
It has a built-in filter for the poor folks that use these proprietary services like Twitter X, Microsoft GitHub, and Discord Username.
I wouldn’t apply anywhere asking exclusively for these platforms instead of something generic like: instant messaging, public code forge(s), weblog/microblog(s). I would encourage you, reader, to ask around & make sure your org isn’t hiring based on proprietary service usage. Heaven forbid your applicant is from a place under US sanctions & literally couldn’t use the services even if they wanted …or like your candidate has any values about privacy.
Resume field would get an api endpoint that only returns a json resume, and only if the request header is application/json. And the json resume would have embedded json.
I love it. If everyone did that, we could even write a sensible fontend for people, so they can look for a job instead of fighting with some sap module that’s not even properly translated from german.
SAP developement has become international, even the german version is badly translated. Paired with industry best practices (this is what Volkswagen does, with a little customization you can adopt it for your beauty salon) it will make businesses thrive!
I wish we just had a standardized format for resumes. Then as you say various front ends could just formatted however was most convenient for the reviewer.
Besides it’s almost all handle by AI these days anyway so there isn’t a lot of point making it look flashy.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Actually pretty cool idea. :)
deleted by creator
Cute but I mean… You just copy paste it into postman and fill in the blanks. It doesn’t really show anything, it’s just novel.
I’m not gonna be as cynical as the other people on here saying that it’s because they just want to have a machine/AI process your application. But at the same time I’m gonna be even more cynical, because if they think that machines/AI aren’t already processing your PDF resumes, then you’re crazy lol
You’d be surprised at how many imbeciles a simple step like this will weed out. Lotta unqualified people applying to everything
I’d pass so hard. Thank goodness the only “interviews” I’ve ever needed in 30 years have been the polar opposite of this kind of cringe.
Honestly that’s more user friendly than 9 out of 10 application forms I’ve run into.
The best way for me to avoid this mess for now has always been an email with my pdf files attached.
Wow, I would pass on this job so fast.
Not because it’s hard to fire up
curlor something, but because any company that thinks this is a better solution than a human reviewing a resume needs to be smacked. Because you know what the very next step is? They’re going to ask for a resume, and then make you sit through that bullshit where you type your resume into a hundred different boxes into their candidate management system / workday / talento / etc., and promise to “get back to you soon.”You know how you can check if a candidate can interact with an API? Send them a coding test. Ask questions. Do some whiteboarding with them. This sort of shit is just some HR
lackeyninja thinking they’re clever and edgy.That’s a lot of assumptions. What I see here is “Do fizzbuzz before we look at your resumee, will you”.
I mean an API call isn’t hard, it cuts down in the amount of resumes probably meaning your resume will be more likely to be looked at. And it let’s then know you know the very basics, I’ve seen some shit on recruiting hell forums and I’m ok with this one. You don’t even have to retype anything since the resume field is just a link.
The cringy stuff is “rockstar developer” and ninja, etc. Those are always red flags to me
Cool
That’s really nice idea
I really like this for technical roles. Or tech companies in general. That said, they don’t have any job descriptions or requirements beyond the API request so it’s not easy to tell what they’re looking for or how qualified you are. Plus there’s no posted salary range
The terms “super power” and “code ninja” takes a lot of the offers credibility in my eye.
Once had an applicant with “Excellent Excell skills” on their cv
Hey, I’m a senior developer with 25+ years’ experience and more languages and tools and stacks and environments and so on that is reasonable to list in a comment. In my decades of experience, finding someone who is legitimately good at Excel is a rarity.
Cuz you either graduate to real programming and databases, or languish in some kind of hell where you work in excel all day and have to get good at it to save your sanity
“blockchain” tends to be rather iffy too, especially since it’s seemingly inevitably tied with cryptocurrency or something like it in some form or another.
Honestly as far as hiring for this stuff goes, this is more in the “cute” category for me rather than the “annoying” category.
It has a built-in filter for the poor folks that use these proprietary services like Twitter X, Microsoft GitHub, and Discord Username.
I wouldn’t apply anywhere asking exclusively for these platforms instead of something generic like: instant messaging, public code forge(s), weblog/microblog(s). I would encourage you, reader, to ask around & make sure your org isn’t hiring based on proprietary service usage. Heaven forbid your applicant is from a place under US sanctions & literally couldn’t use the services even if they wanted …or like your candidate has any values about privacy.
deleted by creator
It’s implicit endorsement. It signals that you’re an incomplete candidate without participating in the corporate data collection game.
Resume field would get an api endpoint that only returns a json resume, and only if the request header is application/json. And the json resume would have embedded json.
To be fair, that’s one of the relatively tame and clever one of those.
I love it. If everyone did that, we could even write a sensible fontend for people, so they can look for a job instead of fighting with some sap module that’s not even properly translated from german.
deleted by creator
SAP developement has become international, even the german version is badly translated. Paired with industry best practices (this is what Volkswagen does, with a little customization you can adopt it for your beauty salon) it will make businesses thrive!
SAP, the worst thing to come out of Germany since WW2
I wish we just had a standardized format for resumes. Then as you say various front ends could just formatted however was most convenient for the reviewer.
Besides it’s almost all handle by AI these days anyway so there isn’t a lot of point making it look flashy.
Such things exist. They’re just not widely adopted. https://github.com/jsonresume
Mmm. It’s not going to happen though. Even this company have failed at standardising their own API.
Key for twitter:
"twitter":Key for discord:"discordUsername":Why are they inconsistent?! Who wrote this? Who signed off on it?!
Oh, and for GitHub you provide a url but for twitter and discord it’s just the username?! But the twitter handle has to be prefixed with
@. Why?!Just send it with both “discord” and “discordUsername” for compatibility.
Years later, we’re still trying to figure out which is deprecated and which is the “correct” field
Ambiguous fields, sounds like me fr
You could have different versions of the API that have a different requirements.
I bet it just ends up in some poor bastards mailbox anyway. :)
API is not versioned. Also REST API should not use verbs in their endpoint. POST is already the HTTP verb –
/submitis superfluous.From the picture, it doesn’t appear they ever claim to be a REST API.
If course not, it’s to apply for a job. It’s a WORK API.
This comment was worth the time I spent reading comments in this thread.
Take my upvote and get out of here.
I think, its a good idea. And a cool way to open for job application