> Markdown version of [/jobs/ext/2284864-technical-solutions-engineer](https://www.wearedevelopers.com/jobs/ext/2284864-technical-solutions-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Technical Solutions Engineer

- **Company:** Coinme Inc.
- **Location:** Chicago, IL, United States
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Software Debugging, Datadog, Postman, Web3.js, Api Design, Webhooks, Api Management
- **Published:** August 28, 2026
- **Apply:** https://www.chicagocareersite.com/job.asp?id=3368312877&tx=KR7171FFJ&pt=1&aff=0B19D771-A501-4A5E-8338-2A822B784D54&utm_source=Job%20Feed&utm_medium=textkernel&utm_campaign=DE&utm_term=0B19D771-A501-4A5E-8338-2A822B784D54

## About the Role

Nice to have: crypto or web3 background, especially stablecoins and wallets. Enough coding to build a demo app. Experience with a docs platform like Mintlify. Exposure to KYB and KYC tooling.

## Description

Coinme is part of Polygon Labs, and together we're putting out a stablecoin payments stack: our fiat on and off ramps, Sequence wallets, and settlement on Polygon. Fintechs and financial institutions are integrating it now, and the documentation hasn't caught up. Partners are asking questions that should have been answered in a doc six months ago, and those questions land on engineers who need to be building.

This role fixes that. You'll own our API docs and the integration path, help BD answer technical questions during deals, and take signed partners from kickoff through go-live. Most of the job is figuring out how the stack actually works, then writing it down well enough that the next person doesn't have to ask. If a developer with an AI coding assistant can't integrate us without a call, that's the problem you're solving.

What You'll Do

 * Own the API and integration docs. Rewrite what's wrong, fill what's missing, keep it current as the stack changes
 * Build the quickstarts, sample code, and reference architectures that get a developer from nothing to a working integration
 * Answer technical questions from partners during sales conversations and during builds, and resolve them yourself rather than passing them to engineering
 * Take signed partners live: requirements intake, provisioning once KYB and KYC clear, sandbox testing, webhooks, go-live checks
 * Work with the integration program manager on timelines so partners know what's coming and when
 * Learn the stack deeply: CaaS ramps, Sequence wallets, Trails, OMSX, bank rails, custodial and non-custodial flows, virtual accounts, deposit addresses, webhooks
 * Build demos and sample apps that BD can use to show what the products do
 * Push what you learn back into Product and Engineering. You'll see every rough edge in the API before anyone else does
 * Automate the repetitive parts of onboarding and provisioning, and use AI tools to move faster on docs and support

Who You Are

We're open to two different backgrounds here, and you only need one:

You've run API integrations for customers at a payments or fintech company, taking them from kickoff to production. Or you've owned docs, SDKs, or developer support at an API-first company and want to go deeper into payments.

Either way, you should have:

 * Real hands-on API skills. You can read logs, debug a broken webhook, reason about auth, and work in Postman or Bruno and Datadog. You don't need to be a software engineer, but you do need to solve problems instead of routing them
 * Strong technical writing. You can take a messy system and document it so a stranger can follow it
 * Patience for ambiguity. The stack changes weekly, the docs are thin, and nobody is going to hand you a plan
 * Comfort using AI tools in your daily work, and an eye for how to make our docs work well for developers who are using them too

Payments fundamentals (fund flows, settlement, reconciliation) will help, but we can teach that to the right person.


## Related Videos

- [Smart Contract fundamentals - My first DApp](https://www.wearedevelopers.com/videos/52-smart-contract-fundamentals-my-first-dapp)
- [Are Your APIs Ready for AI Agents](https://www.wearedevelopers.com/videos/2004-are-your-apis-ready-for-ai-agents)
- [Debugging in the Dark](https://www.wearedevelopers.com/videos/1658-debugging-in-the-dark)
- [​Road to Web3](https://www.wearedevelopers.com/videos/584-road-to-web3)
- [Software Engineering Social Connection: Yubo’s lean approach to scaling an 80M-user infrastructure](https://www.wearedevelopers.com/videos/1583-software-engineering-social-connection-yubo-s-lean-approach-to-scaling-an-80m-user-infrastructure)
- [Developer’s Perspective: Overview of the Tezos Blockchain Ecosystem](https://www.wearedevelopers.com/videos/237-developer-s-perspective-overview-of-the-tezos-blockchain-ecosystem)

## Related Articles

- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [Dev Digest 139 - Soft and hard queries](https://www.wearedevelopers.com/magazine/487-dev-digest-139-soft-and-hard-queries)
- [Dev Digest 138 - Are you secure about this?](https://www.wearedevelopers.com/magazine/486-dev-digest-138-are-you-secure-about-this)
- [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this)
- [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)
- [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss)