Lead Customer Solution Architect – Telecom BSS
Optiva, Europe +1
The role
As a Lead Customer Solution Architect you are accountable for the architecture of our largest and most complex customer programmes, and you help set the standard for how Qvantel architects work. You advise operator leadership on what to change and why, and you stay close enough to the build to know it is right. You will also lead the shift to AI-native delivery in our architect community, where designers and builders are increasingly the same person.
What you will do
- Lead end-to-end solution architecture for strategic BSS transformations, from scoping through go-live, and take responsibility for scope and change decisions.
- Work with senior customer leaders to set business priorities and guide them towards accepting the change a new solution brings.
- Act as design authority for your programmes: decide what is solved in the customer solution and what should be harvested back into the Qvantel product, together with Product and Enterprise Architecture.
- Define and improve how we work: requirement and design standards, reusable accelerators, and the AI skills, tooling and review practices our architects use from requirement to build.
- Stay hands-on: prototype, review designs and AI-generated code, and step in on the hardest problems.
- Lead pre-sales on strategic opportunities, including RFPs, executive presentations and solution positioning.
- Mentor and develop architects. Depending on the team, this includes line management of a small group of Solution Architects.
- Take commercial awareness into your advice, including effort, risk and financial impact for Qvantel and the customer.
What you need
- 10+ years in telecom BSS, with a track record of architecting large transformation programmes (convergent charging, billing, CRM, catalog, order management) for operators.
- Experience leading architects or senior engineers, formally or as a technical lead.
- Deep knowledge of cloud-native architecture, microservices, API-led and event-driven design, and TM Forum Open APIs, eTOM and SID.
- Strong cloud background (AWS, Azure or GCP) including Kubernetes-based deployments, security, resilience and observability for billing-critical workloads.
- Hands-on, daily use of AI coding assistants and agentic tools, and a clear view of where they help and where they need guardrails (spec-driven development, MCP, RAG, human review).
- Credibility with C-level and senior operator stakeholders; strong facilitation, negotiation and written communication.