Alpaca Senior Software Engineer to build and evolve Alpaca’s agent-facing developer platform including MCP servers, tools, skills, and APIs. Lead architecture, code, design reviews, and mentorship while shipping initial versions.
Responsibilities
We’re looking for a Senior Software Engineer to build the developer platform that agents and partners use to integrate and build on. You evolve Alpaca’s MCP servers, tools, and skills, and you build the APIs behind them.
You play a central role to define the architecture that provides the fastest time to market for integrators. Builders who embed Alpaca for their end users all use this surface.
This is a hands-on role. You will lead through architecture, code, design reviews, and mentorship, and you will ship the first version yourself. You will partner with Product, Compliance, Risk, and Platform Engineering teams.
Things You Get To Do:
Design and build Alpaca’s agent-facing developer platform: MCP servers, tools, skills, and the APIs behind them.
Evolve that platform as the MCP protocol and connector, plugin, and skill standards change.
Build new APIs that make trading and account capabilities available to apps and agents.
Decide which components the platform renders, so developers and partners build apps faster from shared building blocks.
Keep Alpaca’s execution model current with the MCP protocol and with connector, plugin, and skill standards, and translate what changes into the application architecture of the developer platform.
Own production reliability and quality for the services you build.
Mentor engineers and raise the quality of design and implementation in this area.
Qualification
Shipped a developer-facing APIStrong API designProficiency in Python or TypeScriptStrong architectural judgmentClear communication with engineersWho You Might Be (Nice-to-Haves)Production experience with Go
Required
5+ years of software engineering experience, with ownership of production systems that other developers use.
Shipped a developer-facing API, SDK, or platform as a primary contributor.
Enough MCP architecture to work with stateless and stateful behavior, and experience building to MCP, or to connector, plugin, or skill standards, as they have changed in production.
Strong API design, including schemas, compatibility, and responses other developers can rely on.
Proficiency in Python or TypeScript, and a willingness to work primarily in Go.
Strong architectural judgment, with a record of shipping while requirements are still being defined.
Clear communication with engineers, product, compliance, and risk partners.
Who You Might Be (Nice-to-Haves):
Experience shipping developer-facing tools, SDKs, or MCP servers.
Experience building agents with a framework such as LangChain.
