Client: Province of New Brunswick – RQ00382
We are seeking an experienced
Azure Integration Developer with strong expertise in
Microsoft Azure Integration Services, C#/.NET, Azure DevOps, CI/CD, scalable and fault-tolerant integration solutions, hybrid connectivity, secure Azure integrations, monitoring frameworks, HL7 v2x/FHIR, and Azure technical design documentation. The successful candidate will design, develop, document, install, configure, monitor, troubleshoot, and maintain integration solutions within the provincial
Microsoft Azure Integration Services environment while collaborating with business teams, project managers, project teams, architects, external teams, and the SNB Systems Integration Services team.
Role Snapshot
Client Province of New Brunswick
Office Location Fredericton, New Brunswick
Work Model Remote
Estimated Work Start Date October 19, 2026
Estimated Work End Date April 30, 2027
Business Days 137
Standard Hours 7.5 hours/day
Closing Date/Time September 22, 2026, at 10:30 AM
Work Location & Travel Requirements
Remote – Fredericton, New Brunswick
The location of work will be
Remote, but the proponents should be able to
travel to the Province of New Brunswick at least once a quarter throughout the project duration.
Key Responsibilities
The successful candidate must deliver the following, including but not limited to, in order to successfully complete the engagement.
- Azure Integration Solution Development
- Develop integration solutions that meet business requirements and goals, while maintaining information integrity across all systems and adhering to standards and best practices.
- Design, develop, document, install, and configure Integration solutions within the provincial integration platform (Microsoft Azure Integration Services) environment.
- Work with various stakeholders, including Business Teams, Project Managers, Project Teams, etc., to ensure successful solution implementation.
- Complete all assigned development and maintenance tasks, including:
- Service requests
- Releases
- Incidents
- Problems
- Documentation
- Other assigned development and maintenance activities
- Monitoring, Performance & Troubleshooting
- Monitor, performance-tune, and troubleshoot application and environment issues to meet and adhere to a high level of system availability.
- Work directly with external teams to clarify requirements and present solutions.
- Collaborate with architects and integration developers on design and development best practices.
- Ensure alignment with the SNB Systems Integration Services team.
- Documentation & Knowledge Transfer
- Produce solution documentation following SNB Systems Integration Services team documentation templates.
- Analyse existing integration solutions and update or create solution documentation.
- Review solutions developed with, and transfer knowledge to, the SNB Systems Integration Services team.
Mandatory Requirements
- A University degree in Computer Science or Information Technology is preferred, but an equivalent combination of education and experience may be considered.
- A minimum of five (5) years of IM/IT experience.
- A minimum of three (3) years’ experience developing integration solutions with Azure Integration Services, including but not limited to:
- Logic Apps
- Functions
- App Services
- Service Bus
- Containers
- API Management
- Azure Kubernetes Service
- On-premise data gateway
- A minimum of five (5) years’ experience developing solutions in C# and .NET.
- Excellent communication skills, written and oral, in English.
Scored Requirements
- Microsoft Azure Integration Services Development Experience
- Demonstrated integration solutions development experience with Microsoft Azure Integration Services, including:
- Logic Apps
- API Management
- Service Bus
- App Services
- Azure Functions
- Event Grid
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of reference engagements.
- Duration of referenced engagement.
- Specific Azure services used and scope of work done in each service.
- Amount of development experience, in months or years, with each Azure service.
- Was data validation part of the referenced engagements? If so, describe the technology used to validate the data, e.g. XSD, custom code.
- Was data transformation part of the referenced engagements? If so, describe the data transformation technology that was used, e.g.:
- XSLT
- Logic Apps Data Mapper
- Liquid templates
- Code
- Specific details of the solutions built, including any integration patterns, e.g.:
- Pub/Sub
- Request / Response
- Ordered delivery
- Size of the project team, including:
- Project Managers
- Business Analysts
- Developers
- QA Analysts
- Your specific role and responsibilities in each engagement.
- Azure DevOps, CI/CD & Deployment Frameworks
- Demonstrated hands-on experience with Microsoft Azure DevOps for CI/CD and Azure Deployment frameworks, such as:
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of referenced engagements.
- Projects leveraging Azure Integration Services, such as Logic Apps, Functions, Service Bus, etc., are preferred, but other solutions on Azure will be accepted.
- Highlight the Azure deployment frameworks that were used in the project.
- Identify which Azure services were part of the deployment process.
- Describe how the solution was promoted across different environments, such as:
- Dev
- Test
- Prod
- Other environments
- Duration of referenced engagements.
- Scalable & Fault-Tolerant Azure Integration Solutions
- Demonstrated experience in designing and developing scalable and fault tolerant Azure Integration solutions.
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of referenced engagements.
- Highlight what Azure services/capabilities were used for elastic scale to handle dynamic transaction volumes.
- Describe how the solution was designed for fault tolerance, e.g. multi-geo deployments.
- Describe if any application-level fault tolerant designs were implemented, e.g.:
- Handling of large messages
- Throttling
- Other fault-tolerance approaches
- Duration of referenced engagements.
- High Message Volumes & Large Message Sizes
- Demonstrated experience developing performant solutions that process high message volumes and large message sizes using Microsoft Azure Integration Services.
- Examples include:
- HL7 solutions
- EDI solutions
- Relevant Azure Integration Services include:
- Logic Apps
- API Management
- App Services
- Service Bus
- Azure Functions
- Event Grid
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of referenced engagements.
- Specific details of the solutions built, including:
- Message volumes
- Transaction types
- Transaction size
- Other relevant processing details
- Design patterns for handling high message volume and large messages.
- Highlight both:
- Azure native capabilities
- Application-level designs
- Specific Azure Integration Services products used.
- Duration of referenced engagements.
- Hybrid & Multi-Cloud Integration
- Demonstrated experience developing hybrid solutions that integrate with:
- On-premises databases
- Network shares
- Cloud-based solutions
- Experience using Microsoft Azure Integration Services, including:
- Logic Apps
- API Management
- Service Bus
- Azure Functions
- App Services
- Event Grid
- Experience with Azure Hybrid connectivity services, including:
- On-prem data gateway
- ExpressRoute
- Other applicable connectivity services
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of referenced engagements.
- Describe if the solution integrated with on-premises databases and network shares. If so, explain how hybrid connectivity to on-premises assets was implemented.
- Describe if the solution integrated with applications across multiple cloud providers, such as:
- If so, describe how multi-cloud connectivity was implemented.
- Describe the scope of the work that was done with each Azure Integration Services product.
- Duration of referenced engagements.
- Secure Azure Integration Solutions
- Demonstrated experience in designing and developing secure Azure integration solutions.
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of referenced engagements.
- How was secure communication between Azure services implemented?
- What was the approach for managing secrets and credentials for Azure integrations?
- Highlight any compliance review, including:
- Duration of referenced engagements.
- Azure Integration Monitoring Framework
- Demonstrated experience in designing and developing monitoring frameworks for interfaces built on Azure Integration Services, including:
- Logic Apps
- API Management
- Service Bus
- Azure Functions
- App Services
- Event Grid
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of referenced engagements.
- What was the end-to-end Azure monitoring framework used in the engagement?
- What tools were used for diagnostics and logging for Azure Integration Services, including:
- Logic Apps
- Service Bus
- Functions
- Other applicable Azure Integration Services
- Duration of referenced engagements.
- HL7 v2x and/or FHIR Development Experience
- Demonstrated development experience with HL7 v2x and/or FHIR.
- Experience building HL7 v2/FHIR solutions.
- Azure Integration Services experience is preferred, but experience with other platforms is acceptable.
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of referenced engagements.
- Was the solution built on Azure Integration Services or a different platform? Please specify the integration platform for the referenced engagements.
- Types of systems that were being integrated, including vendor and product.
- Specify HL7v2 message types and/or FHIR resources used.
- Duration of referenced engagements.
- Azure Technical Design Documentation
- Demonstrated experience creating Azure technical design documents describing solution components, including:
- Communication between Azure services and external systems
- Security protocols
- Database architecture
- Other relevant information
- Reference engagements that demonstrate experience and describe your role and responsibilities.
Reference Engagement Details
Clearly Describe The Following In The Response:
- Summary of referenced engagements.
- Describe the types of information/deliverables that were captured in the design document.
- Describe the review and approval process to finalize the design document.
- Describe the tools used to develop the design document, such as:
- Visio
- Word
- Other applicable tools
- Duration of referenced engagements.
Core Technical Skills
- Microsoft Azure Integration Services
- Azure Logic Apps
- Azure Functions
- Azure App Services
- Azure Service Bus
- Azure API Management
- Azure Event Grid
- Azure Kubernetes Service (AKS)
- Azure Containers
- On-premise Data Gateway
- Azure DevOps
- CI/CD
- ARM
- Bicep
- C#
- .NET
- REST/API integration
- Hybrid connectivity
- ExpressRoute
- On-premises database integration
- Network share integration
- Multi-cloud connectivity
- Scalable and fault-tolerant architectures
- High-volume message processing
- Large message processing
- HL7 v2x
- FHIR
- EDI
- XSD
- XSLT
- Logic Apps Data Mapper
- Liquid templates
- Pub/Sub
- Request/Response
- Ordered delivery
- Security and credential management
- HIPAA/GDPR compliance considerations
- Azure monitoring, diagnostics, and logging
- Technical solution design documentation
- Visio and Word
Key Collaboration Areas
The Successful Candidate Will Work With And Collaborate Across:
- Business Teams
- Project Managers
- Project Teams
- External teams
- Architects
- Integration developers
- SNB Systems Integration Services team
- Other stakeholders involved in solution implementation
Work Arrangement
Remote – New Brunswick
The location of work will be
Remote. However, the successful candidate should be able to
travel to the Province of New Brunswick at least once per quarter throughout the project duration.
- Office Location: Fredericton, New Brunswick
- Work Model: Remote
- Standard Hours: 7.5 hours per day
- Estimated Work Start Date: October 19, 2026
- Estimated Work End Date: April 30, 2027
- Business Days: 137
- Closing Date/Time: September 22, 2026, at 10:30 AM
- Travel: At least once per quarter to New Brunswick
Additional Requirements
The individual will be required to:
- Sign a non-disclosure agreement.
- Complete the Department’s Privacy Training prior to commencing the assignment.
How to Apply
If you are interested and your experience aligns with the requirements, please submit the following
mandatory documents to
[email protected] by
Tuesday, September 22, 2026, at 10:30 AM:
- Updated Resume in Word format – Mandatory
- Skills Matrix and References – Mandatory
- Expected Hourly Rate – Mandatory
- Visa Status – Mandatory
- LinkedIn ID – Mandatory
Without the mandatory documents, we cannot submit a candidate.
We make sure to screen each and every resume we receive in response to the positions shared, but due to heavy load, it is not possible for us to reply to each and every applicant. However, only shortlisted candidates with the required skills will be contacted.
If you are interested in learning more about this opportunity, please check it out on our career site.
For daily job updates, candidates can also join our
WhatsApp group using the invitation link provided by SMSS.
Email is the best way to reach us.
You have received this message either as a result of contacting our company to express interest in employment or as a result of posting your resume in a location that can be accessed by recruiters or HR specialists, which suggests an interest in being contacted about employment opportunities.
