Careers at QVCCS

The experts to the experts.

We are the specialist team that global systems integrators and large enterprises call when a Genesys Cloud CX solution has to work first time, at scale, connected to everything. If you are highly skilled in your discipline, read on. This page sets out what the role demands and how we assess it.

How to apply Who can apply

01 · What we deliver

Mission-critical contact centres, on a global stage

Every day, millions of people pick up a phone, open a chat or send a message to an organisation they rely on: their bank, their energy supplier, their airline, their insurer, their doctor's surgery, their retailer, their council. Behind each of those moments is a contact centre, and behind a growing share of the world's contact centres is Genesys Cloud CX, a Contact Centre as a Service platform delivered from the cloud. Quo Vadis CCS designs, builds, integrates, proves and supports those solutions, and nothing else. Genesys Cloud CX is our single, deliberate specialism.

Our work spans every industry vertical: financial services and insurance, retail and e-commerce, utilities, telecommunications, travel and hospitality, healthcare, the public sector, manufacturing and logistics. It spans every scale, from a focused local operation to Fortune 500 enterprises with tens of thousands of agents across continents. And it is never a platform in isolation. A modern contact centre is the meeting point of an organisation's telephony, its data, its people and, increasingly, its artificial intelligence.

So we connect Genesys Cloud CX to carriers and SIP providers, through Bring Your Own Carrier (BYOC) Cloud and Premises trunks, number porting and resilient failover. We write the interface contracts that let human agents and machine agents work from the same truth, drawn from the enterprise platforms that run global business: SAP, Oracle, Salesforce, Microsoft Dynamics 365, Zendesk and ServiceNow. And we build data actions into whatever else a client runs: their own databases and APIs, CRM, ERP, billing, order management, marketing, sales, finance and human resources systems. The range of possible integrations is wide, and every one has to be secure, tested and supportable.

Underneath it all sit the hyperscalers. Our solutions reach into Amazon Web Services, Google Cloud and Microsoft Azure for serverless functions, data platforms, identity, speech and generative AI services. A single customer conversation can touch a carrier, an Architect flow, a speech recogniser, a large language model, a CRM lookup, a routing decision, an agent desktop, a workforce management forecast and an analytics pipeline in a matter of seconds. When it works, nobody notices. Making sure it works is our profession.

Genesys Cloud CX at the centre of the enterprise Genesys Cloud CX sits in the centre as a royal blue tile, connected by lines to five groups of systems around it. On the left are telephony and SIP (carriers and SIP providers, BYOC Cloud and Premises, SIP trunks and the PSTN) and the hyperscalers (Amazon Web Services, Google Cloud and Microsoft Azure). On the right are enterprise platforms (SAP, Oracle, Salesforce, ServiceNow, Zendesk and Microsoft Dynamics 365) and client systems reached through data actions (CRM, ERP, billing, marketing, sales, finance, HR and databases). Below the centre are the agents: human agents, AI agents and bots, and agentic AI. A strip at the bottom states that every connection is an interface contract designed, built, tested and supported. WHAT WE DELIVER Genesys Cloud CX at the centre of the enterprise TELEPHONY & SIP Carriers & SIP providers BYOC Cloud & Premises SIP trunks · PSTN HYPERSCALERS Amazon Web Services Google Cloud Microsoft Azure ENTERPRISE PLATFORMS SAP Oracle Salesforce ServiceNow Zendesk Microsoft Dynamics 365 CLIENT SYSTEMS VIA DATA ACTIONS CRM ERP Billing Marketing Sales Finance HR Databases REST APIs called from flows and scripts GENESYS CLOUD CX Routing · Architect flows Integrations · data actions AGENTS Human agents AI agents & bots Agentic AI Every connection is an interface contract we design, build, test and support.
Genesys Cloud CX at the centre: telephony, enterprise platforms, client systems via data actions, hyperscalers and human and AI agents. Every connection is an interface we design, build, test and support.
Read this diagram as text

