Job Overview We are seeking a high-caliber Senior Full-Stack Developer to join our critical Network OSS Service Delivery team. You will lead the design, development, and optimization of high-performance applications handling Network Inventory Systems and Provisioning Systems . In this role, you will build robust Spring Boot backend systems, create modern React interfaces, and implement resilient cloud-native architectures. You will maintain strict ownership of code quality by writing comprehensive unit tests to ensure minimal production bugs. Key Responsibilities Full-Stack OSS Development Design and build high-performance backend microservices using Spring Boot. Develop responsive, intuitive, and modern user interfaces utilizing React. Integrate complex systems through secure, optimized REST and SOAP APIs. Architect low-latency, high-performance database queries to process large-scale telecom datasets. Workflow & Core Orchestration Implement complex orchestration logic using workflow engines (e.g., Temporal, Camunda). Model end-to-end network provisioning and service delivery lifecycles into automated state machines. Optimize distributed system states to ensure high resilience and zero transaction loss. Cloud-Native & DevOps Engineering Deploy applications using containerized architectures including Docker and Kubernetes. Manage and scale cloud-native applications within the Microsoft Azure ecosystem. Collaborate with engineering teams to refine CI/CD pipeline automation and monitoring tools.
Pay:
$50.00 - $55.00 per hour Application Question(s): Can you describe a past project where you worked on Network Inventory Systems, Provisioning Systems, or Telecom OSS/BSS workflows? What specific network data models (e.g., equipment inventory, circuits, services) did you deal with, and what was the scale of the dataset What is your hands-on experience working with distributed workflow engines like Temporal, Camunda, or similar orchestration tools? Describe a challenging asynchronous workflow you implemented and how you ensured zero transaction loss. We process large-scale telecom datasets requiring low-latency queries. Can you share an experience where a backend service experienced performance degradation due to database bottlenecks? How did you diagnose and resolve it?