| Track | Intern | Associate Technical Writer (SE2) | Technical Writer (SE3) | Senior Technical Writer | Staff Technical Writer | Lead | Senior Lead |
|---|---|---|---|---|---|---|---|
| Universal Track | Intern | Entry-Level | Mid-Level | Experienced | Advanced | - | - |
| Individual Contributor Track | - | - | - | - | Staff Technical Writer | - | - |
| People Management Track | - | - | - | - | - | Leads Team and/or Projects | Leads Team and/or Projects |
| Scope | Topic | Intern | Associate Technical Writer (SE2) | Technical Writer (SE3) | Senior Technical Writer | Staff Technical Writer | Lead | Senior Lead |
|---|---|---|---|---|---|---|---|---|
| What they know | Technical Expertise | Has foundational technical/programming knowledge to accomplish small tasks. Is familiar with navigating the command line. | Has foundational technical/programming knowledge to create technical examples (code or API). Is comfortable navigating the command line. | Has foundational technical/programming knowledge to create technical examples (code or API) or complete sample apps with some guidance. Is comfortable navigating the command line. | Deep technical/programming knowledge to create complex technical examples (code or API) or complete sample apps independently. Is an expert navigating the command line. | Technical/programming knowledge and understanding of relevant area is close or on par with the product and/or development team. Uses expertise to create complex technical examples that mirror production environments and best practices. | Has technical expertise of Senior (or greater) | Has technical expertise of Staff (or greater) |
| Writing Ability | Has strong communication and generally writes well. Beginning to learn about technical writing fundamentals and MongoDB's style. Actively improves writing clarity, conciseness, and builds upon team best practices week after week. | Has strong communication and generally writes well. Beginning to learn about technical writing fundamentals and MongoDB's style. Actively improves writing clarity, conciseness, and builds upon team best practices week after week. | Understands a majority of technical writing fundamentals. Writes in accordance with MongoDB's style. | Has an in-depth understanding of techical writing best practices and MongoDB's style. | Has mastered technical writing best practices and shapes style and writing practices at MongoDB. | Has writing ability of Senior (or greater) | Has writing ability of Staff (or greater) | |
| Complexity of writing tasks | Completes small size and complexity writing tasks with some guidance. | Completes moderate size and complexity writing tasks with some guidance. | Completes moderate to large size and complexity writing tasks with minimal guidance. | Completes large and greater sized writing tasks about our most complex subject areas. Makes well-reasoned writing decisions and tradeoffs for clarity and speed. | Performs expert writing and editing tasks. Handles large-scale new feature work, technical debt, and major content refactors. | Contributes partial bandwidth to docs at the Senior level (or above); Leverages knowledge of Senior ICs appropriately | Contributes partial bandwidth to docs at the Staff level (or above); Leverages knowledge of Senior ICs appropriately | |
| Scoping Docs | Produces well-scoped content with mentorship. Learns from peers on how to plan documentation before starting tickets. | Produces well-scoped content with mentorship. Scopes docs for new features with guidance. | Scopes documentation for small/medium projects or features on their own. Given introductory context, can take independently undertake a docs request, project, or issue. | Given a medium to large partially defined docs request, project, or feature, can scope docs and author content that addresses user need independently. | Given a large and poorly defined documentation request, project, or feature, can explore the solution space and prepare doc plans or execution plans which involve major content or IA changes. | Given a large and poorly defined documentation request, project, or issue, can explore the solution space to determine the correct course of action. Comfortable producing POCs or documentation plans to illustrate potential solutions. Coaches their team on scoping and guides them through the process above. | Given a large and poorly defined documentation request, project, or issue, can explore the solution space to determine the correct course of action. Comfortable producing POCs or documentation plans to illustrate potential solutions. Coaches their team on scoping and guides them through the process above. | |
| Copy Reviews | Learning from peers through copy review. Incorporates feedback into subsequent work. | Learning from peers through copy review. Incorporates feedback into subsequent work. Begins reviewing their peers work for smaller areas they are comfortable in. | Does thorough and insightful peer copy reviews. Tests content during reviews if possible in a reasonable amount of time and catches technical issues as well. | Participates in copy reviews, testing, and can sign off on major features. Mentors more junior writers through thoughtful reviews. | Mentors peers through expert copy reviews and can sign-off on page, multi-page, and massive repo-wide level changes. | Scales their impact by training their team through copy reviews. Coaches their team on reviewing content. Spends a signficant portion of their time reviewing their team's work. Can sign off on any reviews in the area they manage. | Scales their impact by training their team through copy reviews. Coaches their team on reviewing content. Spends a signficant portion of their time reviewing their team's work. Can sign off on any reviews in the area they manage. | |
| Collaboration | Collaborates well with their mentors, team members, and other interns when applicable. Grows comfortable with cross-team collaboration, and gains a knowledge of which teams to ask for support for certain tasks. | Collaborates well with their mentors, team members, and other interns when applicable. Comfortable with cross-team collaboration, and has knowledge of which teams to ask for support for certain tasks. | Starts getting involved earlier in the documentation process by reviewing engineering scope/PD/designs and attending Product/Engineering syncs and/or Docs Kickoff meetings. Works with stakeholders (product, engineering, product marketing) to define documentation requirements. | Recognized by development and product teams as an expert in their subject matter area. May be requested to join development team's quarterly planning or requested to LGTM product or engineering documents. | Recognized across the company as an expert in their subject matter area. May be requested to join development team's quarterly planning or requested to LGTM product or engineering documents. | Works with other Leads across Engineering and Product to make sure Docs projects align with the release timeline. | Works with other Leads across Engineering and Product to make sure Docs projects align with the release timeline and business goals. | |
| Tools | Learns to use the docs toolchain, resources, and processes required for their work. | Learns the Docs toolchain and begins debugging minor issues. | Comfortable with the Docs toolchain and is able to debug occasional issues. Assists new and more junior writers with the toolchain. Requests new platform features when needed. | Has mastered the Docs toolchain and is able to debug and diagnose issues. Assists new and more junior writers with the toolchain. Builds strong rapport with Docs Platform team through regular interactions on new feature and support requests. Able to identify areas where additional tooling (scripts, grep, etc.) can improve productivity and efficiency. | Understands the limits of Docs tooling, requests and defines new features to improve writer efficiency or reader experience. May help the platform team with researching external tools and POCs. Regularly helps team members debug rST issues. | Has mastered the Docs toolchain and is able to debug and diagnose issues. Assists new and more junior writers with the toolchain. Builds strong rapport with Docs Platform team through regular interactions on new feature and support requests. Escalates tooling issues when required on behalf of their team. | Expertise on making decisions whether issues are best resolved on the content side or on the platform side, considering both resourcing and the user experience. | |
| Product Knowledge | Has a basic understanding of the products they are responsible for documenting. | Has a basic understanding of the products they are responsible for documenting. Begins developing interest and subject matter expertise in at least one product. | Actively strengthens their understanding of the products they document. Understands the importance of documentation and how it fits into the development cycle at MongoDB. Has subject matter expertise in one product. | Thorough understanding of certain products (all components and relationships between large features). Familiarity with most, if not all, of the products the sub-team documents. Understands the importance of documentation and collaborates with engineering and product early on in the development cycle. | Has a strong technical understanding of all products relevant to own areas of expertise. | Has very broad knowledge of products the team documents and can help in any area when needed. | - | |
| Industry knowledge | Acquires a basic understanding of the value proposition of the MongoDB products with which they work, specifically the value of technical documentation. | Shows interest and initiative in learning new MongoDB products and other industry technology. | Stays up-to-date with any technologies relevant to their work (in the development, data platform, and/or Docs tooling spaces). Advocates for professional development when there is a knowledge gap. | Stays up-to-date with any technologies relevant to their work (in the development, data platform, and/or Docs tooling spaces). Advocates for professional development when there is a knowledge gap. | Uses extensive industry knowledge propose new, innovative solutions and writing content when relevant. | Has informed opinions on what makes excellent documentation and leverages them for competitive analysis. Uses insight from competitors and similarly-sized companies' documentation to inform internal projects. | Has informed opinions on what makes excellent documentation and leverages them for competitive analysis. Uses insight from competitors and similarly-sized companies' documentation to help define the longterm vision of our docs. | |
| Business goals | N/A | Begins learning the importance of documentation and how it supports engineering work. | Understands how their work aligns with engineering and product tactical goals. | Understands how their work aligns with engineering and product tactical goals and how those tactical goals support the greater business goals. | Understands how their work aligns with engineering and product tactical goals and how those tactical goals support the greater business goals. Able to strategically identify net-new or tech debt work that supports these goals. | Understands how their work aligns with engineering and product tactical goals and how those tactical goals support the greater business goals. Able to strategically identify net-new or tech debt work that supports these goals. Advocates for this work and prioritizes it among the team's usual deliverables. | - | |
| Testing and troubleshooting | Begins testing products and verifying documentation requests. | Improves upon testing and verification techniques and begins testing moderate complexity features. Feels comfortable troubleshooting and raising issues/bugs with engineering. | Handles cross-team escalations within area of expertise. Shows good judgement in escalating to their lead or more senior writers. Feels comfortable troubleshooting and raising issues/bugs with engineering. Able to provision and configure test environments when applicable. | Handles cross-team escalations for their area of expertise and adjacent areas. Rarely needs to escalate further. Helps shape testing methodologies on the team in addition to configuring test environments. | Often handles cross-team escalations for their area of expertise and adjacent areas. Rarely needs to escalate further. | Handles cross-team escalations for their area of expertise and adjacent areas. Rarely needs to escalate further. | Handles cross-team escalations for their area of expertise and adjacent areas. Rarely needs to escalate further. | |
| Estimation | Learning how to estimate their work and reflects on inaccurate estimates to make future improvements. | Learning how to estimate their work and reflects on inaccurate estimates to make future improvements. | Estimates their work reasonably accurately and reflects on inaccurate estimates to make future improvements. | Regularly provides accurate estimations and accurate progress reports. | Mentors others on improving estimation abilities and offers their perspective when estimations seem high/low. Trains others on how to split or merge work into tasks that can be easily executed and approved. | Mentors others on improving estimation abilities and guides the team towards delivery. | Skilled at synthesizing estimates and risks projects which are still in early planning phases. Able to approximatethe amount of work that a downstream team will face. | |
| Prioritization & Planning | - | Understands the team's top priorities. Asks for guidance on what to pick up next. | Effectively manages their own independent workload and priority. Augments team velocity by helping fellow writers. Able to triage tickets in their area of expertise. | Contributes to backlog prioritization and maintenance. Provides input on quarterly planning. Able to triage tickets in several areas of expertise. | Advocates for large-scale proactive projects. Can justify need for proactive work and its business case for the team, department, and/or company. Ensures that those projects are scoped prior to quarterly planning. | Prioritizes work across projects and people in line with company goals; Drives the team's quarterly planning Able to triage all tickets for their team. | Works with stakeholders from other areas and products to address issues outside their immediate responsibility and/or that cross team boundaries. | |
| Scaling & Delegation | N/A | N/A | N/A | N/A | Scales their own impact by mentoring and distributing their writing and technical knowledge to others. | Scales their own impact by delegating effectively; ensures tasks are completed as specified without micromanaging. | Engages senior ICs in planning and gives them ownership of projects. | |
| Leadership scope | N/A | N/A | N/A | Leads projects, possibly including 1-2 other writers. | Provides technical leadership for initiatives or large projects involving several individuals. | Manages small teams. Demonstrates strong and sound judgement at the task, project, and personnel levels. | Proven track record managing larger teams and successfully delivering a number of complex projects. Comfortable and confident making challenging decisions with a history of strong and sound judgement at the task, project, and personnel levels. | |
| Organizational Development | Keeps their Lead informed about whether their workload is manageable. | Keeps their Lead informed about whether their workload is manageable. | Keeps their Lead informed about whether their workload is manageable. | Collaborates with their Lead to keep their workload manageable. Raises resource (headcount, funding, etc.) needs to their lead when there is a need or significant efficiency gain. | Keeps their Lead informed about whether their workload is manageable. Raises resource (headcount, funding, etc.) needs to their lead when there is a need or significant efficiency gain. Helps provide clear justifications and returns for the request. | Escalates to senior management when current headcount does not support the planned workload. Provides an informed opinion on the headcount needed to complete future projects. Knows how and when to redistribute work among the team. | - | |
| Recruiting | - | Begins shadowing interviews. | Interviews candidates for their own team and assists other teams when requested. | Interviews candidates for their own team and assists other teams when requested. Can identify good talent with limited exposure to the individual. Able to quickly identify a candidate's strengths and limitations/development areas. Reviews the job description and provides input to help find ideal candidates. | Engages and recruits in communities of practice like conferences, meetups, MongoDB events, Write the Docs etc. Participates actively as speaker, coordinator, etc. Influences interview plan. | Creates job descriptions and interview plans. Recruits a world-class team. Knows the appropriate level of experience to recruit for and when to recruit growth candidates. | Strong ability to sell the role and company to potential candidates. Able to negotiate with candidate (through recruiting) when necessary. Comfortable recruiting for leadership roles, other lead roles and above. | |
| How they behave | Initiative & Accountability | Takes ownership for the technical accuracy and quality of their work. Fixes any issues (content or build) when discovered. | Takes ownership for the technical accuracy and quality of their work. Fixes any issues (content or build) when discovered. | Takes ownership for the technical accuracy and quality of their work. Fixes any issues (content or build) when discovered. Shows initiative and offers assistance when needed without being asked. | Advocates for Docs projects that address user need, reduce team tech debt, or improve writer efficiency. Seeks to move those projects forward with planned epics or, if necessary, through Education or Engineering's. document process (e.g. writes RFCs, PDs, scopes and/or specs). | Writes RFCs, PDs, scopes, and/or specs projects that address a user need, reduct tech debt, or improve writer efficiency with or for the product or engineering teams. | Takes responsibility for their team/project, while still allowing their team members the appropriate level of autonomy. | Takes responsibility for larger teams and multiple projects, while still allowing their team members the appropriate level of autonomy. |
| Problem Solving | Investigates problems independently but knows when to ask for guidance. | Investigates problems independently but knows when to ask for guidance. | Constructively escalates problems and issues. | Keeps discussions focused on important aspects of the problem being solved. | Encourages new of more junior writers to tackle larger projects with their help to build knowledge and skills. | Guides team members to the correct solutions while encouraging collaboration. Keeps discussions focused on important aspects of the problem being solved. | Is skilled at knowing when to guide employees to find their own answers via questioning, vs telling them what to do. Knows when to use each approach. | |
| Mentorship & People Development | N/A | Provides guidance to new or interning technical writers. | Provides guidance to new, entry-level, or interning technical writers. Acts as an onboarding buddy for new writers and may mentor an intern. | Regularly provides guidance to new, entry-level, or interning technical writers. Onboarded and mentored several new writers and interns. | Shapes and refines onboarding practices on the Docs team. Provides feedback and coaching to their team members without the people management aspect. Given the opportunity and autonomy to explore operational concerns outside of management hierarchy. | Provides actionable feedback, coaching, and mentorship to their team members. Counsels each employee on their career growth and has clear written plans for them. Encourages their team members to take on projects or tasks with developmental opportunities. | An experienced & skilled manager and coach. Develops leaders in their team and keeps senior ICs engaged. Has a track record of successfully resolving complex employee issues. Is an example of great people management practices. | |
| Communication | Communicates effectively and respectfully to all employees. Communicates the type of products / work they are interested in so we can best facilitate growth. | Communicates effectively and respectfully to all employees. Communicates the type of products / work they are interested in so we can best facilitate growth. | Earnestly considers differing viewpoints. Leaves their ego aside and is genuinely interested in finding the best solution. | Constructively challenges assumptions. Knows when to advocate for their opinion, make compromises, and when to fold. Reports on their work with an appropriate level of detail. | Critiques their own and others' ideas through a lens of data and validated learning, rather than assumptions. Communicates updates at an appropriate level of detail up and down the hierarchy. Ensures advance notice of work plans and progress. | Fosters a culture of psychological safety. Coaches others on how to communicate effectively and respectfully. | - | |
| Team Culture | Is a positive morale influence on their team members and gets to know their coworkers. | Is a positive morale influence on their team members and gets to know their coworkers. | Is a positive morale influence on their team members and gets to know their coworkers. Encourages and supports their team members. Recognizes good work from colleagues (bonusly, email, slack, etc.) | Significantly influences team culture and morale. May organize social and team building events. | Is a positive influence on the morale of other employees and contributes to a solution-focused culture. | Responsible for keeping team morale, engagement, and retention high. | Fosters a very postiive, friendly, productive, and focused team culture. There is a strong sense of team comradery and output of the whole team in their group. | |
| Core Values | Acts in accordance with MongoDB's core values. | Acts in accordance with MongoDB's core values. | Acts in accordance with MongoDB's core values. | Embodies MongoDB's core values. | Teaches and promotes MongoDB's core values by modeling those behaviors. | Teaches and promotes MongoDB's core values by modeling those behaviors and providing feedback. | Teaches and promotes MongoDB's core values by modeling those behaviors and providing feedback. | |
| Emotional Intelligence | Demonstrates appropriate emotional regulation. Handles conflict and disagreements in a constructive and professional manner. | Demonstrates appropriate emotional regulation. Handles conflict and disagreements in a constructive and professional manner. | Demonstrates appropriate emotional regulation. Handles conflict and disagreements in a constructive and professional manner. | Demonstrates appropriate emotional regulation. Handles conflict and disagreements in a constructive and professional manner. | Demonstrates appropriate emotional regulation. Handles conflict and disagreements in a constructive and professional manner. | Is skilled at navigating interpersonal issues and demonstrates high emotion regulation. Is building expertise in coaching others on how to do so. | Is highly skilled at navigating interpersonal issues and embodies emotional regulation. |
| Role | Years |
|---|---|
| Intern | - |
| Associate Technical Writer (SE2) | 1-2 |
| Technical Writer (SE3) | 2-3 |
| Senior Technical Writer | 5-∞ |
| Staff Technical Writer | ∞ |
| Lead | 5-∞ |
| Senior Lead | ∞ |
-
This is not a checklist, nor is it a complete list of the criteria for promotions and performance evaluations. This is a guide for you to understand management's general expectations and should serve as a starting point for discussion with your manager regarding your performance and role.
-
The expectations at each level are cumulative. All expectations from previous levels apply to subsequent levels.
-
Writers will move into new roles based on their performance and business needs; there is no set time period (minimum or maximum) that an engineer will spend in any one role.
-
If you have any recommended adjustments to this doc, reach out to Jon DeStefano