> A big role of full time employees is not just to code, but to interact to various degrees with PMs/Sales/Customers/the rest of the company stakeholders to varying degrees.
That’s true the further you get up in your career. But most of the time, it is:
- junior developers get tasks where both the business problem and technical solution is well defined and they need a lot of handholding and supervision
- mid level developers get tasks where the business problem is mostly well defined and they use their own judgement to create the technical solution. They should be able to lead work streams or epics
- Senior developers are responsible for leading major deliverables with multiple work streams, epics and are over seeing mid level developers and juniors. This is usually the first level where you spend the majority of your time dealing with strategy and “ambiguity” and with the “business”.
- staff - strategy involving many large implementations.
AI can already do a creditable job as a junior level developer and is rapidly moving up to being able to do the work of a mid level developer.
No matter what your title is, if you are just pulling tickets off the board with well defined business cases, you are doing mid level developer work. My definition is what I’ve seen, heard and read about from every major tech company.
Ok, except I guess I would say your definition of mid-level and junior both fall under what I would consider “junior”— maybe I would call what you define as “junior” as “intern” ?
I don’t see how LLMs completely eliminate anyone who is doing anything more than simply pulling well-defined tickets off a board
While I’ve spoken to people at other BigTech companies about their leveling guidelines, the only one that is still in my personal possession after I left is Amazon’s :).
That’s true the further you get up in your career. But most of the time, it is:
- junior developers get tasks where both the business problem and technical solution is well defined and they need a lot of handholding and supervision
- mid level developers get tasks where the business problem is mostly well defined and they use their own judgement to create the technical solution. They should be able to lead work streams or epics
- Senior developers are responsible for leading major deliverables with multiple work streams, epics and are over seeing mid level developers and juniors. This is usually the first level where you spend the majority of your time dealing with strategy and “ambiguity” and with the “business”.
- staff - strategy involving many large implementations.
AI can already do a creditable job as a junior level developer and is rapidly moving up to being able to do the work of a mid level developer.
No matter what your title is, if you are just pulling tickets off the board with well defined business cases, you are doing mid level developer work. My definition is what I’ve seen, heard and read about from every major tech company.