A hub diagram headed "Genesys Cloud CX at the centre of the enterprise": a central Genesys Cloud CX box is linked by two-way arrows to four groups of systems at the corners and an agents group below.

  1. The central box, "Genesys Cloud CX", lists "Routing · Architect flows" and "Integrations · data actions".
  2. Top left, linked by a two-way arrow: "Telephony & SIP" – "Carriers & SIP providers", "BYOC Cloud & Premises", "SIP trunks · PSTN".
  3. Bottom left, linked by a two-way arrow: "Hyperscalers" – "Amazon Web Services", "Google Cloud", "Microsoft Azure".
  4. Top right, linked by a two-way arrow: "Enterprise platforms" – SAP, Oracle, Salesforce, ServiceNow, Zendesk and Microsoft Dynamics 365.
  5. Bottom right, linked by a two-way arrow: "Client systems via data actions" – CRM, ERP, Billing, Marketing, Sales, Finance, HR and Databases, with the note "REST APIs called from flows and scripts".
  6. Directly below the centre, linked by a two-way arrow: "Agents" – "Human agents", "AI agents & bots", "Agentic AI".
  7. A strip at the bottom reads: "Every connection is an interface contract we design, build, test and support."

02 · Customer and employee experience

What CX and EX mean when you are the one building them

Customer experience (CX) is the sum of every impression an organisation leaves on the people it serves. In a contact centre it is very concrete: how long you waited, whether you had to repeat yourself, whether the bot understood you, whether the person you reached already knew who you were and why you were calling, and whether your problem was actually solved. Customer experience management is the discipline of designing those moments on purpose, measuring them rigorously and improving them continuously.

Employee experience (EX) is the other side of the same coin. A contact centre agent may handle dozens of conversations a shift, each one a stranger with a problem. Their experience is shaped by the tools on their screen, the knowledge at their fingertips, the accuracy of the schedule they were given, the AI that summarises a call so they do not have to, the coaching they receive and the pressure they are under. Poorly integrated systems create swivel-chair work, long silences and frustrated customers. Well-designed ones let people do the human part of the job well. You cannot deliver great CX with poor EX.

For a QVCCS professional, this is not theory. A requirement such as 'recognise the caller and route them to the right person' becomes an ANI lookup data action against the client's CRM, a fallback when the lookup times out, a privacy decision about what is said before the caller is verified, routing rules built on queues and skills, a screen pop on the agent's desktop, a wrap-up that writes back to the record, and the analytics to prove it worked. Each of those is a design decision, a build task, a test case and, one day, a support call. We own every one of them.

The work therefore demands an unusual combination of skills. You need to think like a customer, an agent, a contact centre manager, a security officer and an architect, sometimes in the same meeting. You need to understand telephony and SIP, REST APIs and OAuth, data models and dialogue design, service levels and workforce planning. And you need to explain all of it clearly to people who do not, and should not have to, understand any of it.

One interaction, many systems, two experiences Three horizontal lanes follow one contact. The top lane, customer experience, runs from the customer through a voice or digital channel, an IVR or bot built as an Architect flow, routing to the right queue and skills, being answered with context, to resolution. The middle lane shows the systems under each step: carrier and SIP, speech and NLU, a data action for a CRM lookup, routing, a CRM screen pop with knowledge, and wrap-up with a CRM update and analytics. The bottom lane, employee experience, runs from the schedule in workforce management through the desktop and knowledge, AI assist and summary, coaching and quality, to wellbeing and growth. CX AND EX One interaction, many systems, two experiences CUSTOMER EXPERIENCE Customer Voice or digitalchannel IVR or botArchitect flow Routed to the rightqueue and skills Answered,with context Resolved SYSTEMS Behind every step, an integration to design and test Carrier & SIP Speech / NLU Data action →CRM lookup Routing CRM screen popKnowledge Wrap-up →CRM update · analytics EMPLOYEE EXPERIENCE Schedule (WFM) Desktop & knowledge AI assist & summary Coaching & quality Wellbeing & growth Customer experience and employee experience are two sides of one design.
One customer contact traced across the systems behind it and the employee experience that delivers it. Every step is an integration to design and test.
Read this diagram as text

