Technical Account Manager / Partner Technical Relationships

The Role

You are the technical face of Silvur to our credit union partners. Today we work with numerous credit unions. Each one has an IT team, a security officer, and a digital banking platform, and each one has questions before they'll put Silvur in front of their members: How does our member data move? Where does it live? Who can see it? How does single sign-on work on our platform?

You own those answers. And you know how to deliver them clearly and with enthusiasm. When a partner call has a technical item on the agenda, you're on it. When a security questionnaire arrives, you complete it. When a new partner needs to be stood up, you take them from signed to live.

You will not be building or modifying our product. Our engineering team does that. What you will do is know our platform thoroughly enough to represent it accurately—its architecture, its data flows, its security posture, and its limits—and handle the configuration work that brings each partner online. When something requires a product change, you scope the need clearly and hand it to engineering.

The hardest part of this job isn't any single technical skill. It's holding a credible technical conversation with a credit union's security officer who has veto power over the partnership, without overpromising and without getting defensive.

What You'll Own

• Partner technical relationships. Be the named technical contact across our partner portfolio. Attend partner meetings with technical agenda items. Translate between credit union IT staff and our engineering team in both directions.
• Success and Sales support. Work side-by-side with our Success and Sales teams whenever a conversation has a technical dimension—preparing them beforehand so they know what we can and can't do, and joining the call to handle the technical discussion directly when that's the better answer.
• Partner configuration and credentials. Provision and maintain partner accounts and access: SFTP users and directory setup, single sign-on configuration, API credentials, sending domain records. This is hands-on setup work in existing systems and consoles.
• Data exchange operations. Own the member file relationship with each partner: file specifications, test exchanges, field mapping requirements, and the conversations that happen when a file arrives malformed or late. You'll diagnose what went wrong using our monitoring and logs, and escalate to engineering when the cause is in our code.
• Digital banking integrations. Configure and troubleshoot single sign-on across partner platforms—Alkami, Banno, Candescent, and others. Work through the setup with partner platform teams and their vendors.
• Email authentication. Own SPF, DKIM, and DMARC configuration for partner sending domains, including the DNS delegation conversations with partner security teams. This is a recurring source of partner friction and a meaningful driver of how well our member outreach performs.
• Security and compliance responses. Complete partner security questionnaires and vendor assessments. Explain our SOC 2 controls, data handling practices, encryption posture, and access model accurately. Work with Legal & Compliance on anything that constitutes a formal representation.
• New partner onboarding. Take new partners from contract to live members across the full sequence: security review, data exchange setup, SSO configuration, sending domain authentication, launch verification.
• Reusable artifacts. This matters as much as the reactive work. Specifically:
• A security questionnaire response library, so the fortieth review is a review of a diff rather than a two-week exercise from scratch
• A partner integration guide covering data flows, file specs, SSO patterns by platform, and email authentication requirements
• A standing architecture and data-handling deck that answers the predictable questions before a meeting starts

We will hold time for this work and treat these as dated deliverables, not someday items.

How We Work

We're a Google shop running a deliberately light, AI-first stack: Claude, HubSpot, Umami, Asana, and Linear. Claude is in the workflow all day—not as a novelty, but as the thing that lets a small team carry a portfolio this size. You don't need prior experience with every tool here. You do need to be the kind of person who automates a task the second time you're asked to do it.

Where the Line Sits

To be explicit, since this is the part most candidates ask about:

You do: configure, provision, diagnose, document, explain, and escalate. Set up partner credentials and SSO. Investigate a failed file transfer and determine whether the problem is on their side or ours.

Engineering does: build and change the product and systems that support your work. Modify how data is processed. Ship features. Fix bugs in our code.

What This Role Is Not

• Not a sales role. No quota, no commission. Your incentive is to give partners accurate answers, including inconvenient ones.
• Not a support queue. You'll handle inbound questions, but you're expected to reduce their volume over time through documentation and better partner-facing materials.
• Not a software engineering role. If what you want is to be writing code, you'll be frustrated here and we'd rather tell you now.

Interview Process

1. Intro call (30 min) — role fit and background
2. Technical conversation (60 min) — your experience with integrations, authentication, email deliverability, and partner-facing technical work
3. Live exercise (60 min) — a simulated partner conversation. You'll work through a realistic technical objection from a credit union security team, then draft the follow-up. No take-home, no coding.
4. Team conversations (2 x 45 min) — partnerships and compliance
5. Final conversation with the Head of Product and Engineering