Junior Frontend Engineer Mid Frontend Engineer Senior Frontend Engineer Principal Frontend Engineer Team lead

● Understanding/reading/wri ng English C1 ● Understanding/reading/wri ng English C1 or C2 This is not an engineering ladder role but a set
or C2 ● Excellent grasp of working with Linux or Windows OS of responsibilities and organizational skills that
may be taken by an engineer
General ● Good grasp of working with Linux or
Windows OS

Technical
requirements
 ● HTML ● Modern CSS ● Expert Javascript .all() ● Web Assembly
● CSS ● Advanced Javascript .all() oReac ve Paradigm
● Basic Javascript .all() ○ Prototypes oFactory, Decorator and Observer design pa erns
o Variables scope and hois ng ○ Async/Promises oTranspilers
o Operators and Primi ves ○ Closures ● Expert TypeScript .all()
o Data Structures ○ Object and Func onal Paradigms o Can solve everything in Collec on of TypeScript type
o Na ve Methods ○ Singleton and Module Design Pa erns challenges with online judge
● Basic TypeScript .all() ● Advanced TypeScript .all() ● Expert React .all()
o Primi ve types ○ Type Narrowing o Routers
o Arrays ○ Func on overloads o SSR
o Objects ○ Solid grasp of Crea ng types from types sec on of o Advanced State Management: Design & Architec ng
o Union Types the handbook: TypeScript: Documenta on - Crea ng ● Progressive Web Apps
o Interfaces Types from Types ● Server Side Rendering
o Type Asser ons ● Advanced React .all() ● Advanced Build Tools .some()
● Basic React .all() ○ Hooks o NX
o Create React App ○ Context o Lerna
Development o JSX ○ State Management o Yarn Workspaces
o Components and Component Life Cycle ○ Refs o Deno
o Props vs State ○ Render Props o Snowpack
o Condi onal Rendering ○ High Order Components o RushJS
o Composi on vs Inheritance ○ Portals ● Can implemented an component library from scratch
o Basic Hooks ○ Error Boundaries
● Git ○ Fiber Architecture
● Clean Code ○ API Calls
● Pull Requests ○ Forms
● Code Reviews ● Web Security
● Familiarity with styled component library ● Package Managers
like MaterialUI ● CSS Preprocessors
● Build Tools
● Tes ng .some()
○ React Tes ng Library
○ Jest
○ Cypress or Playwright

● Writes correct and clean code with
guidance; consistently follows stated best
prac ces
● Focus on growing as an engineer, learning
existing tools, resources, and processes
● Has no responsibility for the final success
of the project/feature
● Executes tasks precisely in accordance
with the defined processes
Responsibili es and
expecta ons
● Accepts and understands feedback they
receive
● Ac vely communicates their progress
and contributes to team group
Organiza onal and so skills discussions with ques ons
● Asks for input on task priori es
● Defines tasks with assistance of a more
senior team member
● Storybook
● Understand high-level capabili es of other frontend
frameworks like Angular and Vue
● In-depth knowledge of styled component library like
MaterialUI
● Par cipates in technical design of features with
guidance
● Able to own small-to-medium features from technical
design through comple on;
● Writes correct and clean code
● Makes steady progress on tasks; knows when to ask
for help in order to get themselves unblocked
● Doesn't flail while debugging.
● Has the ability to plan work, meet deadlines and be
accountable for deliverables
● Ability to improvise outside of defined process if
needed for the successful comple on of tasks
● Basic understanding of domains of work of other
teams and how they are cross-dependent with your
team
● Understands and makes well-reasoned design decisions and
tradeoffs in their area; able to work in other areas of the
codebase with guidance.
● End-to-end responsibility on projects of increasing complexity;
contributes to common code
● Able to iden fy, diagnose and put in place ac on plans to
address issues before they become too difficult or costly to
solve.
● Confident balancing taking on technical debt with serving
customer needs and the wider business strategy; Able to
predict some of the possible risks and problems of own work
and others and be able to prevent/communicate them
● Demonstrate good communica on and collabora on skill
● Point of contact for mul ple projects
● Help colleagues and guides them to solve problems and to
understand where tradeoffs can be made
● Can accurately define which tasks are be er to be delegated to
the more junior team members
● Can define tasks for other team members if needed
● Have a good understanding of domains of work of other teams
and how they are cross-dependent with your team.
● Sets direc on at the project/service level and
consistently influences decision-making
● Iden fies and proac vely tackles technical debt
before it grows into debt that requires
significant up-front work to resolve
● Makes others be er through code reviews,
thorough documenta on, technical guidance,
and mentoring or serving as a Tech Lead on a
project
● Iden fies and proposes strategies around
technical problems affec ng their team,
communicates standards and gets buy-in on
solu ons
● Consistently able to reduce the complexity of
projects, services, and processes in order to get
more done with less work
● Creates architecture that enables many
poten al futures without knowing exactly what
the future is
● Known for drama-free launches
● Demonstrate excellent communica on and
collabora on skills, and can explain their work
to both technical and non-technical audiences
● Have a very good understanding of domains of
work of other teams and how they are
cross-dependent with your team. Able to make
proposals for improvement to management.
● Primarily focused on team members.
People and their growth is main focus for
this role
● Can act as a center „point of contact“ for
mul ple team projects
● Par cipates in career planning
promo ons and coaching
● Par cipa on in technical and architecture
decisions
● Par cipa on in performance reviews of
team members
● One-on-one interviews and coaching of
team members
● Aligns with other team leads and
management in achieving roadmap and
company goals
● Drives and directs group discussions to
ensure effec ve communica on amongst
team
● Proac vely gives feedback and can use
their good judgment to make ac onable
improvements
● Demonstrate excellent communica on
and collabora on skills, and can explain
 ● Can priori ze components of their task work and
focuses on the most important things without senior
input
● Clearly communicates status and blockers
● Provide ac onable feedback to peers and shares
knowledge
● Proac vely asks for feedback and is able to use their
good judgment to make ac onable improvements
Note: all requirements down-the-ladder are considered as subsets. For example, requirements for mid includes all the requirements for junior.
Junior and Mid level engineers are expected to focus more on learning while Senior and Principal engineers are expected to create an impact with learned skills
● Proac vely gives feedback and can use their good judgment to
make ac onable improvements
● Scopes and stages work into well-defined milestones to avoid a
monolithic deliverable
● Regularly delivers so ware on- me and is constantly working to
make accurate es mates and deliver on those es mates.
● Proac vely gives feedback and can use their
good judgment to make ac onable
improvements
● Self-mo vated to the point that they create new
work (for themselves and some mes others)
and have their own vision for what needs to be
done
their work to both technical and
non-technical audiences
● Knows how to par cipate in ac ve
listening and give construc ve feedback
● Have an excellent understanding of
domains of work of other teams and how
they are cross-dependent with your
team. Able to make proposals for
improvement to management.