Senior Backend Developer

Experience

6-10 years of relevant software engineering experience.

Role Overview

This is a senior, hands-on backend engineering role with responsibility for solution architecture, API integrations and technical leadership.

The successful candidate will be expected to spend approximately 60-70% of their time writing and reviewing production-quality backend code. This is not a purely managerial, project-management or non-coding architecture role.

The role will also require the candidate to explain the platform, technical progress, risks and delivery decisions to non-technical management teams in clear business language. They will support platform demonstrations, technical discovery and pre-onboarding discussions with prospective customers, partners and suppliers.

About SphereNet

Needs to be updated

Role Purpose The Senior Backend Engineering Lead will be the primary technical owner of SphereNet as backend platform, API integration framework, data architecture and engineering standards.

The role will be responsible for translating product requirements and telecom operating workflows into a secure, scalable and maintainable technical solution.

The successful candidate must be capable of:

- Building production-grade backend services.
- Designing scalable architecture and data models.
- Integrating external carrier and supplier APIs.
- Leading technical delivery and code quality.
- Identifying missing requirements and technical risks.
- Explaining technical matters clearly to management and customers.
- Representing SphereNet credibly in technical and pre-onboarding discussions.

Technical capability alone will not be sufficient. The candidate must understand the commercial and operational purpose of the platform and be able to explain how the technology supports customer outcomes.

Key Responsibilities

Backend Platform Development

- Design, develop and maintain backend services using C#, .NET 8 and ASP.NET Core.
- Build secure and maintainable services supporting customer management, product catalogue, pricing, quoting, orders, provisioning, ticketing, billing, service assurance and renewals.
- Design and implement REST APIs used by the frontend, external partners and suppliers.
- Implement validation, exception handling, audit logging and operational controls.
- Review and improve existing code, repositories and technical components where applicable.
- Ensure software is production-ready, tested, documented and maintained within company-controlled repositories.
- Troubleshoot complex application, integration, database and performance issues.

API and Carrier Integrations

- Design and build a reusable API integration framework.
- Integrate with telecom carriers, suppliers and third-party technology platforms.
- Implement webhooks, polling services, scheduled synchronisation and asynchronous processing.
- Map internal platform data to external carrier and supplier payloads.
- Handle authentication, rate limits, retries, timeouts, failed responses and error recovery.
- Implement idempotency controls to prevent duplicate orders and transactions.
- Build configurable carrier adapters rather than hard-coded point-to-point integrations.
- Support API, CSV and governed manual or semi-automated fallback workflows where external APIs are unavailable.
- Ensure carrier references, submissions, responses, status updates and failures are fully auditable.
- Maintain clear integration documentation covering endpoints, authentication, mapping, statuses, errors and dependencies.

Solution and Data Architecture
- Own SphereNet as backend, data and integration architecture.
- Translate product workflows into coherent technical services and components.
- Design for multi-tenant SaaS operation,



international expansion and configurable country-specific requirements.
- Prevent unnecessary hard-coding of customer, carrier or country-specific logic.
- Design customer and account structures supporting legal entities, operating accounts, billing profiles, sites, users and contacts.
- Ensure quotes, orders, services, invoices, tickets and renewals are linked through a coherent data model.
- Design workflow states, transitions, validation rules, ownership, exception paths and audit events.
- Create and maintain architecture diagrams and technical decision records.
- Balance rapid product delivery with security, scalability and long-term maintainability.

Security, Cloud and Operational Readiness

- Design secure authentication and authorisation using OAuth 2.0, OpenID Connect, JWT and role-based access controls.
- Apply least-privilege principles across internal users, customers, resellers, partners and suppliers.
- Ensure credentials, connection strings and API secrets are stored securely.
- Apply secure coding practices and protect APIs against common application and access-control vulnerabilities.
- Work with QA and DevOps resources to establish controlled development, UAT and production environments.
- Support Azure architecture, Docker, CI/CD pipelines and deployment automation.
- Implement structured logging, error monitoring and integration-health monitoring.
- Ensure releases can be deployed and rolled back through controlled processes.
- Maintain appropriate deployment, support and operational documentation.

Technical Leadership

- Act as the senior technical authority within the engineering team.
- Provide technical direction to frontend, QA, DevOps and future backend engineers.
- Conduct code reviews and enforce coding, security, testing and documentation standards.
- Break requirements into executable engineering tasks.
- Identify technical risks, dependencies and gaps before development begins.
- Mentor developers and improve engineering capability across the team.
- Support technical recruitment as the team expands.
- Escalate blockers and delivery risks promptly.
- Ensure the team delivers production-ready outcomes rather than demonstration-only functionality.

