1. Introduction / Introducción
This Statement of Architecture Services (SoAS) defines the scope, responsibilities, deliverables, and expectations for an outsourced Architecture Service, supporting the Demand Shaping function within Commercial IT and Consumer IT, with additional capability to execute end‑to‑end development of technological solutions —ensuring architectural excellence at market level.
2. Purpose of the Service / Propósito del Servicio
The objective of this service is to provide end‑to‑end solution and integration architecture capabilities during demand shaping and early delivery phases, ensuring that Commercial IT and Consumer IT initiatives are:
· Technically feasible and cost‑effective
· Scalable, secure, and resilient
· Aligned with enterprise and regional architecture standards
· Designed for reuse and integration with existing platforms
The service acts as an embedded execution capability, enabling high‑quality solution definition prior to project approval and delivery.
The service must have the capability to develop and implement the solutions previously designed and approved.
This role is not a governance position and not a regional solution design role. It is an execution-oriented architecture role embedded in the market IT delivery context, accountable for translating local business needs into compliant solutions, applying regional standards locally, and actively enabling the transition from local solutions toward regional or centrally delivered platforms when applicable.
2.1 Key Purposes / Propósitos Clave
- Strengthen technical depth and architectural quality at market level.
- Ensure alignment with Tech principles and IT guardrails.
- Enable platform-first adoption and avoid local fragmentation.
- Support the transition from local to regional/central platforms.
- Provide end‑to‑end architecture for both B2B and B2C market capabilities.
This role is not governance position and not regional solution design role—it is execution-oriented architecture role embedded in the market IT delivery context.
3. Service Scope / Alcance del ServicioEnglish
The Architecture Service applies to Commercial (B2B) IT initiatives and Consumer (B2C) IT initiatives. The scope includes:
· Demand shaping and technical feasibility analysis
· High‑level and detailed solution architecture definition
· Integration architecture (API‑first, event‑driven where applicable)
· Alignment with regional and global platforms (e.g., PWST, SAP, Salesforce, MuleSoft, AWS)
· Architecture due diligence for new demands and material changes
· Architecture documentation required for approval and delivery readiness
The service shall develop and implement the technological solutions defined within the scope mentioned above.
Español
El Servicio de Arquitectura aplica a iniciativas de IT Comercial (B2B) e iniciativas de IT Consumer (B2C). El alcance incluye:
· Demand shaping y análisis de factibilidad técnica
· Definición de arquitectura de solución de alto nivel y detallada
· Arquitectura de integración (API‑first, orientada a eventos cuando aplique)
· Alineación con plataformas regionales y globales (ej. PWST, SAP, Salesforce, MuleSoft, AWS)
· Due diligence arquitectónica para nuevas demandas y cambios relevantes
· Documentación arquitectónica requerida para aprobación y preparación del delivery
El servicio deberá desarrollar e implementar las soluciones tecnológicas que se definan en el alcance antes mencionado.
3.1. Scope of Responsibility / Alcance de Responsabilidades
The service covers all Consumer (B2C) and Commercial (B2B) capabilities, and local integration needs within one market, including but not limited to:
3.1.1 Consumer (B2C) Market Capabilities / Capacidades B2C del Mercado
Market consumer digital solutions, local implementations or extensions of central platforms such as eCommerce, and marketspecific consumer applications required for local operations or regulatory needs.
3.1.2 Commercial (B2B) Market Capabilities / Capacidades B2B del Mercado
Market commercial solutions supporting sales, trade, distributor, and execution processes, including local integrations and extensions of central platforms such as digital retailer engagement and order management systems.
3.1.3 Local Integrations & Data Flows / Integraciones y Flujos de Datos Locales
Interfaces and data exchanges between local B2B and B2C solutions and between local solutions and central platforms, applying approved API and data patterns to support end to end processes and AI-ready data availability.
3.1.4 Local Solutions Portfolio and Architectural Transparency
Maintain an uptodate architectural view of market applications, integrations, and dependencies, ensuring documentation is accurate and produced using standard tools and templates to support the regional portfolio baseline.
3.2 Key Accountabilities / Responsabilidades Clave
- Design end‑to‑end market solutions covering B2B and B2C needs, aligned to IT Domain Architecture guardrails, Enterprise Architecture principles, and Tech standards.
- Lead architectural due diligence for market initiatives and material system changes, ensuring standards are applied and platform‑first options are evaluated.
- Produce and validate local architecture artifacts such as solution outlines, integration designs, logical architectures, data flow diagrams, and security designs using standard templates and tooling.
- Ensure early architecture engagement in demand intake and design phases for local initiatives to reduce late rework and siloed decisions.
- Apply approved regional and central patterns locally and escalate deviations through established governance paths when required.
- Support Architecture Review Board discussions by presenting market solution designs, incorporating feedback, and ensuring compliance is executed locally.
- Coach market teams and vendors on architecture expectations and standards to raise local capability and design consistency.
4. Core Service Activities / Actividades Principales del Servicio4.1 Demand Shaping & Solution Definition
English
· Engage early in demand intake and shaping activities
· Translate business requirements into solution options and target architectures
· Evaluate reuse vs. build alternatives using existing platforms
· Provide architectural input to cost, scope, and timeline estimations
Español
· Participar tempranamente en la captura y modelado de demandas
· Traducir requerimientos de negocio en opciones de solución y arquitecturas objetivo
· Evaluar alternativas de reutilización vs. desarrollo sobre plataformas existentes
· Proveer insumos arquitectónicos para estimaciones de costo, alcance y tiempos
4.2 Solution & Integration Architecture
English
· Define end‑to‑end solution architecture covering applications, integrations, and data flows
· Design integration models following enterprise patterns and API‑first principles
· Validate alignment with global integration, platform, and security teams
· Ensure operational, support, and service considerations are addressed
· Design solutions using the regional and global portfolio building blocks as the first option.
· If no applicable components exist, design AWS‑based architectures in full compliance with the AWS Well‑Architected Framework.
Español
· Definir arquitectura end‑to‑end considerando aplicaciones, integraciones y flujos de datos
· Diseñar modelos de integración siguiendo patrones empresariales y principios API‑first
· Validar alineación con equipos globales de integración, plataformas y seguridad
· Asegurar que los aspectos operativos, de soporte y servicio estén contemplados
· Diseñar soluciones utilizando como primera opción los building blocks del portafolio regional y global.
· En caso de no existir componentes aplicables, diseñar arquitecturas en AWS cumpliendo plenamente con el AWS Well‑Architected Framework.
4.3 Architecture Governance & Due Diligence
English
· Perform architectural due diligence for new solutions and changes
· Validate compliance with enterprise architecture principles and ITPF guidelines
· Identify architectural risks, constraints, and dependencies early
· Provide required architecture inputs to governance or approval forums
Español
· Ejecutar due diligence arquitectónica para nuevas soluciones y cambios
· Validar cumplimiento con principios de arquitectura empresarial y lineamientos ITPF
· Identificar riesgos, restricciones y dependencias arquitectónicas de forma temprana
· Proveer insumos arquitectónicos requeridos para foros de gobierno o aprobación
4.4 Architecture Documentation & Knowledge Management
English
· Produce and maintain architecture artifacts (solution diagrams, integration maps, interaction flows)
· Ensure documentation supports delivery, operations, and incident management
· Maintain architecture visibility and traceability across the demand portfolio
· Continuously improve architecture standards and reusable artifacts
· Technical diagrams (L1–L4) according to the project needs:
o L1 – High-Level Architecture (HLA): Provides a general overview of the system, showing domains, key components, main actors, and high-level interactions.
o L2 – System Architecture / Solution Architecture: Breaks down the system into logical components, services, and communication flows. Includes protocols (REST, HTTPS, messaging), dependencies, integrations, and key data exchange points.
o L3 – Technical Design / Application Architecture: Describes internal structure: modules, microservices, databases, queues, internal layers, design patterns, and security/performance considerations. It defines how components are implemented.
o L4 – Implementation / Deployment Diagram: Shows the concrete infrastructure: servers, containers, network configuration, VPCs, subnets, load balancers, ports, firewalls, CI/CD pipelines, and all elements required for solution deployment and operation.
Español
· Producir y mantener artefactos arquitectónicos (diagramas de solución, mapas de integración, flujos)
· Asegurar que la documentación soporte delivery, operación y gestión de incidentes
· Mantener visibilidad y trazabilidad arquitectónica del portafolio de demandas
· Mejorar continuamente estándares y artefactos reutilizables de arquitectura
- Diagramas técnicos (L1–L4) según necesidades del proyecto:
o L1 – Arquitectura de Alto Nivel: Presenta una vista general del sistema, mostrando dominios, componentes principales, actores involucrados y las interacciones esenciales.
o L2 – Arquitectura de la Solución: Desglosa los sistemas en componentes lógicos, servicios y flujos de comunicación. Incluye protocolos usados (REST, HTTPS, mensajería), dependencias, integraciones y puntos clave de intercambio de datos.
o L3 – Diseño Técnico: Detalla la estructura interna: módulos, microservicios, bases de datos, colas, capas internas, patrones de diseño, y consideraciones de seguridad y rendimiento. Especifica cómo se implementan los componentes.
o L4 – Diagrama de Implementación: Muestra la infraestructura concreta: servidores, contenedores, configuración de redes, VPC, subredes, balanceadores, puertos, firewalls, pipelines CI/CD, y cualquier elemento necesario para el despliegue y operación de la solución.
4.5 Development and Implementation
English
The service will cover the development, implementation, and validation of all technological components defined in the architectural solution.
The scope includes, but is not limited to:
· Infrastructure as Code (IaC) Implementation
o Building, deploying, and maintaining infrastructure using Terraform, ensuring proper version control, traceability, and state management.
o Integrating IaC artifacts with Git repositories, primarily using Bitbucket as the version‑control and deployment‑orchestration platform.
· AWS Cloud Service Deployment
o Provisioning, configuring, and deploying cloud components in AWS, strictly following the approved architectural design.
o Ensuring that all implemented solutions adhere to the AWS Well‑Architected Framework
Español
El servicio comprenderá el desarrollo, implementación y validación de los componentes tecnológicos definidos en la solución arquitectónica.
El alcance incluye, pero no se limita a:
· Implementación de Infraestructura como Código (IaC)
o Construcción, despliegue y mantenimiento de infraestructura mediante Terraform, asegurando versionamiento, trazabilidad y control del estado.
o Integración del código de infraestructura con repositorios Git, utilizando principalmente Bitbucket como sistema de gestión y automatización de despliegues.
· Despliegue de Servicios en AWS
o Provisionamiento, configuración y despliegue de servicios en la nube AWS, siguiendo los lineamientos de arquitectura definidos y los patrones de integración requeridos.
o Implementación de arquitecturas escalables, seguras y alineadas al AWS Well‑Architected Framework
5. Service Deliverables / Entregables del ServicioEnglish
At minimum, the vendor must provide:
· High‑level solution architecture diagrams
· Integration architecture and API interaction diagrams
· Architecture option assessments (reuse vs. build)
· Architecture risk and dependency assessments
· Architecture documentation required for project approval
· Develop and implement technological solutions in AWS using Terraform as Infrastructure as Code and Bitbucket for version control
Español
Como mínimo, el proveedor deberá entregar:
· Diagramas de arquitectura de solución de alto nivel
· Diagramas de arquitectura de integración e interacción de APIs
· Evaluaciones de opciones arquitectónicas (reutilización vs. desarrollo)
· Evaluaciones de riesgos y dependencias arquitectónicas
· Documentación arquitectónica requerida para aprobación del proyecto
· Desarrollar e implementar soluciones tecnológicas en AWS utilizando Terraform como infraestructura como código y Bitbucket para control de versiones.
6. Service Interfaces & Operating Model / Interfaces y Modelo OperativoEnglish
The service operates within Demand Shaping and interfaces with:
· Demand Shaping / Technical Product Owner
· Delivery Management
· Service Management / Service Integrator
· External delivery vendors
· Regional and Global Architecture teams
Architecture engagement is early, continuous, and execution‑oriented, acting as an enabler rather than a gatekeeper.
Español
El servicio opera dentro de Demand Shaping y se integra con:
· Demand Shaping / Technical Product Owner
· Delivery Management
· Service Management / Service Integrator
· Proveedores externos de delivery
· Equipos regionales y globales de Arquitectura
La participación arquitectónica es temprana, continua y orientada a la ejecución, actuando como habilitador y no como punto de bloqueo.
7. Service Boundaries / Límites del ServicioEnglish
In Scope
· Architecture activities during demand shaping and early delivery
· Solution and integration design
· Architectural due diligence and documentation
· Applications development or configuration (AWS or API related)
· Help during Operational support or incident management
Out of Scope
· SLA ownership or service operations
· Final project delivery accountability
Español
Dentro del Alcance
· Actividades arquitectónicas durante demand shaping y fases tempranas
· Diseño de arquitectura de solución e integración
· Due diligence y documentación arquitectónica
· Desarrollos o configuración de aplicaciones (AWS o API)
· Apoyo puntal en Soporte operativo o gestión de incidentes
Fuera del Alcance
· Responsabilidad de SLAs u operación de servicios
· Responsabilidad final de la entrega del proyecto
Tipo de puesto: Tiempo completo
Sueldo: $60,000.00 - $75,000.00 al mes
Lugar de trabajo: remoto híbrido en Miguel Hidalgo, CDMX
