Senior Technical Architect
Senior Technical Architect
Job Summary
Responsibilities
- Propose the technology stack (for example Java, React and a cloud platform) and agree it with the customer's solution architects.
- Write the solution and architecture design: data model, technology stack, high-level architecture diagram, and security and compliance design.
- Align the design with the customer's architecture guidelines and get it approved before development starts.
- Design the data model for product configuration data, including versioned weekly history.
- Design the import of flat-file exports from a product data system and the replication of the existing Excel and macro logic, together with the data engineer.
- Design authentication and authorization that is ready for single sign-on (for example Azure Entra ID) and role-based access.
- Agree non-functional targets (response time, availability, concurrent users, backup and recovery) and verify them.
- Review code for hard-coded credentials, coding standards and maintainability.
- Contribute to the implementation plan, risk register and cutover plan.
- Lead the future-phase assessment: per feature, technical feasibility within the delivered architecture, architectural implications, rough effort estimate, and key risks and dependencies.
- Support the administrator and technical documentation so that the customer's IT team can operate the application without the delivery team.
- During bridging, answer technical questions and support on-call work.
Success measures
- Design approved by the customer's architects before development starts.
- No hard-coded credentials agreed coding standards met, documentation sufficient for third-party maintenance.
- Future-phase assessment report accepted.
Must have
- Architecture of modern web applications (frontend and backend frameworks) and relational database design.
- Role-based access control, audit trail and change-history concepts, and data migration from Excel or flat files into a database.
- API design principles, Git and CI/CD, authentication and authorization frameworks.
- Feasibility assessments and rough effort estimation for future phases.
- Experience replacing spreadsheet-driven processes, including understanding Excel logic (VBA, formulas).
- Business-level English, written and spoken.
Nice to have
- Product data management (PDM/PLM) or product configuration domain knowledge.
- Cloud (Azure) experience and knowledge of messaging systems (for example MQ).
Key Responsibilities
Responsibilities
- Propose the technology stack (for example Java, React and a cloud platform) and agree it with the customer's solution architects.
- Write the solution and architecture design: data model, technology stack, high-level architecture diagram, and security and compliance design.
- Align the design with the customer's architecture guidelines and get it approved before development starts.
- Design the data model for product configuration data, including versioned weekly history.
- Design the import of flat-file exports from a product data system and the replication of the existing Excel and macro logic, together with the data engineer.
- Design authentication and authorization that is ready for single sign-on (for example Azure Entra ID) and role-based access.
- Agree non-functional targets (response time, availability, concurrent users, backup and recovery) and verify them.
- Review code for hard-coded credentials, coding standards and maintainability.
- Contribute to the implementation plan, risk register and cutover plan.
- Lead the future-phase assessment: per feature, technical feasibility within the delivered architecture, architectural implications, rough effort estimate, and key risks and dependencies.
- Support the administrator and technical documentation so that the customer's IT team can operate the application without the delivery team.
- During bridging, answer technical questions and support on-call work.
Success measures
- Design approved by the customer's architects before development starts.
- No hard-coded credentials agreed coding standards met, documentation sufficient for third-party maintenance.
- Future-phase assessment report accepted.
Must have
- Architecture of modern web applications (frontend and backend frameworks) and relational database design.
- Role-based access control, audit trail and change-history concepts, and data migration from Excel or flat files into a database.
- API design principles, Git and CI/CD, authentication and authorization frameworks.
- Feasibility assessments and rough effort estimation for future phases.
- Experience replacing spreadsheet-driven processes, including understanding Excel logic (VBA, formulas).
- Business-level English, written and spoken.
Nice to have
- Product data management (PDM/PLM) or product configuration domain knowledge.
- Cloud (Azure) experience and knowledge of messaging systems (for example MQ).
Skill Requirements
Responsibilities
- Propose the technology stack (for example Java, React and a cloud platform) and agree it with the customer's solution architects.
- Write the solution and architecture design: data model, technology stack, high-level architecture diagram, and security and compliance design.
- Align the design with the customer's architecture guidelines and get it approved before development starts.
- Design the data model for product configuration data, including versioned weekly history.
- Design the import of flat-file exports from a product data system and the replication of the existing Excel and macro logic, together with the data engineer.
- Design authentication and authorization that is ready for single sign-on (for example Azure Entra ID) and role-based access.
- Agree non-functional targets (response time, availability, concurrent users, backup and recovery) and verify them.
- Review code for hard-coded credentials, coding standards and maintainability.
- Contribute to the implementation plan, risk register and cutover plan.
- Lead the future-phase assessment: per feature, technical feasibility within the delivered architecture, architectural implications, rough effort estimate, and key risks and dependencies.
- Support the administrator and technical documentation so that the customer's IT team can operate the application without the delivery team.
- During bridging, answer technical questions and support on-call work.
Success measures
- Design approved by the customer's architects before development starts.
- No hard-coded credentials agreed coding standards met, documentation sufficient for third-party maintenance.
- Future-phase assessment report accepted.
Must have
- Architecture of modern web applications (frontend and backend frameworks) and relational database design.
- Role-based access control, audit trail and change-history concepts, and data migration from Excel or flat files into a database.
- API design principles, Git and CI/CD, authentication and authorization frameworks.
- Feasibility assessments and rough effort estimation for future phases.
- Experience replacing spreadsheet-driven processes, including understanding Excel logic (VBA, formulas).
- Business-level English, written and spoken.
Nice to have
- Product data management (PDM/PLM) or product configuration domain knowledge.
- Cloud (Azure) experience and knowledge of messaging systems (for example MQ).