Developer Advocate

Navii is an AI recruiter, running this search on behalf of Nasiko.

HERE'S HOW IT WORKS

Rather than your resume sitting in a queue, you have a conversation with Navii about your experience and what you want next. What you say reaches Nasiko's hiring team in your own words. It is a required step, and there is nothing to schedule.

NEXT STEP

A conversation with Navii about this role:

https://app.heynavii.ai/careers/developer-advocate-devrel-11f58537

ABOUT NASIKO

Nasiko builds AI-agent production infrastructure for developers and sells to enterprises: TokenOps for model and agent spend, policy enforcement for how agents reach models, tools, data and credentials, and multi-agent execution. It is the commercial layer on MIT's Project Nanda, backed by Mayfield, NVIDIA Inception and GitHub's open source security fund.

THE ROLE

This seat owns the developer side end-to-end, turning technical work like the MCP gateway, LLM router, workload-aware routing and sandboxing into developer engagement that actually leads to adoption.

Also a fit if you call yourself: Developer Advocate, Developer Relations Lead, Solutions Engineer.

THE WORK

You will be the credible technical voice to developers building on agent infrastructure, and you will bring an audience with you, or build one fast with real signal.

• Engage developers where they already are: Twitter/X first, plus GitHub and Project Nanda chapters, so Nasiko shows up consistently with substance, not noise.

• Turn technical capabilities into "I want to try that" developer experiences: posts, examples, hands-on walkthroughs, and resources that make the MCP gateway, routing and sandboxing feel usable.

• Represent Nasiko in the real world by showing up at developer conferences and open source spaces, and making those appearances convert into ongoing community momentum.

• Bring developer pain back into product by listening closely to what builders struggle with and translating it into clear feedback for the team.

• Build repeatable developer-facing output so the community does not depend on one-off bursts. Your work becomes a system.

WHAT YOU'LL NEED

• A proven developer-facing presence across platforms like Twitter/X and GitHub, and the ability to communicate technical ideas clearly to that audience.

• Genuinely technical depth. You can go beyond vocabulary and explain agent infrastructure in a way developers trust.

• Comfort with agent infrastructure concepts such as MCP, A2A, gateways, runtimes, and coding harnesses.

• Hands-on judgment. You can take a technical feature and decide what developers need to see, try, and share.

EVEN BETTER IF

• You have translated complex agent infrastructure into developer-friendly assets (tutorials, examples, demos, or hands-on guides) that drive engagement.

• You have participated in open source and supported developer communities and events, including coordinating across regions or chapters.

WHO THRIVES HERE

• You are at your best when you can get precise about what developers actually need, then turn that into concrete content and experiments.

• You communicate with clarity and intent. You do not guess what people mean, and you iterate until the message matches the outcome.

• You can handle ambiguity without spiraling. You move between big-picture community goals and the granular details that make execution work.

• You care about feedback loops. You listen, learn, and adjust quickly based on what developers respond to.

THE TEAM

You will work closely with the team covering the enterprise GTM motion and existing marketing support, while you own the developer engagement side with a technical lens. The goal is simple: make Nasiko's developer story match the quality of the product.

COMPENSATION AND LOGISTICS

$140,000 to $180,000 base salary, with equity potentially included. Full-time. Hybrid in Palo Alto, two to three days per week in office. You should be in or around the SF Bay Area to take part in community and attend events. Benefits include standard health and time-off offerings, with details shared during the conversation.

NON-TRADITIONAL BACKGROUNDS

If you have built and shared technical work in any developer-facing environment, open source, community, technical content you actually shipped, or hands-on demos, we want to hear from you.