Solutions Consultant

Role Purpose & Context

Role Summary

The Solutions Consultant is responsible for independently showing prospective clients how our product works and why it's the right technical choice for them. You'll be the person who takes a client's messy problem and clearly demonstrates how our solution fits right in, often through live demos and proof-of-concept trials. You'll work at the intersection of our sales team and the client's technical staff, translating their business challenges into technical requirements and then proving our ability to meet them. When this role is done well, our Account Executives close deals faster because the client's technical team is fully on board. When it's not, we lose deals to competitors who might not even have a better product, just a better technical story. The challenge is balancing sales urgency with technical rigour, making sure we don't over-promise. The reward is seeing a client's 'aha!' moment when they realise our tech is exactly what they've been looking for.

Reporting Structure

• Reports to: Manager, Solutions Consulting
• Direct reports:
• Matrix relationships: Technical Sales Engineer, Pre-Sales Engineer, Sales Engineer,

Key Stakeholders

Internal:

• Account Executives (your sales partners)
• Product Management (for feedback on features)
• Customer Success (for smooth handovers)
• Sales Operations (for process improvements)

External:

• Client Technical Leads (architects, engineers)
• Client IT Managers
• Client Project Managers
• Mid-market business owners

Organisational Impact

Scope: You're directly responsible for the technical 'win' in a sales cycle. Your ability to clearly articulate our product's value and handle technical objections means the difference between a closed deal and a lost opportunity. You'll influence revenue growth by ensuring our solutions are technically sound and compelling to mid-market clients, which in turn helps us hit our overall sales targets. Honestly, without you, our sales team would be trying to sell a complex product with one hand tied behind their back.

Performance Metrics

Quantitative Metrics

1. Metric: Technical Win Rate
2. Desc: The percentage of sales opportunities you support that successfully pass the client's technical evaluation stage.
3. Target: >80% of supported opportunities
4. Freq: Quarterly
5. Example: If you support 20 opportunities in a quarter and 17 of them get a technical 'thumbs up' from the client, that's an 85% technical win rate. We're looking for consistent performance here.
6. Metric: Demo Delivery Volume
7. Desc: The number of qualified product demonstrations you deliver to prospective clients.
8. Target: 15-20 qualified demos per quarter
9. Freq: Weekly/Monthly review, Quarterly summary
10. Example: Delivering 18 impactful demos in Q2, where each demo was well-researched and tailored to the prospect's needs, would be right on target. It's not just about quantity, but quality of engagement.
11. Metric: Proof of Concept (PoC) Conversion Rate
12. Desc: The percentage of PoCs you manage that ultimately lead to a closed-won deal.
13. Target: >65% of managed PoCs
14. Freq: Quarterly
15. Example: If you run 10 PoCs and 7 of those deals close, that's a 70% conversion rate. This shows your ability to scope and execute trials that genuinely prove value and lead to sales.
16. Metric: Average Deal Size (Supported)
17. Desc: The average Annual Contract Value (ACV) of deals where you played a significant technical role.
18. Target: Contribute to £1.5M+ ACV annually
19. Freq: Annually
20. Example: If the total ACV of deals you helped close this year is £1.8M across 10 deals, your average supported deal size is £180K. This shows your impact on larger, more strategic opportunities.

Qualitative Metrics

