CTC007608 - Technology architect - RFP GRICS
Secteur industriel: Éducation
Type d'emploi: Contract
Durée: Two years and Eleven months
Mode de travail: Remote
Description
Duration: 1st year 1540 hours, 2nd year 1540 hours, 3rd year 750 hours
Remote: mostly remote with some on-site requirements. The resource may need to be available for on-site meetings or workshops with GRICS staff during normal business hours upon request. The GRICS offices are near the Viau metro in Montreal east.
Language: We are looking for French speaking candidates. English is a nice to have
Introduction:
Join our progressive and innovative team at CTC as we embark on a strategic journey to secure a pivotal bid. We are seeking a seasoned Technology Architect with a wealth of experience and a comprehensive skill set in technology solution architecture to lead our technical efforts in response to an RFP. The Technology Architect will be responsible for formalizing the architecture of existing technology solutions and developing a roadmap for the future evolution of systems, considering technical issues and data exploitation objectives, as well as the operational mode of GRICS. If you are looking to make a significant impact and lead technology architecture solutions that drive success, we want you on our team!
The Technology Architect will be responsible for formalizing the architecture of existing technology solutions and developing a roadmap for the future evolution of systems, taking into account technical issues and data exploitation objectives, as well as the operational mode of GRICS.
He/she will have a thorough understanding of the architecture and issues associated with legacy solutions, as well as the benefits of adopting the technologies used by modern solutions. His/her job will be to understand and translate GRICS' business needs into viable solutions, and to define a roadmap to overcome the challenges of current solutions and capitalize on their strengths.
The primary focus will be on system alignment rather than system design, while requiring in-depth knowledge of their current state and evolutionary potential.
The Resource must be comfortable communicating, explaining and defending the strategies and directions they propose according to their discipline or mandate, as they may be required to communicate this information to various levels of management.
In particular, the Technology Architect is responsible for :
-
assessing the impact of potential technological solutions on business needs, determining the most appropriate solutions, and ensuring their feasibility and alignment with GRICS' overall architecture;
-
identify potential system and technology evolution issues by putting current and future needs into perspective;
-
anticipate the evolution of systems to facilitate data exploitation, taking into account the challenges posed by the obsolescence of legacy systems and the requirements of modern technologies;
-
document the current state of the GRICS systems ecosystem and chart its evolution by exploiting industry architecture frameworks to facilitate understanding of their architecture. In particular, this framework will be useful for understanding data sources and flows, links between systems, different user profiles and their interaction with systems, etc.
The main activities of the Technology Architect include :
-
participating in the realization of the strategic vision of software solutions, based on GRICS strategies and architecture principles;
-
contributing to the assessment of the maturity of software solutions, and participating in plans to ensure their sustainability, by recommending solutions to reduce technological debt or make a technological transition, as well as various follow-ups with teams;
-
support solution implementation efforts to ensure quality, security, confidentiality, performance and robustness;
-
act as a reference for teams as a technology solutions expert on technological orientations and the architecture of software solutions;
-
ensure optimal operation of best practices, such as continuous integration and deployment, automation and testing, etc;
-
guide the evolution of various software components, tools and libraries, in partnership with the platform team;
-
work with the architecture team and development teams to identify and improve interdependencies between software solutions and their potential integrations where applicable;
-
coach and train team members as required;
-
conduct technology watch, evaluate new technology components and define proofs of concept to improve the effectiveness of software solutions;
-
produce documents and diagrams essential to the understanding of software solutions in the sector;
-
propose recommendations to management on technological orientations, investments, risks and potential impacts of technologies used for all solutions.
The Technology Architect must meet the following minimum requirements:
-
have at least eight (8) active years of experience as a technology solution architecture consultant;
-
have carried out at least three (3) solution architecture mandates over the past five (5) years, with the aim of proposing system optimization and transformation scenarios;
-
have already worked with .NET development frameworks from 4.8 to 7;
-
previous experience in the Visual Studio and Git development environments.
The Technology Architect must have expertise in various spheres:
Technological sphere :
-
Microsoft Azure cloud services;
-
modern security protocols (OAuth2, OpenIDConnect);
-
industry frameworks such as Vue.js, React, Angular;
-
C/C++ and SQL programming languages;
-
automation tools, including Powershell and Azure CLI;
-
data programming languages (SQL, Python, R, Scala).
Architecture sphere :
-
classic multi-tier architectures (2-tier, 3-tier, n-tier);
-
web architectures such as Serverless, SPA PWA, API/GraphQL ;
-
distributed systems architectures (Service Bus, SOA, microservices);
-
deployment architectures such as monoliths, SOA and containers;
-
classic design patterns (singleton, factory, observer, repository, etc.) and "anti-patterns";
-
industry-recognized architectural practices of dependency, modularity and refactoring;
-
TOGAF and/or Zachmann architecture frameworks;
-
business domain-driven design (BDD), SOLID and object-oriented development principles;
-
data design patterns (ETL, Datamart, Star schema, OLAP, ODS, Pipeline).