KabuK Style Inc.のTechnical Writer — KabuK Exchangeの求人

KabuK Style is building the next generation infrastructure for the global travel industry.

Our flagship product, HafH, already connects over 30,000 accommodations across 130+ countries and serves a rapidly growing international customer base. As we scale, we are developing a new B2B platform that powers travel distribution, supplier integrations, pricing optimization, and booking infrastructure for partners around the world.

Our platform connects hotels, travel agencies, OTAs, channel managers, wholesalers, and internal KabuK products through a unified distribution, pricing, reservation, billing, and partner operations layer. The platform is designed to support Japanese hotel distribution to global demand channels while also enabling redistribution of global travel supply across partners.

We are looking for a Technical Writer to help turn complex platform architecture, APIs, product workflows, onboarding processes, and operational knowledge into clear documentation for internal teams, external partners, hotels, developers, and future customers.

This is an early platform contractor role. You will work closely with Product, Engineering, QA, Solutions, Partner Success, and Operations to create the documentation foundation that supports external launch, partner onboarding, API adoption, support operations, and long-term platform scalability.

You will create and maintain clear, structured, and accurate documentation across product specifications, API references, integration guides, onboarding materials, operational playbooks, release notes, troubleshooting guides, terminology glossaries, and partner-facing help content.

This role requires someone who can understand technical systems deeply enough to document them accurately, but also communicate them clearly enough for non-technical users, business stakeholders, hotels, and external partners.

You will not simply “write documents.” You will help define how knowledge is organized, maintained, governed, and reused across the platform organization.

▼Platform Documentation
Create and maintain documentation for KBKx platform services, including but not limited to:

• API Gateway
• Identity and Account Management
• Pricing Service
• Inventory and Supply Management
• Booking Engine
• Reservation Service
• Billing and Payments
• Supplier and Distribution Integrations
• Partner Extranet
• Hotel Onboarding
• Admin Console
• Reporting and Analytics
• Operational Workflows

Translate complex product and engineering concepts into structured documentation that can be understood by technical and non-technical audiences.

Work with Product Managers, Engineering Leads, Backend Engineers, QA, DevOps, and Solutions team members to ensure documentation is accurate, complete, and aligned with current platform behavior.

▼API and Integration Documentation
Create clear API documentation for internal and external developers, including:

• API overviews
• Authentication and authorization flows
• Endpoint references
• Request and response examples
• Error codes
• Webhook documentation
• Integration lifecycle guides
• Partner onboarding guides
• Testing and certification instructions
• Troubleshooting documentation

Support the development of external partner documentation for OTAs, travel agencies, channel managers, wholesalers, and direct hotel partners.

Help establish documentation standards for API naming, field descriptions, versioning, examples, and change communication.

▼Product and Operational Documentation
Create and maintain product documentation for internal and external users, including:

• Admin console guides
• Partner extranet guides
• Hotel onboarding manuals
• Distribution setup guides
• Pricing configuration guides
• Billing and payment process guides
• Incident response documentation
• Support escalation guides
• Release notes
• FAQ and help center content

Document operational workflows across Product, Engineering, QA, Finance Operations, Partner Success, and Support.

Help convert existing product specs, meeting notes, diagrams, and tribal knowledge into structured documentation that can be maintained over time.

▼Knowledge Management
Design and maintain a scalable documentation structure for the platform organization.

Help define documentation categories, ownership, review cycles, versioning rules, and quality standards.

Create a shared glossary of platform terms, acronyms, statuses, services, partner types, and transaction flows.

Ensure documentation is easy to search, easy to update, and useful for onboarding new employees, outsourced teams, partners, and customers.

Identify gaps in documentation and proactively work with stakeholders to close them.

▼Cross-Functional Collaboration
Work closely with:

• Product Managers to document product requirements, workflows, and user-facing behavior
• Engineering Leads and Backend Engineers to document services, APIs, integrations, and technical constraints
• QA to document test scenarios, known issues, release criteria, and regression coverage
• DevOps to document environments, deployment processes, monitoring, and incident procedures
• Solutions and Partner Success to document onboarding, implementation, and troubleshooting processes
• Finance Operations to document billing, payments, reconciliation, and adjustment workflows
• Leadership to ensure documentation supports external launch readiness

