Role Description We are modernising how our technical documentation is authored, validated, and delivered. Writers author in DITA XML; a Jenkins-based CI/CD pipeline validates the content, converts it through a two-step conversion (DITA → Markdown → HTML) using tools we own and maintain, and deploys the output to a staging server that runs our in-house Doc Review Tool. Reviewers open review sessions directly from linked JIRA tickets, and their verdicts flow back into JIRA automatically. You will own significant parts of this platform. The tools you build are used every day by our writers and reviewers, so the feedback loop is short and the impact is visible. What You'll Build - Doc Review Tool (primary): - A web application that opens from a JIRA deep link, renders staged HTML, captures inline annotations, and writes verdicts back to JIRA. Session lifecycle, concurrency, and the callback layer are yours. - Custom converters: - Two Node-based command-line tools: DITA-to-Markdown (resolves conrefs / keyrefs, emits Common Mark with front matter) and Markdown-to-HTML (templates, search index, asset fingerprinting). - Jenkins pipeline & shared library: - Declarative Pipeline plus Groovy helpers that encapsulate JIRA and Doc Review Tool integration. You also own the Docker build image that packages the toolchain. - JIRA integration: - REST API v3 end-to-end: transitions, custom fields, structured comments, outbound webhooks that trigger merge jobs. What You'll Do - Design, build, and maintain the systems above as production code used daily by writers and reviewers. - Handle failure modes deliberately: what happens when JIRA is down, when a session expires, when a webhook is late. Prefer graceful degradation over silent failure. - Cover integration boundaries with automated tests that run in CI. - Partner with technical writers on features that improve authoring and review; partner with DevOps on deployment, secrets, and observability. - Reviews pull requests and write concise design notes for non-trivial changes. - Keep runbooks and technical docs current — this is a documentation platform team; we hold ourselves to a higher bar here. Qualifications - 5+ years building and shipping production web applications (or 3+ years with clear senior-level impact). - Strong full-stack chops: comfortable owning both backend services and browser-side UI in a single codebase. JavaScript / TypeScript (Node.js) and a modern UI framework (React preferred). - REST API integration experience at a system-of-record level (JIRA, GitHub, Salesforce, or similar): pagination, rate limits, retries, auth. - Working experience with CI/CD (Jenkins, GitHub Actions, GitLab CI, or equivalent), either as heavy user or as author of shared pipeline code. - Comfortable with Git/GitHub, Linux command line, and Docker. Solid automated testing habits. - You write things down. Design notes, PR descriptions, runbooks — concise, structured, unambiguous. - Comfortable working with non-engineers; technical writers are the primary users of this platform. Nice to Have - Familiarity with DITA XML, DITA-OT, or another structured-content pipeline (Antora, Sphinx, MkDocs). - Groovy / Jenkins shared library experience; static-site generators or Markdown pipelines (unified/remark, markdown-it). - Atlassian ecosystem (JIRA REST v3, ADF comment bodies, JQL); SARIF or another structured lint-report format. - A background in technical writing, or a track record of collaborating deeply with a documentation team. What Success Looks Like - First 90 days: you have shipped a substantive change (a converter feature, a Doc Review Tool improvement, or a shared-library helper) and are handling PR reviews for at least one component. - First 6 months: you own at least one integration surface end-to-end and have led the design of a non-trivial change through review and rollout. - First year: you are influencing the platform roadmap and shaping team engineering practices — testing standards, deployment approach, on-call playbook. Why Join - Real users, fast feedback. Writers and reviewers use what you build daily; when something is good or broken, you hear about it within hours. - Full-stack ownership. You build the CLI, the service, the UI, the CI integration, and the deployment path — few web developer roles give you all of that. - Interesting engineering. Cross-system integration, structured content transformation, session and workflow modelling — not another CRUD app.