Building reliable enterprise systems by day, and exploring AI-powered products by night.
I'm a Telecom BSS Engineer working on enterprise-scale systems across Product Catalogue, CRM, Order Management, Provisioning, Middleware, Billing, and Oracle databases.
My work sits at the intersection of complex business systems and technology—designing integrations, APIs, database solutions, and workflows that help large telecom platforms communicate reliably.
Outside enterprise systems, I build products and experiment with AI-powered developer tools, mobile applications, and modern full-stack architecture.
I enjoy solving problems where domain knowledge matters as much as code.
Experience and ongoing work across telecom domains:
- Product & Package Catalogue
- Customer Relationship Management (CRM)
- Order Management
- Telecom service provisioning and activation
- Middleware and enterprise API integrations
- CSG Kenan / telecom billing ecosystem
- Oracle SQL & PL/SQL
- Integration with network and provisioning systems
I'm particularly interested in understanding and designing modern, modular telecom architectures aligned with TM Forum principles.
Working with enterprise middleware that connects modern APIs with complex backend systems.
Client / CRM / Channel
│
▼
REST APIs
│
▼
Middleware Layer
│
├── Validation
├── Transformation
├── Orchestration
└── Error Handling
│
▼
Enterprise Backend Systems
Areas I work with:
- REST API design and integration
- JSON and XML payload transformation
- XSD-based contract understanding
- Middleware orchestration
- Enterprise transaction flows
- Oracle database integration
- Apache Tomcat
- BEA Tuxedo
- Solaris and Linux environments
Currently designing a modern Telecom Product & Package Catalogue Engine as a hands-on architecture and engineering project.
The goal is to explore how modern telecom BSS platforms model:
- Product Specifications
- Service Specifications
- Product Offerings
- Bundles and Add-ons
- Eligibility Rules
- Market Availability
- Catalogue Versioning
- Configurable Product Relationships
- CRM and Customer modelling
- Order Management integration
- Multi-tenant architecture
The architecture explores alignment with TM Forum information models while keeping the implementation practical for real-world telecom systems.
Product Catalogue
│
▼
Customer / CRM
│
▼
Order Management
│
▼
Product Inventory
│
▼
Service Provisioning
│
▼
Billing & Charging
The objective is simple: understand how a modern, composable Telecom BSS can be designed beyond traditional monolithic stacks.
AI-powered editor for SQL, PL/SQL, and domain-specific developer workflows.
An experimental full-stack product inspired by modern AI-assisted development environments.
- Context-aware AI assistance
- SQL & PL/SQL workflows
- Selection-based AI actions
- AI-powered code refinement
- Monaco Editor integration
- LLM pipeline orchestration
- Domain-aware prompting
Next.js · TypeScript · Monaco Editor · Google Genkit · Gemini API · Firebase · GCP
The idea came from working daily with SQL and enterprise systems and wanting better tools for domain-heavy development workflows.
A mobile-first product concept focused on solving a surprisingly complex problem:
Managing the finances of a wedding or large family event collaboratively.
Traditional expense trackers are designed for individuals. Weddings and major events involve:
- Multiple families
- Multiple contributors
- Shared and private expenses
- Different responsibilities
- Informal budgets
- Vendor coordination
- Payment tracking
The goal is to build an event finance and planning platform, starting with weddings.
- Collaborative event budgeting
- Family and group-based financial tracking
- Role-based access
- Shared and private expenses
- Budget vs actual tracking
- Vendor and payment management
- Event planning workflows
- AI-assisted budgeting guidance
- Future taxation and financial assistance possibilities
React Native · Expo · TypeScript · Supabase · PostgreSQL · SQLite · Offline-first architecture
Users & Families
│
▼
Event Workspace
│
┌──────┼───────────┐
▼ ▼ ▼
Budget Expenses Vendors
│ │ │
└──────┼───────────┘
▼
Financial Insights
│
▼
AI Planning Assistance
While weddings are the starting point, the larger idea is to create a reusable platform for collaborative financial planning for major life events.
Telecom BSS · Product Catalogue · CRM · Order Management · Provisioning · Billing · Middleware
Java · REST APIs · JSON · XML · XSD · Apache Tomcat · BEA Tuxedo
Oracle Database · SQL · PL/SQL · PostgreSQL
Linux · Solaris · Shell Scripting
TypeScript · Next.js · React · React Native · Expo · Node.js
LLM APIs · Google Genkit · Gemini · GCP · Firebase · Supabase
- Modern Telecom BSS architecture
- TM Forum information models and Open Digital Architecture
- CRM and Customer domain modelling
- Product Catalogue architecture
- Order orchestration
- API-first enterprise architecture
- Domain-Driven Design concepts
- AI-assisted developer tools
- Mobile product development
- Offline-first applications
- Cloud-native application architecture
Domain understanding before implementation.
A technically correct system can still fail if the underlying business model is wrong.
I enjoy working on problems involving:
- Clear domain boundaries
- Reliable integrations
- Well-designed API contracts
- Scalable data models
- Configurable systems instead of hard-coded logic
- Practical architecture over unnecessary complexity
- Products built around real user problems
Build things that solve real problems in domains you actually understand.
- Discussions around Telecom BSS architecture
- Product Catalogue, CRM, and Order Management design
- Middleware and enterprise API architecture
- Telecom billing systems
- AI-powered developer tooling
- Mobile and SaaS product ideas
- Open-source collaborations
- Building interesting technical products
| Platform | Link |
|---|---|
| Ashish Sharma | |
| ashishweasley@gmail.com | |
| 💻 GitHub | @ashish8official |
| 🧠 Catalyst Canvas | View Project |