Web Development Intern

Web Development Intern – Developer Relations About Infrasity Infrasity is an **engineering-led GTM company** . We partner with DevTools, infrastructure, and AI startups to help them launch fast, showcase product features, and reach their developer audience. Our work spans technical content, community-driven distribution, and developer-focused marketing all with the depth and credibility of engineers. Web Development Intern – Technical Content About Infrasity Infrasity is an engineering-led GTM company. We partner with DevTools, infrastructure, and AI startups to help them launch fast, showcase product features, and reach their developer audience. Our work spans technical content, community-driven distribution, and developer-focused marketing all with the depth and credibility of engineers. **Role Overview** You'll build small, sharp, public things: agents, MCP servers, Claude skills, and open-source repos. Some serve Infrasity's own GTM stack (e.g. our MCP server at app.infrasity.com/api/mcp, our dev-gtm-claude-skills repo); some turn a client's product into a working demo developers can clone and run. Writing matters — clean READMEs, a tight launch post — but it's how you ship what you built, not the deliverable itself. If your instinct when you learn a new tool is "let me wire up an agent / skill / repo around it," this is your role. **Responsibilities** * Build and ship MCP servers, Claude skills, agents, and CLIs — real, runnable, public. * Stand up open-source repos end to end: working code, clean README, examples, and a launch (GitHub, Reddit, Dev.to, HN where it fits). * Turn client product features into developer-first artifacts: sample apps, SDK integrations, automation workflows. * Write the docs the build needs — READMEs, quickstarts, walkthroughs — grounded in code you actually wrote. * Instrument and watch traction: stars, clones, backlinks, signups. Tie what you ship to outcomes. * Engage in the communities where your work lands — answer questions, take feedback, iterate. **What Success Looks Like** * A steady stream of public, working artifacts (repos / skills / MCP servers / agents) that developers star, clone, and use. * Launches that drive real backlinks and traffic to Infrasity and client sites. * Developers treat Infrasity's output as credible because the code holds up — not because the post reads well. **You Should Apply If** * You've shipped something public: an OSS repo, an MCP server, a Claude skill, an agent, a working SDK demo. **Share links — code first.** * You're comfortable reading a product's docs/API and building against it without hand-holding. * You can write a clear README and a launch post once the thing works.