Digital Identity / Developer Infrastructure
Moca Network — AIR Kit
Owning the technical relationship with enterprise partners — from first scoping call through documentation, reference builds and live integration.
- Role
- Developer Advocacy · Integration & Sales Engineering · DevRel
- Years
- 2025 — Present
- Links
- docs.moca.network
Context
Identity infrastructure only matters if partners can actually integrate it. The work sits between enterprise stakeholders who need commitments and engineering teams who need clear requirements.
Problem
Enterprise partners and independent developers approach the same SDK with different mental models, different constraints and different definitions of 'done'.
Architecture
- Integration paths documented per partner profile rather than one generic quickstart.
- Reference implementations that mirror the real integration surface instead of toy examples.
- Feedback loop from partner onboarding back into SDK design and product decisions.
What I built
- Developer and enterprise-facing documentation, including docs.moca.network.
- Proofs of concept and example implementations to accelerate ecosystem adoption.
- AI-assisted initiatives to improve developer experience and enterprise workflows.
- Partner onboarding material and technical alignment between roadmap and sprint delivery.
Technology
Hard parts
- Translating enterprise requirements into engineering scope without diluting either.
- Keeping documentation truthful as the SDK surface evolves.
Outcome
Clearer integration paths for partners and a tighter loop between developer feedback and SDK design.
Next case study
EB1 →Contact
Tell me what you're building — and what's blocking it.
If the problem sits somewhere between financial infrastructure, product and engineering, there's a good chance I can help.
Book an intro call
30 min · video
Prefer to write first? armmamyan@gmail.com