Technical Architect

The Technical Architect will work with developers and other architects to create low-level designs (LLDs). The role includes hands-on low-code/no-code development, and the role holder must also have an understanding of the C# code used in the core product. This role would be ideal for a developer looking to make the move into architecture.

Solutions must be cost-effective, scalable, and supportable, and aligned with Inchcapes principles, standards, and frameworks. The role-holder will:

• Provide low-level solution designs in response to high-level architectural designs.

• Acquire deep technical knowledge of Inchcapes key products and platforms.

• Contribute to low-code/no-code development of ancillary products.

• Provide guidance to peers on architectural and developmental best-practice.

• Collaboratively maintain and propose changes to the design, architecture and technology standards, principles, framework, and guardrails.

• Ensure architectural standards, governance, and principles are implemented effectively by auditing assigned IT programs, projects, products, and small works.

• Optimise deliverables for business value realisation, considering reusability of solutions, architectural building blocks, components, and designs.

• Review new and existing designs against standards and principles.

• Ensure relevant processes are standardised, resilient and tested to meet agreed business requirements.

• Assess new technologies for effectiveness and better cost-to-value for business problems.

Key accountabilities

• Work in collaboration with stakeholder groups, providing technical guidance and support to ensure the successful and cost-effective delivery of projects.

• Deliver low-level designs as part of defined overall solutions, aligning with architectural principles and best practices.

• Solution development based on existing technology stack to limit technological creep. The Inchcape ecosystem is mostly AWS, C# and React. Services are loosely coupled and integrated mainly through REST interfaces.

• Align designs with business goals and objectives.

• Consider future scalability and integration.

• Identify and assess new technology for potential adoption within ISS.

• Create feasibility studies and proofs of concept for given business problems.

• Management and governance of technology bricks and technical debt, for hardware and software used in production and non-production environments