About the roleVasion is looking for a Staff Technical Account Manager to set how technical account management is practiced across our Federal customers. You will be the senior technical authority after the sale for civilian, defense, and other regulated government accounts, where the architecture, the compliance boundary, and the mission stakes all raise the bar. We modernize how organizations handle documents, print, and content workflows, replacing fragmented legacy tools with a single, secure platform. In Federal, that means doing it inside authorization boundaries, restricted networks, and change windows that leave little room for surprises.
This is a practice-level role. You will not only run a book of strategic accounts. You will define the standards, planning method, and reusable assets the rest of the team uses to do strong work on Federal accounts.
At a Glance- Segment: Federal government: civilian agencies, Department of Defense and its components, and Federal system integrators and partners
- Vertical focus: Federal and regulated public sector
- Engagement model: Post-sales technical leadership across adoption, retention, and expansion, with practice-level ownership
- Work model: Remote; ability to travel up to 25%
- Security: Active or previously held U.S. security clearance required (see Requirements)
- Success metrics: Gross retention across the Federal book, trend in repeat escalations, risk identified before the customer raises it, adoption milestones met, expansion ARR influenced
What Success Looks LikeFederal customers experience one consistent standard of technical care, no matter which TAM or partner is serving them. Risk is classified the same way across the book and triggers the same response. Escalations lead to systemic fixes, not repeated recovery. Product and Engineering hear about authorization-boundary, release-timing, and architecture risk early and with evidence. Renewals and expansions in this segment are won because the technical trust was already built.
Where You'll Have ImpactSetting the standard for Federal technical account management and leading on the most consequential accounts.- Federal advisory standard: Define what counts as a risk signal in Federal environments, how risk is classified, and the advisory response each class triggers, so assessments are consistent across the team. Anticipate how product roadmap, release, and compliance changes will land across the Federal book, and advise ahead of the change rather than after it.
- Technical planning method: Own the planning method for the Federal practice, including what a target state must specify, how horizons are set, and how the forward technical calendar tracks authorization milestones, impact level transitions, audits, change freezes, and end-of-life dates. Aggregate plans into a view of where the Federal installed base is heading, and bring it to Product and Engineering as an input to roadmap and lifecycle decisions.
- Technical leadership across products and teams: Act as the technical lead where remediation spans several products or teams. Define how escalation response is structured, staffed, and evidenced so it does not depend on individual heroics. Turn recurring issues into systemic correction, with the evidence Product and Engineering need to make a decision.
- Service delivery standard: Define how Federal engagements are structured, delivered, and evidenced against entitlement. Orchestrate Professional Services, Support, and partners so delivery quality is consistent regardless of who executes it. Aggregate delivery and adoption data to spot retention and adoption risk before it shows up account by account.
- Compliance-aware adoption: Help Federal customers get the full value of what they own while staying inside their authorization boundary, including serverless and secure print management, smart card and badge-based authentication, restricted and segmented network deployments, and document workflow and capture use cases.
- Executive and partner engagement: Engage customer technical executives on the highest-consequence accounts, and represent Vasion's technical position with Federal partners, integrators, and sponsoring agencies.
- Reusable assets and enablement: Build the reference architectures, diagnostic assets, playbooks, and enablement that let the team replicate strong Federal work. Calibrate the judgment of other TAMs so plans, assessments, and confidence levels are comparable across accounts.
- Own a book of strategic Federal accounts: Hold the technical relationship on the most complex Federal accounts, including multi-department and multi-sponsor structures where one TAM protects retention across the whole.
What You BringDeep technical authority, Federal compliance fluency, and the judgment to set a standard others can follow:- Post-sales technical leadership: Proven ability to lead a practice or a program, not just a book, including standards, playbooks, review, and teaching.
- Architecture and systems thinking: Authoritative expertise in cloud and hybrid architecture, and in restricted, segmented, and air-gapped environments and large device fleets.
- Networking and identity: Strong grasp of DNS, proxies, firewalls, LDAP and SSO, and Federal authentication patterns including CAC/PIV smart card.
- Security and compliance: Working knowledge of FedRAMP, DoD Cloud Computing SRG Impact Levels (IL4/IL5/IL6), NIST 800-53 and 800-171, FIPS-validated cryptography, STIG hardening, vulnerability and continuous monitoring, and the ATO process as customers experience it.
- Domain expertise: Print, Workflow, and Output Automation in cloud and hybrid environments.
- Technical toolbox: Diagramming; bash and/or PowerShell; SQL; RESTful APIs; Jira; AI-assisted workflows.
- Executive communication: Clear, calm technical communication with customer technical executives, program managers, and security officers, especially when the answer is unwelcome.
QualificationsSenior-level post-sales experience and the clearance to work Federal accounts:- Active or previously held U.S. government security clearance [confirm minimum level, e.g., Secret or higher; confirm with HR and Legal how "previously held" is treated, and whether U.S. citizenship is required]
- 8-10+ years in technical account management, post-sales engineering, or senior technical support for SaaS or enterprise software, including significant time supporting Federal or other regulated customers [confirm]
- Track record leading the technical response on high-consequence escalations spanning several products or teams
- Demonstrated experience mentoring other technical staff and setting standards or reusable assets that others adopted
- Strong writing and presentation skills, including to executive audiences
- Bachelor's degree in Computer Science, Information Systems, Engineering, or a related technical field, or equivalent experience
- English language proficiency; additional language skills valued
What Sets You ApartFederal instincts that identify risk and opportunity before anyone asks:- Hands-on experience supporting a DoD or civilian agency, a Federal system integrator, or a FedRAMP-authorized SaaS provider
- Experience supporting a customer through an ATO, an impact level transition, or a FedRAMP annual assessment
- Experience with Federal vulnerability management, including POA&M and continuous monitoring processes
- Track record of turning field findings into product or engineering change
- Experience representing a vendor at Federal industry events or partner engagements
Benefits- Flexible work environment
- Discretionary Vacation Bonus
- Flexible paid time off
- Paid parental leave
- Competitive pay
- A full suite of traditional benefits
- Training/Advancement opportunities
- 401k with company match and immediate vesting
- Mental health & coaching support
- Financial wellness education
- Company-contributed HSA
- On-site perks include gym, pickleball, snacks & drinks, arcade, theater room, etc.
Visit https://www.vasion.com to learn more about Vasion.
