Stefanini is hiring a .NET Developer Sr. to design, develop, integrate, and maintain backend services for digital solutions and platforms in the telecommunications sector. The company describes itself as more than 30,000 "geniuses" connected from 41 countries, doing what they love and co-creating a better future.
The role is focused on keeping backend systems scalable, secure, high-performing, and traceable, with correct integration into both internal and external systems. In simple terms, this is a backend engineering job where the developer builds the plumbing that lets telecom products talk to each other reliably.
.NET Developer Sr. Role: Two Telecom Projects in One Job
The person hired will take part in two projects. Project A covers the integration of information and services in Tigo. Project B covers the migration of APIs from Azure to OnPremise.
These are two different kinds of work. The Tigo project is about connecting systems and data so services work together. The migration project is about moving APIs off a cloud setup (Azure) and onto on-premise infrastructure. Both require a developer who understands how backend services are built, connected, and kept stable.
Skills and Experience Required for the Backend Developer Job
Stefanini lists clear requirements for the position. The candidate should have 4 to 5 years of experience in backend services, with experience in integration, plus 2 years of experience with DevOps methodologies.
On the technical side, the stack is .NET — .NET Core in any version, preferably v6. The role also requires development and consumption of REST APIs.
- Backend experience: 4–5 years in backend services, including integration work
- DevOps: 2 years working with DevOps methodologies
- Stack: .NET / .NET Core, any version, preferably v6
- APIs: Development and consumption of REST APIs
- Projects: Tigo integration and Azure-to-OnPremise API migration
What This .NET Developer Sr. Job Means for Candidates
This is a senior-level opening, and the requirements match that label. Four to five years of backend work plus two years of DevOps experience is not an entry-level profile. The candidate needs to be comfortable with both building services and working within a DevOps culture.
The preference for .NET Core v6 gives a hint about the environment. It suggests the team works on a modern .NET stack, even though the posting says any version is acceptable. The REST API requirement is central, because both projects depend on services talking to each other — one through integration, the other through migration.
The two projects also tell candidates what kind of problems they will solve. Integration work in Tigo means connecting information and services across systems. The Azure-to-OnPremise migration means moving APIs while keeping performance, security, and traceability intact. Both are the kind of tasks that test a developer's understanding of how backend systems behave in production.
Our Take: A Clear, Focused Senior Backend Opening
In our view, this posting is straightforward and specific, which is a good sign. Stefanini states the experience level, the stack, the DevOps requirement, and the exact projects the hire will work on. Candidates know what they are applying for before they send a resume.
To put it plainly, the strongest fit here is a developer who has spent years building and integrating backend services and is not afraid of migration work. Moving APIs from Azure to OnPremise is rarely simple — it touches security, performance, and how internal and external systems connect. The Tigo integration project adds a second layer of complexity, because integration work depends on getting many systems to agree with each other.
For readers considering this role, the message is simple: highlight your integration experience and your DevOps background, and be ready to talk about REST APIs and .NET Core in detail. For Stefanini, the bar is set clearly — and that clarity is exactly what a senior job posting should have.