Three horizontal lanes follow one contact from left to right: customer experience at the top, the systems behind it in the middle, and employee experience at the bottom.

  1. The "Customer experience" lane runs in six linked steps: "Customer", then "Voice or digital channel", then "IVR or bot" (an "Architect flow"), then "Routed to the right queue and skills", then "Answered, with context", and finally "Resolved", which is highlighted.
  2. The "Systems" lane is introduced with "Behind every step, an integration to design and test", and dashed lines link each customer step after "Customer" to the systems below it.
  3. Under "Voice or digital channel" sits "Carrier & SIP".
  4. Under "IVR or bot" sit "Speech / NLU" and "Data action → CRM lookup".
  5. Under "Routed to the right queue and skills" sits "Routing".
  6. Under "Answered, with context" sits "CRM screen pop, Knowledge", and under "Resolved" sits "Wrap-up → CRM update · analytics".
  7. The "Employee experience" lane runs in five linked steps: "Schedule (WFM)", then "Desktop & knowledge", then "AI assist & summary", then "Coaching & quality", then "Wellbeing & growth".
  8. A strip at the bottom reads: "Customer experience and employee experience are two sides of one design."

03 · The standard

The experts to the experts: our standard

Global systems integrators trust QVCCS as a safe pair of technical hands on demanding Genesys Cloud CX programmes – in effect, the integrator to the integrators – and we deliver directly to enterprises as well. Think of the specialist surgical team a major hospital calls in for the hardest cases. Our clients are already experts. They come to us for the work they cannot afford to get wrong, and they judge us by that standard.

For every engagement we muster a multidisciplinary squad from our own bench of certified specialists, and we take collective responsibility for the outcome. Even when only one or two of us are visible to the client, we are backed by the whole practice: design authority, engineering standards, peer review and the specialist knowledge of every colleague. That only works if every member of the team is someone the rest of the team would stake their reputation on.

That is why we recruit from the top 5% of each talent pool. The people who do well here combine deep technical skill with careful professional conduct: clear writing, precise documentation, honest status reporting, composure on a remote go-live bridge at two in the morning and the humility to have their work peer-reviewed. Talent without discipline will not succeed here, and neither will discipline without talent.

If you recognise yourself in this description, we want to hear from you. If you are not sure yet, that is a sensible place to be: invest in the certifications, the projects and the evidence that will make the case for you, and apply when you can prove it. We would rather receive a smaller number of outstanding applications than a large number of hopeful ones.

04 · Humans, machines and agentic AI

The work is changing, and expectations are rising

For decades, contact centre technology connected customers to people. Today, a growing share of conversations is handled wholly or partly by machines: bots that answer questions, AI that listens and suggests, and now agentic AI that does not just answer but acts, checking an order, updating a record, booking a callback or changing a booking through the same enterprise systems a human agent would use. The line between a human agent and a machine agent is being redrawn every quarter.

That raises the bar for everyone who builds these systems. A bot that gives a wrong answer is embarrassing. An AI agent that takes a wrong action, on the wrong account, without an audit trail, is a serious incident. Every action a machine can take has to be designed as deliberately as an interface contract: what it may do, with what permissions, with what data, how it fails safely, when it hands over to a human with full context, and how every step is logged and tested. Responsible AI, data protection and security are engineering requirements here, not afterthoughts.

At the same time, the human role becomes more valuable, not less. When machines handle the routine, people handle the complex, the sensitive and the exceptional. Designing that partnership well, so that the customer never feels the seam between human and machine, is a demanding design challenge. Our AI specialists, developers, analysts and architects work on exactly that problem, for clients whose scale means getting it right matters.

