Solution Architect
Summary
Telecom Billing & BSS Solution Architect (10–15 yrs) based in Hyderabad who owns end-to-end charging, rating, billing and BSS architecture, leads legacy-to-cloud transformation, and defines API/integration architecture (TM Forum Open APIs, Kafka, microservices) across multi-vendor telecom programmes.
Telecom Billing & BSS Architect
Experience: 10–15 years
Location: Hyderabad
Function: Technology – IT Delivery
Role: Telecom Billing Solution Architect
Role Overview
We are looking for an experienced Telecom Billing Solution Architect with 10–15 years of strong experience in telecom billing, charging, rating and BSS transformation.
The role will be responsible for defining end-to-end billing and BSS architecture, translating business requirements into scalable technology solutions, and driving architecture across customer, product, order, charging, billing, payment, collections and revenue-management domains.
The candidate should have strong telecom domain knowledge and the ability to work across business, product, technology and implementation teams in a complex multi-vendor environment.
Key Responsibilities
1. Billing Architecture
- Own the end-to-end architecture for telecom charging, rating, billing and invoicing.
- Design solutions covering:
- Online and offline charging
- Usage rating and mediation
- Recurring, one-time and usage-based charging
- Discounts, promotions and bundles
- Convergent billing
- Prepaid/postpaid billing
- Account and bill-cycle management
- Payments and adjustments
- Collections and dunning
- Partner/interconnect billing and settlement
- Design scalable solutions capable of supporting high-volume transaction and billing workloads.
- Define billing architecture for B2C, B2B and enterprise customers.
2. End-to-End BSS Architecture Knowledge
Understanding of the complete Lead-to-Cash / Order-to-Cash journey across:
Customer → Product Catalogue → CPQ → Order Management → Provisioning → Usage → Mediation → Charging/Rating → Billing → Payment → Collections → Revenue Assurance
Ensure seamless integration between BSS and OSS platforms.
3. Product & Catalogue Architecture Knowledge
- Understanding for enterprise product catalogue and commercial offer management Architecture.
- Ensure consistent product, pricing and charging models across BSS platforms.
- Support rapid introduction of new products, bundles, promotions and monetisation models.
4. Transformation & Modernisation
- Define target-state architecture for modernising legacy billing platforms.
- Lead architecture for legacy-to-cloud/native billing transformation.
- Define migration strategies for customer, account, billing, usage, payment and historical data.
- Assess build-vs-buy and product/platform options.
- Identify opportunities to simplify legacy BSS landscapes and reduce integration complexity.
5. Integration & API Architecture
- Strong Understanding of architecture across CRM, CPQ, Product Catalogue, Order Management, Billing, Mediation, Payment, Collections, ERP and OSS systems.
- Strong understanding of REST APIs, event-driven architecture, Kafka/message brokers, ESB/API gateways and microservices.
- Apply TM Forum Open APIs where appropriate, particularly APIs around Product, Customer, Order and Billing management.
- Ensure loosely coupled and reusable integration architecture. TM Forum Open APIs are increasingly used to decouple BSS/OSS systems and support vendor-independent integration.
6. Architecture Governance
- Produce and govern:
- High-Level Designs
- Solution Architecture
- Integration Architecture
- Data flows
- Sequence diagrams
- API specifications
- Logical and physical architecture
- Establish architecture standards and design principles.
- Conduct architecture reviews and ensure adherence to enterprise technology standards.
- Identify technical risks, dependencies and architectural gaps.
7. TM Forum & Telecom Standards
Good understanding of:
- TM Forum eTOM
- TM Forum Open APIs
- Telecom BSS/OSS reference architectures
Particular familiarity with TMF APIs covering Product, Customer, Order and Billing is highly desirable.
8. Cloud & Modern Architecture
Experience with modern architecture principles including:
- Microservices
- API-first architecture
- Event-driven architecture
- Cloud-native platforms
- Containerisation
- Kubernetes
- CI/CD
- Distributed databases
- Real-time processing
- Observability and resiliency
Experience with AWS, Azure or GCP is desirable.
9. Stakeholder & Delivery Leadership
- Work closely with business, product, operations and technology stakeholders.
- Translate complex business requirements into practical architecture.
- Lead architecture discussions with vendors and implementation partners.
- Provide technical direction to development and implementation teams.
- Support solution estimation, technology selection and RFP/RFI evaluations.
- Present architecture and recommendations to senior management.
Mandatory Technical / Domain Skills
Telecom Billing
Strong hands-on/domain experience in:
- Rating
- Charging
- Billing
- Mediation
- Invoice generation
- Bill formatting
- Usage processing
- Account management
- Payments
- Collections
- Adjustments
- Dispute management
- Revenue assurance
- Partner/interconnect billing
BSS
Strong understanding of:
- CRM
- Product Catalogue
- CPQ
- Order Management
- Billing
- Charging
- Mediation
- Payment
- Collections
- Revenue Assurance
- Customer Care
- Enterprise/B2B BSS
The role should understand the business journey and system interactions, not merely the billing application itself. Contemporary BSS architecture roles commonly cover CRM, order management, billing, mediation, provisioning, collections, customer care and Lead-to-Cash.
Preferred Product Experience
Experience with one or more telecom BSS/billing platforms such as:
- Kenan
- Amdocs
- Netcracker
- Oracle BRM / Billing
- CSG
- Ericsson Charging/BSS
- Nokia BSS
- SAP BRIM
- Optiva
- Hansen
- Comarch
- Openet / Evolved Intelligence
- Other major telecom charging and billing platforms
Specific product experience is less important than strong telecom billing architecture and domain expertise.
Experience & Qualifications
- 10–15 years of overall IT/telecom experience.
- At least 7–10 years of significant experience in telecom billing/BSS.
- Proven experience in solution architecture for large telecom transformation programmes.
- Experience working with Tier-1/Tier-2 telecom operators is preferred.
- Bachelor's degree in Engineering, Computer Science, IT or equivalent.
- Strong experience working in Agile / SAFe / large transformation programmes.
Key Competencies
- Strong telecom domain expertise
- Deep billing and monetisation knowledge
- End-to-end BSS understanding
- Architecture and solution-design capability
- Strong analytical and problem-solving skills
- Excellent communication and stakeholder-management skills
- Ability to work across business and technology teams
- Strong vendor-management capability
- Ability to simplify complex architecture
- Ability to balance strategic architecture with practical implementation
Ideal Candidate Profile
The ideal candidate is not simply a billing application specialist.
They should be able to take a requirement such as:
"Introduce a new B2B telecom product with usage-based charging, discounts, recurring billing and partner settlement"
and independently define how the requirement flows through:
Product Catalogue → CPQ → Order Management → Customer/Account → Provisioning → Mediation → Rating → Charging → Billing → Invoice → Payment → Collections → Revenue Assurance
while defining the APIs, events, data flows, system responsibilities and integration architecture.
Key Success Measures
- Successful delivery of scalable telecom billing architecture.
- Reduction in billing defects and revenue leakage.
- Improved time-to-market for new products and tariff plans.
- Reduction of legacy platform dependencies.
- Improved integration standardisation and API reuse.
- Successful migration to modern/cloud-native BSS platforms.
- Architecture compliance across programmes and vendors.
- Improved billing performance, reliability and operational efficiency.
What they ask for
Required
- 10–15 years of overall IT/telecom experience
- At least 7–10 years of significant experience in telecom billing/BSS
- Proven experience in solution architecture for large telecom transformation programmes
- Bachelor's degree in Engineering, Computer Science, IT or equivalent
- Strong experience working in Agile / SAFe / large transformation programmes
- Hands-on/domain experience in telecom billing: rating, charging, mediation, invoicing, usage processing, payments, collections, revenue assurance
- Strong understanding of BSS domains: CRM, product catalogue, CPQ, order management, billing, charging, mediation, payment, collections, customer care
- Understanding of the end-to-end Lead-to-Cash / Order-to-Cash journey and BSS-OSS integration
- Strong understanding of REST APIs, event-driven architecture, Kafka/message brokers, ESB/API gateways and microservices
- Experience with modern architecture: microservices, API-first, cloud-native platforms, containerisation, Kubernetes, CI/CD, distributed databases, real-time processing
- Good understanding of TM Forum eTOM, TM Forum Open APIs and BSS/OSS reference architectures
Preferred
- Familiarity with TMF APIs covering Product, Customer, Order and Billing management
- Experience with AWS, Azure or GCP
- Experience with one or more telecom BSS/billing platforms (e.g. Kenan, Amdocs, Netcracker, Oracle BRM, CSG, Ericsson, Nokia BSS, SAP BRIM, Optiva, Hansen, Comarch, Openet)
- Experience working with Tier-1/Tier-2 telecom operators