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
  • Week 1: Focus on environment setup and introductions
  • Week 2: Focus on digesting information dump
  • Weeks 3 - 4: Focus on solidifying role in the team
  • Weeks 5 - 8 (Month 2): Work on your first project as dev owner
  • Weeks 9 - 11 (Month 3): Work on more and/or larger projects as dev owner
  • Week 12: Informal performance evaluation
  • Weeks 13 - 16 (Month 4): Act on your performance evaluation and focus on community
  • Weeks 17 - 20 (Month 5): Become an authority
  • Weeks 21+ (Month 6+): Continue to grow as an engineer, be a leader in the community, and be an integral part of the Mattermost engineering org

Was this helpful?

Edit on Git
Export as PDF
  1. Operations
  2. Workplace
  3. PeopleOps
  4. Working at Mattermost
  5. Onboarding

Engineer onboarding timeline and expectations

PreviousStaff onboardingNextManager onboarding

Last updated 2 years ago

Was this helpful?

This is the general timeline and expectations for new engineers starting at Mattermost. It is meant to guide new engineers, help them focus on the right tasks, and set expectations to help them be successful at Mattermost. It is not a hard timeline in any sense and circumstances may shorten, lengthen, or re-order the timeline.

Week 1: Focus on environment setup and introductions

  • Set up equipment and environment (e.g. complete the day 1 checklist)

    • Get laptop, set up developer environment

    • Clone Enterprise repo

    • Log in to all accounts (Gmail, GitHub, JIRA, Okta, Community, Community Daily)

    • Expense equipment

    • HR set up (benefits, health insurance, etc.)

  • Meet the team

    • Meet with a different team member for 30 minutes each day

  • Meet with your dev lead

    • Meet for at least 10 - 15 minutes each day

  • Attend weekly team/company meetings to get the feeling for them

    • Sprint Planning

    • Company All Hands

    • Developer Meeting

    • R&D Meeting

    • Developer Hangouts

    • Video Game Hour

  • Join important channels

  • Read and understand Mattermost's core values and Leadership Priciples

  • Review video calling etiquette

  • Work on 1 - 3 small tickets to get used to dev processes

  • Introduction at the R&D Meeting

Week 2: Focus on digesting information dump

  • Continue getting used to processes and workflows

    • Sit in on some spec/design/technical meetings - your dev lead should send you invites to these meetings

    • Do some code reviews - your dev lead should assign you to some

  • Introduction meetings

    • Meet with a different team member for 30 minutes each day

  • Mentor for the week is a senior teammate

    • Meet for at least 10 - 15 minutes each day

  • Meet with dev lead

    • Meet 2 - 3 times in the week

    • Go over core values and Leadership Principles with dev lead

  • Work on 1 - 3 small tickets

Weeks 3 - 4: Focus on solidifying role in the team

  • Start taking a more active role as a member of your dev team

  • Begin to participate in some spec/design/technical meetings

    • Provide feedback/ask questions, have an active role in the meetings

  • Mentor for each week is a different teammate

    • Meet for at least 10 - 15 minutes each day

  • Meet with dev lead

    • Meet once a week and start regular weekly 1-1s

  • Work on some medium size tickets

Weeks 5 - 8 (Month 2): Work on your first project as dev owner

  • Begin work on your first relatively large task (40 mana) and be the dev owner of it

  • Act as the dev owner in the spec/design/technical meetings

  • Write up a brief technical specification if necessary

  • Work on small/medium tickets each sprint alongside the larger task

Note: It's expected that your first project takes longer to complete than usual

Weeks 9 - 11 (Month 3): Work on more and/or larger projects as dev owner

  • Take what you learned being dev owner on your first project and improve upon it

  • Act as dev owner and write technical specs for more and larger projects

  • Work on small/medium tickets to fill in gaps

  • Complete deliverables in a more timely fashion

  • Attend a "Tech Moonshots" developer meeting

Week 12: Informal performance evaluation

  • Dev lead will give you your performance evaluation

  • A self-survey will be sent to you

  • Surveys will be sent out to your peers and you are:

    • Evaluated on what's being done well, what could be improved

    • Evaluated on core values and Leadership Principles

  • The goal is to let you know how you’re performing and to help you improve and be a better engineer

Weeks 13 - 16 (Month 4): Act on your performance evaluation and focus on community

  • Continue to improve on fulfilling engineering responsibilities and completing quality deliverables in a timely fashion

  • Begin acting on any feedback given during the performance evaluation

  • Start taking a more active role in the open source community

    • Proactively answer questions in channels

    • Create Help Wanted tickets and mentor contributors working on them

    • Find a community buddy (a contributor you interact with fairly often)

  • Start helping to answer customer support questions

Weeks 17 - 20 (Month 5): Become an authority

  • Start to become an authority on some part of the product/codebase

    • Begin thinking about what part of the code you want to “own” - what do you want to be known for at Mattermost

    • Could be something you built on a past project

    • Be the “go to” person for that area

    • Tends to happen naturally if you take true ownership of the projects you’ve worked on

  • Create some Help Wanted tickets/campaigns to get the community involved in your area of authority

    • Focus on high impact tasks

    • Think about what you would work on if there were three of you, and use the community to help you as your clones

  • Complete engineering responsibilities and deliverables on pace with fellow teammates

Weeks 21+ (Month 6+): Continue to grow as an engineer, be a leader in the community, and be an integral part of the Mattermost engineering org

Introduction at the

Review the sheet to understand expectations and responsibilities for your level

https://community.mattermost.com/core/channels/developers
https://community.mattermost.com/core/channels/developers-meeting
https://community.mattermost.com/core/channels/thank-you
https://community.mattermost.com/private-core/channels/announcements
https://community.mattermost.com/private-core/channels/confidential-bugs
https://community.mattermost.com/private-core/channels/off-topic
https://handbook.mattermost.com/company/about-mattermost#leadership-principles
http://hulen.com/video-conf-peevs/
Customer Obsession Meeting
Engineering Titles/Levels