AI Agentic Trading Expert

CoinMarketCap; Singapore; In loco; SGD 100.000 - 180.000; Tempo pieno

Descrizione del lavoro

CoinMarketCap is seeking an experienced platform engineer to design and ship official skills across a 14-domain taxonomy and define SDK ergonomics and revenue-sharing contracts for third-party developers. You will own the MCP server and CLI, making skill authoring as seamless as writing a Vercel function.

You will partner with teams to land CMC skills inside live agent products, implement cross-agent protocol adapters, and feed integration learnings back into the SDK.

Competenze

• Crypto-native fluency: can explain DEX AMMs, perp funding, bridge risk, on-chain identity.
• Experience contributing to SDK/CLI/API adopted by developers; strong opinions on docs.

Mansioni

• Design and ship official skills across a 14-domain taxonomy (Leverage, Assets, Portfolio, Pulse, Plays, Risk, etc.).
• Define publishing standards, SDK ergonomics, and the skill-signing/revenue-share contracts for third-party developers.
• Own the MCP server and CLI to simplify skill authoring like writing a Vercel function.
• Partner with teams to land CMC skills inside live agent products; drive cross-agent protocol adapters.
• Co-design and run CMC for Agent hackathons; write technical content and represent at Web3 × AI events.
• Improve LLM grounding for crypto context; build evaluation harnesses for skill accuracy and honesty.

Conoscenze

SDK design

CLI tooling

Agent integrations

LLM grounding

Web3 / AI events

Developer relations

Documentation writing

Solidity basics

Strumenti

MCP server

CLI

LangGraph

OpenClaw

Descrizione del lavoro

Key Responsibilities

• Design and ship the official skills spanning our 14-domain taxonomy (Leverage, Assets, Portfolio, Pulse, Plays, Risk, etc.) — covering market analysis, on-chain liquidity, identity resolution, derivatives, and DeFi primitives.
• Define publishing standards, SDK ergonomics, and the skill-signing / revenue-share contract that third-party developers will build against.
• Own the MCP server and CLI that make skill authoring feel as easy as writing a Vercel function.

Build The Capabilities Market (Supply Side)

• Design and ship the official skills spanning our 14-domain taxonomy (Leverage, Assets, Portfolio, Pulse, Plays, Risk, etc.) — covering market analysis, on-chain liquidity, identity resolution, derivatives, and DeFi primitives.
• Define publishing standards, SDK ergonomics, and the skill-signing / revenue-share contract that third-party developers will build against.
• Own the MCP server and CLI that make skill authoring feel as easy as writing a Vercel function.

Drive Agent‑Side Integrations (Demand Side)

• Partner with teams to land CMC for Agent skills inside live agent products.
• Implement A2A / cross-agent protocol adapters so a skill published once is discoverable and callable everywhere agents live.
• Feed integration learnings back into the SDK — every painful integration becomes a docs page or a helper API.

Grow the Developer Community (Ecosystem & Hackathons)

• Co‑design and run CMC for Agent hackathons — tracks, bounties, reference repos, judging rubrics, and the technical support Discord during event weekends. Deep collaboration expected with BNB Hack Local Series, YZi Labs EASY Residency, and Virtuals/ACP ecosystem events.
• Write the technical content that makes developers choose us: launch posts, cookbook recipes, video walkthroughs, and "build-with-us" threads.
• Be the technical face at Web3 × AI events.

Engineering & Grounding

• Improve LLM grounding on crypto‑specific context (tokens, contracts, narratives) to cut hallucination and latency on trading‑adjacent queries.
• Build evaluation harnesses that measure skill accuracy, reliability, and economic honesty — not just latency and uptime.

Requirements

• Crypto‑native fluency: you can explain DEX AMMs, perp funding, bridge risk, and on‑chain identity without reaching for Google. Comfortable reading Solidity even if you don't write it daily.
• AI agent systems, hands‑on: function calling, tool use, MCP, and at least one of LangGraph / OpenClaw in production — not just tutorials.
• Developer‑product instincts: you've built or heavily contributed to an SDK, CLI, or API that outside developers actually adopted — and you have opinions about why most developer docs are bad.