Who does the work is changing A left-to-right spectrum of four columns, shaded from white to royal blue. A self-service bot answers FAQs and status questions; agentic AI acts – checking an order, updating a record or booking a callback through interface contracts, within guardrails; an AI-assisted human is augmented with suggestions, summaries and knowledge; and a human expert judges, bringing empathy to complex cases and exceptions. Arcs between neighbouring columns show each handoff carrying full context, and a dashed guard box under the agentic AI column lists permissions, an audit trail and tested failure paths. HUMAN AND MACHINE AGENTS Who does the work is changing HANDOFF WITH FULL CONTEXT HANDOFF WITH FULL CONTEXT HANDOFF WITH FULL CONTEXT SELF-SERVICE BOT Answers FAQs Status AGENTIC AI Acts Checks an order Updates a record Books a callback Through interface contracts, within guardrails AI-ASSISTED HUMAN Augments Suggests Summarises Finds knowledge HUMAN EXPERT Judges Empathy Complex cases Exceptions Permissions · audit trail · tested failure paths MORE AUTOMATED MORE HUMAN JUDGEMENT When an AI can act, every action must be designed, permissioned, tested and auditable.
From self-service bot to human expert: who does the work is changing, and every handoff must carry full context.
Read this diagram as text

Four columns arranged left to right along a spectrum from "More automated" to "More human judgement", linked by handoff arrows across the top.

  1. Column 1, "Self-service bot", with a bot icon: "Answers" – "FAQs" and "Status".
  2. Column 2, "Agentic AI", with a bot icon: "Acts" – "Checks an order", "Updates a record", "Books a callback", "Through interface contracts, within guardrails".
  3. A dashed box hangs below the Agentic AI column: "Permissions · audit trail · tested failure paths".
  4. Column 3, "AI-assisted human", with a person icon: "Augments" – "Suggests", "Summarises", "Finds knowledge".
  5. Column 4, "Human expert", with a person icon and highlighted: "Judges" – "Empathy", "Complex cases", "Exceptions".
  6. An arc labelled "Handoff with full context" runs from each column to the next: bot to agentic AI, agentic AI to AI-assisted human, and AI-assisted human to human expert.
  7. A double-headed axis under the columns runs from "More automated" on the left to "More human judgement" on the right.
  8. A note at the bottom reads: "When an AI can act, every action must be designed, permissioned, tested and auditable."

Disciplines we hire

Six disciplines. One bench. One standard.

Every role sits on our specialist bench and works in multidisciplinary squads. Whatever your discipline, you will work alongside architects, consultants, engineers, testers, trainers and support specialists, and you will be expected to understand their work as well as your own.

  • Developers

    Senior Developer · Software Developer

    Build integrations, data actions, middleware, custom applications and automation on the Genesys Cloud Platform API, SDKs and notifications, in TypeScript and JavaScript and with the cloud services of the hyperscalers. Version control, code review, automated testing and secure handling of credentials are non-negotiable.

    A week in the life
    • Monday: squad stand-up, then pick up a data action and its interface contract from the backlog.
    • Midweek: build and unit-test the integration against a sandbox org, and raise it for peer review.
    • Thursday: pair with a tester on the negative cases, and fix what review found.
    • Friday: document the change in the build book and demo it to the squad.
  • Engineers

    Senior Platform Practice Lead · Lead Engineer · IT Systems, Telecoms & SIP Engineer · Support Engineer

    Design and prove the telephony and platform foundations: BYOC Cloud and Premises trunks, carriers and SIP signalling, number plans, Edges, networks and resilience, then keep live services healthy with monitoring, incident response and root-cause analysis.

    A week in the life
    • Monday: review the weekend's trunk and Edge alarms and close out any open incidents.
    • Midweek: design a BYOC trunk change with the carrier, and write its test and rollback plan.
    • Thursday: run the change in a planned window, with a second engineer checking each step.
    • Friday: root-cause write-up for anything that misbehaved, and update the runbook.
  • Business analysts

    Senior Business Consultant / Business Analyst · Business Analyst

    Lead discovery and requirements workshops, map journeys and processes, write user stories with testable acceptance criteria, and keep a requirements traceability matrix that links every need to a design, a build and a test.

    A week in the life
    • Monday: run a discovery workshop with the client's operations team.
    • Midweek: turn the notes into user stories with testable acceptance criteria.
    • Thursday: walk the architect and testers through the stories and update the traceability matrix.
    • Friday: play back to the client what we heard, and agree what is in and out of scope.
  • Project and programme managers

    Programme Manager · Project Manager · Managed Services Lead · Managed Service Delivery Manager

    Plan and govern delivery across clients, integrator partners and third parties: critical paths, RAID logs, change control, cut-over planning and status reporting that tells the truth early.

    A week in the life
    • Monday: plan the week against the critical path, and update the RAID log.
    • Midweek: chair the integrator and client checkpoint, and chase third-party dependencies.
    • Thursday: walk through the cut-over plan with every party who has a task in it.
    • Friday: write a status report that tells the truth early, including what is at risk.
  • Architecture, testing and service

    Enterprise Solution Architect · Solution Architect · Systems Integration Tester · UAT Lead · Trainer · Technical Account Manager

    Architect solutions across the enterprise and own design authority, prove them through systems integration and user acceptance testing, train users and trainers, and act as the trusted technical adviser through the life of a service.

    A week in the life
    • Monday: design authority review of a proposed routing change.
    • Midweek: write test cases from the acceptance criteria, and run a systems integration test cycle.
    • Thursday: train a group of team leaders and capture what confused them.
    • Friday: service review with a managed services client: incidents, changes and what to improve next.
  • AI specialists

    Conversational and agentic AI

    Design and build bots, virtual agents and agentic AI that act through interface contracts: dialogue design, intents and knowledge, prompt and model design, guardrails, evaluation, safe handover to humans and auditable behaviour.

    A week in the life
    • Monday: review last week's bot transcripts for where callers got stuck.
    • Midweek: redesign a dialogue path and its guardrails, then test it against an evaluation set.
    • Thursday: agree the handover rules to human agents with the operations lead.
    • Friday: release the change with its evaluation results and a rollback plan.

