> Markdown version of [/jobs/ext/3559167-solutions-architect-regulated-markets](https://www.wearedevelopers.com/jobs/ext/3559167-solutions-architect-regulated-markets). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Solutions Architect, Regulated Markets - **Company:** Vasion, Inc. - **Location:** St. George, UT, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Amazon Web Services, Microsoft Azure, Bash Shell, Command-Line Interface, Cloud Computing, Domain Name System (DNS), Hyper-V, Python (Programming Language), Linux System Administration, Networking Basics, Windows PowerShell, Security Assertion Markup Language (SAML), Virtual Local Area Networks, Virtualization Technology, Google Cloud, Agentic-AI, Infrastructure Automation Frameworks, Integration Frameworks, Vmware - **Published:** October 2, 2026 - **Apply:** https://diversityjobs.com/main/sendform/8/8/28176/1/18499686?backUrl=%2Fcareer%2F18499686%2FSolutions-Architect-Regulated-Markets-Utah-St-George ## About the Role * Deep enterprise deployment experience: Eight or more years deploying infrastructure software into complex enterprise or public sector environments, with clear ownership of outcomes rather than handoffs. * Identity and authentication depth: Strong working command of SAML, SSO, directory integration, certificate-based authentication, and common identity providers. * Networking fundamentals under pressure: DNS, TLS and certificate chains, firewalls, proxies, VLANs, and the ability to isolate a problem in a network you did not design and cannot fully see. * Hyperscale, virtualization, and appliance platforms: Practical command of cloud infrastructure (AWS, Azure, GCP, or comparable hyperscalers), virtualization platforms (VMware, Hyper-V, or comparable), and virtual appliance deployment, sizing, and troubleshooting. * Linux administration and scripting: Comfortable at the command line, reading logs, and automating with PowerShell, Python, or Bash. * Demonstrated learning velocity: Evidence of acquiring new technical domains to real depth, since this portfolio will expand under you. * Customer-facing composure: Proven ability to hold a technical conversation with a frustrated customer under real pressure, and to keep it factual and forward-moving. * Judgment about what generalizes: A track record of turning one-off solutions into reusable assets rather than solving the same problem repeatedly., * Public sector deployment experience: Direct work with PIV and CAC authentication, FedRAMP authorized environments, DoD networks, or government cloud regions. * Print infrastructure or output management background: Experience with enterprise print management, print protocols, or document output platforms. * Workflow automation platforms: Exposure to document workflow, process automation, or integration platforms. * Other regulated industry experience: Healthcare, financial services, or comparable environments with badge-based authentication, strict change control, or audit-driven constraints. * Cloud and endpoint breadth: Azure, AWS, or GCP, plus VDI platforms and endpoint management tooling. * Agentic AI acumen ## Description Vasion is hiring a Solutions Architect for our regulated and federal business, where the hardest technical problems in our portfolio live. You will be the person who owns the defensible technical answer when a federal customer asks whether something can work inside their authentication, network isolation, and accreditation constraints, and who defines the path forward when the standard answer does not apply. This is a depth role rather than a breadth role. Architectural fluency without current, detailed product knowledge does not survive contact with a regulated deployment, so we are looking for someone who goes deep on the product and stays there as the portfolio evolves. What you'll do * Build depth on new capabilities ahead of demand: Reach working depth on newly released capability before customers force the question, surfacing integration gaps and unsupported edge cases while they can still be addressed. * Be the technical authority on federal and regulated requirements: Own the answer on whether our architecture meets a customer's authentication, authorization, and accreditation requirements, and clearly state where current product capability ends. * Codify the patterns that keep recurring: Turn the most complex recurring problems into reusable reference designs, so future engagements inherit proven solutions rather than rediscovering them. * Assess technical risk and manage it: Evaluate risk posture, architecture constraints, and deployment feasibility on the highest-complexity opportunities, then define the mitigations, sequencing, or architectural changes that make the solution deployable. * Design beyond the standard template: Define architecture, integration points, and cutover approach for environments that exceed what standard delivery patterns cover. * Protect context across the handoff: Supply the technical assumptions, constraints, integration points, and success criteria into joint technical kickoffs, so nothing essential is lost between the deal team and delivery. * Execute the hardest cutovers: Take the customer environment through cutover where complexity exceeds what standard delivery supports, rather than handing a design over and stepping away. * Diagnose root cause on escalations: Supply the definitive technical diagnosis when a deployment stalls or a production issue surfaces, separating root cause from reported symptom. * Convert friction into fixes: Classify what you encounter by root cause, then drive recurring patterns into product input, service offerings, or enablement with named owners, so the same problem does not return to you a third time.