System Architect- Sa Savings

The client is looking for a systems architect who works with all individual savings teams, above the designers.
They know the systems map, understand the business logic and make technical implementation decisions jointly with the solution architect: they run detailed impact analyses and raise concerns about a solution.
They do not code daily but read and debug code when a team is stuck and answer the questions of designers, many of whom are ramping up. Classic .NET, .NET Core and React are hardly negotiable.
The rest of the stack is assessed as a whole, and databases are interchangeable.
Two years of architecture is enough: the expectation is someone able to understand, explain and carry out architecture work, not an author of complex architectures.
Candidate sought: A .NET and React developer who moved into architecture about 2 years ago, has worked across legacy and cloud and can unblock a team by reading its code.
Collaborative and full of ideas, they challenge practices without imposing their own and learn quickly.
Requirements
Key Requirements:
Classic .NET, .NET Core, C# and React
Relational databases (SQL), MongoDB or equivalent
Concepts: cloud and on-premises, application lifecycle and DevOps, event-driven, scheduled processing
Technical implementation decisions, design, architecture and decomposition patterns
Reading and debugging code, technical support to designers
High-availability, high-volume systems
Engineering practices: object-oriented, SOLID, unit testing, TDD, BDD (to be validated)
Hybrid ecosystem, legacy and cloud
Positive leadership, collaboration, explaining complex concepts and ability to challenge
Asset:
Salesforce and MuleSoft (not blocking)
C4 modeling, Structurizr or equivalent
Appetite for AI (development tools, documentation)
Profile sought:
Hands-on Systems Architect who can read code, challenge teams, and influence technical decisions.
Strong experience with .NET and React in a hybrid environment (legacy and cloud).
Experience with SQL and/or MongoDB, as well as event-driven architecture.
Approximately 5 years of IT experience, including 2 years in an architecture role.
Profiles to avoid:
Developers with no architecture responsibilities.
Cloud-native profiles with no legacy/on-prem experience.
Solution Architects who have not worked with code recently.
#J-18808-Ljbffr