Baselayer
Forward Deployed Engineer
San Francisco, California$160k–$230kmidAdded today
About this role
Baselayer seeks a Forward Deployed Engineer to build and ship integration surfaces for an emerging agentic economy platform. You'll translate partner needs into working verification APIs, MCP servers, and demos within days, bridging technical partnerships and core platform engineering.
What you'll do
- Ship partner integrations from initial technical call through production deployment
- Build rapid prototypes, demos, and reference implementations for partner meetings and conferences
- Own API quality, documentation, sample code, and sandbox environments for developers and agents
- Get MCP server listed and featured in agent builder directories and marketplaces
- Participate in agent builder communities and represent Baselayer as a technical builder
- Translate partner constraints into specs for core platform team and feed field learnings into product roadmap
What they're looking for
- TypeScript and/or Python
- REST API design and integration (webhooks, OAuth, JWT)
- MCP (Model Context Protocol) server development
- LLM tool-calling and agent frameworks
- Rapid prototyping and demo development
- Customer/partner-facing technical communication
- Verifiable credentials and identity infrastructure (preferred)
- Payments domain experience (preferred)
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Baselayer
Baselayer builds identity verification solutions that help customers integrate and implement technical systems. The company is hiring Solutions Engineers to bridge engineering and customer success by facilitating technical integrations and translating complex concepts for diverse audiences.
View all jobs at BaselayerLikely interview questions
- Walk us through a time you shipped an integration from initial partner conversation to production—what was your timeline and how did you manage scope?
- How have you designed APIs that are both developer-friendly and agent-friendly, and what trade-offs did you make?