Anakin

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 onboarding 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 onboarding 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 once 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 onboarding 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 onboarding 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

GTM Automation Engineer Why this role exists We are building a revenue engine that scales through systems, not headcount. This role exists to design and harden the automation layer across the GTM stack — inbound, outbound, routing, enrichment, lifecycle transitions, alerts, dashboards, and workflow health. The goal is simple: GTM processes should run fast, correctly, and reliably, without silent failures, duplicate actions, or brittle logic. This is not a classic RevOps admin role. This is a builder role for someone who wants to own the automation infrastructure behind revenue execution — the layer that turns messy GTM intent into clean, auditable, scalable systems. If you enjoy translating ambiguity into logic, preventing operational drift, and building workflows that survive real-world edge cases, this role is for you. What you’ll own You will own the systems and automation layer across the GTM lifecycle. Core stack You should expect to work across: Workflow / orchestration: n8n, Make, Zapier, Workato, Tray.io, Retool CRM / GTM systems: HubSpot, Close, Apollo, Clay, Airtable Comms / collaboration: Slack, Gmail, Google Sheets, Notion APIs / integration layer: REST APIs, webhooks, auth flows, OAuth LLM / AI tooling: OpenAI, Claude, Gemini APIs Scripting / validation: JavaScript / Python / SQL where needed We do not expect you to blindly connect tools. We expect you to understand where automation ends and engineering judgment begins. What the role actually involves 1) Architect and harden GTM automations Build and maintain reliable workflows across marketing, sales, recruiting, and customer success functions. This includes: triggers branching logic routing retries fallback paths failure alerts manual review logic auditability You should think like a systems engineer, not just a workflow builder. 2) Own inbound automation Design flows that capture, qualify, enrich, route, and follow up on inbound demand. Examples: form submissions lead capture meeting-booking triggers enrichment flows dedupe-safe lead creation territory / segment based routing SLA-sensitive follow-up alerts only after successful downstream writes Fast is not enough. Routing needs to be fast and correct. 3) Build outbound enablement workflows Support SDRs and AEs with systems that reduce manual work and improve consistency. Examples: sequencing triggers task creation account research pipelines personalization support flows field completeness checks stage-based nudges leadership alerts hygiene enforcement The goal is not more workflow for the sake of workflow. The goal is cleaner execution with fewer misses. 4) Own data hygiene and governance You will be the quality gate across GTM systems. This includes: deduplication logic lifecycle stage definitions property governance naming conventions ownership rules access controls audit checks data quality reviews You should care deeply about correctness. Silent data drift is a bug. 5) Build integrations with observability Maintain integrations across internal and external systems using a mix of iPaaS, APIs, webhooks, and code where necessary. You will also implement monitoring such as: run failures timeout alerts duplicate-action checks workflow uptime broken data-flow detection incident runbooks A workflow that “usually works” is not production-grade. 6) Build the GTM truth layer Create and maintain dashboards and operational reporting across the funnel. Examples: inbound volume MQLs / SQLs routing SLAs pipeline creation speed-to-lead stage conversion workflow failure rates funnel leakage enrichment quality manual-review load You should be comfortable building systems that are not only automated, but measurable. 7) Document systems that survive scale Document: workflow maps integration dependencies business rules fallback logic owner-routing logic failure conditions governance rules change history Good documentation should make the system easier to audit, extend, and debug. What success looks li

Software Engineering Intern (Backend / Systems / Scraping Infrastructure) Anakin (YC S21) | min. 6 months to 12 month Internship | PPO Track Location: HSR Layout, Bangalore (In-office, Mon–Fri) Stipend: ₹25,000/month Duration: minimum 6 month and max. 12 months About Anakin Anakin is the data engine behind real-time competitive intelligence of global online commerce companies. We help large internet businesses understand markets faster by collecting, structuring, and generating insights from massive volumes of public web data. Our systems operate across categories, geographies, and constantly changing websites. That means the engineering problems here are not toy problems. They involve scale, reliability, anti-bot systems, dynamic pages, messy edge cases, and production pressure. If you want an internship where you mostly shadow people, this is not that. If you want to work on real systems, solve hard backend problems, and earn a serious PPO on merit, keep reading. What this role is This is a hands-on backend/systems internship for campus developers who want to become strong engineers early. You will work on real production-facing problems across backend systems, APIs, automation, data pipelines, scraping infrastructure, reverse engineering, debugging, and reliability. You will not be hired to “learn around the edges.” You will be expected to understand problems clearly, write code that works, debug what breaks, and improve systems with ownership. This role is designed for people who want steep learning, high accountability, and a front-row seat to how a high-speed startup engineering team operates. Why this role is hard This internship is hard because the problems are real. Web systems change without warning. Dynamic websites break. Anti-bot measures evolve. Production bugs rarely come with clean answers. Good code is not enough; you need judgment, debugging discipline, speed, communication, and persistence. You will be expected to: understand ambiguous problems quickly break them into workable parts ship clean solutions test edge cases ask for help intelligently when blocked recover fast when things fail This is not a “complete one assignment and wait” internship. This is a builder’s internship. What you will work on Build and scale backend systems, internal services, APIs, and data pipelines Work on scraping and web automation infrastructure for dynamic websites Debug production issues and improve reliability, performance, and maintainability Write clean, testable, secure, maintainable code Participate in code reviews, architecture/problem discussions, and testing strategy Benchmark tools, explore better approaches, and improve engineering workflows Ship features end-to-end with strong ownership Proactively identify bottlenecks, bugs, and opportunities for system improvement What we’re looking for Technical Strong fundamentals in Data Structures and Algorithms Good programming skills in Python, Java, or any solid backend language Strong understanding of backend fundamentals, APIs, databases, and debugging Hands-on project experience in one or more of the following: backend development automation APIs web crawling/scraping reverse engineering systems projects Comfort with reading documentation, experimenting, and learning independently Ownership Takes tasks from start to finish instead of waiting to be told every next step Communicates clearly when blocked Has high standards for output and follow-through Likes solving problems deeply instead of superficially Can handle feedback, pressure, and iteration AI usage We value thoughtful use of AI tools. Using AI to move faster is good. Blindly depending on AI without understanding what the code does is not. We are looking for engineers who can use AI as leverage, not as a substitute for thinking. Who will do well here You’ll likely do well if: you enjoy solving difficult technical problems you like backend/systems more than surface-level UI work you get energy fro