Actually, no, you know what?
-
Asta [AMP]replied to Asta [AMP] last edited by [email protected]
@[email protected] Actually, you know what, I'm gonna go ahead and post his rejection and my response, as well, because in hindsight it's total horseshit
In particular, this came after I objected to the transcript ranking requirement, and he rejected me based on technical grounds. I had extensive experience in Python and passed the technical test, and they were only taking Django out of the codebase so didn't need to be an expert for that.
So why, precisely, did he need my academic transcript to reject me? Why couldn't he have done that before, as he already had all the information that he used to reject me? Why did he wait until he had documents that
A. indicated I'm trans
B. indicated my age
to do that? -
@[email protected] They send you a questionnaire that asks something like twenty questions and ask for detailed answers; mine ended up being around 18 pages or so.
And... no, the job involved zero manipulations of 3D shapes done via a 2D visual plane. -
@[email protected] I checked on that posting a few months after that and it was still open, for the record.
-
Captain Superfluousreplied to Asta [AMP] last edited by
Fake opening?
(I've seen a lot of them myself)
https://www.cnbc.com/2024/08/22/ghost-jobs-why-fake-job-listings-are-on-the-rise.html
-
Asta [AMP]replied to Captain Superfluous last edited by
@[email protected] it would be weird to devote developer time on interview cycles for fake postings… I would think. But then again, maybe not. Although my god: the risk associated with doing actual interviews for a fake posting would be enormous, I think, since you’re potentially rejecting perfectly qualified and hireable candidates for bullshit reasons.
Still.