About this role
Job Description
Mandate Overview
- 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
- Runtime environment: Azure, Windows Server, IIS, REST Web API, Kafka, Docker, Kubernetes, HELM, Git
- 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