Solution Architect II

Hagerty
•Remote

About The Position

As a Solution Architect II on Hagerty’s Engineering Architecture team, you will create well-designed software solutions that account for long-term strategic direction while delivering business value through timely releases. The team places business capabilities into Hagerty’s Technology Portfolio of Software Assets, architects software services, designs APIs, and maintains clear bounded contexts. Solution architects communicate why solutions are needed, how they are implemented, and what they achieve, aligning audiences across the organization. The role owns bounded contexts across software product domains, including serving as a subject matter expert for one to three complex business domains, building shared understanding of those domains, decomposing business capabilities into bounded contexts, and maintaining context maps. It also designs inter-context APIs and messages, determines whether to extend, refactor, or build software, and creates design artifacts such as OpenAPI specifications. The architect communicates technical solutions to technical and nontechnical stakeholders, supports product decisions, evaluates and documents design tradeoffs, and works with Application Architecture and Engineering to assess and improve architectural maturity. The position is open to U.S. remote work. Team members living within 20 miles of the Traverse City headquarters work from the office three days per week. Quarterly-event travel may be required.

Requirements

  • Strong communication skills, including the ability to explain technical concepts to audiences with varying levels of technical skill and build shared understanding.
  • Ability to lead and contribute to product-design discussions aligned with business strategy.
  • Ability to create visual artifacts that represent contexts, designs, and shared understanding, and to write effectively about how software works.
  • Broad experience building software, including knowledge of programming languages, deployment, databases and persistence, and software patterns and anti-patterns.
  • Fundamental knowledge of API design, HTTP communication, REST and RPC styles, data movement such as polling, eventing, and messaging, and integration patterns and lifecycle.
  • Hands-on experience designing and implementing identity solutions, including identity-provider implementation and management; OAuth/OIDC authentication and authorization; SSO; customer identity features such as registration, MFA, and passwordless access; token design, lifecycle, signing, and revocation; session management; and API and service-to-service communication.
  • Growth mindset and commitment to continuous learning and sharing knowledge with teammates.
  • Experience in a visible senior role and willingness to collaborate with others.
  • Ability to work independently and positively impact multiple initiatives with competing priorities.
  • Interest in identifying the underlying problem to solve, as well as delivering a solution.
  • Familiarity with public-company requirements, including Sarbanes-Oxley and applicable regulations, where relevant to the role.

Nice To Haves

  • Experience deploying and/or integrating software with the Duck Creek Insurance Platform.
  • Having read Domain Driven Design by Eric Evans.
  • Familiarity with modeling tools such as C4.
  • Tendency to take the lead when no leader is present.
  • Comfort speaking to audiences of all sizes.
  • Experience writing .NET code.
  • Experience designing and releasing APIs using both REST and RPC styles.
  • Interest or experience in creating API documentation with tools such as OpenAPI.

Responsibilities

  • Own and maintain bounded contexts between software product domains in Hagerty’s Technology Portfolio.
  • Act as a subject matter expert on one to three complex business domains and build shared understanding of their encapsulation and purposes.
  • Decompose new business concepts and capabilities into bounded contexts and create and maintain context maps describing interactions with other portfolio contexts.
  • Design and own inter-context communication specifications, including HTTP APIs and messages, that serve current and future business needs.
  • Decide whether to extend, refactor, or build software to address business capabilities and product features.
  • Establish durable domain concepts in API resources and create design artifacts, including OpenAPI documentation, that are straightforward to implement and test.
  • Explain technical concepts and solutions to nontechnical stakeholders and publish solution artifacts.
  • Champion product-domain capabilities to stakeholders and other product teams, and inform product decisions with technical knowledge and software experience.
  • Evaluate solution-design tradeoffs such as speed, technical debt, vendor cost, and complexity, and document decision rationale.
  • Recommend implementation approaches informed by product roadmaps and business strategy.
  • Measure architectural maturity in supported product contexts and propose improvements in collaboration with Application Architecture and Engineering.
  • Publish and adopt reusable integration patterns between contexts.
  • May travel for quarterly events.
  • For applicable SOX-compliant roles, design, execute, and document assigned internal controls and attest to the completeness, accuracy, and compliance of financial reporting data.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service