@freemo hadoop seems to be very important to list it twice :)

@freemo

> [image of list of tech buzzwords followed by the caption "I typically ask recruiters which of these are Pokémon"]

I'd probably fail! (not that I'd ever be a recruiter)

More seriously, this guy seems to list technologies is so many different areas (frontend web dev, data science, systems programming, etc) that I'm not sure I'd penalize a recruiter for not knowing/caring what some of the buzzwords are—especially if they're looking to hire in just one of those areas

@codesections Fair point. Though depends on how you view a recruiter. If the intention is to negotiate on your behalf then id want someone with extensive tech knowledge. If their only goal is to forward me jobs and take a cut, not so much.

Since I am very stern on retaining the power to negotiate price (something recruiters try to discourage) it is less important to me. I really dont let them plat their usual games that a more passive person might allow.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.