A sample assessment exercise

A retailer wants callers who have waited more than three minutes in queue to be offered a callback instead of holding. The callback must keep the caller's place, respect the contact centre's opening hours, and record the reason for the call in the client's CRM. You have 90 minutes and a one-page brief.

What we ask for

  1. A short design note: how the call flows, where the decision is made and why.
  2. The interface contract for the CRM data action: inputs, outputs and failure cases.
  3. Five test cases, including at least two that should fail safely.
  4. The three risks you would raise with the client first, and what you would do about each.

The exercise is set for your discipline. A project manager, for example, plans and governs the same change rather than building it. We look for the same things as in the rest of the process: technical depth, the quality of your reasoning and evidence, clear writing, sound judgement and professional conduct.

Who can apply

Four requirements. No exceptions.

We can only consider applications from people who meet every one of the following requirements at the time they apply. Applications that do not meet them will not be accepted or assessed. We will tell you so, but we are unable to enter into further correspondence about them.

  1. 1
    Resident in the United KingdomYou must live in the United Kingdom. Every role is home-based within the UK.
  2. 2
    Right to live and work in the UKYou must already have the right to live, work and seek employment in the United Kingdom. We are unable to sponsor visas.
  3. 3
    UK National Insurance numberYou must hold a UK National Insurance number, or be eligible for one and provide it before you start.
  4. 4
    Full evidence of your skills and experienceEvery skill, qualification, certification and period of experience you claim must be evidenced. Claims without evidence are not assessed.

Applications that do not meet all four requirements will not be accepted.

We carry out the statutory right-to-work check, reference checks and pre-employment screening to the Baseline Personnel Security Standard (BPSS) before employment begins. Some client roles also require UK Security Check (SC) clearance; where they do, we will tell you.

Four requirements. No exceptions. Four numbered tiles on the left, each with a tick, list the requirements to apply: resident in the United Kingdom; the right to live and work in the UK; a UK National Insurance number, or eligibility for one, provided before you start; and full evidence of your skills and experience. All four lines flow into a gate. When all four are met, the gate leads to a royal blue tile reading application considered; a dashed branch from the gate leads to a warning tile stating that if any requirement is missing the application is not accepted. A strip at the bottom notes that right-to-work and pre-employment checks, BPSS and SC where a client requires it, follow at offer. WHO CAN APPLY Four requirements. No exceptions. 1 Resident in the United Kingdom 2 Right to live and work in the UK 3 UK National Insurance number or eligible – provided before you start 4 Full evidence of your skills and experience GATE All four met? YES Application considered All four requirements met and evidenced ANY MISSING ANY REQUIREMENT MISSING Application not accepted Right-to-work and pre-employment checks (BPSS, and SC where a client requires it) follow at offer.
Four requirements to apply: UK residence, the right to work, a National Insurance number and full evidence. Any requirement missing and the application is not accepted.
Read this diagram as text

