I don't mean to downplay the author's skills, but I don't see how creating an input simulation library fast-tracks someone for consideration in an AI-related engineering role.
It mentioned an "open position in the team implementing the secret, unreleased feature of Claude Desktop," which doesn't specify whether the "secret" feature is AI-related or UI-related. My guess leans towards the former.
You got me, adding “using enigo” makes all the difference — I guess position is exclusively for working with this one library and that’s the position they got overloaded with applications on and couldn’t process one sent by OP.
It clearly does make a difference as to why he thought his experience was relevant to the job (i.e. what we were discussing before), and I think you agree with that hence your somewhat "selective" omission when you posted the quote.
I wasn't making a statement about whether his experience was relevant to the job. I don't know the author and don't automatically doubt his knowledge. I was simply sharing the opinion that being the author of that UI library alone does not fast-track someone for the "Software Engineer working on Claude Code" position at Anthropic.
I wasn't aware of that; it wasn't clearly specified. It only mentioned a "secret" feature, but I assumed it was AI-related rather than UI-related. Additionally, Anthropic's Claude Code position on their website states that they expect their developers to work across the stack, including both front-end and back-end.
