Key responsibilities
- Assume technical responsibility for enterprise applications and their integrations.
- Diagnose complex application failures, performance bottlenecks, and data-processing issues.
- Maintain Go and Node.js services, APIs and asynchronous workflows.
- Review inherited code, implement secure fixes and maintain meaningful regression tests.
- Manage reproducible builds, controlled releases, configuration and rollback procedures.
- Support Docker deployments, Ansible automation and production monitoring.
- Maintain runbooks and participate in incident response and an agreed-upon on-call rotation.
- Complete knowledge transfer and train backup engineers.
Application responsibilities and delivery
- Deliver usable frontend interfaces, backend services, APIs, and business workflows. Maintain JavaScript/TypeScript, Node.js/AdonisJS, and Go services, with hands-on maintenance and integration capability in Python and Java.
- Cover NUMAN number management and SIM provisioning; PromoSMS campaign management; SMS152 keyword and reply services; WFM quality evaluation; CCSM subscription workflows through IVR, SMS, and USSD.
- Cover WEBCC IVR151/IVR152 menus and dialplans, agent and supervisor tools, queues, call routing and transfers, recordings, wallboards and reporting. Maintain FreeSWITCH/SIP and Kannel/SMPP integrations; investigate relevant Lua/FreePBX components where deployed. Interpret SIP signaling, SDP/media and DTMF behaviors to diagnose call setup, routing, IVR and contact centre failures.
- Work with the technical lead on CAMELOCK CAMEL screening, GMLC location services and VLR event capture. Maintain relevant Go/SIGTRAN, Restcomm and Java/JBoss interfaces; share Cedar application interfaces with the Senior Data Platform Engineer.
- Own secure UI/API changes, tests, builds, CI/CD, configuration, monitoring, and rollback. Maintain Python, Java, Go, and Node.js/TypeScript middleware/adapters with API/protocol contracts, message mapping, validation, authentication, timeouts, retries, idempotency, error handling, observability, and version compatibility. Implement applicable TM Forum Open API resource/data models and interoperability tests. Test simulated endpoints, duplicate requests, and workflow recovery; use Docker, Ansible, and Temporal where deployed.
Cross-team integration and support
- Work closely with PS Core, Signaling/SPS, IN, HLR/HSS, Billing, OSS/BSS, IT Development, DWH & Mediation, BI, VAS, Network Information Security, IP/MPLS and IT System Administration Team (SAT).
- Build and maintain middleware/APIs and adapters with IT Development and the relevant platform owners.
- Cover subscriber, service-order and provisioning flows; VAS voice/messaging/subscription services; charging/billing interfaces; data contracts and status exchange.
- Agree authentication, approved access, endpoint connectivity, versions, field mapping and joint acceptance.
- Test retries, duplicate protection, rejected requests, reconciliation and rollback.
- Respect each team’s system ownership; agree change, incident and recovery responsibilities.
Key outcomes
- Maintainable web interfaces, APIs and telecom workflows across the assigned applications.
- Tested releases that preserve IVR, messaging and customer-service functions.
- Documented builds, rollback, and support procedures usable by a deputy engineer.
Allocation and service ownership
- The three engineers share application ownership across NUMAN, WEBCC, WFM, CCSM/CARE, PromoSMS and SMS152, with specialist work on CAMELOCK, GMLC and VLRInsert/VLRDump and shared Cedar interfaces. Allocate primary services by demonstrated strengths; retain cross-cover and code review. Each engineer must meet the core full-stack development and production-support requirements.
Working arrangements and performance
- Protect live services and data through approved access, tested changes, verified rollback and authorised production deployment or maintenance. Escalate unavailable access, unsupported dependencies and material risks; retain evidence of change and recovery outcomes.
- Own assigned deliverables, usable documentation and trained backup cover. Agree priorities, capacity, escalation, planned maintenance and an on-call rota with the reporting manager; no individual is expected to provide continuous coverage alone.
- Agree priorities through the reporting line. Track delivery quality, repeat incidents, change failures, tested recovery, documentation, and backup readiness. Infrastructure ownership remains with the assigned infrastructure team; coordination does not transfer reporting authority.