Solution Engineer — North America

This is a hands-on engineering role at the customer edge.
Not a ticket queue.
Not an account manager reading from a script.
Not a note-taker on customer calls.
You unblock customers by writing code that helps them integrate, run customized demos, and get thier solution to production.
Credence ID builds digital identity products that run in the real world — mobile ID (mDL) verification, biometric hardware, and the SDKs behind them. Our customers are government agencies, enterprises, stadiums, and airports. When one of them starts an evaluation, somebody technical has to take them from “this looks interesting” to a working integration in production. That somebody is you.
You'll be the first engineer most customers meet. During evals and pilots you'll build the proof-of-concept, wire up the API and SDK integrations, run the demos, and chase down whatever breaks. Once they buy, you stay on through deployment.
What You'll Actually Do
• Own the technical side of customer evaluations — demos, onboarding, pilots, and the path to production
• Build POCs, sample apps, and integration scripts against our APIs, SDKs, and hardware (Android is a big part of our world)
• Turn vague customer requirements into working prototypes, fast
• Reproduce and troubleshoot customer-reported issues, then drive them to resolution with Engineering and QA
• Run technical training and demos for customer teams
• Team up with Sales and pre-sales on solution proposals, technical inquiries, and RFP/RFI responses — you write the parts that have to be technically right
• Feed what you learn in the field back to Product and Sales — you'll see problems before anyone else does
• Use AI coding tools daily to prototype, test, debug, and document faster
What We Care About (Read This Carefully)
You can build. Degree in CS, EE, CE, or similar, and 0–3 years of experience — a strong fresh grad with real projects beats five years of watching other people code. Show us something you built: a repo, an app, a hardware hack, a class project you took further than the assignment required.
You can talk to people. You'll be in front of customers from week one — explaining, demoing, and sometimes saying “I don't know yet, let me find out.” Clear writing and clear speaking are not optional here.
You debug like it's a sport. A customer says “it doesn't work.” You figure out what “it” is, reproduce the failure, isolate the cause, and don't let go until it's fixed.
You're AI-native. You use Claude, Copilot, or similar tools every day and can show us how they make you faster — not “I tried ChatGPT once.”
You take ownership. Small company. Nobody hands you a runbook. If a customer is stuck, it's your problem until it isn't.
Nice to Have
Exposure to digital identity, mDL, mobile wallets, NFC, BLE, QR/PDF417, biometrics, or PKI. None of it is required — we'll teach the domain. We can't teach curiosity.
What This Role Is (and Isn't)
It is a 3-month contract first. That's deliberate — you see how we work, we see how you work, and if it fits, you convert to full-time. Most people in your shoes should treat it as a 90-day interview where you get paid and ship real things.
It is a launchpad. Do this well and the paths open up: solutions architecture, product, or core engineering.
It isn't a pure coding job. Half your week is customer-facing. If you want to sit behind a compiler with headphones on, this isn't your seat.
It isn't scripted. Every customer integration is different — different stack, different constraints, different surprises.
Culture Notes
We're a small, fast-moving team. People get responsibility early and are expected to run with it. We value people who understand the customer, get hands-on with the technology, build quickly, and test their own work before someone else has to.
How to Apply
Send a short note about the most interesting thing you've built and why, plus a link to it if one exists. No AI-written replies — we'll know, and it defeats the purpose of hiring someone who can communicate.

Work arrangement
Yes