Mattermost Handbook
Need help?How to spend company moneyHow to update the HandbookRelease overview
0.2.1
0.2.1
  • Mattermost Handbook
  • Company
    • About Mattermost
      • List of terms
      • Business model
      • Mindsets
    • "How to" guides for staff
      • How to set up a 1-1 channel
      • How to update the handbook
      • How to manage Handbook notifications
      • How to change mobile device
        • How to handle a lost mobile device
      • How to do a mini-retrospective
      • How to autolink keywords in Mattermost
  • Operations
    • Company operations
      • Areas of Responsibility
      • Mattermost Leadership Team (MLT)
        • MLT cadence
      • Company measures
        • Metrics definitions
        • FY23 goals board
        • MLT metrics
      • Company cadence
      • Company policies
        • Community response policy
        • Security policy
      • Company processes
        • Issue/solution process
        • Company agreements
        • Publishing
          • Public web properties
          • Publishing guidelines
            • Brand and visual design guidelines
            • Voice, tone, and writing style guidelines
              • Contribute to documentation
            • Confidentiality guidelines
          • Post-publication quality control process
      • Handbook processes and policies
        • Handbook onboarding
      • Fiscal year planning
    • Research and Development
      • Organization
        • Tech Writing
        • Data engineering
        • Delivery
        • Cloud Platform
        • Site Reliability Engineering
        • GRC
        • Product Security
        • Security Operations
      • Processes
        • Feature Labels
      • Product
        • Product planning
          • Product philosophy and principles
          • Prioritization process
          • Release planning process
          • Roadmap views
          • Release plan
          • Launch plan
          • Feature requests
        • Development process
          • Mobile feature guidelines
          • Deprecation policy
          • Mattermost software requirements process
          • Jira ticket lifecycle
          • Creating new Jira bug tickets
            • Priority levels for tickets
            • Jira fix versions
        • Release process
          • Release overview
          • Feature release process
          • Dot release process
          • Security release process
          • Mobile app release process
          • Desktop app release process
          • Release tips
          • Release scorecard definitions
        • How-to guides for Product
          • How to use productboard
          • How to record a roadmap video
          • How to update integrations directory
          • How to write a feature release announcement
        • Product Management team handbook
          • Product Management Areas of Ownership
          • Product Manager onboarding
          • Product Manager levels
          • Professional development
        • Product Design team handbook
          • Product Design levels
        • Technical Writing team handbook
          • Work with us
          • User interface text guidelines
          • Documentation style guide
          • Our terminology
          • Guidelines for PMs and developers
          • Guidelines for community contributions
          • Technical Writer levels
          • Docathon 2021
            • Getting started with contributing
        • Growth
          • A/B testing methodology
          • PQL definition
        • Analytics
          • Product Analyst Engineer levels
          • Looker
            • Dashboards
            • Explores
          • Telemetry
        • Developer relations
        • Product team hangouts
      • Engineering
        • Infrastructure engineering
          • Cloud infrastructure cost KPIs
          • Cloud data export process
          • Cloud churn process
          • Reliability Manifesto
          • Production Readiness Review
          • Infrastructure Library
        • Integrations team processes
        • Plugin release process
        • Data Engineering
        • Sustained Engineering
          • On call
        • How to go to a conference
        • Public speaking
        • Core contributor expanded access policy
      • Quality Assurance
        • QA workflow
        • QA testing tips and tools
        • Rainforest process
    • Messaging and Math
      • How-to guides for M&M
        • How to create release announcements
        • How to create screenshots and GIFs
        • How to write Mattermost case studies
        • How to write guest blog posts for Mattermost apps and services
        • How to write Mattermost recipes
        • How to compose tweets
        • How to create a split test for web page
        • How to run meetups
        • How to run executive dinners
      • Checklists for M&M
        • Blog post checklist
        • Bio checklist
      • Mattermost websites
      • Demand generation reporting
      • M&M Asana guidelines
      • Content marketing
        • How to use the editorial calendar
        • Content development and distribution
        • Video content guidelines
        • How to contribute content
    • Sales
      • Deal Desk
      • Partner programs
      • Lead management
    • Deployment Engineering
      • Overview
      • Workflows
      • Frequently Asked Questions
      • Playbook for MME Sev 1 Outages
      • Status Update Template
    • Program Management
    • Customer Success
      • Customer Support
    • Legal
      • Contracts
      • Ironclad Basics
        • Company-Wide Workflows
        • Sales Contracts and Workflows
        • Signing a Contract and Contract Repository
    • Finance
      • Budget
      • How to use Airbase
        • Access Airbase
        • Navigate Airbase
        • How to submit a purchase request
        • How to submit a reimbursement request
        • How to review a reimbursement request
        • Vendor portal guide
        • Frequently asked questions
      • Onboarding
        • Vendor onboarding
        • ROW staff onboarding
      • Staff member expenses
        • How to spend company money
        • How to spend company money: Internships
        • Corporate credit card policy
        • How to access Airbase
        • Gifting policy
        • How to book airfare and travel
        • How to reimburse the company
        • How to convert currencies
        • How to get paid
      • Arrange a Bounty Program
      • Naming files and agreements
      • Risk management
        • Mattermost U.S. consulting agreements
      • Operations playbook
    • Security
      • Policies
      • Privacy
        • Data deletion requests
        • Data subject access requests
      • Product Security
        • Product Vulnerability Process
        • Working on security-sensitive pull requests
        • Secure Software Development guide
      • Security Operations
        • User guides
    • Workplace
      • PeopleOps
        • HR cadences
        • HR systems
        • HR Processes
        • Working at Mattermost
          • Onboarding
            • Things everyone must know
            • Staff onboarding
            • Engineer onboarding timeline and expectations
            • Manager onboarding
            • Frequently asked questions
          • Learning and development
          • Mattermost communication best practices
          • Paid time off
            • Out of office email example
          • Travel
            • Business travel insurance
          • Leaves of absence
            • Pregnancy leave
            • Baby bonding parental leave
            • Jury duty
          • Workplace program
          • Relocation
          • Total rewards
        • Performance reviews
          • Formal review process
          • New staff performance review
          • Informal review process
        • Transfers and promotions
        • Offboarding instructions for managers
        • People compliance
      • People policies
      • Groups
        • Staff Resource Groups
      • Approvals and iteration
      • IT
        • IT helpdesk
        • Hardware and software purchases
        • Hardware buy back policy
        • Software systems
  • Contributors
    • Contributors
      • Equity, diversity, and inclusion
      • How to contribute to Mattermost
        • Community Content program
        • Documentation contributions
        • Help Wanted tickets
        • Localization
        • Contribution events
      • Mattermost community
      • Contributor kindness
      • Community systems
      • Guidelines and playbooks
        • Social engagement guidelines
        • Contribution guidelines and code of conduct
        • Mattermost Community playbook
        • How to run a Hackathon
        • Hacktoberfest event organizer guide for Mattermost
    • MatterCon
      • Staff information privacy management
      • Mattermost events code of conduct
      • MatterCon2021
    • Join us
      • Ice-breakers
      • Help Wanted tickets
      • Localization
      • Mattermost GitHub sponsorship
      • Things candidates should know
      • Staff recruiting
      • Recruiting cadences
        • Product Manager hiring process
      • Exec recruiting
        • EA logistics
  • Help and support
    • Contact us