You should be comfortable asking detailed questions, challenging unclear requirements, and pushing for accuracy when documentation gaps could create operational risk.

• External API documentation for partners
• Internal technical documentation for engineering and product teams
• Partner onboarding documentation
• Hotel onboarding and extranet guides
• Operational runbooks
• Billing and payments documentation
• Troubleshooting and support guides
• Release notes and change logs
• Glossary and taxonomy documentation
• Internal knowledge base for platform teams
• External help center content for future platform users

• Understand the KBKx platform structure, core services, partner types, and documentation needs
• Audit existing documentation, product specs, diagrams, and knowledge gaps
• Define a documentation structure for internal and external platform documentation
• Begin building the platform glossary and terminology reference
• Identify the highest-priority documentation needed for external launch readiness

Within the first 3 months, you will:

• Create or improve key onboarding and technical documentation for MVP services
• Establish documentation templates and standards for product, API, operations, and partner-facing documentation
• Create initial API and integration documentation for priority services
• Document key operational workflows for support, QA, incident handling, and partner onboarding
• Establish documentation review and maintenance workflows with Product and Engineering

Within the first 6 months, depending on contract extension and platform needs, you may:

• Own the internal documentation structure for the platform team
• Create partner-facing API and onboarding documentation for external launch readiness
• Maintain release notes and change documentation for platform services
• Produce operational runbooks for support, QA, incident handling, and partner onboarding
• Help reduce repeated questions, onboarding friction, and implementation ambiguity
• Build documentation standards that can scale as the platform grows

• Documentation audit and gap analysis
• Platform documentation structure
• API documentation templates
• Service overview templates
• Partner onboarding documentation
• Hotel onboarding documentation
• Integration guides
• Troubleshooting guides
• Operational SOPs
• Incident response runbooks
• Release note templates
• Platform glossary and acronym list
• Internal knowledge base structure
• External documentation portal recommendations

Final deliverables will be agreed based on contract scope, platform priorities, and candidate availability.

You will have a meaningful role in shaping how the platform is understood, adopted, implemented, supported, and scaled. Your work will directly impact partner onboarding, developer experience, customer support, internal team efficiency, and external launch readiness.

As an early member of the Platform team, your scope may evolve based on business needs, platform maturity, and your strengths and interests. This role is not limited to the responsibilities outlined above.

The ideal candidate is someone who can operate between Product, Engineering, Operations, and external partners.

You should be able to sit with an engineer and understand an API flow, then turn that information into documentation that a partner developer can use. You should also be able to sit with a Product Manager or Operations team member and document business workflows in a way that reduces confusion, support burden, and onboarding time.

You are structured, precise, curious, and comfortable with ambiguity. You do not wait for perfect inputs. You know how to ask the right questions, extract the right information, and create documentation that makes a complex platform easier to understand and operate.

• Experience as a Technical Writer, Documentation Specialist, Developer Advocate, Product Documentation Manager, or similar role
• Experience documenting APIs, SaaS platforms, developer tools, enterprise software, infrastructure platforms, or complex business systems
• Ability to understand technical architecture, data flows, APIs, workflows, and system behavior
• Strong writing ability in English
• Ability to explain complex technical concepts clearly and concisely
• Experience working with engineers, product managers, QA, support, or implementation teams
• Experience creating documentation for both technical and non-technical audiences
• Strong information architecture and knowledge management skills
• Ability to work independently in an early-stage, fast-changing platform environment
• Strong attention to detail and commitment to accuracy
• Comfortable working across incomplete requirements and evolving systems

• Experience documenting REST APIs, webhooks, authentication flows, or integration platforms
• Experience with OpenAPI / Swagger or similar API documentation tools
• Experience with documentation platforms such as Confluence, Notion, GitBook, ReadMe, Docusaurus, Mintlify, Stoplight, or similar tools
• Experience with Git-based documentation workflows
• Experience in travel technology, hospitality, OTA, channel manager, fintech, payments, B2B SaaS, or marketplace platforms
• Experience writing partner onboarding guides or implementation documentation
• Experience creating support runbooks, incident playbooks, or operational SOPs
• Japanese, Korean, or other Asian language ability is a plus but not required
• Experience working with remote or distributed engineering teams
• Experience building documentation systems from an early stage