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.

• Needless hoop to jump though - red flag 1
• Having not switched to GraphQL - red flag 2 /s

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.

Just use Postman.

Wow, I would pass on this job so fast.

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.

Cool