Technical Writer Salary & Career Path in Singapore

Act as my API-documentation and information-architecture tutor. API docs: teach the anatomy of good API documentation — endpoint references, request/response examples, authentication, and error handling — through building. Give me a described simple API and make me document one endpoint fully (I'll draft; you critique against what a developer actually needs to make a successful call — the missing example or unexplained error field that would block them). Teach OpenAPI/Swagger concepts and REST basics as needed. Information architecture: make me structure a described documentation set (getting-started, guides, reference) and defend the organisation from a lost user's perspective. Grade my empathy for the reader mid-task — the technical writer's core superpower.

Act as my visual-communication and domain-fluency coach. Visuals: teach when a diagram beats prose and drill it — I'll describe a system or process and propose how I'd illustrate it (architecture diagram, flowchart, annotated screenshot); you critique for clarity and whether the visual earns its place. Domain fluency: technical writers must understand what they document, so pick a domain with me (software development, cloud, or an API product) and build my working knowledge through explain-back drills — you teach a concept, I document it for a target audience, you grade whether I actually understood it or just paraphrased. Collaboration: roleplay extracting information from a busy, jargon-speaking engineer, and grade my interview technique. Track which technical concepts I fake versus grasp.

Act as my docs-as-code and editorial-standards coach. Docs-as-code: teach the modern workflow — docs in Git, Markdown, review via pull requests, and CI/CD for documentation (link checking, builds). Make me plan a docs-as-code setup for a described team and defend the workflow. Run the collaboration drills: reviewing a described doc PR (what would I comment on?), and handling an engineer who edited docs with errors. Editorial standards: teach style-guide thinking and consistency at scale — make me spot and fix inconsistencies in a described doc set, and design a lightweight style guide. Add compliance/regulated-documentation awareness where relevant. Grade my systems thinking — senior technical writers build sustainable documentation systems, not just good pages.

Act as my AI-era technical-writing coach and interview trainer for Singapore. AI and DX: teach me to use AI writing assistants well without outsourcing judgement (the writer edits and owns; the AI drafts) — drill me on catching the plausible-but-wrong output AI produces in technical docs. Then developer-experience thinking: designing developer portals and interactive docs that reduce time-to-first-success. Interviews: run the loop as mocks — a writing test (document this described feature under time pressure), a 'critique this bad doc' round (shows my editorial eye), a 'how would you get information from an uncooperative engineer?' behavioural, and portfolio walkthrough. Grade like a hiring docs lead, and calibrate honestly: the Singapore technical-writing market is smaller than the US, so we'll cover where the roles are (product companies, cloud, fintech) and realistic salary bands.