Here's an article about it: https://dev.to/maggiecodes_/how-i-applied-to-a-tech-job-using-a-post-request-193d
The thing that annoys me is the response. It should return status 201 created and the id of the new resource for future delete/update operations. Instead it returns 200 ok and some clear text. Wouldn't want to work with such an API.
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.
You can book this as a service for only $499/$999 per month from a dodgy website with no company adress but bold claims about time savings. Lol. Source: https://applybyapi.com/#pricing
But the best thing is: you can't send your open jobs by API. You need to use a rich text editor:
Post your job Upload your logo and use our easy rich text editor to make your posting shine. Unlimited job postings are included with every plan.
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
To be fair, that's one of the relatively tame and clever one of those.
I honestly enjoy stuff like this. I'm employed again recently, fully remote and decent pay thankfully, but I do appreciate stuff like this. It takes some of the monotony out of applying for jobs at least lol
That's really nice idea
I like it, but it's a dick move to require that the resume be hosted at a remote URL. Lots of developers don't have their CV on a website, and one of the strongest devs I've met doesn't even have a LinkedIn profile.
Support a file upload or just Base64-encoded data and you've got something here though.
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.
I think, its a good idea. And a cool way to open for job application
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.Honestly as far as hiring for this stuff goes, this is more in the "cute" category for me rather than the "annoying" category.
I really like this 'new' ProgrammerHumour
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.
Just use Postman.
Cool
