Product Developer, intern
Infrasity
Posted 17 Nov 2026, 09:59 IST
This job at a glance
- Who can apply
- Freshers and up to 1 year
- Must know
- MarketingREST APIsGit
- Work
- On-site in New Delhi · internship
- Pay
- Not stated by the employer.
- Skill demand
- REST APIs21%Marketing11%Git8%of 98 similar fresher jobs posted in India this week
- Listed
- 17 Nov 2026 · still open
Sign in free to see which of these skills your resume already shows.
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.
Key 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.
Qualifications
- 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.