NasikoHybrid in Palo Alto (in/around SF Bay Area; 2–3 days/week in office)

Developer Advocate / DevRel

$140,000–$180,000 base salary; equity potentially included
Location
Hybrid in Palo Alto (in/around SF Bay Area; 2–3 days/week in office)
Type
—
Conversation
~25 min
Company
Nasiko

About the role

Nasiko

Nasiko builds AI-agent production infrastructure for developers and sells to enterprises. We’re hiring a Developer Advocate / DevRel seat to own the developer side end-to-end—turning our 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’ll be the credible technical voice to developers building on agent infrastructure—and you’ll bring an audience with you (or build one fast, with real signal). Concretely, you’ll:

  • 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 MCP gateway / routing / 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 doesn’t 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’ve translated complex agent infrastructure into developer-friendly assets (tutorials, examples, demos, or hands-on guides) that drive engagement
  • You’ve participated in open source and/or supported developer communities and events, including coordinating across regions or chapters

Who Thrives Here

  • You’re 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 don’t 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 + Comp, Logistics and Benefits

You’ll work closely with the team covering the enterprise GTM motion (founding AE) 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.

  • Location / work model: Hybrid in Palo Alto, 2–3 days per week in office
  • In-person requirement: You should be in/around the SF Bay Area to participate in community and attend events
  • Compensation: $140,000–$180,000 base salary, with equity potentially included (details shared during conversations).

Benefits (details shared during the conversation) include standard health and time-off offerings.

Non-Traditional Backgrounds

If you’ve 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.

What you'll bring

MCPA2Agatewaysruntimescoding harnessesLLM routerworkload-aware routingsandboxing

How you work

Developer communicationtechnical storytellingclarity and intentfeedback loopslisteningiterationcomfort with ambiguityhands-on judgment

About Nasiko

Nasiko is the open runtime platform for deploying and operating AI agents in production.

Use any harness. Reach any model. Measure every token. Change nothing.

Teams use Nasiko to deploy, run, secure, observe, and optimize agents across any model, framework, tool, or infrastructure—without losing visibility into what’s executing, what’s happening, and where time and spend are going.

Why now AI costs are rising, security/governance gaps are widening, and agent workflows are fragmented—making them harder to operate at scale.

Our origin Nasiko started from hands-on work running Claude Code, Codex, Cursor, and similar tools. We realized teams couldn’t easily answer what agents are running, who is spending what, which models are being used, and what agents are actually doing. Nasiko was built as Open Runtime—with coding harnesses, frameworks, and tools included—so one command discovers the agents already running and provides visibility into usage and cost across harnesses, models, users, and teams without changing how developers work.

©2026 NaviiNeopolis Global, IncTerms