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.
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.
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.
Hey, that’s me! I query my workforce data from the HRIS with M and SQL. In HR land, that makes me a super senior data scientist compared to VLOOKUP guy who hasn’t even heard of XLOOKUP or even INDEX/MATCH, that asshole.
/serious Well, yes, most APIs are meant for system-to-system interaction, that's kind of a given. But since this particular API is clearly meant for human-to-system interaction, returning a human-readable response is adequate. Yes, a better design would probably allow the client to specify additional parameters about the desired response.
/back-to-jokes Yeah, well this kind of sums up most of my job applications. I send an application and the recruiting people are all like "OK".
I also notice that the job you apply for seems to be a different value than what is displayed on the page. Seems like the documentation needs updating as well 😔
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
Twitter is even worse. I don’t have twitter, I don’t want twitter, I don’t need twitter and neither does anybody else. On top of that, twitter is dead.
For me Twitter was and I guess still is the best thing for immediate notifications of stuff you like.
I used it for notifications about preorders of limited editions, news, people, etc. It wasn’t perfect as some accounts are quite spammy but it was the best thing out there. RSS isn’t used as much nowadays, newsletter usually are sent at certain time or delayed so not very immediate and Idk what else is out there sort from those two (or using an equivalent social account).
Always will call X as Twitter. Same as Meta as Facebook Inc, Microsoft 365 as MS Office, or whatever other companies unnecessarily rebranding themselves these days with their ugly less iconic logos.
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).
I understand this line of thinking, but unless they specify what “flavor” of JSON they accept, I think it’s safe to assume they only accept what’s in spec. What I find weird is that they immediately contradict the spec with their example by writing JavaScript. Should the content-type then be application/javascript? They can easily document the parameters outside the request body instead of adding comments.
Also, yes, I know I’m being pedantic, but if I’m applying for a job, it’s a two way application. They need to give me reason to trust that they’re worth working for. Making up rules along the way when referencing a commonly known spec doesn’t give me much confidence.
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 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