What You’ll Actually Do as a Solution Architect Digital Platform:
Design the platform architecture — from API layers and event-driven patterns to identity, data flow, and multi-tenancy. You own the blueprint.
Evaluate and choose technology — whether it’s an API gateway, a message broker, or a WMS integration. You’ll run structured PoCs, not gut-feel decisions.
Set the technical direction — create architecture decision records (ADRs), define golden paths, and guide the team toward patterns that scale.
Bridge business and engineering — translate what product and leadership need into technical plans that engineers can rally behind.
Govern without slowing people down — establish lightweight review processes, reference architectures, and guardrails that help teams move faster, not slower.
Stay hands-on when it matters — jump into code reviews, prototype critical integrations, debug gnarly production issues. This isn’t an ivory tower role.
Mentor and grow the team — run architecture workshops, pair with engineers, and raise the technical bar across the org.
What You Should Bring:
Cloud-native platforms: Real experience designing and running production systems on AWS — not just certifications.
API and integration design: REST, GraphQL, event-driven architectures, message brokers (Kafka, RabbitMQ). You know when to use what
Containers and orchestration: Kubernetes, service mesh, and the ecosystem around it. You’ve operated this at scale.
Security fundamentals: OAuth2/OIDC, Zero Trust, API security, secrets management. Security is part of your design, not an afterthought.
DevOps and observability: CI/CD pipelines, GitOps workflows, and full-stack observability (logs, traces, metrics). You’ve built and maintained these
Nice to Have:
Experience with warehouse management systems (WMS), ERP, or supply chain platforms
Familiarity with architecture frameworks like TOGAF, C4 model, or ArchiMate