1. Metric: Client Technical Satisfaction
2. Desc: How satisfied clients are with your technical explanations, support during PoCs, and overall engagement.
3. Evidence: Direct feedback from clients to Account Executives or your manager; clients proactively asking for you on follow-up calls; positive comments in post-PoC surveys (if applicable); successful, smooth technical handovers to Customer Success.
4. Metric: Internal Account Executive (AE) Feedback
5. Desc: The quality of collaboration and support you provide to your sales partners.
6. Evidence: AEs consistently seeking you out for deals; positive comments in internal team reviews; AEs feeling well-prepared for technical conversations after working with you; smooth pre-call planning and post-call debriefs.
7. Metric: Knowledge Base Contribution & Accuracy
8. Desc: Your active participation in keeping our internal technical knowledge base current and accurate.
9. Evidence: Regularly updating existing articles with new product information or common technical objections; authoring new articles based on common client questions or successful PoC configurations; your colleagues frequently referencing your contributions; catching and correcting outdated information.
10. Metric: Proactive Problem Solving
11. Desc: Your ability to anticipate technical issues during the sales cycle and propose solutions before they become blockers.
12. Evidence: Identifying potential integration challenges early in discovery and suggesting workarounds; flagging product limitations to the AE and Product team before a client encounters them; preparing 'landmine' question responses in advance; suggesting alternative technical approaches to clients when their initial idea isn't feasible with our product.

Primary Traits

• Trait: Empathetic Problem-Solver
• Manifestation: You're the person who truly listens when a client describes their headache, not just waiting for your turn to speak. You'll ask 'why' a few times to really get to the root of their problem, often rephrasing it back to them to make sure you've got it right. You'd rather sketch out a solution on a whiteboard with them than just click through slides. You're trying to understand their world, their specific challenges, and how our tech can genuinely make their life easier, not just what features we've got.
• Benefit: Clients don't buy features; they buy solutions to their actual problems. If you can accurately diagnose what's truly bothering them – 'You're not just trying to back up data, you're trying to meet a 15-minute Recovery Time Objective for your tier-1 apps' – you build immense trust. That trust is what wins the technical evaluation, especially in a competitive mid-market.
• Trait: Intellectually Curious
• Manifestation: You've got a genuine itch to know how things work, even beyond our own product. Maybe you've got a little home lab, or you're dabbling in a personal coding project. You're probably the first one to dig into new product features internally, just to see what they can do. You might even read competitor API documentation for fun – yes, for fun. You're always asking 'what if?' and 'how does that connect?'
• Benefit: Technology moves at lightning speed. If you're relying on last year's knowledge, you'll quickly lose credibility with technically savvy clients. This curiosity means you can handle unexpected questions, position our product against emerging technologies, and keep up with the ever-changing landscape. It's essential for staying relevant and effective in a technical sales role.
• Trait: Poised & Articulate
• Manifestation: You can explain really complex technical stuff to anyone, from a CEO who just wants the high-level picture to a seasoned engineer who's going to grill you on the details. You use analogies that actually make sense. If a demo fails live – and trust me, they sometimes do – you don't panic; you calmly troubleshoot or pivot. When a sceptical engineer asks a tough question, you answer with data and respect, not defensiveness.
• Benefit: As a Solutions Consultant, you're the face of our product's quality and our company's technical expertise. If you can't communicate clearly or you lose your cool under pressure, it erodes customer confidence in both our technology and our team. Your ability to translate and reassure is crucial for getting that technical 'yes'.

Supporting Traits

• Trait: Resilient
• Desc: Honestly, you'll lose deals you thought were in the bag. Demos will sometimes go wrong. You need to be able to dust yourself off, figure out what happened, and bounce back quickly for the next client. It's about learning from setbacks, not dwelling on them.
• Trait: Self-Directed
• Desc: You're often out there on your own, managing your schedule, prioritising your learning, and prepping for calls. Your manager isn't going to hold your hand every day. You need to be able to figure things out and keep yourself organised without constant supervision.
• Trait: Influential
• Desc: You're not just presenting; you're persuading. You need to influence clients externally to see our product's value, and sometimes, you'll need to influence our own Product or Engineering teams internally to consider client feedback or address a bug. It's about building consensus and getting people on board with your technical vision.

Primary Motivators

1. Motivator: Solving Technical Puzzles
2. Daily: You get a real buzz from diving deep into a client's existing architecture, identifying the bottlenecks, and then figuring out exactly how our product slots in to fix it. It's like being a detective, but for tech.
3. Motivator: Seeing Clients Succeed
4. Daily: It's not just about closing the deal; it's about knowing that the solution you helped architect will genuinely improve a client's operations or save them money. You care about the long-term impact.
5. Motivator: Continuous Learning & Mastery
6. Daily: You're always keen to get your hands on the latest product release, dig into a new cloud service, or understand a competitor's strategy. The idea of becoming a true expert in a rapidly evolving field really excites you.

