Revelo: Engineering Ladder

Scope & Impact

• Writes code and tests according to project standards and practices.

Technical Execution

• Debugs and is capable of solving simple bugs.
• Participates in the development of simple tasks.

Ownership & Autonomy

• Can put code into a production environment and take care of possible bugs and improvements.

Leadership & Collaboration

• Asks for help only when needed and learns from it.
• Is receptive and open to suggestions for improvement in code reviews.
• Participates in team ceremonies, and is not just a listener.

Scope & Impact

• Develops, delivers, and maintains new features.

Technical Execution

• Understands the architecture of applications related to their team according to their specialty and the interfaces between applications.
• Makes constant deliveries even within the same significant feature.
• Conducts code reviews that help maintain area standards and practices.
• Develops code that is concise, clear, tested, and easy for others to understand.

Ownership & Autonomy

• Is responsible for the complete code cycle: development, testing, deployment, and subsequent corrections or improvements.
• Acts on bugs and problems reported by third parties, following the department's processes.

Leadership & Collaboration

• Discusses scope with the Product team and helps estimate feature complexity.
• Clearly and actively communicates the status of the activities for which they are responsible to the team and the manager. Example: informs about progress during daily meetings and, at any time by message, impediments or unforeseen situations.
• Builds a good relationship with the people on the team: with Tech and Product on a day-to-day basis and Operations to resolve bugs. Example: promotes effective communication, avoiding looking for blame and solving problems. Responds to directly communications (slack, email, etc) respectfully.

Scope & Impact

• Independently responsible for the complete project and feature delivery cycle, including code design, development, testing, deployment, and tracking.

Technical Execution

• Improves code quality, testability, and maintainability whenever possible. Example: makes suggestions for technical improvements during housekeeping meetings and during task development.
• Conducts code review observing the impact on the current code. Example: code design; quality of test coverage of new code; cohesion; performance implications; security implications.
• Understands the architecture of the company's applications to the point of knowing how to develop features and solve bugs between application integrations according to their specialty.
• Is proficient in one or more of the technologies used at the company. (E.g. Ruby, Rails, Javascript, Python, Vue.js, Kotlin, Dart, or Flutter). Example: messaging via Rabbit MQ, use of sidekiq for queues and async tasks, BFF, use of services, presenters, queries, value objects, and other patterns, SOLID, Everest, Unit tests with Jest, native platform (Android/IOS), etc.

Ownership & Autonomy

• Mainly works on team priorities helping the team to deliver fast.
• Estimates and manages the time and risk of the deliveries for which they are responsible. Makes the squad and the manager aware as soon as possible about unplanned risks (E.g. delivery delay or scope increase)

Leadership & Collaboration

• Ensures that knowledge is shared with the team and is not positioned as a single point of failure. (E.g.: communicating with teams and stakeholders via Slack and creating wikis)
• Crosses team or area boundaries to solve problems. Scales up issues that have a broader scope. Example: during technical refinement, participates in discussions about the technical solution, helps define which tasks need to be done, and identifies risks. During development, the tech team communicates about changes in the daily implementation, by message on Slack or huddle.
• Participates actively and relevantly in team ceremonies. Example: helps define the technical solution and tasks, identifies opportunities for improvement, and suggests actions in the retrospective. Anticipates technical and product issues in refinement.

Scope & Impact

• Leads or significantly contributes to large projects, typically projects with multiple people and/or multiple teams.
• Is an expert in a technical area. Mastery of the architecture, tools, libraries and standards of one or more technologies used in Revelo. It is capable of designing solutions with multiple components/services interacting via APIs. Knows the inner workings of parts of the framework/library, best practices and ways to ensure good performance. Example: defines services and responsibilities, collaborates on architecture definitions, has extensive knowledge in architectural patterns, MVC, DDD, Clean Architecture.

Technical Execution

• Is recognized by those closest to them for high quality and impactful contributions.
• Can solve complex problems in several ways, such as scale, uncertainty, significant context, and integration between different software.
• Understands the company application architecture in detail. Knows why the architecture is that way and how the applications are related. Can propose and implement improvements in this architecture. Example: identify opportunities for improvement, present a change plan (from short to long term) and carry out the implementation, when possible.
• Analyzes, proposes, and implements new technology (tools, libraries, services, etc.) that boost the product or the team's productivity.
• Can give precise predictability of deliveries.

Ownership & Autonomy

• Prioritizes the essential things for the company and the area and does not waste energy on unimportant tasks. Example: tasks that move the business needle or architecture tasks that facilitate development or reduce risks. Know the best time to attack technical debt.
• Estimates and manages project schedule and risk.

Leadership & Collaboration

• Builds a good relationship with stakeholders: customers, product managers, or people close to them. Helps them identify technical risks and clarify ambiguities/lapses in business rules.
• Works with other members of the tech team to solve impediments to the delivery of tasks. Example: during daily meetings (or at any time) it monitors the progress of the tasks of the entire tech team, identifies when it is out of the plan and acts to assist in the evolution/delivery of the task.
• Assists the manager in evaluating the technical performance of other developers.

Team Building

• Provides technical mentoring and can improve team members' skills. Example: recommendation of study materials, constant recommendation of talks, people, and blogs to follow. Do 1:1 or pair-programming for training.
• Delegates tasks to people or teams responsible for the context and maintains the visibility of the issue (E.g. oncall, bugs, emergencies, everyday tasks).
• Advises the software manager with insights and recommendations to improve the team. Example: Gives technical feedback about team members, suggests improvements to ceremonies, and helps with product decision-making.

Technical Execution

• Influences leaders on technology strategy.
• Ensures technical designs are validated for major projects and advises teams to improve execution.
• Defines technical strategy and executes to improve products, infrastructure or processes.

Scope & Impact

• Demonstrated success in leading large or strategic business domains that had a clear impact on business success.
• Sets an architectural direction for the company and helps develop systems based on it.
• Has a strong track record of influencing and delivering projects with business impact and priority, has managed projects with a small number of developers.

Leadership & Collaboration

• Uses negotiation and patience to collaborate with other leaders, ensuring the process and being an example to others.
• Collaborate across multiple teams and disciplines to solve problems and resolve technical debates.
• Stay tuned for changes in the company to anticipate and prevent obstacles instead of hiding them from the team.

Team Building

• Mentor other engineers of levels immediately below yours (Forms new Technical Leaders).
• Form multidisciplinary teams or different teams for relevant own projects.