2024-0161 Backend Software Developer (.NET/C#, RabbitMQ) – FRI 30 Aug

  • Anywhere

Deadline Date: Friday 30 August 2024

Requirement: Medical Management Prototype – Backend Software Developer

Location: OFF-SITE

Note: Please refer to your Subcontract Agreement, article 6.4.1.a, which states “Off-Site Discount: 5% (this discount is applicable to all requirements, and applies when the assigned personnel are permitted to work Off-Site, such as at- home)”. Please be sure to price this discount in your overall price proposal when submitting bids against off-site RFQs

Required Start Date: No Later Than 7 October 2024

End Contract Date: 31 December 2024

Required Security Clearance: NO SECURITY CLEARANCE REQUIRED

Special Terms and Conditions: Non-disclosure agreement must be signed

1 INTRODUCTION

The NATO Information and Communication Agency (NCI Agency) is currently involved in the development of new capabilities for NATO as well as in the support of existing capabilities. In the light of these activities, the C2 Centre is looking for a backend software developer experienced in designing and implementing asynchronous communication between services with RabbitMQ.

More specifically, the work will support the development of messaging component of Medical Management Prototype application.

2 SCOPE OF WORK

Under the direction of the Service Delivery Manager and in close collaboration with the project team, the software developer will design and implement the messaging component of the Medical Management Prototype Application.

This includes the following activities:

Participate in requirements elicitation, analysis and design discussions,

Design and implement messaging component using RabbitMQ and integrate it with existing .NET web application,

Design and execute integration tests in collaboration with the project team,

Document implemented solution.

The development work will be carried out accessing remotely the NCIA engineering facilities.

The contractor will be part of a team and will work using an Agile and iterative approach. The content and scope of each sprint will be agreed during the sprint-planning meeting.

3 DELIVERABLES AND PAYMENT MILETONES

Each sprint is planned for a duration of 10 working days. At the end of each sprint, a detailed report of the activities conducted should be submitted.

The payment shall be dependent upon successful acceptance of the Delivery Acceptance Sheet (DAS) – (Annex B) including the EBA Receipt number

Invoices shall be accompanied with a Delivery Acceptance Sheet (Annex B) signed by the Contractor and project authority.

The following deliverables are expected in 2024 from the work on this statement of work:

Deliverable 01 Sprints for Medical Management Prototype message component development

Quantity: 4

Payment Milestones: After each sprint completion

Estimated Start Date: As soon as possible but not later than 07 October 2024

End Date: NLT 31 Dec 2024

2024 Option: 07th October until 31st December 2024

Deliverable 01 Sprints for Medical Management Prototype message component development

Quantity: Up to 2

Payment Milestones: After each sprint completion

Estimated Start Date: As soon as possible but not later than 07 October 2024

End Date: NLT 31 Dec 2024

2024 Option: 07th October until 31st December 2024

4 COORDINATION AND REPORTING

The contractor shall provide services off-site (remotely).

The contractor will be required to provide the services from a NATO country.

The contractor shall participate remotely in daily scrum meetings, sprint planning, sprint retrospectives and other on-line meetings using tools adopted by the team and according to service delivery manager’s instructions.

For each sprint to be considered as complete and payable, the contractor must report the outcome of their work during the sprint, first verbally during the sprint review meeting and then in writing within three (3) days after the sprint’s end date. The format of this report shall be a short email to the service delivery manager mentioning briefly the work held and the development achievements during the sprint.

5 SCHEDULE

This task order will be active immediately after signing of the contract by both parties.

The BASE period of performance is expected to be not later than 07th October 2024 and 31st of December 2024.

6 SECURITY

The security classification of the work will be up to NATO UNCLASSIFED. A NATO security clearance is not required.

7 CONSTRAINTS

All the documentation provided under this statement of work will be based on NCI Agency templates or agreed with project point of contact.

All scripts, documentation and required code will be stored under configuration management and/or in the provided NCI Agency tools.

8 PRACTICAL ARRANGEMENTS

The services related to the deliverables must be accomplished by ONE contractor.

The contractor may be required to travel to other sites within NATO for completing these tasks. Travel arrangements will be the responsibility of the contractor and the expenses will be reimbursed in accordance with Article 5.5 of AAS Framework Contract and within the limits of the NCIA Travel Directive.

9 QUALIFICATIONS

[See Requirements]

Requirements

9 QUALIFICATIONS

The consultancy support for this work requires a software developer with the following qualifications:

  • Minimum of 5 years of experience with software development in C# within multinational team using agile approach,
  • Minimum of 3 years of experience with developing .NET applications using RabbitMQ,
  • Practical experience with message queuing protocols such as MQTT and AMQP, message brokers, queues and exchanges,
  • Practical experience with configuring, monitoring and securing RabbitMQ deployment to production environments,
  • Experience with Microsoft Azure, especially Azure DevOps,
  • Excellent troubleshooting, problem solving, and analytical skills,
  • Ability to conduct all work in English