Solutions Architect II

Overview

As a Solution Architect II on our DIT (Digital Innovation Technology) Architecture team you will create software solutions that are well designed and take a long-term strategic view. By considering the impact of design choices today against an understanding of a software product’s strategic direction, our solution architects seek to limit future constraints and provide the correct amount of flexibility while delivering business value with timely releases.

The team achieves this by placing business capabilities into Hagerty’s Technology Portfolio of Software Assets, by architecting software services, designing APIs, and maintaining clear bounded contexts between each. As excellent communicators and leaders within the organization, they ensure all audiences are aligned on why our software solutions are required, how they are implemented, and what they achieve.

Ready to get in the driver’s seat? Join us!

Own and maintain bounded contexts between software product domains in our Technology Portfolio by -

• Acting as a subject matter expert on 1-3 complex domains within our business
• Building shared understanding around the encapsulation and distinct purposes of your domains
• Decomposing new business concepts and capabilities into bounded contexts
• Creating and maintaining context maps that detail your context’s interactions with others in the Portfolio

Design and own inter-context communication specifications that serve the needs of the business now and in the future by -

• Designing HTTP APIs and messages that provide solutions to business capabilities and product features
• Deciding whether to extend, refactor, or build new software
• Establishing strong domain concepts in your API resources that can evolve naturally, over narrow bespoke solutions
• Writing excellent design artifacts (OpenAPI, etc.) that make solutions simple to implement and easy to test

Elevate the communication of the enterprise around technology and how it serves our strategy by -

• Explaining technical concepts and solutions to nontechnical stakeholders both ad-hoc and by publishing solution artifacts
• Championing the capabilities of your product domain(s) to stakeholders and other product teams
• Informing product decision making via your technical knowledge and experience creating software

Mature Architectural thinking at Hagerty by -

• Evaluating tradeoffs in solution design (e.g. speed, technical debt, vendor cost, complexity) and documenting how you reached your decisions
• Being opinionated on implementation based on your knowledge of your product’s roadmaps and the business’ strategy
• Measuring architectural maturity in the product contexts you support, and proposing ways to improve that maturity by working with Application Architecture and Engineering
• Publishing and adopting common integration patterns between contexts that can be easily re-used by other architects and teams

You’re a talented communicator

• You meet people where they are and then build shared understanding
• Comfortable and effective explaining technical concepts to audiences of varying level and technical skill
• Lead and contribute to discussions around product design per business strategy
• Bias towards creating visual artifacts that represent contexts, designs, and shared understanding
• You enjoy learning and then sharing what you’ve learned with others
• You write effectively about how software works

You have a breadth of experience building software

• Programming languages
• Deployment
• Databases/Persistence
• Patterns and anti-patterns

You have a Fundamental knowledge of technology concepts

• API Design
• HTTP Communication
• REST /RPC Styles
• Data movement-- polling, eventing, messaging
• Integration patterns and lifecycle
• Identity— Authentication and Authorization

You have experience being in a visible senior role and want to collaborate with others

You enjoy operating independently, and can concurrently positively impact multiple initiatives with competing priority

You love discovering the actual problem that needs to be solved as much as solving it

• You’ve deployed and/or integrated software with the Duck Creek Insurance Platform
• You’ve read Domain Driven Design by Eric Evans
• You…