Powered by GitBook
On this page
  • Level 1: Product Analyst I
  • Level 2: Product Analyst I
  • Level 3: Product Analyst II
  • Level 4: Product Analyst II
  • Level 5: Senior Product Analyst
  • Level 6: Senior Product Analyst
  • Level 7: Staff Product Analyst
  • Level 8: Principal Product Analyst
  • Level 9: Distinguished Product Analyst

Was this helpful?

Edit on Git
Export as PDF
  1. Operations
  2. Research and Development
  3. Product
  4. Analytics

Product Analyst Engineer levels

These levels serve to help Product Analysts assess their opportunities for career growth in the Product Analytics function. The levels below follow a growth track in the art and craft of Product Analysts and not in a person management track.

The level descriptions below are transferable to comparable analyst roles, such as a Product Analytics Engineer and a Data Analyst.

Level 1: Product Analyst I

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Executes defined tasks across the data analytics stack.

High Impact

Supervision: "How much do I rely on my manager?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high impact.

Receives detailed instruction on most tasks. Asks appropriate questions, and knows when to stop and ask for help. Works in cooperation with peers at the same level with ease. Utilizes the knowledge of others with more experience.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Works effectively in teams to align priorities and manage execution.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans across staff, open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Considers the customer's perspective when making decisions. Knows when to ask clarifying questions.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Regularly participates in team discussions for ongoing feature work. May lead discussions on smaller topics. Learns new skills and establishes goals and context quickly by asking precise questions.

Level 2: Product Analyst I

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Influences and executes defined tasks and features across the data analytics stack.

High Impact

Supervision: "How much do I rely on my manager?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high impact.

Receives general instruction on day-to-day work, and detailed instruction on new assignments or unfamiliar tasks. Works in cooperation with peers at the same level with ease. Utilizes the knowledge of others with more experience.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Works effectively in teams to align priorities and manage execution.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans across staff, open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Understands and applies basic level best practices for customer impact within their daily work. Will ask for input on more complicated topics.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Regularly participates in team discussions for ongoing feature work. May lead discussions on smaller topics. Actively seeks out tasks and projects that work towards opportunities for growth.

Level 3: Product Analyst II

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Designs, leads and delivers high impact features and changes across the data infrastructure stack.

High Impact

Supervision: "How much do I rely on my manager?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high impact.

Receives general instruction on new assignments or unfamiliar tasks. Participates in cross-functional groups towards building significant new functionality.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Begins to work directly with PM, Engineering, and GTM, aligning the data modeling and analysis done by the team, with product, engineering and GTM requirements.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans across staff, open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Can navigate moderately complex decisions and thought process about how features and implementations bring customer value, and can make decisions in these areas independently. Starts to understand and contribute to cross-feature and/or cross-team implications of customer impact.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Drops fluidly into team projects, ramps quickly and leads initiatives to successful outcomes. Leads discussions on small and mid-size topics. Participates actively in discussion and efforts that cross teams in Engineering, Product, and GTM. Actively seeks out tasks and projects that work towards opportunities for growth.

