Documentation Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc.
We need to extract content.
Let's parse sections.
About the role: from "What We Do": "The Marketing and Communications team at Mapbox is responsible for shaping the company's public image and promoting its cutting-edge location technology solutions. Through building strategic campaigns, high-quality content, and excellent documentation, the team effectively communicates Mapbox's value to customers, prospects, developers, partners, and stakeholders. Our goal is to highlight product features, share customer success stories, and build brand awareness, showcasing Mapbox as the leading location technology company."
That's prose. Could be
.
Responsibilities: from "What You'll Do": bullet list:
- As part of the Mapbox Developer Relations team, you'll help keep docs.mapbox.com accurate, current, and easy to use for our community of developers. This is a hands-on, day-to-day role: you'll be the person making the small fixes, updates, and improvements that keep our documentation trustworthy, while building the coding and product knowledge to take on bigger documentation projects over time.
- Make routine updates to docs.mapbox.com: correcting errors, clarifying language, updating code samples, and keeping content in sync with product changes.
- Triage incoming user feedback on documentation, working with partners across the org to fix issues quickly and escalate the ones that need deeper attention.
- Manage the git/GitHub workflow for docs contributions — branching, pull requests, and reviews — since our docs live in a static site built with markdown/MDX and React.js.
- Work directly in the Mapbox product (web, mobile, and/or embedded SDKs) to understand what you're documenting, rather than editing from a distance.
- Partner with product teams to support new feature and product launches with clear, accurate documentation.
- Help prototype lightweight tooling or workflows (e.g., a simpler way to trigger small text changes) that make it faster and easier to keep docs up to date.
- Support other Developer Relations initiatives as needed, including community programs and general upkeep of the docs platform.
We need to preserve all substantive info. Could break into list items each as
- . The first sentence is a bit long; could keep as one
- . Ensure we don't lose details.
Requirements: from "What We Believe Are Important Traits For This Role": paragraphs:
"We're looking for a North America-based web developer who also writes well — not a technical writer looking to learn to code, and not a senior engineer looking for a pure engineering role. This is a great fit for someone who wants to grow into a versatile Developer Relations career. You're a developer first: comfortable with git/GitHub workflows, markdown/MDX, and React.js. Mapbox's documentation site requires real coding ability to contribute to, not just prose editing. You write clearly and enjoy explaining technical concepts — through docs, tutorials, or troubleshooting guides. You're curious and willing to dig in: Mapbox spans web, mobile, and embedded platforms, and you'll need to actually use the product to write about it accurately. You can manage several small projects at once, prioritize independently, and see each through to publication with minimal oversight. Prior experience with Mapbox, digital mapping, or location technology is a plus but not required — willingness to learn the product deeply is what matters most. 2-4 years of professional experience."
We can turn into list items maybe each trait. But we can also keep as prose
. However instruction: Use
- for any list of duties/requirements/benefits. This is a list of traits/requirements; we could make a list. But we need to preserve all detail; we can break into items each covering a trait. Let's extract each bullet:
- North America-based web developer who also writes well (not a technical writer learning to code, not a senior engineer seeking pure engineering role).
- Want to grow into a versatile Developer Relations career.
- Developer first: comfortable with git/GitHub workflows, markdown/MDX, and React.js.
- Documentation site requires real coding ability to contribute to, not just prose editing.
- Write clearly and enjoy explaining technical concepts — through docs, tutorials, or troubleshooting guides.
- Curious and willing to dig in: need to use product across web, mobile, embedded to write accurately.
- Can manage several small projects at once, prioritize independently, see each through to publication with minimal oversight.
- Prior experience with Mapbox, digital mapping, or location technology is a plus but not required — willingness to learn the product deeply is what matters most.
- 2-4 years of professional experience.
We'll make
- for each.
Benefits: from "How We Support You": list:
- Hybrid/Remote Options: Enjoy flexibility to work comfortably from home or periodically from an office where applicable.
- Comprehensive Healthcare: Private medical coverage for you and your dependents.
- Family-First Support: Generous maternity and paternity leave policies to support your growing family.
- Fertility & Family Building: Inclusive fertility support. Grow your family on your terms.
- Lifestyle Spending Account: Contributions to support your health, wellness, and personal growth.
- Balance & Brainpower: Mental health support for you and your dependents.
- Rest & Recharge: Flexible paid time away, company holidays, and generous absence policies.
- Time Off to Give Back: Dedicated paid volunteering time in addition to your standard PTO.
- Invest & Grow: Retirement plans with competitive matching.
We'll make list.
Pay: from "Our annual base compensation for this role ranges from $82,450 - $111,550 for most US locations and 5% to 10% higher for US locations with a higher cost of labor. Job level and actual compensation will be decided based on factors including, but not limited to, individual qualifications objectively assessed during the interview process (including skills and prior relevant experience, potential impact, and scope of role), market demands, and specific work location. Please discuss your specific work location with your recruiter for more information."
We need to preserve all substantive info. Could be a
with that text.
We must not include boilerplate like EEO, privacy policy, etc. The ending includes "By applying for this position, you acknowledge that you agree to the Mapbox Privacy Policy which is linked here. We are committed to a fair and equitable hiring process. We do not discriminate against any protected class." That's boilerplate; remove.
Also remove "What We Value" section? Actually we haven't used it. The "What We Value" paragraph: "In addition to our core values, which are not unique to this position and are necessary for Mapbox leaders: We value high-performing creative individuals who dig into problems and opportunities. We believe in individuals being their whole selves at work. We commit to this through supportive health care, parental leave, flexibility for the things that come up in life, and innovating on how we think about supporting our people. We emphasize an environment of teaching and learning to equip employees with the tools needed to be successful in their function and the company. We strongly believe in the value of growing a diverse team and encourage people of all backgrounds, genders, ethnicities, abilities, and sexual orientations to apply."
That's somewhat overlapping with benefits and culture; but we already have Benefits section covering many of those points. However the "What We Value" includes statements about valuing high-performing creative individuals, whole selves, teaching/learning environment, diverse team. This is substantive content not covered elsewhere. Should we include a section? Possible headings: "Values" or "Culture". But allowed headings list includes Skills, Benefits, Pay, Schedule, etc. Not "Values". Could we put under "Skills"? Not appropriate. Could we put under "About the role"? Might be okay to add as a paragraph after About the role? But instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.) - implies we can use those headings; but we could also add other headings if needed? Safer to stick to those. The content about values could be folded into Benefits or About the role? Benefits already covers health care, parental leave, flexibility, etc. The values about high-performing creative individuals, teaching/learning, diverse team could be placed under "About the role" as part of company culture. But we already used About the role for "What We Do". Could expand About the role to include both what we do and what we value. That would preserve all info.
Thus About the role section will contain both "What We Do" and "What We Value". We'll combine into prose maybe two paragraphs.
Let's craft About the role:
Paragraph 1: The Marketing and Communications team at Mapbox is responsible for shaping the company's public image and promoting its cutting-edge location technology solutions. Through building strategic campaigns, high-quality content, and excellent documentation, the team effectively communicates Mapbox's value to customers, prospects, developers, partners, and stakeholders. Our goal is to highlight product features, share customer success stories, and build brand awareness, showcasing Mapbox as the leading location technology company.
Paragraph 2: In addition to our core values, which are not unique to this position and are necessary for Mapbox leaders: We value high-performing creative individuals who dig into problems and opportunities. We believe in individuals being their whole selves at work. We commit to this through supportive health care, parental leave, flexibility for the things that come up in life, and innovating on how we think about supporting our people. We emphasize an environment of teaching and learning to equip employees with the tools needed to be successful in their function and the company. We strongly believe in the value of growing a diverse team and encourage people of all backgrounds, genders, ethnicities, abilities, and sexual orientations to apply.
That
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to extract content. Let's parse sections. About the role: from "What We Do": "The Marketing and Communications team at Mapbox is responsible for shaping the company's public image and promoting its cutting-edge location technology solutions. Through building strategic campaigns, high-quality content, and excellent documentation, the team effectively communicates Mapbox's value to customers, prospects, developers, partners, and stakeholders. Our goal is to highlight product features, share customer success stories, and build brand awareness, showcasing Mapbox as the leading location technology company." That's prose. Could be
. Responsibilities: from "What You'll Do": bullet list: - As part of the Mapbox Developer Relations team, you'll help keep docs.mapbox.com accurate, current, and easy to use for our community of developers. This is a hands-on, day-to-day role: you'll be the person making the small fixes, updates, and improvements that keep our documentation trustworthy, while building the coding and product knowledge to take on bigger documentation projects over time. - Make routine updates to docs.mapbox.com: correcting errors, clarifying language, updating code samples, and keeping content in sync with product changes. - Triage incoming user feedback on documentation, working with partners across the org to fix issues quickly and escalate the ones that need deeper attention. - Manage the git/GitHub workflow for docs contributions — branching, pull requests, and reviews — since our docs live in a static site built with markdown/MDX and React.js. - Work directly in the Mapbox product (web, mobile, and/or embedded SDKs) to understand what you're documenting, rather than editing from a distance. - Partner with product teams to support new feature and product launches with clear, accurate documentation. - Help prototype lightweight tooling or workflows (e.g., a simpler way to trigger small text changes) that make it faster and easier to keep docs up to date. - Support other Developer Relations initiatives as needed, including community programs and general upkeep of the docs platform. We need to preserve all substantive info. Could break into list items each as
. However instruction: Use
- for any list of duties/requirements/benefits. This is a list of traits/requirements; we could make a list. But we need to preserve all detail; we can break into items each covering a trait. Let's extract each bullet:
- North America-based web developer who also writes well (not a technical writer learning to code, not a senior engineer seeking pure engineering role).
- Want to grow into a versatile Developer Relations career.
- Developer first: comfortable with git/GitHub workflows, markdown/MDX, and React.js.
- Documentation site requires real coding ability to contribute to, not just prose editing.
- Write clearly and enjoy explaining technical concepts — through docs, tutorials, or troubleshooting guides.
- Curious and willing to dig in: need to use product across web, mobile, embedded to write accurately.
- Can manage several small projects at once, prioritize independently, see each through to publication with minimal oversight.
- Prior experience with Mapbox, digital mapping, or location technology is a plus but not required — willingness to learn the product deeply is what matters most.
- 2-4 years of professional experience.
We'll make
- for each.
Benefits: from "How We Support You": list:
- Hybrid/Remote Options: Enjoy flexibility to work comfortably from home or periodically from an office where applicable.
- Comprehensive Healthcare: Private medical coverage for you and your dependents.
- Family-First Support: Generous maternity and paternity leave policies to support your growing family.
- Fertility & Family Building: Inclusive fertility support. Grow your family on your terms.
- Lifestyle Spending Account: Contributions to support your health, wellness, and personal growth.
- Balance & Brainpower: Mental health support for you and your dependents.
- Rest & Recharge: Flexible paid time away, company holidays, and generous absence policies.
- Time Off to Give Back: Dedicated paid volunteering time in addition to your standard PTO.
- Invest & Grow: Retirement plans with competitive matching.
We'll make list.
Pay: from "Our annual base compensation for this role ranges from $82,450 - $111,550 for most US locations and 5% to 10% higher for US locations with a higher cost of labor. Job level and actual compensation will be decided based on factors including, but not limited to, individual qualifications objectively assessed during the interview process (including skills and prior relevant experience, potential impact, and scope of role), market demands, and specific work location. Please discuss your specific work location with your recruiter for more information."
We need to preserve all substantive info. Could be a
with that text. We must not include boilerplate like EEO, privacy policy, etc. The ending includes "By applying for this position, you acknowledge that you agree to the Mapbox Privacy Policy which is linked here. We are committed to a fair and equitable hiring process. We do not discriminate against any protected class." That's boilerplate; remove. Also remove "What We Value" section? Actually we haven't used it. The "What We Value" paragraph: "In addition to our core values, which are not unique to this position and are necessary for Mapbox leaders: We value high-performing creative individuals who dig into problems and opportunities. We believe in individuals being their whole selves at work. We commit to this through supportive health care, parental leave, flexibility for the things that come up in life, and innovating on how we think about supporting our people. We emphasize an environment of teaching and learning to equip employees with the tools needed to be successful in their function and the company. We strongly believe in the value of growing a diverse team and encourage people of all backgrounds, genders, ethnicities, abilities, and sexual orientations to apply." That's somewhat overlapping with benefits and culture; but we already have Benefits section covering many of those points. However the "What We Value" includes statements about valuing high-performing creative individuals, whole selves, teaching/learning environment, diverse team. This is substantive content not covered elsewhere. Should we include a section? Possible headings: "Values" or "Culture". But allowed headings list includes Skills, Benefits, Pay, Schedule, etc. Not "Values". Could we put under "Skills"? Not appropriate. Could we put under "About the role"? Might be okay to add as a paragraph after About the role? But instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.) - implies we can use those headings; but we could also add other headings if needed? Safer to stick to those. The content about values could be folded into Benefits or About the role? Benefits already covers health care, parental leave, flexibility, etc. The values about high-performing creative individuals, teaching/learning, diverse team could be placed under "About the role" as part of company culture. But we already used About the role for "What We Do". Could expand About the role to include both what we do and what we value. That would preserve all info. Thus About the role section will contain both "What We Do" and "What We Value". We'll combine into prose maybe two paragraphs. Let's craft About the role: Paragraph 1: The Marketing and Communications team at Mapbox is responsible for shaping the company's public image and promoting its cutting-edge location technology solutions. Through building strategic campaigns, high-quality content, and excellent documentation, the team effectively communicates Mapbox's value to customers, prospects, developers, partners, and stakeholders. Our goal is to highlight product features, share customer success stories, and build brand awareness, showcasing Mapbox as the leading location technology company. Paragraph 2: In addition to our core values, which are not unique to this position and are necessary for Mapbox leaders: We value high-performing creative individuals who dig into problems and opportunities. We believe in individuals being their whole selves at work. We commit to this through supportive health care, parental leave, flexibility for the things that come up in life, and innovating on how we think about supporting our people. We emphasize an environment of teaching and learning to equip employees with the tools needed to be successful in their function and the company. We strongly believe in the value of growing a diverse team and encourage people of all backgrounds, genders, ethnicities, abilities, and sexual orientations to apply. That
- for each.
Benefits: from "How We Support You": list:
- Hybrid/Remote Options: Enjoy flexibility to work comfortably from home or periodically from an office where applicable.
- Comprehensive Healthcare: Private medical coverage for you and your dependents.
- Family-First Support: Generous maternity and paternity leave policies to support your growing family.
- Fertility & Family Building: Inclusive fertility support. Grow your family on your terms.
- Lifestyle Spending Account: Contributions to support your health, wellness, and personal growth.
- Balance & Brainpower: Mental health support for you and your dependents.
- Rest & Recharge: Flexible paid time away, company holidays, and generous absence policies.
- Time Off to Give Back: Dedicated paid volunteering time in addition to your standard PTO.
- Invest & Grow: Retirement plans with competitive matching.
We'll make list.
Pay: from "Our annual base compensation for this role ranges from $82,450 - $111,550 for most US locations and 5% to 10% higher for US locations with a higher cost of labor. Job level and actual compensation will be decided based on factors including, but not limited to, individual qualifications objectively assessed during the interview process (including skills and prior relevant experience, potential impact, and scope of role), market demands, and specific work location. Please discuss your specific work location with your recruiter for more information."
We need to preserve all substantive info. Could be a