Software Engineers

• Develop and maintain application components based on detailed technical and functional specifications.
• Write clean, scalable, and maintainable code in accordance with best practices and organizational coding standards.
• Conduct unit and integration testing to ensure software meets functional and performance requirements.
• Participate in code reviews to ensure quality and consistency.
• Collaborate with stakeholders to clarify requirements and resolve technical issues.
• Ensure adherence to project timelines and deliverables.
• Maintain documentation related to code, processes, and system configurations.
• Provide 90 days of post-implementation support for bug fixes and application stabilization.
• Provide training and transition to state software engineers after implementation of the system.

SPECIFIC DUTIES

• Analyze Attachment A – Scope and Attachment B – User Stories to fully understand application architecture, user workflows, and technical requirements.
• Implement application features using technologies as specified in Attachment A, Section 8.2 Technology Stack.
• Develop front-end components using technologies as specified in Attachment A, Section 8.2 Technology Stack.
• Integrate with backend systems, databases (e.g., SQL Server), and external APIs, if applicable.
• Complete unit and integration testing.
• Package and deploy application builds to development, test, and production environments.
• Adhere to version control practices using Azure DevOps.
• Participate in Agile/Scrum ceremonies (standups, sprint planning, retrospectives).
• Participate in requirements verification sessions.

QUALIFICATIONS

• Strong communication skills, both verbal and written, with the ability to convey technical concepts clearly.
• Professional and approachable demeanour, representing the project to stakeholders in a courteous, impartial, and credible manner.
• Proven ability to identify, document, and escalate technical issues, ensuring prompt and clear communication with project management.
• Skilled in developing recommendations and facilitating issue resolution in collaboration with state staff.
• Demonstrated ability to build and maintain effective working relationships with state technical teams and cross-functional project staff.
• Adaptable and dependable in high-demand project environments, able to manage multiple priorities and meet tight deadlines.
• Bachelor’s degree in computer science, Information Systems, or a related field (or equivalent practical experience).
• Minimum of 3 years of hands-on experience developing applications using C# and the .NET Framework (.NET 6/7 preferred).
• Experience with ASP.NET MVC and/or ASP.NET Core, building scalable and secure web applications.
• Proficient in SQL, with practical experience working with Microsoft SQL Server utilizing Entity Framework and/or ADO.NET.
• Experienced with Visual Studio as a development environment and Git-based version control systems for source code management.

The successful candidate should have the following knowledge and experience for this position:

• Experience with Azure services (App Services, Azure SQL, DevOps).
• Knowledge of front-end frameworks such as Angular, React, or Blazor.
• Familiarity with CI/CD pipelines.
• Experience working within Agile/Scrum methodologies.
• Experience working with government or enterprise-level applications.

Coding Styles, Standards, and DevOps

Code formatting

1. Naming conventions and code style
2. Proper async usage for all I/O operations
3. Spell checking
4. NuGet package vulnerability scanning
5. Treat all or specified warnings as errors
6. Prevent code with violations from being committed
7. Code reviews

    Local Development (Dev)

•  
  1. An .editioning file at the solution level enforces consistent formatting, naming conventions, and code style.
  2. Built-in Visual Studio analysers report warnings to developers, including improper async usage and general best practice violations.
  3. A spell-checking extension can be added to Visual Studio to catch typos in comments and string literals.

  Azure DevOps (CI/CD)

•  
  1. Vulnerability scanning is integrated into Visual Studio through the NuGet Package Manager.
  2. Warnings will be treated as errors and will prevent successful builds.
  3. Enforce a branching strategy and policies to ensure code is not committed directly to the main branch and that all code is validated and reviewed via pull requests.
  4. Use pull request build validation to enforce automated checks (build, tests, analysers).
  5. Validate unit tests as part of the CI pipeline to ensure code quality and prevent regressions