Technical Solutions Architect

The Technical Solutions Architect will serve as the bridge between business requirements, solution design, development teams, infrastructure, and external service providers, ensuring that all solutions are technically sound, scalable, secure, and aligned to enterprise architecture standards.

Key Business Drivers

1. End-to-End Systems Integration Expertise

Our solutions increasingly require integration across multiple internal and external platforms, APIs, databases, and third-party services. A Technical Architect is required to:

• Identify optimal integration patterns and technologies.
• Ensure seamless communication between systems.
• Resolve complex integration challenges across distributed environments.
• Evaluate system dependencies and potential impacts before implementation.
• Define integration standards and best practices.

2. API and Service Architecture Leadership

The Technical Architect must possess strong expertise in:

• RESTful APIs
• SOAP Web Services
• Microservices Architecture
• Event-Driven Architecture
• Service Contracts and API Governance

This includes:

• Designing API specifications.
• Defining request and response structures.
• Mapping business requirements to HTTP methods (GET, POST, PUT, PATCH, DELETE).
• Designing and validating JSON and XML payloads.
• Ensuring compliance with API security standards.
• Knowledge of Swagger/OpenAPI specifications

Example Responsibilities

• Define API contracts and payload structures.
• Design error handling standards and response codes.
• Review authentication and authorization mechanisms.
• Ensure API versioning strategies are followed.
• Create technical specifications for consuming and exposing services.

3. Technical Validation and Service Testing

The architect should guide teams in validating integrations and service functionality using industry-standard tools such as:

• Postman
• SoapUI
• Swagger UI

Responsibilities include:

• Defining API test strategies.
• Validating request and response payloads.
• Troubleshooting integration failures.
• Analysing HTTP status codes and service logs.
• Supporting SIT, UAT, and Production readiness activities.

4. Database and Data Mapping Expertise

The Technical Architect should:

• Produce data mapping documents.
• Design database schemas.
• Define source-to-target mappings.

Examples include:

• API-to-database field mapping.
• Entity relationship modelling.
• Master data integration.
• Data transformation requirements.
• Legacy-to-modern platform migration mappings.

5. Solution Design and Requirement Translation

Technical Architect should assist in translating business requirements into detailed technical solutions.

This includes:

• Functional and technical requirement analysis.
• High-level and low-level solution design.
• Sequence diagrams and integration flows.
• Technical impact assessments.
• Non-functional requirement definition.
• Capacity and performance planning.

The architect will ensure requirements are technically feasible and align with enterprise standards before development begins.

Please Note:

As all iqbusiness roles require honesty in the handling of or access to cash, finances, financial systems, or confidential information; our recruitment process requires that the following background checks be completed: credit, criminal, ID, and qualification verification.

iqbusiness is committed to sustainable growth and transformation, we embrace diversity and employ previously disadvantaged individuals