Content Writing - Internship

About the internship:Make sure the person following our instructions never has to guess. Developers do not read our marketing. They read our documentation, or they ask an AI that read our documentation. Either way, docs are where we win or lose the build, and the difference between a developer shipping and giving up is usually one missing sentence. This is not a role where you tidy up what engineers hand you. You will follow our own instructions on a clean machine, find the exact point where they stop working, and fix it. That is the whole job, repeated. It is also the most honest work in the building. Either the quickstart runs or it does not, and nobody can argue with you about it.

Selected intern's day-to-day responsibilities include:

1. Run quickstarts and integration guides on a clean environment and record every point of failure

2. Rewrite the steps that fail, and add missing prerequisites

3. Update code samples to the currently shipping SDK version

4. Write new guides for features that have none

5. Write long-form content for the funnel: tutorials, integration walkthroughs, migration and comparison pieces that people arrive on and act from

5. Fix broken links, stale screenshots and incorrect page metadata

6. Interview engineers to source accurate technical detail

7. Maintain a log of recurring documentation defects and report them to the owning teamWho can apply:Only those candidates can apply who:are available for full time (in-office) internshipcan start the internship between 16th Oct'26 and 20th Nov'26are available for duration of 6 monthshave relevant skills and interestsStipend:INR₹ 15,000 - 20,000 /monthDeadline:[hidden]:59:59Other perks:Certificate, Letter of recommendation, Flexible work hours, Informal dress code, 5 days a week, Free snacks & beveragesSkills required:Social Media Marketing, Content Writing, Creative Writing and Technical WritingOther Requirements:1. You can read code even if you do not write much of it. You can tell what a snippet is doing and spot when it contradicts the text above it.2. You are comfortable in a terminal, a package manager and a code editor3. You are precise by temperament. Inconsistent naming bothers you.4. You ask the question everyone else is too embarrassed to ask, which is usually the one the reader has too5. You finish. An almost-correct guide is a broken guide.6. You have built something with an SDK or an API, however small7. You have contributed documentation to an open source project, even a typo fix8. You know what MCP is, or you will have worked it out before the interview9. You have strong opinions about a documentation site you admire, and can say whyAbout Company:CometChat is a full-stack conversational platform built to unify every layer of interaction, bringing together real-time chat, messaging, voice, video, AI agents, moderation, notifications, and analytics in one modular, developer-first solution.

Our latest product, Crossword, brings conversational AI to commerce, built for high-transaction businesses where conversation drives retention and revenue. Our company has seen rapid growth, marked by participation in the Techstars Boulder Accelerator in 2019, followed by investments from experienced investors, including a Series A round. We were also recognized on Forbes' 2026 America's Top 500 Startup Employers list, reflecting the team and culture we've built. We believe the future interface is conversation, not clicks. That's why we're building the infrastructure for AI-powered conversations from human-to-human and human-to-agent to multi-party AI collaboration.

Responsibilities

Make sure the person following our instructions never has to guess. Developers do not read our marketing. They read our documentation, or they ask an AI that read our documentation. Either way, docs are where we win or lose the build, and the difference between a developer shipping and giving up is usually one missing sentence. This is not a role where you tidy up what engineers hand you. You will follow our own instructions on a clean machine, find the exact point where they stop working, and fix it. That is the whole job, repeated. It is also the most honest work in the building. Either the quickstart runs or it does not, and nobody can argue with you about it.

Selected intern's day-to-day responsibilities include:

1. Run quickstarts and integration guides on a clean environment and record every point of failure

2. Rewrite the steps that fail, and add missing prerequisites

3. Update code samples to the currently shipping SDK version

4. Write new guides for features that have none

5. Write long-form content for the funnel: tutorials, integration walkthroughs, migration and comparison pieces that people arrive on and act from

5. Fix broken links, stale screenshots and incorrect page metadata

6. Interview engineers to source accurate technical detail

7. Maintain a log of recurring documentation defects and report them to the owning team