Potential Demotivators

Honestly, this role isn't for everyone. If you thrive on predictable routines or expect every piece of your work to go smoothly, you might find it tough. You'll often be dealing with imperfect information, tight deadlines, and sometimes, outright frustration.

Common Frustrations

1. The Unqualified Demo Request: Getting pulled into a last-minute demo by an Account Executive for a prospect who hasn't been properly vetted. It feels like a waste of your valuable prep time.
2. Product Gaps & Bugs: Being on the front line, having to explain away a known product limitation or find a creative workaround for a bug in front of a sceptical client. It's tough when you can't deliver perfection.
3. Losing on Politics, Not Tech: Spending weeks proving our solution is technically superior, only for the deal to fall through because of a pre-existing relationship, internal politics, or a budget cut. It's demoralising.
4. Context Switching Fatigue: Juggling a deep technical dive for a potential enterprise client in the morning, then switching gears for a high-level, quick demo for a small business in the afternoon. It's mentally exhausting.
5. AE-TSEN Compensation Misalignment: Sometimes, there's friction because Account Executives are focused purely on closing the deal, while you're trying to ensure the technical viability and long-term success of the solution. Different priorities can clash.

What Role Doesn't Offer

1. A predictable 9-to-5 schedule: Client calls and demo prep often spill over, especially when you're working across time zones.
2. Absolute technical perfection: Our product is great, but like any software, it has limitations. You won't always have a perfect answer for every technical challenge.
3. Solo work: While you're self-directed, you're constantly collaborating with AEs, product teams, and clients. If you prefer to just put your head down and code, this isn't it.

ADHD Positives

1. The constant context switching and varied nature of the work (demos, PoCs, research, client calls) can be really engaging and prevent boredom, which is great for ADHDers.
2. The need for quick, on-the-spot problem-solving during live demos can tap into hyperfocus and quick thinking.
3. The external pressure of client deadlines can be a strong motivator to get things done.

ADHD Challenges and Accommodations

