5 Mkdocs Jobs

About the Role We are looking for an experienced Technical Writer to join our product and engineering teams. This role involves creating clear, comprehensive, and user-friendly documentation for our applications, developer APIs, and integration workflows. You will work closely with engineers, product managers, and designers to produce documentation that empowers users and developers to use our platform effectively. Key Responsibilities Documentation Creation Write and maintain end-user guides, technical documentation, API reference docs, and integration guides . Ensure that all documentation is clear, concise, structured, and up-to-date. Produce quick start guides, tutorials, FAQs, and release notes . API Documentation Collaborate with engineers to document REST/GraphQL APIs using tools such as Swagger/OpenAPI . Provide code samples, request/response examples, and integration workflows. Collaboration & Process Work closely with product managers and engineers to understand requirements, workflows, and new features. Participate in scrum meetings and design sessions to anticipate documentation needs early. Content Management Own the documentation lifecycle, including organization, versioning, and publishing . Establish and maintain a documentation style guide and best practices . Tooling and Delivery Use modern documentation tools for authoring, collaboration, and publishing. Manage online documentation portals and knowledge bases for external and internal audiences. Required Skills and Qualifications Technical Writing Expertise 4+ years of experience as a technical writer or documentation specialist . Ability to explain complex technical concepts in simple, structured documentation . Domain Knowledge Experience documenting enterprise applications, APIs, and integrations . Familiarity with REST APIs, GraphQL, JSON data structures , and software development workflows. Modern Documentation Tools (Experience in several of these)Markdown / AsciiDoc / reStructuredText Swagger / OpenAPI / Postman / Redocly for API documentation Confluence / Notion / GitBook / ReadTheDocs / Docusaurus Static site generators (Hugo, MkDocs, Jekyll) for docs-as-code Version control systems (Git/GitHub) Soft Skills Excellent written and verbal communication. Detail-oriented, with strong organizational and planning skills. Ability to work independently and as part of a cross-functional team. Preferred Qualifications Experience with docs-as-code workflows integrated with CI/CD. Exposure to developer-focused documentation (SDKs, APIs, libraries). Familiarity with UX writing principles . Education Bachelors degree in English, Communications, Computer Science, or a related field (or equivalent experience). What We Offer Opportunity to create world-class documentation for enterprise users and developers . Collaborative environment with direct access to product managers, designers, and engineers . Competitive salary, benefits, and growth opportunities. Show more Show less

The Technical Writer role in Melbourne will require you to collaborate with Engineers to gain a deep understanding of the COE product and its documentation needs. Your primary responsibilities will include producing high-quality documentation that adheres to relevant standards and is tailored to the target audience. This will involve crafting user-friendly text for interfaces, online help resources, and developer guides. Additionally, you will be tasked with developing tutorials to assist end-users in navigating various applications and software tools. A key aspect of the role will be the analysis of current and potential content to identify opportunities for content reuse and single-sourcing. Moreover, you will be responsible for establishing and managing the information architecture. To excel in this position, you should possess expertise in documentation tools like Code framework and have familiarity with the Developer Platform/Backstage. Knowledge of developer platforms such as Backstage, along with proficiency in YAML and MkDocs, will be essential for effectively fulfilling the duties of this role. Additionally, experience in Software Development Life Cycle (SDLC) processes will be advantageous for this position.,

The technical writer role in Melbourne/Sydney involves collaborating with Engineers to gain a deep understanding of the COE product and its documentation requirements. You will be responsible for producing high-quality documentation that adheres to relevant standards and is suitable for the target audience. This includes writing user-friendly interface text, online help, and developer guides, as well as developing tutorials to assist end-users in using various applications. Additionally, you will analyze current and potential content to identify opportunities for reuse and single-sourcing, while also creating and managing the information architecture. The ideal candidate should have experience working with documentation frameworks like Docs like Code and be well-versed in the Developer Platform/Backstage environment. Proficiency in developer platform tools such as Backstage, YAML, and MkDocs is essential for this role. Familiarity with the Software Development Life Cycle (SDLC) is also beneficial. Should you require further clarification or have any inquiries, please feel free to reach out.,

