Solution Architect

Job Summary

To define solution architecture based on business requirements and established standards in line with the defined future state enterprise IT landscape.

Key Responsibilities

1.

Define Target Architecture:

Design the future-state OM architecture**(often omnichannel)Align with enterprise standards (cloud, microservices, APIs, event-driven)Ensure scalability, resilience, and flexibility2.**Business–IT Alignment

Translate business goals (faster fulfillment, better CX, cost optimization) into architecture Work closely with: Business stakeholders (sales, supply chain, customer service)Product ownersIT delivery teams3.Assess Current Landscape

Evaluate existing OMS, ERP, WMS, CRM systems Identify gaps, redundancies, and technical debt Create as-is → to-be roadmap**4.**Technology Selection

Recommend OMS platforms (e.g., SAP S/4, Salesforce OMS, IBM Sterling, Manhattan)Decide on: Integration patterns (API-led, ESB, event streaming)Data architecture (MDM, real-time vs batch)Cloud strategy (AWS, Azure, GCP)5.Integration Architecture

Design integrations across: e Commerce platformsERPWarehouse/Logistics Payment systems Promote reusable APIs and canonical data models6.Governance & Standards

**Establish architecture principles, guardrails, and review boards Ensure compliance with security, data privacy, and enterprise policies7.**Transformation Roadmap

Define phased rollout (MVP → scale)Balance quick wins with long-term architecture vision Manage dependencies across program

Skill Requirements

Java/Kotlin microservices, cloud-native frameworks (Spring Boot / Quarkus)Architecture

Applications: Java/Kotlin microservices, cloud-native frameworks (Spring Boot / Quarkus)Integration: APIs, API gateway (kong), integration frameworks Eventing & Workflow: Messaging/streaming, sagas, long-running workflows (Temporal)Runtime: Docker / podman, Cloud Run, Kubernetes (GKE)Data: Relational (Postgres) , NoSQL (MongoDB, BigTable, Big Query), caching, data pipelines Platform: Containers, Kubernetes, cloud runtimes, IaCCross-Cutting: Security, observability, CI/CD, Dev Sec Op

Other Requirements

Java/Kotlin microservices, cloud-native frameworks (Spring Boot / Quarkus)Architecture

Applications: Java/Kotlin microservices, cloud-native frameworks (Spring Boot / Quarkus)Integration: APIs, API gateway (kong), integration frameworks Eventing & Workflow: Messaging/streaming, sagas, long-running workflows (Temporal)Runtime: Docker / podman, Cloud Run, Kubernetes (GKE)Data: Relational (Postgres) , NoSQL (MongoDB, BigTable, Big Query), caching, data pipelines Platform: Containers, Kubernetes, cloud runtimes, IaCCross-Cutting: Security, observability, CI/CD, Dev Sec Op