Tara Singh Senior Documentation Engineer
Bengaluru, India • tara.singh.docs@gmail.com • +91 80 555 0184
Profile Summary
- Senior Documentation Engineer with 8 years of experience building docs infrastructure for developers on an API platform and collaboration suite used by back-end and integration engineering teams across developer tooling, API platforms, and integration software, specializing in spec-driven docs, tested code samples, and docs CI.
- Hands-on coverage across docs platform (Docusaurus), spec format (OpenAPI 3), docs CI (GitHub Actions), and SDK languages (curl, Node, Python, and Go), credentialed through B.Tech in Computer Science, IIIT Bangalore.
- Deep craft in API reference generated from OpenAPI with examples that compile and run, docs-as-code pipelines that build, lint, and ship the site on every merge, snippet-testing harnesses that catch a broken sample before it hits production, and versioning, changelogs, and deprecation comms tied to the API lifecycle, applying methods such as embedded with engineering on PRs, API design reviews, and release planning and time-to-200 tracked on every quickstart and folded back into the next release to deliver docs that get a developer from zero to a successful API call in one read.
- Engaged collaborator working cross-functionally with API Engineering, Platform, SDK, DevRel, and Support inside a docs engineering team embedded with the API platform and SDK orgs, contributing to API design reviews, SDK release planning, and the spec-to-docs handoff that ties every endpoint shipped to a documented and tested reference page.
- Mentor who shares craft and fosters a culture of every code sample is tested in CI against the live SDK before the docs ship and link integrity, spec drift, and OpenAPI lint run as gating checks on every PR through paired PR review and snippet-harness contributions, while running a monthly API design review with Engineering and a Bengaluru docs-engineering meetup and contributing OpenAPI tooling and Redocly plugins back to the public ecosystem.
Technical Skills
- API Specs & Reference:
- OpenAPI 3 and Swagger, AsyncAPI for events and webhooks, GraphQL schemas and SDL, Protobuf and gRPC reflection, Spectral and Redocly linting, JSON Schema and JSON-LD, OpenAPI to Redocly and Stoplight generation
- Docs Platforms & SSGs:
- Docusaurus and MDX, Redocly Reference and Portal, MkDocs with Material, ReadMe and Mintlify, Stoplight Elements, Hugo and Next.js docs themes, Markdoc and remark plugins
- Docs-as-Code & CI:
- GitHub Actions for docs CI, Vercel and Cloudflare Pages preview deploys, Vale and Spectral linting, link checkers and dead-link gates, build caching and incremental rebuilds, branch-based versioning, Lefthook and pre-commit hooks
- Tested Code Samples:
- curl, Node, Python, and Go samples, snippet-test harnesses run on every PR, request and response capture from real sandbox runs, fixture-based replay tests, multi-language snippet generators, golden-file diff checks
- Onboarding & Quickstarts:
- time-to-first-200 instrumentation, copy-paste quickstart flows, end-to-end integration walkthroughs, sandbox keys and try-it consoles, getting-started ladders, hello-world to production paths
- SDK & Integration Docs:
- SDK reference across Node, Python, Go, Java, and Ruby, webhook and event payload guides, OAuth and API-key flows, idempotency and retry patterns, rate-limit and pagination guides, server-side and browser-side examples
- Tooling & Automation:
- Node and Python scripts for doc generation, custom Docusaurus and MDX plugins, OpenAPI to TypeScript types, schema-diff and breaking-change detectors, changelog generators from PR labels, GitHub bots and pull-request automation
- Information Architecture:
- developer portal IA across concepts, guides, and reference, progressive disclosure for senior and new readers, search-first IA tuned for Algolia DocSearch, versioned trees and stable URL design, taxonomy and cross-linking strategy
- Versioning & API Lifecycle:
- versioned API docs with stable URLs, changelog from spec diffs, deprecation notices and sunset timelines, migration guides between major versions, breaking-change comms tied to engineering release notes
- Credentials & Education:
- B.Tech in Computer Science, IIIT Bangalore, prior Software Engineer experience that specialized into docs, contributor to the Redocly and OpenAPI ecosystems on GitHub
Education
International Institute
of Information Technology Bangalore
B.Tech in Computer
Science
Work Experience
Postman
Senior Documentation
Engineer
- Owned the docs platform and public API reference for the Postman API docs platform, public API reference, and SDK guides across the API platform reaching 430,000 monthly developer readers across 520 live reference pages, paired with 9 API engineering and SDK leads on the docs roadmap, the spec-to-docs handoff, and the reader-facing surface of every shipped endpoint.
- Drove spec-driven reference around API reference generated from the source-of-truth OpenAPI spec with Redocly and a custom Docusaurus theme, generating 180 endpoints and 42 webhook events from the spec on every release, and cutting spec-to-docs drift from 14% to under 1% through Spectral lint and a spec-diff bot in CI.
- Built the docs-as-code infrastructure on a docs-as-code pipeline on GitHub Actions with Spectral lint, Vale style, link checks, and preview deploys on every PR, standardizing the site on Docusaurus, cutting CI build time to under 90 seconds on every preview deploy, and shipping 780 docs pull requests in three years.
- Ran tested code samples through a snippet-testing harness that compiles and runs every code sample against a live sandbox on every PR, keeping 1,600 snippets green across 6 SDK languages, and dropping sample breakage caught after merge from 22 a quarter to 2 a quarter across the public reference.
- Shipped developer onboarding around copy-paste quickstart flows instrumented for time-to-first-200 across every supported SDK, authoring 24 quickstarts tied to the most common integration paths, and cutting median time-to-first-200 from 17 min to 4 min across the supported SDKs.
- Wrote the docs tooling around Node and Python scripts that generate reference, lint specs, diff schemas, and post changelogs straight from PR labels, shipping 11 internal docs tools, gating 140 broken links a month at PR time, and saving the docs team 32 author hours a sprint that used to go to manual reference upkeep.
- Owned versioning, changelogs, and the API lifecycle on versioned docs trees with auto-generated changelogs, deprecation notices, and migration guides tied to every API release, maintaining 3 active API versions side by side, publishing 210 changelog entries from spec diffs, and lifting support-ticket deflection from 31% to 58% on the migrated and rewritten reference.
Hasura
Software Engineer,
Developer Docs
- Wrote SDK and integration docs around SDK and integration docs spanning the Node, Python, and Go clients plus the GraphQL schema reference, covering 4 client SDKs end to end, and shipping 38 integration guides across Postgres, BigQuery, and the major front-end frameworks the platform shipped support for.
- Reshaped the developer portal information architecture on a developer portal IA split into concepts, guides, and reference with Algolia DocSearch tuned for senior and new readers, organizing 9 top-level sections across concepts, guides, and reference, and lifting search success from 58% to 81% on the most-trafficked queries.
- Embedded with engineering on embedded with the GraphQL engine team on API design reviews, RFCs, and the docs PR queue, attending 46 API design reviews and flagging 14 RFCs that needed migration guides before the change could ship to a stable version.
- Wrote doc-generation automation around Node scripts and a Gatsby plugin that generated GraphQL schema docs and migration tables straight from the source repo, shipping 7 generation scripts adopted by the docs team, and cutting manual edit time per release from 18h to 4h a sprint across the GraphQL schema and migration reference.