Four numbered requirements on the left converge on a central gate, which branches to an accepted outcome on the right and a rejected outcome below it.

  1. Requirement 1, ticked: "Resident in the United Kingdom".
  2. Requirement 2, ticked: "Right to live and work in the UK".
  3. Requirement 3, ticked: "UK National Insurance number", "or eligible – provided before you start".
  4. Requirement 4, ticked: "Full evidence of your skills and experience".
  5. Lines from all four requirements merge into one arrow pointing into the "Gate", which asks "All four met?".
  6. The "Yes" arrow leads right to "Application considered", with the note "All four requirements met and evidenced".
  7. A dashed "Any missing" branch leads down and right to a warning box marked with a cross: "Any requirement missing – Application not accepted".
  8. A strip at the bottom reads: "Right-to-work and pre-employment checks (BPSS, and SC where a client requires it) follow at offer."

Qualifications

Two routes in, one standard

Graduate entry

A master's degree in software development, software engineering, computer science or a similar applied discipline, from a UK university, or an overseas master's degree confirmed comparable to a UK master's by a UK ENIC Statement of Comparability (include the statement). Include your transcript, your dissertation or final project title and summary, and evidence of any practical software you have built.

Experienced professionals

Full evidence of the nature and tenure of the skills and experience you are claiming, with dates and named roles. Show what you personally designed, built, tested or led, on which platforms and at what scale; list every certification with its verification ID or link; and be ready to name referees who can confirm it. Genesys Cloud CX experience is a strong advantage, but outstanding engineers, analysts and project professionals from adjacent fields are welcome to apply.

Two routes in, one standard Two panels side by side. On the left, the graduate route: a master's degree in software development, software engineering, computer science or a similar applied discipline, awarded by a UK university or an overseas master's confirmed comparable by UK ENIC. On the right, the experienced route: current, evidenced experience, shown as a checklist of roles and dates, projects and what you personally delivered, certifications with verification IDs, and referees who can confirm it. Both routes flow into one shared tile – the same assessment, the same standard – above the takeaway that claims without evidence are not assessed. TWO ROUTES IN One bar, two ways to clear it GRADUATE ROUTE Master's degree IN Software development · software engineering · computer science · a similar applied discipline AWARDED BY A UK university – or an overseas master's confirmed comparable by UK ENIC EXPERIENCED ROUTE Current, evidenced experience Roles and dates (tenure) Projects and what you personally delivered Certifications with verification IDs Referees who can confirm it The same assessment, the same standard Claims without evidence are not assessed.
Two routes in, a relevant master's degree or current, evidenced experience, both judged by the same assessment and the same standard.
Read this diagram as text

Two side-by-side panels headed "One bar, two ways to clear it", each with an arrow into one shared box below them.

  1. The left panel, "Graduate route", is headed "Master's degree".
  2. Under "In" it lists "Software development · software engineering · computer science · a similar applied discipline".
  3. Under "Awarded by" it reads "A UK university – or an overseas master's confirmed comparable by UK ENIC".
  4. The right panel, "Experienced route", is headed "Current, evidenced experience" and has four ticked items: "Roles and dates (tenure)", "Projects and what you personally delivered", "Certifications with verification IDs" and "Referees who can confirm it".
  5. An arrow from each panel leads into one shared box: "The same assessment, the same standard".
  6. A warning strip at the bottom, marked with a cross, reads: "Claims without evidence are not assessed."

The recruitment process

What happens after you apply

