Andrey (azangru) wrote,
Andrey
azangru

An attempt to formalize developer seniority levels by GitLab (from a job ad):

How we define our levels

Junior Frontend Engineer

Typically equates to less than 2 years of experience


  • Technical Skills

    • Needs guidance writing modular and maintainable code

    • Has less experience with HTML, CSS & JavaScript


  • Code quality

    • Leaves code in substantially better shape than before

    • Needs prompting to fix bugs/regressions


  • Communication

    • Needs help to manage time effectively

    • Participates in frontend technical conversations


  • Performance & Scalability

    • Needs help writing production-ready code

    • Has little to no experience writing large scale apps


Intermediate Frontend Engineer

Typically equates to 2 to 4 years of experience


  • Technical Skills

    • Needs minimal guidance to write modular, well-tested, and maintainable code


  • Leadership

    • Propose new ideas, needs guidance in performing feasibility analyses and scoping the work

    • Capable of leading medium sized features, bug fixes, and integrations with limited guidance from leads or seniors (Eg. Begin to show architectural perspective)

    • Should be striving to make the entire team more productive through their efforts. This might be through mentoring junior developers, or by improving the team's process, documentation, testing or tooling in a way that helps everyone in the team be more effective.


  • Code quality

    • Leave code in better shape than before (Eg. Leave tests in better shape than before: faster, more reliable, more comprehensive, etc.)

      • Strive to reduce complexity contained as much as possible: if a feature is complex, that's sometimes unavoidable, but Intermediate Developers show that they can reduce or mitigate complexity in their changes


    • Fix bugs/regressions without much prompting from team

    • Monitor overall code quality/build failures


  • Communication

    • Provide thorough and timely code feedback for peers, generally leaving minimal work for later reviews / maintainers

    • Able to communicate on technical topics and present ideas to the rest of the team

    • Proactive in asking for guidance from others when needed

    • Keep issues up-to-date with progress


  • Performance & Scalabilty

    • Writes production-ready code with minimal assistance

    • Fixes performance issues on GitLab.com with minimal guidance using our existing tools, and identify areas of improvements where needed


Senior Frontend Engineer

Typically equates to 4+ years of experience


  • Technical Skills

    • Write modular, well-tested, and maintainable code


  • Leadership

    • Propose new ideas, performing feasibility analyses and scoping the work

    • Capable of leading complicated features, bug fixes, and integrations with limited guidance from leads (Eg. Begin to show architectural perspective)

    • Should make the entire team more productive through their efforts. This might be through mentoring junior developers, or by improving the team's process, documentation, testing or tooling in a way that helps everyone in the team be more effective.


  • Code quality

    • Leave code in substantially better shape than before (Eg. Keep complexity contained as much as possible, Leave tests in better shape than before)

    • Fix bugs/regressions quickly

    • Monitor overall code quality/build failures


  • Communication

    • Provide thorough and timely code feedback for peers, leaving minimal work for later reviews / maintainers

    • Able to communicate clearly on technical topics and present ideas to the rest of the team

    • Keep issues up-to-date with progress


  • Performance & Scalability

    • Excellent at writing production-ready code with little assistance

    • Are able to fix performance issues on GitLab.com with minimal guidance using our existing tools, and improve those tools where needed




It doesn’t all quite make sense (e.g. junior developer, despite all the listed shortcomings requiring babysitting, somehow manages to ”leave code in substantially better shape than before”), but is an interesting exercise nonetheless.
Subscribe

  • (no subject)

    A hilarious piece of web comedy in the style of Monty Python. Can only be viewed on the author's web page, because privacy settings. But so worth it.…

  • (no subject)

    A very impressive demo of real-time noise suppression software for Linux called NoiseTorch: - audio demo on the Linux for Everyone podcast…

  • (no subject)

    Twitter is having fun:

  • Post a new comment

    Error

    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 0 comments