Technical Solution Consultant

• As a Technical Solution Consultant, you’ll help make sure the integrations and custom development we sell are clearly defined, technically feasible and ready to deliver. You’ll work across Sales, Product, Engineering and Implementation to turn customer needs into accurate, decision-ready scope
• We’re looking for a Technical Solution Consultant to own the technical scoping of integrations and custom development for new and expanding customers
• You’ll make sure what we sell is clearly defined, deliverable and ready to hand over to Product and Engineering for build. You’ll translate complex technical discovery into requirements, assumptions, exclusions, acceptance criteria, responsibilities and statements of work that everyone can understand and act on
• This role is deliberately focused on pre-sales consulting, technical scoping and scope accountability. You will not build, engineer, configure or technically test integrations or custom development. Build and technical testing sit with Product and Engineering, while delivery sits with Implementation
• Your job is to make sure those teams receive a complete, accurate and decision-ready scope, and to remain the technical point of accountability for that scope throughout the project
• Let’s be clear from the start: this isn’t a role where you simply document customer requirements or pass questions between teams. You’ll challenge unclear requirements, identify delivery risk early, define what has and hasn’t been agreed and make sure technical commitments are realistic before a customer signs
• Leading Technical Discovery: Running discovery with prospects across HRIS, payroll, leave, time and attendance, EPOS, LMS, BI, middleware, identity and other third-party systems
• Mapping the Technical Landscape: Understanding systems of record, data flows, interfaces, dependencies, operational constraints and the customer’s wider technology environment
• Assessing Feasibility: Determining which requirements are standard, configurable, bespoke, out of scope or dependent on Product and Engineering delivery
• Defining Requirements: Creating integration and custom development requirements, field mappings, transformation rules, validation logic and exception-handling expectations to the level Engineering needs to estimate and build
• Clarifying Responsibilities: Defining customer responsibilities, vendor responsibilities, assumptions, exclusions, prerequisites and technical constraints
• Estimating Delivery: Providing directional or committed estimates, clearly stating the assumptions and confidence level behind each and validating them with Product and Engineering where required
• Supporting Commercial Scoping: Providing technical input for proposals, solution designs, commercial line items and statements of work
• Defining Acceptance: Establishing acceptance criteria, test responsibilities, delivery dependencies and cutover assumptions before contract signature
• Resolving Open Questions: Identifying unresolved technical questions and ensuring they are resolved, explicitly caveated or excluded from scope before signature
• Creating Handover Packs: Producing structured technical handover packs covering agreed scope, specifications, mappings, interface inventory, assumptions, exclusions, acceptance criteria, dependencies, risks and open questions
• Running Handover Sessions: Bringing Product, Engineering and Implementation together so delivery teams understand what was agreed and why
• Structuring Demand: Consolidating upcoming integration and custom development demand from Sales into clear Product and Engineering intake packages, including customer context, contractual status, reuse potential, requirements, dependencies, risks, estimated effort, urgency and the decision required
• Separating Customer Need From Product Capability: Distinguishing customer-specific requirements from reusable product capability
• Escalating Decisions: Taking Product and Engineering decisions forward with a clear recommendation and supporting evidence, then communicating agreed decisions back to Sales, Solution Consulting, Implementation and customers
• Owning Technical Accountability: Acting as the technical point of contact for the agreed scope throughout implementation
• Answering Scope Questions: Helping Implementation, Product, Engineering, customers and suppliers understand the requirements, intent and boundaries of what was agreed
• Assessing Scope Misses: Reviewing potential scope misses against the statement of work and handover pack and determining whether an issue is a scoping gap, change request, defect or out of scope
• Leading Rectification: Where a scope miss needs to be rectified, defining revised requirements, estimating the impact and taking the change through the appropriate route
• Representing Rotageek: Setting realistic expectations with customers and suppliers about what will change, when it will change and any associated cost
• Maintaining Change Control: Keeping a decision log and change record for the scope you own
• Creating Test Scripts: Working with Implementation and the customer to create test scripts and scenarios that validate delivered integrations or custom development against the agreed scope and acceptance criteria
• Covering Real-World Scenarios: Ensuring scripts consider happy paths, negative cases, duplicates, overlapping transactions, invalid data, retries, partial data and timing scenarios relevant to the scope
• Defining Test Ownership: Helping establish test data requirements and sign-off responsibilities with Implementation and the customer
• Documenting Defects: Reviewing test outcomes for items within your scope and documenting bugs and required changes clearly for Engineering, including expected behaviour, actual behaviour, evidence and reference to the agreed requirement
• Routing Issues Correctly: Distinguishing configuration, data-quality, integration, product and third-party issues so that each is routed to the right owner
• Supporting Ongoing Service: Contributing known issues and scope-related notes to the handover into Support and Customer Success
• Running Workshops: Facilitating technical discovery workshops, design reviews and scope-clarification sessions with prospects, customers and third-party suppliers
• Building Relationships: Working effectively with customer IT teams, payroll leads, HR teams, operations stakeholders and external system providers
• Setting Expectations: Explaining scope, dependencies, technical constraints and what will and will not be delivered
• Challenging Constructively: Questioning unclear or unrealistic requirements before they become commitments
• Creating Reusable Assets: Building and maintaining integration catalogues, partner playbooks, requirements templates, mapping packs, test script templates, SOW schedules and handover pack templates
• Using AI Responsibly: Applying AI and automation tools to improve requirements analysis, mapping, estimation, test script design and documentation
• Capturing Evidence: Recording recurring integration requirements, partner constraints and scope misses as structured evidence for Product and Engineering planning
• Improving the Process: Feeding lessons from scope misses back into templates and processes so future statements of work are more accurate
• Measuring Quality: Contributing to metrics focused on scope accuracy, rework, change requests and avoidable escalations
• What Success Looks Like in Your First Six Months:
• ✅ Integration and custom development feasibility, assumptions, dependencies, exclusions and responsibilities are understood before a customer signs
• 📝 Statements of work contain clear technical scope, acceptance criteria, responsibilities, prerequisites and delivery assumptions
• 🤝 Product, Engineering and Implementation inherit complete handover packs and can start build and delivery without reconstructing requirements
• 📦 Product and Engineering receive consolidated, decision-ready demand rather than fragmented customer requests
• 🔎 Scope misses are rare and, when they occur, are assessed, rectified and fed back into scoping practice quickly
• 🧪 Test scripts reflect the agreed scope, and bugs and required changes are documented clearly enough for Engineering to act on them first time
• 💬 Everyone involved understands what was agreed, who owns what and where the risks are
• 🔁 Recurring patterns become reusable scoping templates, playbooks and structured product requirements

Benefits

• Work from home, work from a coffee shop, work where suits you. We also provide global co-working membership if desired
• Unlimited holiday: 25 days holiday + 1 extra on your birthday (excl. bank holidays) — We believe plenty of holidays set us up for success so allow annual leave requests above this as part of our unlimited leave policy
• £250 WFH setup budget + all the hardware you need
• Enhanced parental leave
• Private medical insurance with Vitality and support for mental health

• Confidence can sometimes hold us back from applying for a job. But we’ll let you in on a secret: there’s no such thing as a ‘perfect’ candidate. Rotageek is a place where everyone can grow. So however you identify and whatever background you bring with you, please apply if this is a role that would make you excited to come into work every day

• 📞 Screening Call: Virtual via Google Meet with one of our team to learn more about your experience, your approach to technical discovery and what excites you about the role
• 💻 Competency Interview: You’ll meet the hiring manager and explore your experience with integrations, technical scoping, statements of work, estimation, customer conversations and cross-functional delivery
• 🏢 Final Stage Interview: You’ll meet members of the wider team and talk through how you would assess feasibility, create a technical handover and manage a scope question during implementation
• Ready to help us make technical commitments clear, feasible and deliverable? Apply Now!