As a Technical Writer, you will be responsible for creating and maintaining technical documentation to support various teams within the organization. Your core technical skillsets will include expertise in technical writing and documentation strategy, with a focus on API documentation for REST and SDKs in languages such as Python, JavaScript, and Java. You should also possess programming abilities to read and write in Python and JavaScript, with Java being desirable. Your role will involve creating code samples and multi-language walkthroughs to assist developers in understanding and implementing various features. Additionally, you should have knowledge of front-end and back-end integration, as well as experience with documentation-as-code tooling such as MarkDown, Sphinx, MkDocs, and Docusaurus. Familiarity with version control systems like Git and CI/CD workflows for automated documentation builds will be essential. You will be responsible for tracking usage and feedback metrics, auditing for accuracy, and reviewing documentation pull requests to ensure the quality of the content. In terms of process and collaboration skills, you should be well-versed in Agile methodologies, including participation in sprint planning and stand-up meetings. Effective cross-functional communication with engineers, developer relations teams, and no-code users is crucial. You should have a strong sense of user empathy and advocacy, catering to both technical and non-technical audiences. Establishing style guides and standards, and enforcing consistency in documentation will be part of your responsibilities. Experience with low-code or no-code platforms will be considered a bonus, along with engagement in open-source communities and best-practice research. Your role will involve collaborating with various teams and stakeholders to deliver high-quality technical documentation that meets the needs of the target audience. Overall, as a Technical Writer, your role will be pivotal in ensuring clear and comprehensive documentation that supports the development and usage of various products and services within the organization.,

Senior Technical Writer The One Who Can Make Our Docs Sing (and Not in Comic Sans) Lets be clear right out of the gate: We’re not looking for a “person who can type words into a page.” We’re looking for that rare unicorn of a technical writer who knows that documentation is as much a product as the product itself. Someone who sees the art in clarity, the science in structure, and the satisfaction in hitting “publish” on something so good people actually thank you for it. Here at blueBriX , we build healthcare tech that actually helps people — not just something that looks impressive in a demo and falls apart in the real world. And to do that? Our documentation has to be bulletproof, developer-approved, and genuinely useful. Because bad docs? They cost time, money, and patience — three things we refuse to waste. What We’re Sick Of (and You Probably Are Too) API docs that look like someone dumped their brain into Notepad and called it a day. Release notes that ramble like a bad podcast. “We’ll update the docs later” as an acceptable sentence. Teams who think writing and documentation are interchangeable. If you’ve just nodded so hard you almost sprained your neck, keep reading. What You’ll Actually Be Doing (And yes, this is the part where you either get excited or close the tab.) Wrangling chaos — turning messy product specs, half-baked Jira tickets, and “oh yeah, I forgot to mention” Slack messages into crisp, usable documentation. Building API docs so clear even junior devs can build without pinging you 20 times. Owning the content strategy — if it’s written, you either wrote it or made it better. Making sure our docs and our product are always in sync (no “we’ll fix it later” excuses). Partnering with Product, QA, and SMEs to actually understand the tech before you explain it. Gathering feedback from users and iterating until the docs work as hard as the code. You’ll Know This Role Is For You If You’ve stared down an undocumented API and thought, Challenge accepted. You’ve cut a 10-page release note down to three pages and made it better in the process. You get genuinely irritated when terminology isn’t consistent across a platform. You’ve been the person who quietly fixed the developer-written “documentation” before it saw daylight. You’ve muttered “Not on my watch” at bad help text. Stuff We’ll Brag About Offering An on-site role in Kochi, Kerala — because leaning over someone’s desk beats waiting three hours for a chat reply. A team that respects your craft and knows good documentation saves everyone’s sanity. A gym in the office — so you can work your brain and your biceps in the same building. Ownership, impact, and the chance to leave your fingerprints on something that matters. Who Shouldn’t Apply People who think “technical writing” means copy-pasting from Jira. Folks who need to be reminded what they’re working on. Anyone who thinks “good enough” is a compliment. Final Word: If you’re the type of technical writer who thinks clarity is power, precision is non-negotiable, and “good docs” is a compliment worth chasing — then stop scrolling. Apply. Bring your brain, your precision, and maybe a red pen. You’re going to need it. blueBriX is ready for you. Are you ready for us?