Skip to main content

66degrees

Backend Engineer (.NET), Contract

United States, Remote (Remote)midAdded today

About this role

66degrees seeks an experienced .NET backend engineer to design and develop scalable, cloud-native applications for AI and analytics projects. This 5+ month contract role requires deep .NET expertise, knowledge of Java or Python, and hands-on experience with modern cloud platforms and CI/CD practices.

What you'll do

  • Design, develop, and maintain scalable cloud-native .NET applications
  • Collaborate with cross-functional teams to define and deliver new features
  • Implement unit tests and follow Test-Driven Development practices
  • Set up and maintain CI/CD pipelines for deployment and integration
  • Participate in Agile ceremonies and code reviews using Git
  • Work with Azure, Google Cloud Platform, or AWS cloud services

What they're looking for

  • .NET Core and C# (4+ years)
  • Object-oriented programming and design patterns
  • Entity Framework and Microsoft SQL Server
  • Java or Python
  • CI/CD tools and Agile practices
  • Git, GitHub, or GitLab version control
  • Unit testing frameworks and TDD methodologies
  • Cloud platforms (Azure, GCP, or AWS)

Benefits

  • Remote position in the United States
  • 5+ month contract opportunity
  • Work on AI and analytics-focused projects
  • Collaborative, fast-paced team environment
  • Professional growth within an AI transformation company
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

66degrees

66degrees facilitates migrations to Google Workspace and provides technical support for implementation engagements. The company is hiring Google Workspace Deployment Engineers who work across Google and Microsoft environments to manage both small and large client migrations.

View all jobs at 66degrees

Likely interview questions

  • Walk us through your experience upgrading legacy .NET Framework applications to modern .NET—what challenges did you face?
  • Describe your approach to implementing CI/CD pipelines. Which tools have you used and why?