Junction Technical Implementation Analyst responsible for owning lab certifications end-to-end and building automation to streamline manual processes. Acts as the primary contact for lab partners and manages multiple certifications simultaneously.
Responsibilities
Own lab certifications end-to-end: pick up new requests from Quest and LabCorp, build the test plan, run the cases, and get each account over the line.
Keep ~30 moving at once: know where every certification stands and chase whatever is stuck without being asked.
Be the go-to person for our lab partners: reliable, organized back-and-forth with Quest, LabCorp, and our other partners on test cases and issues.
Push the automation further: a lot of certification work today is still manual, and we expect most of the happy path to be automated within the next year. You’ll be the one building that — with scripts, agents, whatever cuts the manual work — not just running the process by hand.
Get hands-on with the data: dig into our backend, databases, and API responses when a result doesn’t land the way it should — in practice this means running scripts yourself (sandbox overrides, Quest order pulls, HL7 changes), not flagging it for someone else to fix.
Run the other partner processes: set up lab accounts and sub-accounts, track pricing requests, and make sure our team always knows where things stand.
Keep customers informed: maintain the docs that explain certification and account setup to customers and our sales team.
Find the next process to fix: spot other lab workflows that are manual and repetitive, and make the case for automating them.
What success looks like
Every certification and partner process has a clear owner, status, and next step. Nobody has to ask where things stand.
Accounts go live faster, with less back-and-forth with our partners.
At least one more lab partner process has moved out of a spreadsheet or inbox and into something that mostly runs itself.
Qualification
Ecosystem thinkingTechnically mindedHands-on scriptingAI-nativeProject managementHigh ownershipDependable with partnersWhat this role isn'tYou want a pure engineering roleYou want a fully defined playbook
Required
Implementation or integrations experience: 2+ years running implementations, integrations, or technical support for an API-based or similarly technical product.
Ecosystem thinking: you've worked somewhere with an active network of partners and integrations, not just a customer and a vendor. You understand that improving a process with a lab partner affects our customer and our customer's customer.
Technically minded: you can make code changes and ship fixes yourself — in a script, a database query, or an API integration — without needing an engineer to review your work line by line. You don’t need to be an engineer, but you need real coding ability, not just comfort reading code.
Hands-on scripting: you’re comfortable writing SQL and scripting in Python or JavaScript — this is how you’ll actually get the job done.
AI-native: you already use AI tools every day and have built them into your workflows. When something is repetitive, AI is the first thing you reach for.
Project management: you can keep dozens of things moving at once without anything slipping.
High ownership: you see a problem and want to solve it next. The best person for this role looks at the manual work and decides it shouldn't need a human.
Dependable with partners: you're clear, organized, and responsive with outside contacts, and you'll represent Junction with our lab partners.
Preferred
You don't need to tick every box to fit in here. If the problems we're solving genuinely interest you and you know you can contribute, we'd love to talk.
What this role isn't
You're looking for a customer success role: you'll talk to customers when it helps get them live, but most of your time is with lab partners and our internal teams.
You want a pure engineering role: you'll work with code and data, but the job is owning a process and automating it, not shipping product. With that said, this isn’t a role where you can avoid code — you’ll be writing and shipping changes yourself, just not building product features.
You're happy doing the same task the same way forever: certification is repetitive by nature, and your job is to make it less so.
You want a fully defined playbook: our tooling is a strong start, but how far we take it is up to you.
