Strong Junior .NET + Azure Developer (ConnectWise)

• Inventory and document
  • Work closely with your Team Lean and help to identify, categorize, and document security items
  • Help to identify Azure DevOps pipelines and other types of infrastructure that may also be impacted
• Help to develop proofs of concept for tackling the various authentication upgrade paths that are available
  • Work closely with and present findings to your Team Lead in order to make the best decision for refactoring
  • Maintain awareness of both local and deployed needs
• Implement the agreed upon solutions and patterns across multiple projects and repositories
  • Consider unit and integration tests
  • Work closely inside the development team to deploy and monitor releases

Skills/Experience

• Comfortable navigating and editing C# source code in .NET and TypeScript-based projects
• Good understanding of OOP/OOD principles
• Ability to work with minimal supervision and learn quickly
• Basic technical documentation skills

Bonus

• Experience in working with Azure cloud
• Experience in working with infrastructure-as-code definitions (Helm, Bicep, or Terraform)

Team size and members level?

This is an independent sub-team of 5 FTEs - Senior Developer\TL + 3 Senior Developers + Junior Developer.

Who works on our side, on customer’s side? (PM, PO, Architect, etc.)

You will be working directly with Director of Engineering on the Customer side.

How long do we work with this customer? How long the project lasts and what is the estimate period for duration, growth plans?

We've been working with this customer for 5+ years. However, this specific project is a short-term on - 4 - 6 months. After the project is finished, there is a chance to join the main development team for long-term. 

At what stage is the project? (requirements gathering, design, start of development, active dev., final stage of dev., maintenance and support)

There is already a working product, but there are a lot of enhancements planned to be implemented.

What development practices and approaches are used?

Mostly Kanban-based.

Where the system is hosted/deployed? Architecture type? Application types?

Hosted in Azure.

Development methodology? Releases frequency?

Usually weekly releases.

Describe communication channel (direct or through PM\TL; response speed, voice, chat, mail?)

You will communicate directly with Director of Engineering on the Customer side.

B-trips – possible, required? How often? Where?

Not expected.

Which professional growth possibilities can project give to the candidate?