DevRel

Build With Developers. Not Just For Them.

At Anakin, we’ve built an early-stage API product designed for speed, experimentation, and real developer feedback.

We’re looking for a

DevRel

who lives on the internet - someone who understands developer conversations, builds communities naturally, and knows how to turn feedback into product momentum.

This is not a passive content role. It’s high-ownership, high-visibility, and deeply impact-driven.

What You’ll Focus On (First 3–6 Months)

• Reduce friction (docs, examples, clarity)
• Identify and deeply support the first serious API users
• Increase meaningful developer sign-ups
• Build structured feedback loops into engineering
• Refine messaging through real developer conversations

~80% of this role is external-facing, engaging developers globally (US-facing exposure preferred).

What You’ll Do

• Improve API documentation and flows
• Engage developers across HN, Reddit, Discord, Twitter/X, etc.
• Separate curiosity from real usage
• Collect and synthesize actionable product feedback
• Help debug integrations and close the loop fixes ship
• Create lightweight technical content (guides, demos, walkthroughs)

What We’re Looking For

• ~1 year of DevRel / API-facing experience (flexible for high-impact profiles)
• Prior DevRel preferred, or strong proof of building in public (community, writing, open-source)
• Strong communication + comfort with APIs and integrations
• Ability to turn developer conversations into product insights
• Comfortable with ambiguity and fast-changing products

If you care more about real adoption than surface-level community numbers, this role is for you.

Candidate FAQs – Developer Relations

Question: What do we do at Anakin

• Answer: At Anakin, we turn the internet into a reliable data source for software. We provide developer tools that let you access any web data, including websites, apps, and documents, through a clean API. Our platform handles all the hard parts, such as scraping behind logins, rate limits, proxies, and JavaScript heavy pages, so you get structured, reliable data without spending weeks building and maintaining pipelines. Essentially, we make the outside world programmable for developers and companies of any size.

Question: Who are the founders

• Answer: - Mohit Prateek (IIT Bombay)

• Rashmi Bala (IIT Kanpur)

Question: What about funding & revenue

• Answer: We’ve raised USD 1.8M in seed funding, are currently at USD 3.25M in revenue, and are profitable.

Question: What is the headcount

• Answer: As of Feb 2026, we are 60+ team members.

Question: What is the base location? Is it remote, hybrid, or in-office

• Answer: The role is based out of HSR Layout, Bangalore. We work from the office Monday to Friday.

Role-Specific FAQs

Question: What does DevRel mean at Anakin

• Answer: DevRel here is not about events or vanity community metrics. It’s about:

• Improving developer experience
• Supporting serious API users
• Building tight feedback loops into engineering
• Driving meaningful adoption

~80% of the role is external-facing.

Question: What will success look like in the first 3–6 months

• Answer: - Reduced friction (docs, examples, clarity)

• First serious API users identified and supported
• Increase in meaningful developer sign-ups
• Structured product feedback influencing roadmap

Question: Is this a content-heavy role

• Answer: Content is part of it, but not the core. The focus is on real conversations, debugging support, and improving developer experience. Lightweight technical content supports this.

Question: Is prior DevRel experience mandatory

• Answer: Preferred, yes. If not formally in DevRel, you should demonstrate strong community-building or “building in public” experience (open-source, Twitter/X, Discord, writing, etc.).

Question: How technical does this role need to be

• Answer: You should be comfortable discussing APIs, integrations, debugging issues, and developer workflows. You don’t need to be a senior backend engineer, but you must be technically credible.

Question: What kind of developer audience are we targeting

• Answer: Primarily global developers, with preference for US-facing exposure. Strong communication skills for international audiences are important.

Question: What is the hiring process

• Answer: Typically 2–3 structured rounds, including:

• Community/product thinking assessment
• Technical & DevRel depth discussion
• Final round with leadership

We maintain a strong hiring bar - high conviction candidates move forward.

• ~1 year of DevRel / API-facing experience (flexible for high-impact profiles)
• Prior DevRel preferred, or strong proof of building in public (community, writing, open-source)
• Strong communication + comfort with APIs and integrations
• Ability to turn developer conversations into product insights
• Comfortable with ambiguity and fast-changing products