Our process is deliberately thorough, because the people who join us will be trusted with systems our clients depend on. Every applicant is assessed against the same five published criteria, set out below, and every interview follows a structured format so that each candidate is judged fairly and consistently. We aim to respond to every application within five business days of receiving it.

  1. 01ApplySend your CV or résumé, a covering note and your evidence to careers@qvccs.com.
  2. 02Evidence reviewWe review your application and evidence against the requirements and criteria on this page, and aim to respond within five business days.
  3. 03Screening interviewShortlisted applicants are invited to an initial interview, typically with the Managing Director or the Head of Professional Services.
  4. 04Discipline meetingNext, you meet a team leader from the discipline closest to your role, to learn about the life and workflow of a QVCCS team member and to explore your expertise in depth.
  5. 05Offer and checksA conditional offer follows, subject to the right-to-work check, references, BPSS screening and, where a client role requires it, SC clearance.
  6. 06StartOnboarding, your equipment and your first squad, and a probationary period of at least six months.

What we assess, at every stage

  1. Technical depthHow well you understand the platforms, protocols and practices of your discipline, and how deeply you have used them.
  2. Quality of evidenceWhether what you claim is specific, dated, verifiable and clearly your own work.
  3. Written communicationWhether your covering note, documents and answers are clear, precise and easy to act on.
  4. JudgementHow you weigh risk, choose between options, and know when to stop and ask.
  5. Professional conductHow you work with others, take review, keep commitments and handle sensitive information.

Working at QVCCS

Clear terms, high expectations

Our clients trust us with mission-critical systems: the contact centres that carry their customers' conversations, payments and personal data. That trust shapes how we work, and our employment contracts reflect it: they set out, fairly and in balance, what the work asks of you and what we give in return.

Working hours

The core working day is 9am to 6pm, Monday to Friday. Delivery keeps our clients' hours rather than our own, so the working day flexes around cut-overs, go-lives and major incidents.

On call and out of hours

At many stages of a project, and in live service, lead engineers may be on call or asked to work outside normal office hours, such as on a go-live bridge in the early morning. We plan it in advance wherever we can, share it fairly across the squad, and your contract sets out how it is recognised.

Travel

Our work is delivered remotely by default. Some engagements call for time at a client's site, anywhere in the world; when one does, we agree it with you in advance and your contract sets out how it is handled.

Work from home

All positions are home-based within the UK. You provide reliable, dependable, high-availability internet access and a suitable, private place to work. All client work is delivered remotely unless otherwise mutually agreed.

UK payroll

Every employee is paid through UK payroll in pounds sterling. PAYE income tax and National Insurance contributions are deducted and paid to HMRC in accordance with UK legislation.

Paid holiday

Paid holiday as set out in your contract, with time to rest planned around the delivery calendar.

Pension

Employer contributions to a workplace pension.

Equipment

We provide all the IT equipment your role requires, set up and secured to our standards.

Training and certification

We fund the training and certification exams your role and your pathway require, and the time to prepare for them.

Probation

Every new employee completes a probationary period of at least six months, during which we confirm together that the role and the standard are the right fit.

Certification

Engineers and developers achieve Genesys Cloud Certified Professional within their first six months, then continue through the full range of Genesys certifications. Project managers and other non-technical roles follow the recognised certifications of their own profession. Training continues after probation.

Backed by the practice

You will never work alone. Squads, peer review, design authority and the whole bench stand behind every piece of work you deliver.

Your first six months: onboarding, certification and delivery A horizontal track runs from day one to the probation review, which comes after a minimum of six months. Above the track, three swim lanes run the full length of the period: onboarding, covering IT equipment, standards and secure working from home; certification, with engineers and developers reaching Genesys Cloud Certified Professional within six months and project and other roles taking the recognised certifications of their own profession; and delivery, working inside a multidisciplinary squad, peer-reviewed and backed by the whole practice. The track ends at a royal milestone tile for the probation review, above the takeaway that certification is required in every role. YOUR FIRST SIX MONTHS Probation is where the standard is proved ONBOARDING IT equipment · standards · secure working from home CERTIFICATION Engineers and developers: Genesys Cloud Certified Professional within six months Project and other roles: the recognised certifications of their own profession DELIVERY Inside a multidisciplinary squad · peer-reviewed · backed by the whole practice DAY ONE MINIMUM SIX MONTHS MILESTONE Probation review After a minimum of six months Certification is required in every role, whatever skills you arrive with.
Onboarding, certification and delivery run side by side from day one to a probation review after a minimum of six months.
Read this diagram as text

