Please mention DailyRemote when applying
AI Summary
Lead technical vendor engagement and configure OCS data models, product catalogues, and quota management APIs. Integrate OCS with Entitlement Servers and PCRF while managing production deployment and post-go-live operations.
- Own OCS vendor engagement: technical lead on all vendor integration discussions.
- Configure OCS data model: Plan ID, Account ID, Quota, Balance, Credit, Expiry lifecycle.
- Integrate OCS with Entitlement Server (profile update API — Diameter Ro/Gy).
- Build account provisioning flow: create OCS account on SIM activation event.
- Configure product catalogue: plans, bundles, add-ons, data passes.
- Implement quota management APIs: top-up, deduction, balance query.
- Implement credit balance and start/end (expiry) lifecycle management.
- Collaborate with other team members to integrate OCS as workflow activities.
- OCS ↔ PCRF integration: quota threshold → policy trigger via Diameter Gx.
- Billing reconciliation and reporting APIs.
- OCS production deploy, failover configuration, and load testing.
- Post go-live: OCS operations, new plan launches, quota adjustments, billing investigations.
Requirements
Must Have
- 4–6 years of telecom charging / billing engineering experience — a must.
- Required: OCS platform hands-on experience — a must.
- – Configuration, administration, and troubleshooting of an OCS — any vendor: Ericsson, Huawei, Nokia, Netcracker, Alepo, PortaOne, Aradial, opensource, etc.
- – Understanding of online charging architecture: CTF, OCF, Rating, Account Balance Management.
- Required: Diameter protocol — must be able to read and debug Diameter messages independently — a must.
- Ro interface (online charging) — credit control, used for OCS ↔ network element.
- – Gy interface — for OCS ↔ PGW/GGSN data charging.
- – Gx interface — for OCS/PCRF policy and charging rules.
- Product catalogue management: plans, bundles, quota pools, validity rules — a must.
- Balance management: top-up, consumption, threshold triggers, expiry — a must.
- REST API integration — consuming and building APIs for billing and account management — a must.
- SQL — querying and understanding OCS data models, billing databases — a must.
- Fluent English — a must.
Strong Advantage
- Experience with 3GPP charging standards (TS 32.240, 32.251, 32.299).
- MVNO or telecom operator experience — understanding of MVNO billing models.
- Entitlement Server / PCRF integration experience.
- Webbing server / OCS middleware configuration.
- Experience connecting OCS to a workflow engine or orchestration platform.
Nice to Have
- eSIM provisioning and charging — GSMA SGP.22, SM-DP+.
- Roaming charging: TAP/RAP, NRTRDE, inter-operator settlement.
- Python or Go — for scripting, test tooling, Temporal activity development.
- Kubernetes — understanding how OCS components are deployed.
About Webbing
Founded in early 2010, Webbing is a global data MVNO that delivers enterprise grade, global connectivity and IoT services across more than 200 countries and 600+ mobile carriers' networks. Webbing's secured network delivers network protection and web content intelligence.
Enterprise customers can manage, monitor, and optimize data usage in real-time with Webbing's powerful software platform. Gain visibility by application type and have the power to white list applications and limit non-business applications with the click of a button, saving money and improving compliance.
What we offer
- Fully remote
- An exciting and challenging greenfield platform with great skill and knowledge development opportunities.
- The opportunity to join a team of highly professional specialists in an international environment.
- The opportunity for professional development within a reputable international innovative and growing company.
Automatically Apply to the Best Remote Jobs
Stop the endless job search. Our AI finds and applies to the best jobs for you.
