Senior Solutions Architect

Role Purpose & Context

Role Summary

The Senior Solutions Architect is here to win the technical evaluation for our biggest clients. You'll dive deep into their existing systems, figure out what's really bothering them, and then show them exactly how our product fixes it – often designing a bespoke solution on the fly. This directly impacts our ability to close multi-million-pound deals, so it's pretty crucial. Day-to-day, you'll sit right at the intersection of our sales team and the client's technical leadership. You're taking complex technical requirements and turning them into clear, compelling solution proposals that the client's CISO or Head of IT can get behind. When you do this well, we win deals faster, and our clients get a solution that actually works for them. If it's not done properly, deals stall, we lose credibility, and the sales team gets really frustrated, which is fair enough. The real challenge here is balancing what the client *thinks* they want with what they *actually* need, all while staying true to what our product can deliver today. You'll often be the bearer of 'tough news' when a feature isn't quite there yet, but you'll also be the hero who finds a clever workaround. The reward? Seeing your carefully crafted solution help land a massive client, and knowing you were the one who made it technically possible.

Reporting Structure

• Reports to: Manager, Solutions Consulting
• Direct reports: None (but you'll mentor 1-2 junior team members)
• Matrix relationships: Senior Solutions Consultant, Principal Presales Engineer, Technical Sales Lead,

Key Stakeholders

Internal:

• Account Executives (your primary partners)
• Sales Managers and Directors (they'll rely on your technical expertise)
• Product Managers (you're their eyes and ears in the market)
• Engineering Leads (you'll work with them on feasibility and customisations)
• Sales Operations (for pipeline reporting and process improvements)

External:

• Senior Client Technical Teams (CTOs, CISOs, Enterprise Architects)
• Client Business Stakeholders (Heads of Department, Programme Managers)
• Client Procurement and Legal Teams (for technical due diligence)
• Third-Party Integrators or Consultants (when our solution fits into a wider ecosystem)

Organisational Impact

Scope: Your work directly influences our technical win rates and the average deal size for enterprise accounts. By providing robust, credible technical solutions, you shorten sales cycles and build long-term client trust, which is absolutely essential for recurring revenue. You're also a critical feedback loop for our Product team, helping them understand what the market genuinely needs.

Performance Metrics

Quantitative Metrics

1. Metric: Technical Win Rate
2. Desc: The percentage of assigned enterprise opportunities where our solution was deemed the technical best fit by the client.
3. Target: Target: >70% technical win rate on all assigned enterprise deals
4. Freq: Measured: Quarterly, reviewed monthly with your manager
5. Example: Example: Out of 10 enterprise deals you supported last quarter, 7 moved forward with our technical recommendation, even if the commercial terms were still being negotiated.
6. Metric: Proof of Concept (PoC) Success Rate
7. Desc: The percentage of PoCs you lead that successfully meet or exceed the pre-defined technical and business success criteria.
8. Target: Target: 90% of PoCs meet or exceed success criteria
9. Freq: Measured: Per PoC completion, aggregated quarterly
10. Example: Example: You ran 5 PoCs this quarter; 4 hit every target, and the fifth exceeded expectations, leading to a faster close.
11. Metric: Average Deal Size Influence
12. Desc: The average contract value of deals where your technical solutioning played a significant role in expanding the scope or securing the win.
13. Target: Target: Influence deals with an average Annual Contract Value (ACV) of £150K+
14. Freq: Measured: Quarterly, by tracking deals you've actively supported
15. Example: Example: Your deep dive into a client's integration needs led to an additional £50K module being added to a deal that was initially only £100K.
16. Metric: Sales Cycle Length (Technical Stage)
17. Desc: The average time it takes for a deal to move from initial technical discovery to a technical win, for deals you're involved in.
18. Target: Target: Reduce average technical sales cycle by 10% year-on-year
19. Freq: Measured: Annually, based on CRM stage progression
20. Example: Example: Last year, the average technical evaluation took 60 days. This year, your efficient PoC management and clear solutioning brought it down to 54 days.

Qualitative Metrics

1. Metric: Client Technical Trust & Advocacy
2. Desc: How much clients trust your technical recommendations and are willing to advocate for our solution internally.
3. Evidence: Evidence: Clients proactively asking for your advice on unrelated technical challenges; getting direct referrals from client technical teams; positive feedback in post-deal surveys or direct testimonials about your expertise and professionalism.
4. Metric: Internal Collaboration & Product Influence
5. Desc: How effectively you work with internal teams, especially Product and Engineering, and how much your market insights influence product direction.
6. Evidence: Evidence: Product Managers regularly seeking your input on feature roadmaps; Engineering teams consulting you on architectural decisions for new features; positive feedback from Account Executives about your partnership and support; your solutions being adopted as best practices by other SAs.
7. Metric: Mentorship & Team Contribution
8. Desc: Your effectiveness in guiding and developing junior Solutions Architects, and your overall contribution to team knowledge and best practices.
9. Evidence: Evidence: Junior team members actively seeking your guidance; positive feedback from mentees on their development; your contributions to internal knowledge bases (e.g., Confluence); leading internal training sessions on new products or technical approaches; creating reusable demo assets or solution templates for the team.

Primary Traits

• Trait: Empathetic Problem-Solver
• Manifestation: You're the person who really listens when a client describes a headache, not just nodding along. You'll ask 'why' a few times to get to the actual root cause, not just the symptom. You can take their jargon and translate it into a clear technical problem, then flip it into a business benefit. Honestly, it's about making them feel heard and understood, then showing them the path forward.
• Benefit: This trait builds serious trust. If you're just pushing features without understanding their world, you'll propose solutions to the wrong problems. That leads to a 'technical win' that falls apart post-sale, and frankly, that's a waste of everyone's time and money. We need you to solve *their* problems, not just *our* problems.
• Trait: Articulate & Persuasive
• Manifestation: You can explain a complicated API integration to a non-technical CEO using a simple analogy, like comparing it to a universal adapter. You'll confidently defend a security architecture choice to a sceptical CISO, backing it up with facts and a calm demeanour. When you're in a room with 20 stakeholders, you can command attention and keep everyone engaged during a demo, even when things get a bit technical.
• Benefit: You're the face of our technical credibility in the sales cycle. If you can't communicate clearly and convincingly, clients won't trust that our product actually works as advertised. That means deals stall, and we lose out. Your ability to simplify the complex and make it compelling is absolutely critical.
• Trait: Composed Under Pressure (Resilience)
• Manifestation: Picture this: the live demo environment crashes mid-presentation to a room full of executives. Instead of panicking, you smoothly say, 'Well, this is a perfect chance to show you our disaster recovery protocol!' and switch to a backup video without missing a beat. Or an executive asks a really hostile, unexpected question; you'll pause, acknowledge their concern, and then deliver a calm, structured answer that defuses the tension.
• Benefit: Let's be real, things *always* go wrong in live presentations and complex client meetings. Panic erodes confidence instantly – both the client's confidence in us and the sales team's confidence in you. Your ability to remain calm, in control, and adaptable reassures everyone that they're dealing with a true professional who can handle any curveball.

Supporting Traits

• Trait: Insatiably Curious
• Desc: You're genuinely driven to understand how different businesses operate, how various technologies fit together, and what makes a client's world tick. You'll dig into new tech trends just for the fun of it.
• Trait: Self-Directed
• Desc: You can juggle multiple complex deals, manage your own time, and prioritise tasks across different clients without needing constant supervision. You're proactive in finding answers and moving things forward.
• Trait: Collaborative
• Desc: You see the Account Executive as your partner in crime, not just someone who brings you work. You'll actively work to make the entire sales team successful, sharing insights and helping wherever you can.
• Trait: Pragmatic
• Desc: You know when a 'good enough' solution is the right answer to get a deal over the line, rather than over-engineering a perfect but overly complex and time-consuming architecture. You balance technical purity with commercial reality.

Primary Motivators

1. Motivator: Solving Complex Puzzles
2. Daily: You love diving into a client's messy tech stack and figuring out how our product can cleanly integrate and solve their business problems. It's the thrill of the intellectual challenge.
3. Motivator: Being the Technical Expert & Go-To Person
4. Daily: You enjoy being the person everyone turns to for the deep technical answers, both internally and externally. You get satisfaction from explaining complex concepts clearly.
5. Motivator: Direct Impact on Business Outcomes
6. Daily: You're motivated by seeing your technical work directly contribute to closing significant deals and helping clients achieve their business goals. Your efforts aren't just theoretical.

Potential Demotivators

Honestly, this job isn't for everyone. You'll often find yourself in situations where the 'urgent' request that disrupted your Thursday gets deprioritised on Friday, or you'll spend 30+ hours building a bespoke PoC for a prospect who then 'goes dark' and never responds. You'll certainly build beautiful solution diagrams that never get deployed because the business moved on, or the deal was lost on pricing. If you need to see every piece of your work make it to production, or if you can't handle the inherent ambiguity and occasional waste of effort that comes with sales, you'll really struggle here.

Common Frustrations

1. The Account Executive promising a feature that is, at best, a vague idea on the product roadmap, then turning to you in the meeting and saying, '...and my partner here can show you how it works.'
2. Spending days building a bespoke PoC for a prospect who then 'goes dark' and never responds again. It feels like unpaid consulting, and it's frustrating.
3. Being pulled into 'discovery' calls that are actually unqualified demos for prospects who have no budget, authority, or real need. It's a time sink.
4. The constant tension with the Product team between what the market is demanding *today* and what their six-month roadmap allows. You're always trying to bridge that gap.
5. Losing a deal you've already 'technically won' because of pricing, politics, or a last-minute decision from a new executive you never even met.
6. Having your week's carefully planned work derailed by a last-minute, 'urgent' request for a demo from a different time zone. Flexibility is key, but it's still annoying.
7. Explaining the same fundamental technical concept for the fifth time to a sales rep who, frankly, refuses to learn the basics. Patience is a virtue here.

What Role Doesn't Offer

1. A predictable, routine 9-5 schedule. Sales cycles are unpredictable, and client needs change fast.
2. Guaranteed deployment of every solution you design. Many deals won't close, or requirements will shift.
3. Deep, heads-down coding or engineering work. This is client-facing technical problem-solving, not product development.
4. Complete control over the sales process. You're a critical partner, but the AE owns the commercial relationship.

ADHD Positives

1. The varied nature of client problems and deals means less routine and more novel challenges, which can be highly engaging.
2. The need for quick thinking and adaptability in live demo situations can be a strength.
3. The role often involves hyper-focusing on complex technical architectures for specific clients, which can be very rewarding.

ADHD Challenges and Accommodations

1. Managing multiple complex deals and priorities simultaneously can be challenging; we can help with structured project management tools and regular check-ins to keep things on track.
2. Documentation, while essential, might feel tedious; breaking it into smaller, manageable tasks or using templates can help.
3. The open-plan office environment or constant travel might be overstimulating; we offer noise-cancelling headphones and flexibility for focused work from home when possible.

Dyslexia Positives

1. Strong visual-spatial reasoning is often a hallmark of dyslexia, which is incredibly valuable for architecting complex solutions and creating clear diagrams.
2. Excellent verbal communication skills, often developed as a compensatory strategy, are critical for explaining technical concepts persuasively.
3. The ability to see the 'big picture' and make connections between disparate ideas is a huge asset in solution design.

Dyslexia Challenges and Accommodations

1. Reading and writing lengthy RFP responses or detailed technical documentation can be time-consuming; we encourage the use of dictation software, proofreading tools, and templates.
2. Organising complex information might require specific strategies; we can provide tools like mind-mapping software and offer support for structuring written output.
3. We're happy to offer screen readers, text-to-speech software, and allow for alternative formats for presenting information where appropriate.

Autism Positives

1. A deep, logical approach to problem-solving and technical architecture is highly valued in this role.
2. The ability to focus intently on technical details and identify inconsistencies or edge cases is a significant strength.
3. A preference for clear, direct communication can cut through ambiguity in complex technical discussions.

Autism Challenges and Accommodations

1. The highly social and often unpredictable nature of sales interactions can be draining; we support scheduled 'focus time' away from client calls and provide clear agendas for meetings.
2. Interpreting unspoken social cues or navigating office politics can be tricky; we aim for transparent communication and provide direct feedback.
3. Sensory overload from open-plan offices, travel, or busy client sites might be an issue; we offer quiet workspaces, noise-cancelling options, and flexibility for remote work.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Senior Solutions Architect (5-8 years experience)
2. Responsibilities: Lead the technical sales cycle for our most complex enterprise accounts, acting as the primary technical point of contact from discovery through to the technical win. This means you're often the one clients trust most.
3. Design bespoke, comprehensive solution architectures that integrate our product seamlessly into a client's existing (and often messy) technical ecosystem. You'll be drawing diagrams, mapping data flows, and making it all look easy.
4. Own the end-to-end execution and success of Proof of Concepts (PoCs) and Proof of Value (PoVs) for strategic accounts. This involves defining clear success criteria, managing client expectations, and delivering compelling results that drive the deal forward.
5. Mentor and guide 1-2 junior Solutions Architects, providing technical reviews of their work, helping them unstick tricky problems, and supporting their professional development. You're helping build the next generation.
6. Represent our company's technical vision, product roadmap, and security posture to senior client technical leadership (CTOs, CISOs, Enterprise Architects). You'll need to speak their language and earn their respect.
7. Contribute significantly to our internal knowledge base by creating new demo assets, solution templates, and best practices documentation that the wider Solutions Consulting team can use. You're making everyone else's job easier.
8. Lead the technical response strategy for complex Requests for Proposal (RFPs) and Requests for Information (RFIs), coordinating input from various internal teams and crafting persuasive technical narratives that highlight our competitive advantages.
9. Supervision: You'll typically check in with your Manager bi-weekly or on a project-by-project basis for strategic alignment. Day-to-day execution is largely autonomous; you're expected to manage your own workload and priorities across multiple complex deals.
10. Decision: You have full authority for technical decisions within your assigned project scope (e.g., tool selection for a PoC, optimal integration patterns, architectural recommendations). You'll recommend budget allocations for PoC resources (up to roughly £10K) but won't approve them independently. For significant changes to deal strategy or timelines, you'll consult with your Account Executive and Solutions Consulting Manager.
11. Success: You'll know you're succeeding when your technical win rate consistently hits over 70% on enterprise deals, your PoCs almost always meet their success criteria, and junior team members actively seek your guidance. Beyond the numbers, clients will see you as a trusted technical advisor, and internal teams will value your insights into market needs.

Decision-Making Authority

• Type: Technical Architecture Design for a Client
• Entry: Follows pre-defined templates; all designs reviewed by a Senior SA.
• Mid: Designs standard architectures independently; complex scenarios reviewed by a Senior SA.
• Senior: Full autonomy to design complex, bespoke architectures for enterprise clients; consults with Product/Engineering on novel requirements.
• Type: Proof of Concept (PoC) Scope & Success Criteria
• Entry: Assists in PoC execution; scope and criteria defined by a Senior SA.
• Mid: Defines scope and criteria for routine PoCs; complex PoCs with Senior SA guidance.
• Senior: Owns and defines PoC scope and success criteria for all strategic enterprise deals, ensuring alignment with commercial goals.
• Type: Internal Technical Best Practices & Mentorship
• Entry: Consumes and applies existing best practices; receives mentorship.
• Mid: Contributes to internal knowledge base; informally guides new joiners.
• Senior: Leads the development of new technical best practices; formally mentors 1-2 junior Solutions Architects.

Competency Requirements

Foundation Skills (Transferable)

These are the core human skills that underpin everything you do. You can be the most technically brilliant person in the room, but if you can't talk to people or solve problems collaboratively, you won't get very far in Sales.

• Category: Communication & Presentation
• Skills: Executive-level Presentation: Confidently present complex technical solutions to C-suite executives, simplifying jargon and focusing on business impact.
• Technical Storytelling: Weave compelling narratives around technical features, showing how they solve real-world problems for clients.
• Active Listening: Truly hear and understand client needs, even when they're not explicitly stated, asking probing questions to get to the root cause.
• Objection Handling: Calmly and effectively address technical objections and concerns from sceptical clients, turning challenges into opportunities.
• Category: Problem-Solving & Critical Thinking
• Skills: Complex Solution Design: Architect robust, scalable, and secure technical solutions that address intricate client requirements and integrate with diverse systems.
• Root Cause Analysis: Quickly diagnose technical issues or business pains during discovery, identifying the underlying problems rather than just the symptoms.
• Strategic Thinking: Understand how our technical solutions fit into a client's broader business strategy and how they contribute to their long-term goals.
• Trade-off Analysis: Evaluate different technical approaches, weighing their pros and cons (cost, complexity, time-to-value) to recommend the optimal path.
• Category: Collaboration & Influence
• Skills: Cross-functional Partnership: Work seamlessly with Account Executives, Product, Engineering, and Customer Success to deliver a cohesive client experience.
• Internal Advocacy: Represent client needs and market feedback to internal teams, influencing product roadmap decisions and technical priorities.
• Mentorship & Coaching: Guide and develop junior Solutions Architects, sharing your expertise and helping them grow their technical and sales skills.
• Negotiation (Technical): Navigate technical negotiations with clients, finding common ground and securing agreement on solution scope and requirements.
• Category: Adaptability & Resilience
• Skills: Managing Ambiguity: Thrive in situations where requirements are unclear or constantly changing, bringing structure and clarity to complex problems.
• Grace Under Pressure: Maintain composure and effectiveness during high-stakes client presentations or when facing unexpected technical challenges.
• Continuous Learning: Stay up-to-date with rapidly evolving technologies, industry trends, and our product's capabilities, always looking to expand your knowledge.
• Feedback Incorporation: Actively seek and use feedback from clients and internal teams to continuously improve your approach and solutions.

Functional Skills (Role-Specific Technical)

These are the specific technical and domain-specific skills you'll need to excel. It's a blend of deep technical knowledge, understanding how sales works, and knowing our product inside out.

Technical Competencies

• Skill: Discovery & Requirements Gathering
• Desc: Systematically uncovering a client's true business pains and technical constraints, moving beyond their stated needs to identify the root cause problem they're trying to solve. This means asking the right questions and listening more than you talk.
• Level: Advanced
• Skill: Proof of Concept (PoC) / Proof of Value (PoV) Management
• Desc: Scoping, defining, and executing time-bound trials with crystal-clear success criteria that directly map to the client's desired business outcomes. You're preventing 'scope creep' and making sure we don't do unpaid consulting.
• Level: Advanced
• Skill: Solution Selling & Value Engineering
• Desc: The practice of mapping technical features to specific, quantifiable business value (e.g., 'Our API integration reduces manual data entry, saving your team 20 hours per week, which equates to £50K annually'). You're showing them the money.
• Level: Advanced
• Skill: RFP/RFI Response Strategy
• Desc: Deconstructing complex Request for Proposal/Information documents, managing the response process across multiple internal teams, and crafting compelling technical narratives that highlight our competitive differentiators. It's a project management task in itself.
• Level: Advanced
• Skill: Technical Feasibility & Gap Analysis
• Desc: Rigorously assessing if our current product can meet a prospect's requirements, identifying any gaps, and architecting viable workarounds or clearly communicating limitations to the sales team. Honesty and creativity are key here.
• Level: Advanced
• Skill: Enterprise Architecture Fluency
• Desc: The ability to confidently discuss concepts like microservices vs. monoliths, data residency, API gateways, and identity federation (SAML/OAuth) with a client's C-suite and technical architects. You need to speak their language.
• Level: Advanced

Digital Tools

• Tool: Salesforce (Sales Cloud, CPQ)
• Level: Advanced
• Usage: Building complex dashboards to track PoC success rates and technical win rates; mastering multi-product deal configuration in CPQ; influencing CRM data model design for presales reporting.
• Tool: Reprise/Demostack (or similar demo automation)
• Level: Advanced
• Usage: Building custom, interactive demos from scratch, often with prospect data; creating and managing a library of reusable demo assets for the team.
• Tool: Figma / Miro / Lucidchart
• Level: Advanced
• Usage: Designing complex, multi-system solution diagrams from a blank canvas; facilitating technical workshops with clients using collaborative whiteboarding tools; creating high-fidelity mockups for custom solutions.
• Tool: Postman
• Level: Advanced
• Usage: Writing basic scripts and tests for API integrations during PoCs; demonstrating API capabilities to technical client teams; troubleshooting integration issues.
• Tool: Confluence / Jira / Slack (or MS Teams)
• Level: Advanced
• Usage: Owning Confluence spaces for technical knowledge and best practices; writing detailed Jira tickets for Product based on client feedback; leading technical discussions and knowledge sharing in Slack/Teams.
• Tool: Gong.io / Chorus.ai (or similar sales intelligence)
• Level: Advanced
• Usage: Analysing competitor mentions and technical objection patterns across the team's calls; building custom reports using AI insights to refine messaging and training.
• Tool: Tableau / Power BI Premium (or similar reporting)
• Level: Intermediate
• Usage: Building custom dashboards to track PoC success rates, technical win rates, and demo activity for your team or region. You'll also consume executive dashboards.

Industry Knowledge

• Area: Cloud Computing Architectures
• Desc: Deep understanding of public cloud platforms (AWS, Azure, GCP), including IaaS, PaaS, SaaS models, security best practices, and common integration patterns. You'll need to talk multi-cloud strategies with confidence.
• Area: Data Integration & API Management
• Desc: Expertise in various data integration methods (ETL, API-led, streaming), API design principles, and API gateway concepts. Clients will ask about connecting everything together.
• Area: Cybersecurity Fundamentals
• Desc: Solid grasp of cybersecurity principles, data privacy regulations (GDPR, CCPA), identity and access management (IAM), and common security frameworks. You'll be grilled by CISOs.
• Area: Software Development Life Cycle (SDLC)
• Desc: Familiarity with agile methodologies, DevOps practices, and modern software development processes. This helps you speak the same language as client engineering teams.

Regulatory Compliance Regulations

• Reg: GDPR (General Data Protection Regulation)
• Usage: Understand how our product handles personal data, data residency requirements, and security measures to ensure compliance, especially when discussing solutions with European clients.
• Reg: ISO 27001 (Information Security Management)
• Usage: Be able to explain our company's adherence to ISO 27001 standards and how our security controls meet these requirements, particularly for clients with stringent security policies.
• Reg: Industry-Specific Regulations (e.g., PCI DSS, HIPAA)
• Usage: Recognise when a client operates in a highly regulated industry and understand the basic implications for solution design, knowing when to bring in specialist legal or compliance teams.

Essential Prerequisites

• At least 5 years of experience in a client-facing technical role, such as Solutions Consultant, Presales Engineer, or Technical Account Manager, with a proven track record of supporting enterprise sales.
• Demonstrable experience designing and presenting complex technical solutions, including architectural diagrams and data flow maps, to senior technical and business stakeholders.
• A strong technical background in cloud platforms, APIs, data integration, and cybersecurity concepts – you need to be able to hold your own in deep technical conversations.
• Proven ability to manage and execute successful Proof of Concepts (PoCs) or Proof of Value (PoVs) from definition to delivery, with clear, measurable outcomes.
• Experience mentoring junior team members or leading technical initiatives within a team environment.

Career Pathway Context

To really thrive as a Senior Solutions Architect, you'll have already mastered the fundamentals of technical sales and solutioning. You'll have a solid understanding of our product and the market, and you'll be ready to take on bigger, more complex challenges with less direct supervision. This isn't a role where you're just learning the basics; you're expected to hit the ground running and lead.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: Prompt Engineering & LLM Integration
• Why: Honestly, competitors are already using generative AI to draft RFP responses in minutes, not hours. Analysts who figure this out will outproduce their peers significantly. This isn't a 'nice-to-have' anymore; it's becoming critical within the next 6-12 months.
• Concepts: [{'concept_name': 'Context windows and token limits', 'description': 'Understanding how much information an LLM can process at once and how to manage it effectively.'}, {'concept_name': 'Temperature settings for different tasks', 'description': 'Knowing when to make an LLM creative (high temperature) versus factual (low temperature) for different outputs.'}, {'concept_name': 'RAG architectures for proprietary data', 'description': 'Implementing Retrieval-Augmented Generation to ensure LLMs use our specific, accurate company knowledge, not just general internet data.'}, {'concept_name': 'Output validation and hallucination detection', 'description': "Developing methods to quickly check if an LLM's output is accurate and identifying when it's 'making things up'."}, {'concept_name': 'Prompt chaining for complex analysis', 'description': 'Breaking down complex tasks into smaller, sequential prompts to guide the LLM through multi-step problem-solving.'}]
• Prepare: This month: Set up and experiment with GitHub Copilot or similar AI coding assistants for any scripting or demo environment setup.
• Next month: Build one automated first-draft RFP response using an LLM API (e.g., OpenAI, Claude) and our internal documentation.
• Month 3: Explore RAG implementation for a specific internal use case, like generating product FAQs from our Confluence pages.
• Month 4: Document the productivity gains from your AI experiments and share your findings and best practices with the wider team.
• QuickWin: Start using Claude or ChatGPT today to draft email summaries, brainstorm solution ideas, or create quick outlines for presentations. No formal approval needed, and you'll see immediate benefits.
• Skill: Ethical AI & Trust in Solutions
• Why: As AI becomes more integrated into our products and our clients' operations, questions about bias, transparency, and data privacy are becoming paramount. Clients, especially in regulated industries, will demand clear answers. This is becoming important within 12-18 months.
• Concepts: [{'concept_name': 'Explainable AI (XAI)', 'description': 'Understanding how to articulate *why* an AI made a certain decision, not just *what* it decided.'}, {'concept_name': 'Bias detection and mitigation in AI models', 'description': 'Recognising potential biases in data or algorithms and how to address them in solutions.'}, {'concept_name': 'Data governance for AI', 'description': 'Ensuring data used for AI training and operation adheres to privacy and ethical standards.'}, {'concept_name': 'Regulatory landscape for AI', 'description': 'Basic awareness of emerging AI regulations (e.g., EU AI Act) and their impact on solution design.'}, {'concept_name': 'Human-in-the-loop processes', 'description': 'Designing solutions where human oversight and intervention are built into AI-driven workflows.'}]
• Prepare: This quarter: Read a few articles or listen to podcasts on ethical AI in business applications.
• Next quarter: Identify one area in our product or a client solution where AI ethics might be a concern and research how to address it.
• Month 6: Participate in an internal discussion or training session on responsible AI practices.
• Month 9: Begin incorporating ethical considerations into your solution narratives for relevant clients.
• QuickWin: When discussing AI features with clients, proactively ask about their concerns regarding bias or data privacy, and note down common questions to help us build better responses.

Advancing Technical Skills

• Skill: Advanced Cloud Native Architectures
• Why: Clients are moving beyond basic cloud adoption to truly cloud-native solutions, demanding deeper expertise in serverless, containerisation (Kubernetes), and advanced microservices patterns. This is critical within 12 months.
• Concepts: [{'concept_name': 'Serverless computing (AWS Lambda, Azure Functions)', 'description': 'Designing and explaining event-driven architectures without managing servers.'}, {'concept_name': 'Container orchestration (Kubernetes, Docker Swarm)', 'description': 'Understanding how applications are deployed, scaled, and managed in containerised environments.'}, {'concept_name': 'Service mesh concepts (Istio, Linkerd)', 'description': 'Explaining how to manage communication between microservices in complex distributed systems.'}, {'concept_name': 'Cloud security best practices (least privilege, network segmentation)', 'description': 'Designing highly secure cloud environments that meet enterprise standards.'}]
• Prepare: This quarter: Complete an advanced certification in one major cloud provider (e.g., AWS Solutions Architect - Professional).
• Next quarter: Build a small, personal project using serverless functions or containers to get hands-on experience.
• Month 6: Engage with our internal engineering teams on their cloud-native initiatives and learn from their challenges.
• Month 9: Start incorporating advanced cloud-native patterns into your client solution designs and discussions.
• QuickWin: Follow key cloud architecture blogs and podcasts. When a client mentions Kubernetes, ask a specific, informed question to show you're up to speed.
• Skill: Data Mesh & Data Fabric Concepts
• Why: As businesses grapple with vast amounts of distributed data, traditional data warehousing approaches are evolving. Clients are increasingly asking about modern data architectures to manage their data assets. This is important within 18-24 months.
• Concepts: [{'concept_name': 'Data as a Product', 'description': 'Understanding the paradigm shift where data domains are treated as independent products with clear APIs and ownership.'}, {'concept_name': 'Decentralised Data Governance', 'description': 'Explaining how data quality, security, and compliance are managed across distributed data domains.'}, {'concept_name': 'Self-serve Data Platforms', 'description': 'Discussing the infrastructure that enables domain teams to manage and expose their data products easily.'}, {'concept_name': 'Semantic Layer & Knowledge Graphs', 'description': 'Understanding how to create a unified view of data across disparate sources for easier consumption and analysis.'}]
• Prepare: This quarter: Read Zhamak Dehghani's 'Data Mesh' book or key articles on the topic.
• Next quarter: Identify clients who are struggling with data silos and brainstorm how data mesh/fabric principles could help.
• Month 6: Discuss these concepts with our Product team to see how they might influence our own data strategy.
• Month 9: Start incorporating these architectural patterns into your strategic client conversations where relevant.
• QuickWin: If a client mentions 'data silos' or 'getting a single source of truth,' ask them about their current data governance challenges and if they've explored decentralised approaches.

Education Requirements

Experience Requirements

Level: Minimum | Req: A Bachelor's degree in Computer Science, Engineering, Information Technology, or a closely related technical field. | Alts: We're pragmatic here. If you've got equivalent practical experience (typically 8+ years in a highly technical role) and can prove your chops, we're absolutely interested. We value demonstrable skill over a piece of paper. | Level: Preferred | Req: A Master's degree in a relevant technical field or an MBA (if you're eyeing a leadership path). | Alts: Relevant industry certifications (like those below) or significant contributions to open-source projects can often be just as valuable, if not more so.

Preferred Certifications

• Cert: AWS Certified Solutions Architect - Professional / Azure Solutions Architect Expert / Google Cloud Professional Cloud Architect
• Prod: Amazon Web Services / Microsoft Azure / Google Cloud
• Usage: These demonstrate deep expertise in designing and deploying scalable, secure, and resilient solutions on major cloud platforms, which is critical for our enterprise clients.
• Cert: Salesforce Certified Technical Architect (CTA)
• Prod: Salesforce
• Usage: If our product deeply integrates with Salesforce, this shows an exceptional understanding of the Salesforce platform and ecosystem, which is invaluable for complex integrations.
• Cert: TOGAF 9 Certification (The Open Group Architecture Framework)
• Prod: The Open Group
• Usage: Shows a structured approach to enterprise architecture, which helps in designing robust, long-term solutions for large organisations.
• Cert: Certified Information Systems Security Professional (CISSP)
• Prod: ISC²
• Usage: Demonstrates a strong understanding of information security principles and practices, crucial for addressing client security concerns and designing secure solutions.

Recommended Activities

• Regularly attend industry conferences (e.g., AWS re:Invent, Dreamforce, Gartner IT Symposium) to stay current on trends and network.
• Actively participate in online technical communities (e.g., Stack Overflow, GitHub, relevant subreddits) and contribute to discussions.
• Dedicate time each week for self-study, online courses (Coursera, Udemy, Pluralsight), or reading technical books on emerging technologies.
• Seek out opportunities to present at internal 'lunch and learns' or external meetups, honing your presentation and technical storytelling skills.
• Pursue additional certifications that align with your career goals and the evolving needs of our product and market.

Career Progression Pathways

Entry Paths to This Role

• Path: Solutions Consultant (L2) to Senior Solutions Architect (L3)
• Time: 2-3 years as a Solutions Consultant
• Path: Technical Account Manager (TAM) to Senior Solutions Architect (L3)
• Time: 3-5 years as a TAM
• Path: Product Specialist / Implementation Consultant to Senior Solutions Architect (L3)
• Time: 3-5 years in a product or implementation role

Career Progression From This Role

• Pathway: Lead / Staff Solutions Architect (L4)
• Time: 3-5 years as a Senior Solutions Architect
• Pathway: Manager, Solutions Consulting (L5)
• Time: 3-5 years as a Senior Solutions Architect

Long Term Vision Potential Roles

• Title: Director, Solutions Architecture (L6)
• Time: 5-10 years from Senior SA
• Title: VP, Global Presales & Solutions (L7)
• Time: 10-15+ years from Senior SA
• Title: Principal / Distinguished Architect (IC Path)
• Time: 5-10 years from Senior SA

How Zavmo Delivers This Role's Development

DISCOVER Phase: Skills Gap Analysis

Zavmo maps your current competencies against all requirements in this job description through conversational assessment. We evaluate your foundation skills (communication, strategic thinking), functional skills (CRM expertise, negotiation), and readiness for career progression.

Output: Personalised skills gap heat map showing strengths and priorities, estimated time to competency, neurodiversity accommodations.

DISCUSS Phase: Personalised Learning Pathway

Based on your DISCOVER results, Zavmo creates a personalised learning plan prioritised by impact: foundation skills first, then functional skills. We adapt to your learning style, pace, and neurodiversity needs (ADHD, dyslexia, autism).

Output: Week-by-week schedule, each module linked to specific job responsibilities, checkpoints and milestones.

DELIVER Phase: Conversational Learning

Learn through conversation, not boring modules. Zavmo uses 10 conversation types (Socratic dialogue, role-play, coaching, case studies) to build competence. Practice difficult QBR presentations, negotiate tough renewals, and handle churn conversations in a safe AI environment before facing real clients.

Example: "For 'Stakeholder Mapping', Zavmo will guide you through analysing a complex enterprise account, identifying key decision-makers, and building an engagement strategy."

DEMONSTRATE Phase: Competency Assessment

Zavmo automatically builds your evidence portfolio as you learn. Every conversation, practice scenario, and application example is captured and mapped to NOS performance criteria. When ready, your portfolio supports OFQUAL qualification claims and demonstrates competence to employers.

Output: Competency matrix, evidence portfolio (downloadable), qualification readiness, career progression score.