A timeline headed "Probation is where the standard is proved", with three parallel lanes above a track that runs from day one to a probation review milestone on the right.

  1. The "Onboarding" lane spans the whole period and lists "IT equipment · standards · secure working from home".
  2. The "Certification" lane also spans the whole period: "Engineers and developers: Genesys Cloud Certified Professional within six months" and "Project and other roles: the recognised certifications of their own profession".
  3. The "Delivery" lane also spans the whole period: "Inside a multidisciplinary squad · peer-reviewed · backed by the whole practice".
  4. Below the lanes, a track arrow runs from "Day one" on the left to "Minimum six months" on the right.
  5. The arrow points into a "Milestone" box with a tick: "Probation review – After a minimum of six months".
  6. A strip at the bottom reads: "Certification is required in every role, whatever skills you arrive with."

Certification pathway

Certification never stops

Certification is part of the job in every role, and it does not end when probation does.

  1. 01First six monthsEngineers and developers achieve Genesys Cloud Certified Professional, alongside onboarding and their first squad work.
  2. 02After probationEngineers and developers continue through the full range of Genesys certifications: Developer, the Specialist certifications for their work, and AI Essentials.
  3. 03Every yearNew Genesys capabilities bring new training and certifications, allocated to your role as the platform and our clients' needs evolve.
  4. 04Non-technical rolesProject and programme managers, and other non-technical roles, follow an equivalent pathway in their own profession, such as PRINCE2, PMP and Agile certifications from accredited and recognised bodies.

Equal opportunities and inclusion

Judged on your work, and nothing else

We recruit, develop, reward and promote people on the evidence of their skills, their conduct and their work. We do not discriminate on the basis of age, disability, gender reassignment, marriage or civil partnership, pregnancy or maternity, race, religion or belief, sex or sexual orientation, and we treat every applicant and every colleague with the same respect.

Every applicant is assessed against the same published criteria, and every interview follows the same structure. Please leave your photograph, date of birth and marital status off your CV: we do not need them, and we do not use them.

If you need a reasonable adjustment at any stage, such as extra time, a different interview format, written questions in advance or assistive technology, tell us and we will work with you to put it in place. We welcome applicants who are neurodivergent, who have a disability or a long-term health condition, or who are returning to work after a career break.

Inside the team, we expect everyone to treat colleagues, clients and partners with respect. Harassment and bullying are not tolerated, and anyone can raise a concern in confidence, without fear of reprisal.

How to apply

Make your case, with evidence

Email your application to the address below. Put the discipline you are applying for in the subject line, for example 'Application – Software Developer'.

careers@qvccs.com

  • Your CV or résumé, with dates for every role
  • A short covering note: the discipline you are applying for and how you meet our criteria
  • Confirmation that you meet all four requirements under 'Who can apply'
  • Evidence of your qualifications (graduate route) or of the nature and tenure of your experience (experienced route)
  • Every certification you hold, with its verification ID or link
  • Links to work you can share, such as public repositories, publications or portfolios

Please do not send identity documents, passports, right-to-work documents or sensitive personal information with your application. We will ask for what we need, securely, at offer stage.

If you need a reasonable adjustment at any stage of the process, tell us in your application or at any time, and we will work with you to put it in place.

Beware of recruitment fraud. QVCCS will never ask an applicant for money, bank details or payment for training, equipment or checks, and we only recruit through careers@qvccs.com. If you receive a message claiming to be from us that does, please do not respond, and let us know.

Join our talent pool (optional). If we have no suitable role now, we can keep your application for up to 24 months and contact you only about relevant roles at QVCCS. To opt in, include this sentence in your email: 'I consent to QVCCS keeping my application in its talent pool for up to 24 months.' You can withdraw at any time by emailing careers@qvccs.com, and we will delete your application. If you do not opt in, we keep it for no more than 12 months.

We handle your application in line with our privacy policy, including how long we keep it and your rights. Read how we handle applications.

Last reviewed