Management and Customer Communication
- Provide clear updates to non-technical management teams on platform progress, risks, dependencies and upcoming priorities.
- Translate technical activity into business outcomes, customer impact and commercial value.
- Explain complex architecture, defects and integration issues without unnecessary technical jargon.
- Clearly distinguish between functionality that is designed, under development, demonstrated, tested and production-ready.
- Present technical options and trade-offs in a way that supports management decision-making.
- Prepare and deliver platform demonstrations for internal stakeholders.
- Support prospective customer, partner and supplier presentations and technical discovery sessions.
- Explain SphereNets API, security, onboarding and integration capabilities in practical business terms.
- Answer technical questions during pre-onboarding discussions.
- Gather customer requirements and translate them into technical implications and recommendations.
- Avoid making unapproved delivery, technical or commercial commitments.




- Represent SphereNet professionally and credibly in external meetings.

Required Technical Skills Candidates must demonstrate strong commercial experience in:
- C# and .NET 8 or recent versions of .NET Core.
- ASP.NET Core Web API.
- RESTful API design and development.
- SQL Server and/or PostgreSQL.
- Entity Framework Core or an equivalent ORM.
- Database schema design and performance optimisation.
- Modular services or microservice architecture.
- Azure cloud services.
- Docker.
- Azure DevOps or equivalent CI/CD tooling.
- OAuth 2.0, OpenID Connect and JWT.
- Role-based access control.
- OpenAPI or Swagger.
- Git-based source control.
- Unit and integration testing.
- Secure coding, logging and production troubleshooting.

Required Integration Experience Candidates must have practical experience with several of the following:
- Complex third-party API integrations.
- Webhooks and event-driven processing.
- Message queues such as Azure Service Bus or RabbitMQ.
- Background workers and scheduled processing.
- Retry, timeout and circuit-breaker patterns.
- API rate-limit management.
- Idempotent transaction processing.
- Payload mapping and data transformation.
- External authentication and credential management.
- Failed-transaction recovery.
- Integration monitoring and reconciliation.

Desirable Experience Experience in the following areas would be advantageous:
- Telecom, connectivity, mobile, voice or managed services.
- Telecom order management or provisioning.
- B2B SaaS, reseller or marketplace platforms.
- Billing and invoicing.
- Product catalogue and pricing engines.
- Ticketing and service-management platforms.
- NOC, monitoring or service assurance.
- Workflow engines.
- Azure Functions, Service Bus, Key Vault and Application Insights.
- Infrastructure as code.
- AI or LLM service integration.

AI and machine-learning experience is desirable but is not a core requirement. Candidate Profile The successful candidate will:

- Remain highly capable and active in backend development.
- Take ownership rather than wait for detailed instructions.
- Identify missing requirements and risks early.
- Challenge weak assumptions constructively.
- Make pragmatic technical decisions based on evidence.
- Understand that a working demonstration is not the same as production-ready software.
- Communicate confidently with technical and non-technical stakeholders.
- Explain complex subjects accurately and in simple business language.
- Understand the wider customer and commercial purpose of the platform.
- Be comfortable supporting customer and partner meetings.
- Avoid unnecessary complexity and overengineering.
- Produce clear documentation as part of delivery.
- Remain accountable for outcomes rather than activity alone.

Initial 90-Day Outcomes During the first 90 days, the successful candidate will be expected to:

- Review all available requirements, workflows, code and technical assets.
- Produce a technical assessment identifying usable components, risks and gaps.
- Define the backend, API, database, security and integration architecture.
- Establish coding standards, repository controls and code-review processes.
- Define the core customer, account, authentication and RBAC models.
- Deliver the initial backend platform foundation.
- Implement working customer, product, quote and order APIs.
- Establish the reusable carrier and supplier integration framework.
- Deliver at least one working external integration pathway.
- Establish standards for validation, retries, error handling, logging and auditability.
- Provide transparent platform and delivery updates to management.
- Demonstrate working functionality in business terms.
- Support customer, partner or supplier discussions where required.

📌 Senior Backend Developer (Sahibzada Ajit Singh Nagar)
🏢 Sphere Global Solutions
📍 Sahibzada Ajit Singh Nagar