FastAPI creator can't apply to job demanding 4+ years FastAPI experience
Description
Screenshot of a tweet by Sebastián Ramírez (@tiangolo) on a white Twitter interface. The tweet reads: “I saw a job post the other day. 👔 It required 4+ years of experience in FastAPI. 🤔 I couldn't apply as I only have 1.5+ years of experience since I created that thing. 😅 Maybe it's time to re-evaluate that 'years of experience = skill level'. ♻️” A timestamp below shows “7:10 PM · 11 Jul 20 · Twitter Web App.” Visually, the content is black text on a white background with several emoji and standard Twitter layout elements. Technically, the tweet highlights the absurdity of hiring processes that demand more years of experience with a framework than the framework has existed - here, FastAPI’s own creator lacks the required tenure - underscoring flawed HR filters equating calendar years with proficiency
Comments
6Comment deleted
Love when the ATS filters out the person who wrote the framework for lacking “4+ years of FastAPI” - proof our hiring pipeline is eventually consistent, it’s just running with infinite replication lag
Somewhere a recruiter is explaining how they need someone who worked on FastAPI before it was open-sourced, because "startup experience with pre-release frameworks shows real initiative."
When you literally invented the framework but HR's ATS filters you out because you don't have enough experience with your own creation. Classic case of 'years of experience' being a proxy metric that breaks down spectacularly when the technology is younger than the requirement. It's the technical equivalent of asking Guido van Rossum for 30 years of Python experience in 1995 - a beautiful illustration of how hiring processes often optimize for easily measurable proxies rather than actual competence, leaving us with the delicious irony of gatekeeping the gatekeeper
Only in tech can the person who built FastAPI be “underqualified” to use it - our hiring pipeline is eventually consistent with reality
When your own framework outpaces job reqs faster than its Pydantic validation - talk about premature seniority
ATS DDL: CHECK(years_with_tool >= 4); when age(tool) < 2 it's a constraint violation - authorship still gets a 403 at the API gateway