Staff Technical Writer | Remote | USA
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when posting has real, specific content
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment
Let me parse the content:
The posting starts with company description (Grafana Labs info). This could be "About the company" or "About the role". The heading "Description Of Duties" appears, then "Key Responsibilities" with a list. Then "Requirements" with a list. Then "What You'll Bring To The Role" with a list. Then there's a duplicate "What You'll Bring To The Role" with different content (more about personality traits). Then compensation info for UK and US. Then "Why You'll Thrive At Grafana Labs:" with a list of benefits/culture points. Then Equal Opportunity Employer statement (boilerplate, should be removed). Also there's mention of "Benefits include equity, bonus (if applicable) and other benefits listed here." but no specific benefits listed except in the "Why You'll Thrive" section.
I need to consolidate duplicate sections. The two "What You'll Bring To The Role" sections have different content - first is about AI curiosity, technical credibility, judgment, ownership, clarity, bonus. Second is about enthusiasm, managing projects, Elements of Style. I should combine them into one section.
Also, the compensation info appears twice (UK and US). I'll create a Pay section with both ranges.
The "Why You'll Thrive At Grafana Labs" is essentially benefits/culture. I'll make that a Benefits section.
The Equal Opportunity Employer statement is boilerplate - remove.
The company description at the top: "Grafana Labs is the company behind Grafana Cloud..." This is about the company. Could be "About the company" or "About the role". Since the heading "Description Of Duties" appears later, maybe the first part is "About the company". But the instruction says use
for section headings like "About the role". The posting doesn't have an explicit "About the role" heading, but "Description Of Duties" is similar. I'll use "About the role" for the initial description? Actually the first paragraph is company description, then "Description Of Duties" heading. I'll create a section "About the company" for the first paragraph, then "About the role" for the Description Of Duties paragraph? But the Description Of Duties paragraph is a description of the role. Let's see: "We're looking for a Staff Technical Writer to create documentation..." That's about the role. So I'll have:
- About the company (first paragraph)
- About the role (the paragraph under Description Of Duties)
- Responsibilities (Key Responsibilities list)
- Requirements (Requirements list)
- Qualifications (What You'll Bring To The Role combined)
- Pay (compensation ranges)
- Benefits (Why You'll Thrive At Grafana Labs)
But note: the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings.
Let's map:
- About the role: the paragraph describing the role (under Description Of Duties)
- Responsibilities: Key Responsibilities list
- Requirements: Requirements list
- Qualifications: What You'll Bring To The Role (combined)
- Pay: compensation ranges
- Benefits: Why You'll Thrive At Grafana Labs
The company description could be "About the company" but not in the example list. However, the instruction says "e.g." so it's not exhaustive. I'll include it as "About the company".
Now, I need to ensure I don't include filler. The compensation ranges are specific (GBP 81,000 - GBP 97,000 and $123,933 - $148,719). Good.
Benefits: the "Why You'll Thrive" list includes specific benefits: 100% remote, global culture, scaling organization, transparent communication, innovation-driven, open source roots, empowered teams, career growth pathways, approachable leadership, passionate people, in-person onboarding, balance is key (30 days annual leave, 3 days shutdown). That's substantive.
Now, I'll write the HTML.
I'll structure:
About the company
Grafana Labs is the company behind Grafana Cloud...
About the role
We're looking for a Staff Technical Writer to create documentation and learning content that helps people adopt and master Grafana's observability products. You'll work with engineers, product managers, and the Grafana writing team to produce content for a range of products and audiences, from first-time users to experienced practitioners. Because our products and priorities evolve, we're looking for someone who learns new technical domains quickly. AI is part of how this team works. We use AI-assisted workflows and tools throughout the content lifecycle, from research and drafting to review, validation, and maintenance. You'll use these tools every day and help the team get better at using them.
Responsibilities
- Plan, research, write, and maintain documentation and learning content (concepts, tasks, tutorials, references, and in-product learning) that supports adoption and long-term product mastery.
- Use AI tools and workflows to work faster and at a higher quality: drafting, structuring, technical validation, consistency checks, and keeping content current. You apply human judgment to everything AI produces and take responsibility for its accuracy.
- Contribute to the team's shared AI workflows and skills, and look for ways to improve and automate how we create and maintain content as tools and models evolve.
- Partner with engineers, PMs, and other stakeholders to understand product requirements, interview subject matter experts, and turn complex technical detail into clear, accurate content.
- Test what you document. Run the software, follow your own procedures, and flag product and UX gaps you find along the way.
- Let data guide your priorities. We have strong docs and learning analytics. You'll use them, along with user feedback, to find content gaps, prioritize your work, and show the impact of what you ship.
- Work with the documentation manager and other writers to improve information architecture, voice, and consistency across our docs, and to make information easy to find for both people and AI-driven search and assistants.
- Manage several projects at once, using judgment to prioritize and communicate clearly when the plan changes.
- Mentor teammates and share practices that raise the quality of the team's work.
Requirements
- Experience writing or documenting enterprise or developer-facing software, with a portfolio or writing samples that show technical depth.
- Hands-on experience using AI tools and models in your writing workflow (such as LLM assistants, agentic coding tools, or custom prompts and skills), and the ability to explain how you evaluate and verify their output.
- Experience working with docs-as-code: command-line Git, GitHub (pull requests and reviews), Markdown, and common IDEs.
- Comfort working in technical environments. You can set up, run, and troubleshoot software yourself to verify what you write (for example, command line, containers, or Kubernetes, or a willingness to learn quickly).
- Experience collaborating with engineers and product managers to get accurate technical information.
- Experience working remotely and asynchronously on a distributed team.
Qualifications
- Curiosity about AI as a craft. You treat AI workflows as a professional skill. You experiment, share what works, and know where AI helps and where it doesn't.
- Technical credibility. You care about accuracy, you learn new technical domains quickly, and you ask questions until you understand them.
- Strong judgment and editing skills. You can tell good content from plausible-sounding content, and you hold the line on quality.
- Ownership. You manage multiple projects and work well both independently and collaboratively.
- Clarity. You write concisely and plainly for readers of all experience levels.
- Bonus: Experience with observability, monitoring, or cloud-native tooling, or contributing to open source documentation.
- You're an enthusiast for technically accurate content, you're unafraid of managing multiple projects, and you enjoy working both collaboratively and independently. You have a well-used copy of "The Elements of Style".
Pay
In the UK, the base compensation range for this role is GBP 81,000 - GBP 97,000. In the US, the base compensation range is $123,933 - $148,719. Actual compensation may vary based on level, experience, and skillset as assessed in the interview process. Benefits include equity, bonus (if applicable), and other benefits. Compensation ranges are country specific; if you are applying from a different location, your recruiter will discuss your specific market's defined pay range and benefits at the beginning of the process.
Benefits
- 100% remote, global culture — team members across 40+ countries united by collaboration and shared purpose.
- Scaling organization — tackle meaningful work in a high-growth, ever-evolving environment.
- Transparent communication — open decision-making and regular company-wide updates.
- Innovation-driven — autonomy and support to ship great work and try new things.
- Open source roots — built on community-driven values that shape how we work.
- Empowered teams — high trust, low ego culture that values outcomes over optics.
- Career growth pathways — defined opportunities to grow and develop your career.
- Approachable leadership — transparent executives who are involved, visible, and human.
- Passionate people — join a team of smart, supportive folks who care deeply about what they do.
- In-person onboarding — thrive from day one with fellow new "Grafanistas" to learn all about what we do and how we do it.
- Balance is key — global annual leave policy of 30 days per annum, with 3 days reserved for Grafana Shutdown Days to allow the team to really disconnect (compliant with local legislation where applicable).
I should not include the Equal Opportunity Employer statement (boilerplate). Also remove the duplicated "Compensation ranges are country specific..." lines.
Now, ensure no markdown code fences, just HTML fragment.
Let me double-check: The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Staff Technical Writer
for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment Let me parse the content: The posting starts with company description (Grafana Labs info). This could be "About the company" or "About the role". The heading "Description Of Duties" appears, then "Key Responsibilities" with a list. Then "Requirements" with a list. Then "What You'll Bring To The Role" with a list. Then there's a duplicate "What You'll Bring To The Role" with different content (more about personality traits). Then compensation info for UK and US. Then "Why You'll Thrive At Grafana Labs:" with a list of benefits/culture points. Then Equal Opportunity Employer statement (boilerplate, should be removed). Also there's mention of "Benefits include equity, bonus (if applicable) and other benefits listed here." but no specific benefits listed except in the "Why You'll Thrive" section. I need to consolidate duplicate sections. The two "What You'll Bring To The Role" sections have different content - first is about AI curiosity, technical credibility, judgment, ownership, clarity, bonus. Second is about enthusiasm, managing projects, Elements of Style. I should combine them into one section. Also, the compensation info appears twice (UK and US). I'll create a Pay section with both ranges. The "Why You'll Thrive At Grafana Labs" is essentially benefits/culture. I'll make that a Benefits section. The Equal Opportunity Employer statement is boilerplate - remove. The company description at the top: "Grafana Labs is the company behind Grafana Cloud..." This is about the company. Could be "About the company" or "About the role". Since the heading "Description Of Duties" appears later, maybe the first part is "About the company". But the instruction says use
for section headings like "About the role". The posting doesn't have an explicit "About the role" heading, but "Description Of Duties" is similar. I'll use "About the role" for the initial description? Actually the first paragraph is company description, then "Description Of Duties" heading. I'll create a section "About the company" for the first paragraph, then "About the role" for the Description Of Duties paragraph? But the Description Of Duties paragraph is a description of the role. Let's see: "We're looking for a Staff Technical Writer to create documentation..." That's about the role. So I'll have:
- About the company (first paragraph)
- About the role (the paragraph under Description Of Duties)
- Responsibilities (Key Responsibilities list)
- Requirements (Requirements list)
- Qualifications (What You'll Bring To The Role combined)
- Pay (compensation ranges)
- Benefits (Why You'll Thrive At Grafana Labs)
But note: the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those standard headings.
Let's map:
- About the role: the paragraph describing the role (under Description Of Duties)
- Responsibilities: Key Responsibilities list
- Requirements: Requirements list
- Qualifications: What You'll Bring To The Role (combined)
- Pay: compensation ranges
- Benefits: Why You'll Thrive At Grafana Labs
The company description could be "About the company" but not in the example list. However, the instruction says "e.g." so it's not exhaustive. I'll include it as "About the company".
Now, I need to ensure I don't include filler. The compensation ranges are specific (GBP 81,000 - GBP 97,000 and $123,933 - $148,719). Good.
Benefits: the "Why You'll Thrive" list includes specific benefits: 100% remote, global culture, scaling organization, transparent communication, innovation-driven, open source roots, empowered teams, career growth pathways, approachable leadership, passionate people, in-person onboarding, balance is key (30 days annual leave, 3 days shutdown). That's substantive.
Now, I'll write the HTML.
I'll structure:
About the company
About the company
Grafana Labs is the company behind Grafana Cloud...
About the role
We're looking for a Staff Technical Writer to create documentation and learning content that helps people adopt and master Grafana's observability products. You'll work with engineers, product managers, and the Grafana writing team to produce content for a range of products and audiences, from first-time users to experienced practitioners. Because our products and priorities evolve, we're looking for someone who learns new technical domains quickly. AI is part of how this team works. We use AI-assisted workflows and tools throughout the content lifecycle, from research and drafting to review, validation, and maintenance. You'll use these tools every day and help the team get better at using them.
Responsibilities
- Plan, research, write, and maintain documentation and learning content (concepts, tasks, tutorials, references, and in-product learning) that supports adoption and long-term product mastery.
- Use AI tools and workflows to work faster and at a higher quality: drafting, structuring, technical validation, consistency checks, and keeping content current. You apply human judgment to everything AI produces and take responsibility for its accuracy.
- Contribute to the team's shared AI workflows and skills, and look for ways to improve and automate how we create and maintain content as tools and models evolve.
- Partner with engineers, PMs, and other stakeholders to understand product requirements, interview subject matter experts, and turn complex technical detail into clear, accurate content.
- Test what you document. Run the software, follow your own procedures, and flag product and UX gaps you find along the way.
- Let data guide your priorities. We have strong docs and learning analytics. You'll use them, along with user feedback, to find content gaps, prioritize your work, and show the impact of what you ship.
- Work with the documentation manager and other writers to improve information architecture, voice, and consistency across our docs, and to make information easy to find for both people and AI-driven search and assistants.
- Manage several projects at once, using judgment to prioritize and communicate clearly when the plan changes.
- Mentor teammates and share practices that raise the quality of the team's work.
Requirements
- Experience writing or documenting enterprise or developer-facing software, with a portfolio or writing samples that show technical depth.
- Hands-on experience using AI tools and models in your writing workflow (such as LLM assistants, agentic coding tools, or custom prompts and skills), and the ability to explain how you evaluate and verify their output.
- Experience working with docs-as-code: command-line Git, GitHub (pull requests and reviews), Markdown, and common IDEs.
- Comfort working in technical environments. You can set up, run, and troubleshoot software yourself to verify what you write (for example, command line, containers, or Kubernetes, or a willingness to learn quickly).
- Experience collaborating with engineers and product managers to get accurate technical information.
- Experience working remotely and asynchronously on a distributed team.
Qualifications
- Curiosity about AI as a craft. You treat AI workflows as a professional skill. You experiment, share what works, and know where AI helps and where it doesn't.
- Technical credibility. You care about accuracy, you learn new technical domains quickly, and you ask questions until you understand them.
- Strong judgment and editing skills. You can tell good content from plausible-sounding content, and you hold the line on quality.
- Ownership. You manage multiple projects and work well both independently and collaboratively.
- Clarity. You write concisely and plainly for readers of all experience levels.
- Bonus: Experience with observability, monitoring, or cloud-native tooling, or contributing to open source documentation.
- You're an enthusiast for technically accurate content, you're unafraid of managing multiple projects, and you enjoy working both collaboratively and independently. You have a well-used copy of "The Elements of Style".
Pay
In the UK, the base compensation range for this role is GBP 81,000 - GBP 97,000. In the US, the base compensation range is $123,933 - $148,719. Actual compensation may vary based on level, experience, and skillset as assessed in the interview process. Benefits include equity, bonus (if applicable), and other benefits. Compensation ranges are country specific; if you are applying from a different location, your recruiter will discuss your specific market's defined pay range and benefits at the beginning of the process.
Benefits
- 100% remote, global culture — team members across 40+ countries united by collaboration and shared purpose.
- Scaling organization — tackle meaningful work in a high-growth, ever-evolving environment.
- Transparent communication — open decision-making and regular company-wide updates.
- Innovation-driven — autonomy and support to ship great work and try new things.
- Open source roots — built on community-driven values that shape how we work.
- Empowered teams — high trust, low ego culture that values outcomes over optics.
- Career growth pathways — defined opportunities to grow and develop your career.
- Approachable leadership — transparent executives who are involved, visible, and human.
- Passionate people — join a team of smart, supportive folks who care deeply about what they do.
- In-person onboarding — thrive from day one with fellow new "Grafanistas" to learn all about what we do and how we do it.
- Balance is key — global annual leave policy of 30 days per annum, with 3 days reserved for Grafana Shutdown Days to allow the team to really disconnect (compliant with local legislation where applicable).