The title “Solution Architect” is commonly used across various sectors within the tech industry. However, the role and responsibilities of a Solution Architect can differ greatly depending on factors such as the company, project scope, and scale. So, how can technical professionals navigate this diverse landscape throughout their careers? Additionally, when hiring, businesses must ensure they select the right candidate who is the best fit for their unique needs and goals.
Types of Solution Architect: Pre-sales to Customers
It is important in any architecture-focused role to develop core methodologies and consultancy skills that work across multiple technologies and projects. Possessing an understanding of the business sector, its common challenges, and how technology integrates together is extremely valuable. This is often neglected but can be more impactful on a project than detailed knowledge of a single technology.
While working in IT, you may encounter different types of solution architects. Each professional’s perspective varies depending on their commercial priorities. Understanding these differences is crucial to navigating the technology sector and managing projects while staying true to your career path.
A job title does not necessarily reflect a person’s skills or function within a business.
Understanding Solution Architect Roles
A typical business that consumes technology may have different expectations of a solution architect than a technology provider. For example:
- A lead architect in a corporate business may have experience in a small number of end-to-end projects across multiple vendors within a specific business sector.
- An architect at a managed service provider (MSP) may focus on aligning customer needs with pre-defined service offerings.
- A vendor-employed architect typically specializes in their employer’s technology, understanding how it can solve challenges for multiple customers, often with a focus on pre-sales.
Recognizing these differing perspectives can help you navigate projects, learn from others, and shape your career path effectively.
Architect Roles and Their Focus
Customer Architect
Employed by a business that consumes technology
- Focus on business/client-specific, often custom solutions.
- Works across the full project lifecycle, bridging gaps between services to “make it work.”
- Requires deep knowledge of business processes and the ability to integrate multiple vendors.
- May face challenges like cost constraints, tender processes, and competing priorities.
- Limited exposure to the full technology market due to business-specific needs.
Managed Service Provider or System Integrator Architect
Employed by a company that hosts technology for others
- Focused on mapping customer needs to service offerings.
- Requires strong relationship management and high-level understanding of customer projects.
- Offers technical complexity at scale, often working in multi-tenant environments.
- Restricted by partner service models, specific technology stacks, and deal sizes.
Vendor Architect
Employed by a large technology supplier or creator
- Deep dives into specific technologies, often with access to cutting-edge tools.
- Engages in pre-sales, workshops, and sales strategies to showcase value to customers.
- Helps customers form long-term plans for consuming vendor services.
- Often measured on sales metrics like initiated projects or demos.
- Limited to their vendor’s offerings, which can lead to skill gaps in broader technologies.
- Typically does not implement projects but focuses on pre-sales and planning.
Collaboration Between Roles
Understanding the focus of different solution architects can create opportunities for collaboration and learning.
For example, a vendor solution architect might build rapport with a customer solution architect, gathering requirements and evangelizing their technology. The customer architect can use this input to shape their plan, while maintaining their employer’s requirements and ensuring the vendor architect does not overcommit or take on design responsibility.
Similarly, an MSP-focused architect needs to articulate the value of their services while navigating pre-existing design limitations from vendors or customer constraints.
Navigating Challenges
Solution architects frequently work with platforms where some design decisions are predefined by the vendor (e.g., SaaS, IaaS). While this approach meets the needs of most customers, it may require trade-offs. Architects must assess risks and articulate benefits to mitigate potential issues.
In rare cases, cloud providers may offer new features for specific deals, but this can add complexity. It’s crucial to evaluate whether such an approach aligns with project goals and long-term support considerations.
Planning Your Career Path
The competing focuses and constraints of different solution architect roles can guide your career decisions.
- For example, vendor-focused architects often come from partner backgrounds due to their experience in pre-sales, assessments, and larger projects.
- A customer-focused architect may have detailed knowledge of specific sectors, making them valuable for vendor recruitment.
- However, a vendor-focused architect may risk becoming deskilled in broader technologies, while a customer architect may need to enhance their pre-sales skills to pivot to partner or vendor roles.
Developing Skills along the Journey
- Experience and learning: Build relationships and gather insights from architects in different roles to expand your perspective.
- Balance your focus: Each role has pros and cons. Decide what aligns with your long-term goals and interests.
- Stay adaptable: Keep learning and addressing skill gaps to remain competitive.
Collaboration and understanding among solution architects lead to stronger projects and lasting professional relationships. Use each experience as a stepping stone for your career journey.