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.
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.
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
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
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
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.
Is it just me, or does their sample request use invalid JSON? The keys should be in quotes, comments aren't in spec (but commonly supported), and trailing commas are invalid as well (but commonly supported).
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.
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.
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.
I turned over an interview because I had to sign in on the company's portal, there's no way I would do that for an offer I that I did not know previously what would my salary be. Imagine having to do that for every single application. Only if I was desperate after a new job.