Level 4: Product Analyst II

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Designs, leads and delivers high impact features and changes across the data infrastructure stack.

High Impact

Supervision: "How much do I rely on my manager?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high impact.

Receives minimal instruction. Participates in cross-functional groups towards building significant new functionality.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Begins to work directly with PM, Engineering, and GTM, aligning the data modeling and analysis done by the team, with product, engineering and GTM requirements.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans across staff, open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Can navigate moderately complex decisions and thought process about how features and implementations bring customer value, and can make decisions in these areas independently. Starts to understand and contribute to cross-feature and/or cross-team implications of customer impact.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Drops fluidly into team projects, ramps quickly and leads features to successful outcomes. Leads discussions on small and mid-size topics. Participates actively in discussion and efforts that cross teams in Engineering, Product, and GTM. Proactively identifies opportunities for growth, intentionally taking on unfamiliar tasks.

Level 5: Senior Product Analyst

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Sets and delivers architectural vision for high impact features and changes across the data analytics infrastructure.

High Impact

Supervision: "How much do I rely on my manager?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high impact.

Defines new feature assignments for themselves, usually without requiring help. Organizes cross-functional initiatives in building significant new functionality.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Recognized by colleagues as a technical authority, passively influencing discussions and behavior, and working in sync with PM, Engineering, and GTM.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans across staff, open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Can independently make decisions affecting customer (internal and external) value/impact for complex topics within a data deliverable for the company. Leads cross-product, cross-feature, and cross-team discussions related to customer value/impact, and can bring the stakeholders to a decision point.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Frequently called upon to comment on analytical business discussions. Is very comfortable in data discussions, aligns efforts, and develops superior solutions through discussion and analysis. Participates deeply in cross-team efforts. Begins to lead discussions on topics that reach outside of data analytics. Independently researches new technologies and paradigms to improve team efficiency.

Level 6: Senior Product Analyst

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Sets and delivers architectural vision for high impact features and changes across the data analytics infrastructure.

High Impact

Supervision: "How much do I rely on my manager?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high impact.

Defines new feature assignments for other members of the team, usually without requiring help. Leads cross-functional groups, and coordinates and manages the creation of new functionality.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Highly respected by colleagues and community as a technical authority, actively influencing discussions and behavior with input and suggestions, and working in sync with with PM, Engineering, and GTM.

Customer Obsession

Customer Impact: "How do I bring value?" Community spans across staff, open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Can independently make decisions affecting customer (internal and external) value/impact for complex topics within a data deliverable for the company. Leads cross-product, cross-feature, and cross-team discussions related to customer value/impact, and can bring the stakeholders to a decision point.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Frequently called upon to comment on analytical business discussions. Is very comfortable in data discussions, aligns efforts, and develops superior solutions through discussion and analysis. Participates deeply in cross-team efforts. Begins to lead discussions on topics that reach outside of data analytics. Independently researches new technologies and paradigms to improve the entire data organization (engineering, analytics, and science).

Level 7: Staff Product Analyst

Leadership Principle
Competencies
Level Expectations

Ownership

Scope: "What do I work on?" Scope is the domain over which you are expected to show ownership.

Consults on architectural visions for data collection, modeling, and innovations across teams.

High Impact

Supervision: "How much do I rely on my manager?" Community: "How do others work with me?" The need to receive supervision is inversely related to the instinct to choose what is high impact.

Defines new task assignments for members of other teams, usually without requiring help. Mentors and trains new team members while leading the coordination and management of high impact initiatives.

Earn Trust

Influence: "Who do I work with?" As more people and parts of the organization earn your trust, your influence grows.

Frequently sought out by product and engineering leads for opinion on data implementation decisions (both product and technical directions).

Customer Obsession

Customer Impact: "How do I bring value?" Community spans across staff, open-source and enterprise, but ultimately manifests in the same obsession for enabling customers to be successful.

Has ownership for cross-product customer impact topics. Can anticipate complex issues early in the planning and development processes. Starts to anticipate and resolve cross-functional topics and issues.

Self-Awareness

Interaction: "Who relies on me?" Iteration: "How do I improve myself and others?" Self-awareness yields an ability to seamlessly fit into any conversation or effort, interacting with a group to work towards the best possible outcome and always iterating towards the best possible outcome.

Primary technical leader for projects, providing thought leadership in selecting and guiding these efforts. Works regularly with stakeholders outside of data analytics. Is often the intial resource to drive design and architecture efforts for new data collection, modeling, and analysis. Mentors people on data strategy across all of product and engineering. Is a hands on leader for executing on mentorship and training.

Level 8: Principal Product Analyst

Level descriptions to be defined.

Level 9: Distinguished Product Analyst

Level descriptions to be defined.

PreviousAnalyticsNextLooker

Last updated 3 years ago

Was this helpful?