1. Keeping track of multiple deals, client requirements, and internal requests can be overwhelming. We can help with structured CRM usage, clear prioritisation tools, and regular check-ins.
2. Deep technical documentation (yes, it's necessary) might feel tedious. We encourage breaking it into smaller tasks and using AI tools to assist with drafting.
3. Maintaining focus during long, detailed technical discovery calls can be tough. Using active listening techniques, note-taking templates, and short breaks can help. We're open to fidget toys or standing desks.

Dyslexia Positives

1. The strong emphasis on verbal communication, live demonstration, and visual problem-solving (whiteboarding) plays to the strengths often associated with dyslexia.
2. The ability to think creatively about solutions and connect disparate technical concepts can be a real asset in this role.
3. Hands-on work with technology and building things (PoCs) can be more engaging than text-heavy tasks.

Dyslexia Challenges and Accommodations

1. Reading and responding to complex RFPs or detailed technical specifications can be challenging. We use tools like Grammarly, text-to-speech software, and peer review for critical documents.
2. Detailed technical documentation and email communication require precision. We can provide templates, use AI writing assistants, and offer proofreading support.
3. Note-taking during client calls needs to be efficient. We encourage digital note-taking with transcription services and structured templates to capture key points.

Autism Positives

1. The deep technical focus and need for logical, structured problem-solving (especially in PoCs and solution architecture) can be very appealing.
2. The ability to dive deep into specific technical areas and become an expert is highly valued.
3. Clear, factual communication of technical details, rather than vague corporate-speak, is essential and often a strength.

Autism Challenges and Accommodations

1. Navigating complex social dynamics in sales meetings, especially with multiple stakeholders, can be draining. We can provide pre-meeting briefs on client personalities and roles, and allow for 'decompression time' after intense calls.
2. Unexpected changes in demo environments or client requirements can be unsettling. We aim for clear communication of changes and provide ample preparation time for demos.
3. Interpreting non-verbal cues in sales conversations might be difficult. We encourage direct, explicit communication and focus on objective technical requirements.
4. Sensory considerations: We offer flexible working arrangements, noise-cancelling headphones, and options for quieter workspaces when in the office.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Mid-Level Professional (Solutions Consultant)
2. Responsibilities: Independently deliver tailored product demonstrations to mid-market prospects, showcasing how our solution addresses their specific pain points and business goals.
3. Take ownership of Proof of Concept (PoC) engagements, which means scoping the trial, setting clear success criteria with the client, managing the technical setup, and presenting the final results to demonstrate tangible value.
4. Conduct in-depth technical discovery calls to uncover a client's existing infrastructure, integration needs, security posture, and key technical challenges, moving beyond just basic qualification questions.
5. Respond to technical sections of RFPs (Request for Proposals) and RFIs (Request for Information), authoring clear, concise, and compelling answers that highlight our product's strengths.
6. Collaborate closely with Account Executives on deal strategy, helping them identify technical blockers and opportunities, and providing technical guidance throughout the sales cycle.
7. Provide basic technical troubleshooting and support during PoCs, helping clients overcome initial hurdles and ensuring a smooth evaluation experience.
8. Actively contribute to our internal knowledge base by documenting common technical questions, successful PoC configurations, and competitive insights, helping your colleagues learn and grow.
9. Supervision: You'll have weekly check-ins with your manager to discuss pipeline, deal progress, and any blockers. For routine tasks like standard demos or common PoC setups, you'll work independently. For more complex or novel technical challenges, you're expected to flag them and get guidance.
10. Decision: You'll make routine technical decisions within the scope of a demo or PoC, such as choosing the best features to highlight or configuring a standard trial environment. Any decisions impacting budget, significant timeline changes, or requiring custom development will need to be escalated to your manager or the Account Executive. You'll recommend, but not approve, any spend above £2K for PoC resources.
11. Success: Success looks like consistently hitting your technical win rate targets, receiving positive feedback from both clients and Account Executives, and successfully converting a high percentage of your PoCs into closed deals. You'll be seen as a reliable and knowledgeable technical partner who can independently drive the technical aspects of mid-market sales cycles.

Decision-Making Authority

• Type: Product Feature Prioritisation (for demo)
• Entry: Follow pre-defined demo scripts; ask supervisor which features to highlight.
• Mid: Independently select and tailor features for specific client needs based on discovery; consult AE for alignment.
• Senior: Design custom demo narratives and identify new ways to showcase features; influence product team on demo-specific enhancements.
• Type: Proof of Concept (PoC) Scope
• Entry: Execute PoCs based on detailed plans provided by a senior team member; escalate any deviation.
• Mid: Define PoC success criteria and scope with client and AE; propose technical setup; escalate if custom development is needed.
• Senior: Architect complex PoC environments for enterprise clients; negotiate scope with technical leads; manage cross-functional resources.
• Type: Technical Objection Handling
• Entry: Refer to standard FAQ documents; escalate complex objections to supervisor or senior SC.
• Mid: Independently articulate technical differentiators and workarounds for common objections; know when to pull in a specialist.
• Senior: Anticipate and proactively address 'landmine' questions; develop new competitive positioning strategies; train team on advanced objection handling.
• Type: Internal Resource Allocation (e.g., product time)
• Entry: No authority; request help through supervisor.
• Mid: Request support from Product/Engineering for specific PoC issues; justify need to manager.
• Senior: Influence Product roadmap based on aggregate client feedback; negotiate engineering time for critical PoC support.

Competency Requirements

Foundation Skills (Transferable)

These are the fundamental abilities that underpin everything you'll do. They're not just 'nice-to-haves'; they're essential for navigating the complexities of technical sales and building strong relationships.

• Category: Communication & Presentation
• Skills: Active Listening: Truly hearing and understanding client needs and objections, not just waiting to speak.
• Technical Translation: Explaining complex technical concepts clearly to both technical and non-technical audiences, using analogies where helpful.
• Compelling Storytelling: Crafting a narrative around our product that connects features to client business outcomes.
• Live Demonstration: Delivering engaging and interactive product demos, handling unexpected issues with grace.
• Written Clarity: Producing clear, concise, and grammatically correct technical documentation, emails, and RFP responses.
• Category: Problem-Solving & Critical Thinking
• Skills: Diagnostic Thinking: Pinpointing the root cause of a client's technical challenge or an issue during a PoC.
• Solution Design: Architecting viable technical solutions using our product, often integrating with existing client systems.
• Troubleshooting: Methodically identifying and resolving technical issues during demos or PoCs.
• Analytical Reasoning: Evaluating technical requirements and constraints to propose the most effective approach.
• Adaptability: Quickly adjusting your approach and technical explanations based on new information or unexpected client questions.
• Category: Collaboration & Interpersonal
• Skills: Teamwork with AEs: Working seamlessly with your Account Executives, supporting their sales strategy and providing technical expertise.
• Client Relationship Building: Establishing rapport and trust with client technical teams and decision-makers.
• Internal Feedback Loop: Effectively communicating client needs and product gaps back to Product and Engineering teams.
• Conflict Resolution: Handling disagreements or challenging questions from clients or internal teams constructively.
• Mentorship (Informal): Guiding junior team members or new hires on best practices for demos and PoCs.
• Category: Organisation & Time Management
• Skills: Prioritisation: Managing multiple concurrent deals and PoCs, knowing which tasks are most critical.
• Detail Orientation: Catching small technical errors or inconsistencies before they impact a client or a deal.
• Documentation: Maintaining accurate records of client interactions, technical requirements, and PoC progress in the CRM.
• Planning & Preparation: Thoroughly preparing for demos, PoCs, and client meetings, anticipating potential questions or issues.
• Follow-up: Ensuring timely and relevant follow-up after client engagements.

Functional Skills (Role-Specific Technical)

These are the specific methodologies, technical knowledge, and tools you'll be using day-to-day to get the job done. This isn't just theory; it's about practical application.

Technical Competencies

• Skill: Technical Discovery & Qualification
• Desc: Moving beyond basic sales questions to really dig into a prospect's technical landscape: their current systems, integration challenges, security posture, and what a 'technical win' actually looks like for them. It's about asking the right questions to map their current state to their desired future state.
• Level: Intermediate
• Skill: Proof of Concept (PoC) / Proof of Value (PoV) Management
• Desc: The art of running a trial that genuinely proves our product's value. This means defining clear, measurable success criteria, managing the timeline, troubleshooting any hiccups, and presenting the results in a way that shows undeniable business impact.
• Level: Intermediate
• Skill: Solution Selling & Architecture
• Desc: Listening to a client's business problem and then designing a specific, often multi-product, solution. It's about connecting our technical features directly to their business outcomes, not just rattling off what the product does. You'll need to be able to sketch out architectures and explain data flows.
• Level: Intermediate
• Skill: Competitive Technical Differentiation
• Desc: Going beyond marketing fluff to explain *why* our technical approach or architecture is superior to a competitor's. This means understanding their APIs, data models, performance limitations, and being able to articulate our advantages clearly and confidently.
• Level: Intermediate
• Skill: RFP/RFI Response Strategy
• Desc: Treating an RFP not just as a checklist, but as a strategic document. This involves identifying 'wired' questions, influencing requirements where possible, and framing our solution as the most logical choice in your responses.
• Level: Intermediate
• Skill: Stakeholder Mapping (Technical Audience)
• Desc: Identifying and building rapport with the key technical players in a deal – the DevOps engineer, the security analyst, the enterprise architect – and understanding their individual motivations, concerns, and potential objections.
• Level: Intermediate

Digital Tools

• Tool: Salesforce (CRM)
• Level: Intermediate
• Usage: Logging all client interactions, updating technical notes on opportunities, managing PoC stages, and pulling standard reports to track your own activity and deal progress.
• Tool: Walnut / Consensus (Demo & Presentation)
• Level: Intermediate
• Usage: Building custom, interactive product demos from scratch, tailoring them to specific client use cases, and facilitating live, dynamic whiteboarding sessions during client calls.
• Tool: RFPIO / Loopio (RFP/Proposal)
• Level: Intermediate
• Usage: Authoring new, high-quality answers for technical RFP questions, identifying gaps in our existing knowledge base, and contributing new content to the library.
• Tool: Confluence / Notion (Collaboration & KB)
• Level: Intermediate
• Usage: Actively contributing to and updating our internal technical knowledge base, documenting successful PoC configurations, and leading technical discussions in team channels.
• Tool: AWS (EC2, S3, RDS) / Azure (VMs, Blob Storage) / GCP (Compute Engine)
• Level: Basic
• Usage: Navigating the console to spin up instances from pre-defined images or templates for PoC environments, and performing basic configuration changes as needed for client trials.
• Tool: Postman / Insomnia (API Testing)
• Level: Intermediate
• Usage: Writing new, complex API collections to demonstrate integration points, using variables and scripting to create dynamic demo workflows, and troubleshooting API connectivity issues during PoCs.

Industry Knowledge

• Area: Cloud Computing Fundamentals
• Desc: Understanding core cloud concepts (IaaS, PaaS, SaaS), common services (compute, storage, networking, databases), and the basic architectures of major cloud providers (AWS, Azure, GCP). You don't need to be a cloud architect, but you should speak the language.
• Area: Data Integration & APIs
• Desc: Knowledge of how different systems talk to each other, common integration patterns (REST, SOAP, webhooks), and how to demonstrate API capabilities effectively to clients.
• Area: Cyber Security Basics
• Desc: A foundational understanding of common security concerns (data privacy, encryption, access control, compliance standards) relevant to our product and how to address client security questions confidently.
• Area: Software Development Lifecycle (SDLC)
• Desc: Familiarity with how software is built, tested, and deployed, including concepts like Agile methodologies, version control, and CI/CD pipelines. This helps you relate to client engineering teams.

Regulatory Compliance Regulations

• Reg: GDPR (General Data Protection Regulation)
• Usage: Understanding the basic principles of data privacy and how our product helps clients remain compliant with GDPR, especially regarding data handling and storage. You'll need to answer basic client questions on this.
• Reg: Industry-Specific Data Standards (e.g., PCI DSS for payments, HIPAA for healthcare)
• Usage: Recognising when a client operates in a regulated industry and understanding the need to involve specialists for in-depth compliance discussions. You won't be the expert, but you'll know who to pull in.

Essential Prerequisites

• At least 2 years of experience in a technical role, ideally in pre-sales, technical support, or professional services, where you regularly interacted with external clients.
• A solid understanding of our core product's technical architecture and capabilities (or a similar complex B2B SaaS product).
• Demonstrated ability to deliver engaging technical presentations and product demonstrations to both technical and business audiences.
• Proven experience in managing technical trials or Proof of Concepts, from scoping to presenting results.
• Strong problem-solving skills with a track record of troubleshooting technical issues in a client-facing environment.
• Excellent written and verbal communication skills in English; you'll be writing a lot of emails and technical documents.

Career Pathway Context

These aren't just checkboxes; they're the foundational skills you'll need to hit the ground running. If you've been a technical support engineer who loves solving client problems, or a junior developer who enjoys explaining code, you've probably got a good chunk of these already. We're looking for someone who's ready to step up and own the technical 'win' in our sales cycle.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: Advanced Prompt Engineering & LLM Application
• Why: AI isn't just for drafting emails anymore. Competitors are already using Large Language Models (LLMs) to generate detailed technical proposals, summarise complex client requirements from call transcripts, and even suggest custom demo narratives in minutes. Solutions Consultants who master this will significantly outproduce their peers.
• Concepts: [{'concept_name': 'Context Windows & Token Limits', 'description': 'Understanding how much information an LLM can process at once and how to manage it for complex tasks.'}, {'concept_name': 'Temperature & Creativity Control', 'description': 'Knowing how to adjust LLM settings to get factual, precise outputs versus more creative, exploratory ideas for demos.'}, {'concept_name': 'Retrieval-Augmented Generation (RAG)', 'description': 'Learning how to connect LLMs to our internal knowledge base and client-specific documents for highly accurate and relevant responses.'}, {'concept_name': 'Output Validation & Hallucination Detection', 'description': "Developing a critical eye to verify AI-generated content for accuracy and identify when an LLM 'makes things up'."}, {'concept_name': 'Prompt Chaining for Complex Workflows', 'description': 'Breaking down multi-step tasks (like a full PoC report) into a series of AI prompts to automate the entire process.'}]
• Prepare: This month: Start using tools like ChatGPT or Claude for drafting internal communications, summarising meeting notes, and brainstorming demo ideas. Get comfortable with the basics.
• Next quarter: Experiment with a tool like GitHub Copilot or similar AI coding assistants to speed up any scripting or environment setup tasks.
• Month 4-6: Explore using LLM APIs (e.g., OpenAI, Anthropic) to build a simple internal tool for generating draft RFP answers based on our knowledge base.
• Month 7-9: Present your AI productivity gains to the team, sharing best practices and identifying new areas where AI can help.
• QuickWin: Today, use an LLM to draft your demo follow-up emails, summarise internal documentation, or outline your next presentation. It's immediate time-saving with minimal effort.
• Skill: Advanced Cloud Native Architectures & FinOps
• Why: More mid-market clients are moving beyond basic cloud usage to complex, cloud-native deployments. You'll need to understand not just *how* our product runs in the cloud, but *why* certain architectural choices are made, and how to discuss the financial implications (FinOps) of cloud usage with clients.
• Concepts: [{'concept_name': 'Containerisation (Docker, Kubernetes)', 'description': 'Understanding how applications are packaged and orchestrated in modern cloud environments.'}, {'concept_name': 'Serverless Computing (Lambda, Azure Functions)', 'description': 'Knowing the benefits and use cases of event-driven, serverless architectures.'}, {'concept_name': 'Infrastructure as Code (Terraform, CloudFormation)', 'description': 'Familiarity with how cloud environments are provisioned and managed programmatically.'}, {'concept_name': 'Cloud Security Best Practices', 'description': 'Deeper understanding of identity management, network security, and compliance in cloud environments.'}, {'concept_name': 'Cost Optimisation (FinOps Principles)', 'description': 'Discussing how our product helps clients manage and reduce their cloud spending.'}]
• Prepare: This month: Complete an Associate-level cloud certification (AWS Solutions Architect Associate or Azure Administrator Associate).
• Next quarter: Build a small, multi-service application using containers and deploy it to a cloud platform in your personal sandbox.
• Month 4-6: Research and document common FinOps challenges for mid-market clients and how our product helps address them.
• Month 7-9: Start incorporating discussions about cloud cost efficiency into your PoC presentations.
• QuickWin: Start following FinOps communities and cloud architecture blogs. Understand the basic terminology and common challenges today.

Advancing Technical Skills

• Skill: Deepening Product Expertise & Troubleshooting
• Why: As our product evolves and client use cases become more sophisticated, you'll need to move beyond surface-level understanding. Clients will expect you to troubleshoot more complex issues during PoCs and provide deeper architectural guidance.
• Concepts: [{'concept_name': 'Internal Product Architecture', 'description': "Understanding the 'how' and 'why' behind our product's design decisions, not just its features."}, {'concept_name': 'Advanced Debugging Techniques', 'description': 'Using logs, monitoring tools, and developer consoles to diagnose complex issues in real-time.'}, {'concept_name': 'Performance Optimisation', 'description': 'Advising clients on how to get the best performance out of our product in their specific environment.'}, {'concept_name': 'Edge Cases & Limitations', 'description': 'Knowing the boundaries of our product and how to manage client expectations around them.'}]
• Prepare: This month: Spend dedicated time with Product Managers or Senior Engineers to understand upcoming features and architectural decisions.
• Next quarter: Volunteer to run internal 'deep dive' sessions on specific product modules for your team.
• Month 4-6: Take on a more challenging PoC that requires extensive troubleshooting or custom scripting.
• Month 7-9: Document complex troubleshooting guides for the internal knowledge base.
• QuickWin: Regularly review our internal product documentation and release notes. Ask 'why' when a new feature is released, not just 'what'.

Education Requirements

• Level: Minimum
• Req: A Bachelor's degree in Computer Science, Engineering, Information Technology, or a closely related technical field.
• Alts: We're pragmatic. If you've got equivalent practical experience (e.g., 4+ years in a highly technical role like DevOps, Software Engineering, or Technical Support) and can demonstrate a strong grasp of the technical concepts, we're happy to consider that instead of a degree.
• Level: Preferred
• Req: A Master's degree in a relevant technical discipline.
• Alts: Not essential, but it shows a commitment to deep technical learning. Relevant industry certifications are often just as valuable, if not more so.

Experience Requirements

You'll need roughly 2-5 years of hands-on experience in a technical role where you regularly engaged with external clients. This could be in pre-sales, technical account management, professional services, or a highly client-facing technical support role. We're looking for someone who has a proven track record of understanding complex technical problems and effectively communicating solutions.

Preferred Certifications

• Cert: AWS Certified Solutions Architect – Associate
• Prod: Amazon Web Services (AWS)
• Usage: Shows a foundational understanding of cloud architecture, which is crucial for discussing our product's deployment and integration in client environments.
• Cert: Microsoft Certified: Azure Administrator Associate
• Prod: Microsoft Azure
• Usage: Similar to AWS, this demonstrates competence in a major cloud platform, allowing you to speak confidently about Azure-based client infrastructures.
• Cert: Certified Sales Engineer (CSE)
• Prod: Sales Engineering Alliance or similar
• Usage: While not as common, this shows a dedication to the craft of sales engineering and an understanding of best practices in the field.
• Cert: Product-Specific Certifications (e.g., Salesforce Administrator)
• Prod: Relevant software vendors
• Usage: If our product integrates heavily with a specific platform, having a certification in that platform shows you understand the ecosystem our clients operate in.

Recommended Activities

• Attending industry conferences and webinars focused on cloud computing, data integration, or our specific product domain.
• Participating in online courses or bootcamps to deepen your knowledge in areas like advanced scripting, specific cloud services, or API design.
• Engaging with technical communities online (e.g., Reddit, Stack Overflow, LinkedIn groups) to stay current on trends and solutions.
• Volunteering to lead internal 'lunch and learn' sessions on new product features or technical topics you've mastered.
• Regularly reviewing and contributing to our internal knowledge base and documentation.

Career Progression Pathways

Entry Paths to This Role

• Path: Associate Solutions Consultant (L1)
• Time: 1-2 years
• Path: Technical Support Engineer
• Time: 2-4 years
• Path: Professional Services Consultant
• Time: 2-3 years

Career Progression From This Role

• Pathway: Senior Solutions Consultant (L3)
• Time: 3-5 years in current role

Long Term Vision Potential Roles

• Title: Principal Solutions Consultant (L4)
• Time: 5-8 years from current role
• Title: Manager, Solutions Consulting (L5)
• Time: 7-10 years from current role
• Title: Product Manager
• Time: 6-9 years from current role

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.