Is able to design basic functions, avoiding duplication across code bases and interface-breaking changes based on understanding of the overall service architecture.
Design: You are comfortable with the basics of code interface design, and are learning to be more intentional.
Reaction to Feedback: You understand the feedback given and applies it consistently to your work.
SDLC: Understand how certain design decisions affects SDLC in general.
Technical
L1Associate Software Engineer
L2
Software Engineer
Software Engineer
L3
Senior Software Engineer
Senior Software Engineer
L4
Lead Software Engineer
Lead Software Engineer
Software Architecture
The ability to interact and engage with architectural approaches of the organization.
Has a good understanding of, and designs functions that are aligned with, the overall service architecture.
Development: You consistently look for opportunities to learn from other projects and teams.
Design: You show a good intuition for code interface design.
Trade-offs: Identify different technical trade offs taken by adapting certain principle and best practices and start to build a mental model around it.
Development: You consistently look for opportunities to learn from other projects and teams.
Design: You show a good intuition for code interface design.
Trade-offs: Identify different technical trade offs taken by adapting certain principle and best practices and start to build a mental model around it.
Is able to consistently design code independently that is aligned with the overall service architecture.
Design: You have deep architectural and design pattern experience. You consult with team members only on more difficult designs. You set up new projects to ensure architectural success by anticipating future use cases and making design decisions that minimize the cost of future changes.Code: You are able to utilize abstractions and code isolation effectively.
Trade-offs: Makes pragmatic decisions about technical trade-offs within their own code, e.g. Weighs up the benefits of making code more abstract vs specific.
Reasons about making an API call from the client or from the server - it's easier from the client but core experience will be worse.
Design: You have deep architectural and design pattern experience. You consult with team members only on more difficult designs. You set up new projects to ensure architectural success by anticipating future use cases and making design decisions that minimize the cost of future changes.Code: You are able to utilize abstractions and code isolation effectively.
Trade-offs: Makes pragmatic decisions about technical trade-offs within their own code, e.g. Weighs up the benefits of making code more abstract vs specific.
Reasons about making an API call from the client or from the server - it's easier from the client but core experience will be worse.
Regularly works across teams to build a culture for iterative, autonomous development and future scaling.
Technical debt: You understand technical debt as a long-term budgeting and risk management tool. You lead on when to incur more and when to pay it down.
Development: You work with the architecture team to define cross- team architectural approaches. You sometimes employ prototyping for exploration of designs and work towards in cooperating new technologies.
Design: You help several teams make design decisions that minimize the cost of future changes.
Technical debt: You understand technical debt as a long-term budgeting and risk management tool. You lead on when to incur more and when to pay it down.
Development: You work with the architecture team to define cross- team architectural approaches. You sometimes employ prototyping for exploration of designs and work towards in cooperating new technologies.
Design: You help several teams make design decisions that minimize the cost of future changes.
Testing
The ability to understand and implement great testing practices.
Understands how to test code, and the valuable role that testing plays.
Taking responsibility: You've consistently ensured that your code passes tests before creating or merging pull requests.
Improving coverage: You've spotted small areas of low test coverage and patched them.
Testing your code: You consistently write solid unit tests, sometimes with help from more senior engineers.
Taking responsibility: You've consistently ensured that your code passes tests before creating or merging pull requests.
Improving coverage: You've spotted small areas of low test coverage and patched them.
Testing your code: You consistently write solid unit tests, sometimes with help from more senior engineers.
Understands the importance of a testing strategy, with growing levels of autonomy.
Taking responsibility: You've ensured that code committed by your immediate team is well tested and passing.
Improving coverage: You've improved test coverage in adjacent areas of code to your own without being asked.
Testing your code: You usually write detailed unit and functional tests covering edge cases as well as happy paths.
Taking responsibility: You've ensured that code committed by your immediate team is well tested and passing.
Improving coverage: You've improved test coverage in adjacent areas of code to your own without being asked.
Testing your code: You usually write detailed unit and functional tests covering edge cases as well as happy paths.
Independently testing, advising the rest of the team on quality of tests.
Taking responsibility: You consistently look for and can recall quality metrics to demonstrate your test coverage, and monitor in behalf of your team.
Improving coverage: You've worked to improve the quality of your own and your team's test coverage.
Testing your code: You always write full tests for your code unassisted, covering all edge cases even with complex functionality.
Taking responsibility: You consistently look for and can recall quality metrics to demonstrate your test coverage, and monitor in behalf of your team.
Improving coverage: You've worked to improve the quality of your own and your team's test coverage.
Testing your code: You always write full tests for your code unassisted, covering all edge cases even with complex functionality.
A growing leader within the team around testing strategy.
Advocating for testing: You're an internal go-to expert when teams are thinking through testing strategy for new products and problems.
Leading testing strategy: You've defined how your team writes and thinks through test coverage, including tooling and metrics. You've worked with other teams to ensure your strategy covers any crossover.
Advocating for testing: You're an internal go-to expert when teams are thinking through testing strategy for new products and problems.
Leading testing strategy: You've defined how your team writes and thinks through test coverage, including tooling and metrics. You've worked with other teams to ensure your strategy covers any crossover.
Technical Understanding & Prioritization
The ability to develop technical understanding and use this to priorities tasks appropriately.
Shows some confidence in technical understanding including the importance of prioritization.
Task prioritization: You can plan work tasks with help from team members and manager. You deliver based on the agreed priority of works tasks.
Work breakdown: You understand the importance of rightsizing tasks for incremental delivery plus continuous integration.
Technical collaboration: You communicate accurately about all technical subjects in your work.
Understanding code: You are able to gain context within the team's domain with occasional help from more senior engineers. You are comfortable with the basics of code interface design and are learning to be more intentional.
Task prioritization: You can plan work tasks with help from team members and manager. You deliver based on the agreed priority of works tasks.
Work breakdown: You understand the importance of rightsizing tasks for incremental delivery plus continuous integration.
Technical collaboration: You communicate accurately about all technical subjects in your work.
Understanding code: You are able to gain context within the team's domain with occasional help from more senior engineers. You are comfortable with the basics of code interface design and are learning to be more intentional.
Is able to display a clear technical confidence and understanding, prioritizes tasks and acts accordingly.
Task prioritization: You act according to task prioritization whilst noting task dependencies.
Work breakdown: In advance of starting, you ensure that tasks are appropriately sized for incremental delivery and continuous integration, with some help from team members and your manager
Technical collaboration: You can lead technical explanations when appropriate. You know when to listen and give space to team members.
Understanding code: You understand a good amount of the team's domain, and can gain sufficient context to work productively within that.
Task prioritization: You act according to task prioritization whilst noting task dependencies.
Work breakdown: In advance of starting, you ensure that tasks are appropriately sized for incremental delivery and continuous integration, with some help from team members and your manager
Technical collaboration: You can lead technical explanations when appropriate. You know when to listen and give space to team members.
Understanding code: You understand a good amount of the team's domain, and can gain sufficient context to work productively within that.
Is a technical and prioritization leader within the team, including taking some ownership of other team members' technical growth and development.
Task prioritization: You ensure tasks are prioritized correctly, and that dependencies are noted and well understood by the team, including at the epic level. You foster a culture of priority setting and highlight the importance of alignment with organizational strategy.
Work breakdown: You review projects critically, ensuring they are appropriately delineated and understood by the team.
Technical collaboration: You actively facilitate technical discussions between team members and have a deep familiarity with technical topics under discussion.
Understanding code: You understand your team's domain at a high level, including the breadth of services, how they interact, and data flows between systems. You understand adjacent domains as they affect your team.
Task prioritization: You ensure tasks are prioritized correctly, and that dependencies are noted and well understood by the team, including at the epic level. You foster a culture of priority setting and highlight the importance of alignment with organizational strategy.
Work breakdown: You review projects critically, ensuring they are appropriately delineated and understood by the team.
Technical collaboration: You actively facilitate technical discussions between team members and have a deep familiarity with technical topics under discussion.
Understanding code: You understand your team's domain at a high level, including the breadth of services, how they interact, and data flows between systems. You understand adjacent domains as they affect your team.
Is a technical and prioritization leader across a set of related team's domains, consistently pushing boundaries and exploring gaps in understanding.
Task prioritization: You ensures cross-team dependencies are understood by all relevant stakeholders. You foster a culture of priority setting across teams and highlight the importance of alignment with organizational strategy.
Work breakdown: You critically review work across multiple teams, ensuring it is appropriately broken down, and well understood.
Technical collaboration: You proactively seek out gaps in your technical understanding, and work with a variety of team members to fill those gaps.
Understanding code: You have expertise in a set of related team's domains, including the breadth of services, how they interact, and data flows between systems.
Task prioritization: You ensures cross-team dependencies are understood by all relevant stakeholders. You foster a culture of priority setting across teams and highlight the importance of alignment with organizational strategy.
Work breakdown: You critically review work across multiple teams, ensuring it is appropriately broken down, and well understood.
Technical collaboration: You proactively seek out gaps in your technical understanding, and work with a variety of team members to fill those gaps.
Understanding code: You have expertise in a set of related team's domains, including the breadth of services, how they interact, and data flows between systems.
Writing Code
The ability to contribute high quality code production environment.
Is able to write solid code across smaller tasks and tickets.
Language: You're committing quality code in at least one language.
Documentation: You've read documentation before asking for clarification. You've contributed to docs as you work.
Quality: Your code has generally followed correct syntax and structure, only requiring minor improvements.
Language: You're committing quality code in at least one language.
Documentation: You've read documentation before asking for clarification. You've contributed to docs as you work.
Quality: Your code has generally followed correct syntax and structure, only requiring minor improvements.
Is able to consistently write testable, readable code across larger more complex projects.
Language: You're committing quality code in at least one language and have a working understanding of other languages your team needs.
Documentation: You've regularly documented your code and looked to improve documentation elsewhere.
Quality: Your code has always followed correct convention, requiring only minor improvements. You've made trade-offs knowingly.
Language: You're committing quality code in at least one language and have a working understanding of other languages your team needs.
Documentation: You've regularly documented your code and looked to improve documentation elsewhere.
Quality: Your code has always followed correct convention, requiring only minor improvements. You've made trade-offs knowingly.
Is able to consistently write production-ready code across large, complex projects.
Mentoring: You have mentored several junior engineers around code quality.
Language: You're committing quality code in any language your team needs OR you're best in class at one language.
Documentation: Your code is consistently self-documenting where possible. You've regularly maintained, improved and extended existing documentation unprompted.
Quality: You're regularly trusted to lead complex and business-critical coding projects, including guiding others.
Mentoring: You have mentored several junior engineers around code quality.
Language: You're committing quality code in any language your team needs OR you're best in class at one language.
Documentation: Your code is consistently self-documenting where possible. You've regularly maintained, improved and extended existing documentation unprompted.
Quality: You're regularly trusted to lead complex and business-critical coding projects, including guiding others.
Is a go-to within the team and the wider organization across multiple codebases and languages.
Mentoring: You've actively mentored multiple senior engineers across the organization around code quality.
Language: You're best in class at your language of choice, and are committing quality code in other languages the organization needs.
Documentation: You've organized documentation for large code projects efficiently, advising others on best practices where needed.
Quality: You've actively mentored multiple senior engineers across the organization around code quality.
Mentoring: You've actively mentored multiple senior engineers across the organization around code quality.
Language: You're best in class at your language of choice, and are committing quality code in other languages the organization needs.
Documentation: You've organized documentation for large code projects efficiently, advising others on best practices where needed.
Quality: You've actively mentored multiple senior engineers across the organization around code quality.
Agile Working
You know about agile methodology and can apply an agile midest to all aspects of your work. You can work in fast-paced, evolving environment.
You know about agile methodology and the ways you can apply the principles in practice. You can take an open-minded approach; you know why iteration is important and can do it quickly. (Relevant skill level: awareness).
You know about agile methodology and the ways you can apply the principles in practice. You can take an open-minded approach; you know why iteration is important and can do it quickly. (Relevant skill level: awareness).
You have experience of working in agile, including an awareness of agile tools and how to use them. You can advise colleagues on how and why agile methods are used and be able to provide a clear, open and transparent framework in which teams can deliver. You can adapt and reflect and be resilient. You have the ability to see outside of the process. (Relevant skill level: working).
You can identify and compare the best processes or delivery methods to use, including measuring and evaluating outcomes. You know how to help the team to decide the best approach. You can help teams to manage and visualize outcomes, prioritize work and work to agreed minimum viable product (MVP), print and scope. (Relevant skill level: practitioner).
Security
The ability to understand and apply security principls,handle user data approperiately and report secuirity concerns.
_
_
Is able to understand the importance of security.
Knowledge: You understand basic security principles and apply them to your daily work.
User data: You understand the importance of handling user data and do so responsibly.
Reporting: You immediately report security concerns to manager or security teams.
Knowledge: You understand basic security principles and apply them to your daily work.
User data: You understand the importance of handling user data and do so responsibly.
Reporting: You immediately report security concerns to manager or security teams.
Is able to understand the importance of security and starts to see work through a security lens.
Knowledge: You understand general security principles and apply them to your daily work. You ask more senior engineers for help on making decisions that may have security implications.
User data: You understand the importance of handling user data and does so responsibly without exception.
Reporting: You immediately reports security concerns to manager or security teams.
Knowledge: You understand general security principles and apply them to your daily work. You ask more senior engineers for help on making decisions that may have security implications.
User data: You understand the importance of handling user data and does so responsibly without exception.
Reporting: You immediately reports security concerns to manager or security teams.
Stakeholder Management
The ability to ensure that teams are protected and expectations are set correctly.
_
_
Is able to keep tangential teams informed and expectations managed around everyday work updates. Uses judgment about others' reaction when disclosing information and opinions.
Is able to keep tangential teams informed and expectations managed around everyday work updates. Uses judgment about others' reaction when disclosing information and opinions.
Managing Goals and Expectations: You lead on successful projects with external clients, internal stakeholders or partners with a successful outcome, ensuring goals are understood throughout.
Foresight: You work to inform departments, stakeholders or clients of an issue they face without being asked or expected to do so.
Engendering Trust: You bring stakeholders or clients into a process in a way that makes best use of their time and their strengths.
Is able to keep tangential teams informed and expectations managed around everyday work updates. Uses judgment about others' reaction when disclosing information and opinions.
Managing Goals and Expectations: You lead on successful projects with external clients, internal stakeholders or partners with a successful outcome, ensuring goals are understood throughout.
Foresight: You work to inform departments, stakeholders or clients of an issue they face without being asked or expected to do so.
Engendering Trust: You bring stakeholders or clients into a process in a way that makes best use of their time and their strengths.
Known for being efficient and reliable, and doing what they say they will do. Proactively managed expectations even when it results in frustration or personal reputation risk.
Managing Goals and Expectations: You lead multiple smaller projects with external clients or internal stakeholders, with a successful outcome.
Foresight: You anticipate issues or requirements on projects in advance and work to raise those with key people outside your team. This has resulted in noticeable efficiency gains.
Engendering Trust: You run several small to medium sized projects in a leadership capacity, working closely with clients and stakeholders with positive reviews.
Managing Goals and Expectations: You lead multiple smaller projects with external clients or internal stakeholders, with a successful outcome.
Foresight: You anticipate issues or requirements on projects in advance and work to raise those with key people outside your team. This has resulted in noticeable efficiency gains.
Engendering Trust: You run several small to medium sized projects in a leadership capacity, working closely with clients and stakeholders with positive reviews.
Hiring & Org Design
The ability to understand needs of the business and ensure that your team can meet them.
_
_
_
A competent interviewer. Able to follow a structured hiring process, and make a decision.
Deploying teams: You've carved out an additional role for yourself or peers to fulfill a need that a team has.
Employer Brand: You've helped to establish the company as a good employer through promotion on stage or online. You've inputted into the company's careers pages.
Hiring: You are regularly part of hiring panels, and have been hiring manager for at least one hire that passed probation.
Deploying teams: You've carved out an additional role for yourself or peers to fulfill a need that a team has.
Employer Brand: You've helped to establish the company as a good employer through promotion on stage or online. You've inputted into the company's careers pages.
Hiring: You are regularly part of hiring panels, and have been hiring manager for at least one hire that passed probation.
non-Technical
Communication Skills
The ability to communicate well with those around you with sesnitivity to timeless, medium, brevity and tone.
Communicates effectively with immediate peers.
Keeping people informed: You keep immediate peers in the team informed as needed regarding workload and progress.
Looking for feedback: You explain your thought process carefully when required by a peer.
Delivering bad news: You spot blockers to your work and proactively let your immediate peers know.
Effective communicator: You are able to reflect on your own communication style.
Awareness: You know about the need to translate technical concepts into non-technical language and understand what communication is required for internal and external stakeholders.
Keeping people informed: You keep immediate peers in the team informed as needed regarding workload and progress.
Looking for feedback: You explain your thought process carefully when required by a peer.
Delivering bad news: You spot blockers to your work and proactively let your immediate peers know.
Effective communicator: You are able to reflect on your own communication style.
Awareness: You know about the need to translate technical concepts into non-technical language and understand what communication is required for internal and external stakeholders.
Communicates with wider team, feeds back on communication of others.
Keeping people informed: You communicate work updates from your peers across your wider team, and respond to feedback in a timely manner.
Looking for feedback: You consistently ask for critique on your thinking from a wider group, and inform the group which elements you're incorporating into your work.
Delivering bad news: You recognize when you need help from outside your immediate peers and asked for it effectively.
Mentoring communications: You are able to unpick the communication of others around you and offer advice and feedback.
Working: You can translate and communicate accurate information to technical and non-technical stakeholders. You know how to facilitate discussions within a multidisciplinary team, with potentially difficult dynamics. You can advocate for the team externally and manage differing perspectives.
Keeping people informed: You communicate work updates from your peers across your wider team, and respond to feedback in a timely manner.
Looking for feedback: You consistently ask for critique on your thinking from a wider group, and inform the group which elements you're incorporating into your work.
Delivering bad news: You recognize when you need help from outside your immediate peers and asked for it effectively.
Mentoring communications: You are able to unpick the communication of others around you and offer advice and feedback.
Working: You can translate and communicate accurate information to technical and non-technical stakeholders. You know how to facilitate discussions within a multidisciplinary team, with potentially difficult dynamics. You can advocate for the team externally and manage differing perspectives.
Communicates with organization, helps others in team to communicate Keeping people informed: You communicate on behalf of your team to the broader organization on important or divisive projects, handling any questions in a timely manner.
Looking for feedback: You proactively ask for feedback from important stakeholders in your organization early in your work.
Delivering bad news: You communicate changes of plan or slip in timelines to a broad group within your organization and manage expectations effectively until resolution.
Mentoring communicators: You set up processes around more effective communication for your immediate team, and manage its implementation. You proactively offer good feedback to peers on their communication methods.
Practitioner: You know how to listen to the needs of the technical and business stakeholders and explain them to each other. You can manage stakeholders’ expectations . You are flexible and capable of proactive and reactive communication. You know how to facilitate difficult discussions within your team or with diverse senior stakeholders.
Looking for feedback: You proactively ask for feedback from important stakeholders in your organization early in your work.
Delivering bad news: You communicate changes of plan or slip in timelines to a broad group within your organization and manage expectations effectively until resolution.
Mentoring communicators: You set up processes around more effective communication for your immediate team, and manage its implementation. You proactively offer good feedback to peers on their communication methods.
Practitioner: You know how to listen to the needs of the technical and business stakeholders and explain them to each other. You can manage stakeholders’ expectations . You are flexible and capable of proactive and reactive communication. You know how to facilitate difficult discussions within your team or with diverse senior stakeholders.
Communicates with the wider business, including change affecting the work of others, helps teams around them to communicate better.
Keeping people informed: You design the process of communication to communicate with the business around strategically important projects using appropriate mediums.
Looking for feedback: You communicate changes in plans, organizational structure or work situation which directly affects one or more people, and manage any fall out from that change ensuring all parties stay informed and content.
Delivering bad news: You communicate bad news to a group of reports or peers, ensuring that a strategy is in place to manage expectations and morale during the change. Your approach involves thoughtfully designed communication to the top levels of the organization.
Mentoring communicators: You regularly mentor others on communication technique, unpick poor communication in your wider organization and add process where needed. You're comfortable feeding back on the communication of your seniors.
Expert: You can mediate between people and mend relationships, communicating with stakeholders at all levels. You know how to manage stakeholder expectations and facilitate discussions across high risk and complexity or under constrained timescales. You can speak on behalf of or represent the community to large audiences inside and outside of government.
Keeping people informed: You design the process of communication to communicate with the business around strategically important projects using appropriate mediums.
Looking for feedback: You communicate changes in plans, organizational structure or work situation which directly affects one or more people, and manage any fall out from that change ensuring all parties stay informed and content.
Delivering bad news: You communicate bad news to a group of reports or peers, ensuring that a strategy is in place to manage expectations and morale during the change. Your approach involves thoughtfully designed communication to the top levels of the organization.
Mentoring communicators: You regularly mentor others on communication technique, unpick poor communication in your wider organization and add process where needed. You're comfortable feeding back on the communication of your seniors.
Expert: You can mediate between people and mend relationships, communicating with stakeholders at all levels. You know how to manage stakeholder expectations and facilitate discussions across high risk and complexity or under constrained timescales. You can speak on behalf of or represent the community to large audiences inside and outside of government.
Personality Traits
The ability to use your judgment to make decision and do things without needing to be told what to do.
Doesn't wait to be asked. Open minded about their own skillset.
Can-do attitude: You repeatedly demonstrate a positive attitude when given new projects.
Pro-activity in seeking help: If you're stuck on something, you seek help quickly from the correct party.
Follow through: You take on small pieces of work with ill-defined or unknown requirements and help to push through to a successful outcome.
Ownership: Consistent and reliable ownership of the problem through to the solution within the team. Can be trusted to deliver on promises and follow up on next steps.
Teamwork: Helps their teammates when requested. Gives or shares credit where due.
Can-do attitude: You repeatedly demonstrate a positive attitude when given new projects.
Pro-activity in seeking help: If you're stuck on something, you seek help quickly from the correct party.
Follow through: You take on small pieces of work with ill-defined or unknown requirements and help to push through to a successful outcome.
Ownership: Consistent and reliable ownership of the problem through to the solution within the team. Can be trusted to deliver on promises and follow up on next steps.
Teamwork: Helps their teammates when requested. Gives or shares credit where due.
Relentlessly positive in pursuing new ways to solve a problem.Can-do attitude: You see opportunity in every piece of work, however outwardly mundane or solved.
Pro-activity in seeking help: When your team is stuck on something, you are quick to suggest that you all adjust focus, re-frame a problem or talk to someone new.
Follow through: You lead medium to large projects with unknown requirements and helped drive to a successful outcome.
Ownership: Consistent and reliable ownership of the problem through to the solution within and across teams, peers, and partners. No excuses. Accountable and positive in all conditions. Takes ownership of problems and challenges within their remit and doesn't apportion blame to others. Identifies risks and issues and proactively finds solutions to any obstacles.
Teamwork: When requested, helps their teammates overcome obstacles, resolve blockers, and complete work tasks. Gives or shares credit where due.
Pro-activity in seeking help: When your team is stuck on something, you are quick to suggest that you all adjust focus, re-frame a problem or talk to someone new.
Follow through: You lead medium to large projects with unknown requirements and helped drive to a successful outcome.
Ownership: Consistent and reliable ownership of the problem through to the solution within and across teams, peers, and partners. No excuses. Accountable and positive in all conditions. Takes ownership of problems and challenges within their remit and doesn't apportion blame to others. Identifies risks and issues and proactively finds solutions to any obstacles.
Teamwork: When requested, helps their teammates overcome obstacles, resolve blockers, and complete work tasks. Gives or shares credit where due.
Refuses to believe that anything is unachievable. Infectious desire to activate and progress. Like a rocket: just light the fuse.
Can-do attitude: You're constantly creating new opportunities for yourself and those around you. Your team is celebrated for innovation as a result of your contributions.
Pro-activity in seeking help: You recognize a lack of expertise in yourself and your organization, and pro-actively found that expertise in areas not given to you. This leads to a successful outcome on more than one occasion.
Follow through: You adapt your skillset and knowledge to lead large or complex projects to a successful outcome.
Ownership: Committed ownership of the problem through to the solution within and across teams, peers, and partners. No excuses. Accountable and positive in all conditions. Takes ownership of problems and challenges within their remit and outside their domain and doesn't apportion blame to others. Thinks about how to help Intercom succeed, not just their specific team. Identifies and anticipates risks and issues and proactively finds solutions to any obstacles.
Teamwork: Consistently helps their teammates overcome obstacles, resolve blockers, and complete work tasks. Gives or shares credit where due.
Can-do attitude: You're constantly creating new opportunities for yourself and those around you. Your team is celebrated for innovation as a result of your contributions.
Pro-activity in seeking help: You recognize a lack of expertise in yourself and your organization, and pro-actively found that expertise in areas not given to you. This leads to a successful outcome on more than one occasion.
Follow through: You adapt your skillset and knowledge to lead large or complex projects to a successful outcome.
Ownership: Committed ownership of the problem through to the solution within and across teams, peers, and partners. No excuses. Accountable and positive in all conditions. Takes ownership of problems and challenges within their remit and outside their domain and doesn't apportion blame to others. Thinks about how to help Intercom succeed, not just their specific team. Identifies and anticipates risks and issues and proactively finds solutions to any obstacles.
Teamwork: Consistently helps their teammates overcome obstacles, resolve blockers, and complete work tasks. Gives or shares credit where due.
Asks a lot, expects the impossible. Drives others to create their best work. Sees opportunities in everything.
Can-do attitude: You take ill-defined requirements and lead a large group within your organization to make progress on them.
Pro-activity in seeking help: You build relationships with people across your organization without being asked, expressly for the purpose of boosting your ability to achieve great results.
Follow through: You're deeply involved in projects which require your ability to move through uncertainty. You adapt your skillset appropriately for those projects, morphing into what the projects need you to be.
Ownership: Own it for Intercom - expansive, committed ownership of our problems, processes, and opportunities. No excuses. Accountable and positive in all conditions. Takes ownership of problems and challenges within their remit and outside their domain and doesn't apportion blame to others. Thinks about how to help Intercom succeed, not just their specific team. Identifies and anticipates risks and issues and proactively finds solutions to any obstacles.
Teamwork: Consistently helps their teammates overcome obstacles, resolve blockers, and complete work tasks. Gives or shares credit where due.
Can-do attitude: You take ill-defined requirements and lead a large group within your organization to make progress on them.
Pro-activity in seeking help: You build relationships with people across your organization without being asked, expressly for the purpose of boosting your ability to achieve great results.
Follow through: You're deeply involved in projects which require your ability to move through uncertainty. You adapt your skillset appropriately for those projects, morphing into what the projects need you to be.
Ownership: Own it for Intercom - expansive, committed ownership of our problems, processes, and opportunities. No excuses. Accountable and positive in all conditions. Takes ownership of problems and challenges within their remit and outside their domain and doesn't apportion blame to others. Thinks about how to help Intercom succeed, not just their specific team. Identifies and anticipates risks and issues and proactively finds solutions to any obstacles.
Teamwork: Consistently helps their teammates overcome obstacles, resolve blockers, and complete work tasks. Gives or shares credit where due.
Business Context
The ability to look for, understand and use the needs and constraints of the business in your work.
Knows how the business operates on a high level as well as their core team metrics, and can use that knowledge in daily decisions, with help.
Curiosity and acumen: You make an effort to understand why the business exists, how it makes money and the history to date. You know some top-line numbers pertinent to your team.
Balancing needs: You balance the needs of your user with the constraints of the business in several small projects. You're pragmatic in the face of having to find a middle ground.
Curiosity and acumen: You make an effort to understand why the business exists, how it makes money and the history to date. You know some top-line numbers pertinent to your team.
Balancing needs: You balance the needs of your user with the constraints of the business in several small projects. You're pragmatic in the face of having to find a middle ground.
Understands how the business works and the goals of their team. Is able to relate that to their own work.
Curiosity and acumen: You have a strong level of knowledge in domains in which you're working within the company (business economics, customers, constraints and processes), and a good understanding outside those areas.
Balancing needs: You push for user-focused solutions, with an eye on business needs across several larger projects, possibly taking a lead position. Product and business stakeholders agree you're able to make good tradeoffs based on your knowledge.
Curiosity and acumen: You have a strong level of knowledge in domains in which you're working within the company (business economics, customers, constraints and processes), and a good understanding outside those areas.
Balancing needs: You push for user-focused solutions, with an eye on business needs across several larger projects, possibly taking a lead position. Product and business stakeholders agree you're able to make good tradeoffs based on your knowledge.
Is actively finding business insights that they need for their work, using people from outside their team. Helping team-mates to understand the business.
Curiosity and acumen: You can explain how the business works, what the strategy is and how that relates to your work, in conversations with stakeholders internally and externally. You seek extra understanding from beyond your team about areas of the business you don't understand.
Balancing needs: You use your understanding of both product and business needs, to lead at least one major project with significant stakeholder interest. You're driven to solutions that meet all the required needs.
Curiosity and acumen: You can explain how the business works, what the strategy is and how that relates to your work, in conversations with stakeholders internally and externally. You seek extra understanding from beyond your team about areas of the business you don't understand.
Balancing needs: You use your understanding of both product and business needs, to lead at least one major project with significant stakeholder interest. You're driven to solutions that meet all the required needs.
Actively works to understand all aspects of the business. Autonomously looks for data wherever they need to aid their own and their team's understanding. Coaching others in using business needs.
Curiosity and acumen: You take significant effort learning about how and why the business functions the way it does. You bring this knowledge into your work, meaning your presentations always account for stakeholder concerns in advance and engender trust. You help your team uncover business insights to use in their work.
Balancing needs: You are strategically involved in product and feature definition, using the context that your product or client has to significantly change how the work evolves. You're driven to solutions around difficult project constraints that no-one else has seen.
Curiosity and acumen: You take significant effort learning about how and why the business functions the way it does. You bring this knowledge into your work, meaning your presentations always account for stakeholder concerns in advance and engender trust. You help your team uncover business insights to use in their work.
Balancing needs: You are strategically involved in product and feature definition, using the context that your product or client has to significantly change how the work evolves. You're driven to solutions around difficult project constraints that no-one else has seen.
Giving Feedback
The ability to consistently give good feedback, both positive and constructive.
_
_
_
Able to give honest feedback to team members when needed. Understands the position they're in and thinks about appropriate phrasing accordingly.
Understanding best practices: You've read known best practices on effective feedback giving, and can talk confidently about their values.
Feedback on work: Your feedback to peers on their work is honest, actionable and timely. You put the needs of the project over personal inhibitions. You're comfortable with having your mind changed.
Constructive criticism: You can point to several times when you've given a peer constructive criticism in a discrete, timely and actionable manner.
Useful praise: You have repeatedly been quick to praise good work in peers.
Understanding best practices: You've read known best practices on effective feedback giving, and can talk confidently about their values.
Feedback on work: Your feedback to peers on their work is honest, actionable and timely. You put the needs of the project over personal inhibitions. You're comfortable with having your mind changed.
Constructive criticism: You can point to several times when you've given a peer constructive criticism in a discrete, timely and actionable manner.
Useful praise: You have repeatedly been quick to praise good work in peers.