Boris Cherny mapped five archetypes that replace job titles in AI-era teams. Aline.team measures them. Connect GitHub, GitLab or Bitbucket and your profile is ready in about five minutes. We read activity patterns, never your source code.
Google recently published findings from a survey of 5,000 software developers.
According to Google Cloud s DORA report, 90% of respondents already use AI at work, spending an average of around two hours per day working with AI tools.
That number suggests AI is no longer an optional productivity tool. For many developers, it has already become part of the daily workflow.
The more interesting question may no longer be, Should developers use AI?
Amazon s PRFAQ process has long been considered one of the strongest product-planning frameworks: define the customer problem, write the press release and FAQ, and only then begin building.
But AI-assisted development may be changing that sequence.
Small teams can now create rough prototypes quickly, test workflows with users, and discover problems that would have been difficult to identify in a planning document alone.
This may also change what startups should look for when hiring. Instead of evaluating candidates only through job titles, years of experience, or familiarity with specific tools, teams may increasingly value the ability to:
