About Vasion For more than a decade, Vasion has been helping companies simplify their print infrastructure, automate business processes, and integrate their technology in a more secure environment. Our mission, to make digital transformation attainable for everyone, drives a culture of innovation and exploration. We have one simple goal: help organizations simplify processes through automation and integration. So we created simple, cost-effective, and easy-to-implement digital tools that work together, removing bottlenecks and improving efficiency. And we're always on the lookout for new people who can help us innovate, grow, and reach our goal. About the role Vasion 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 Like Federal 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 Impact Setting 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... For full info follow application link.