SOLUTION ARCHITECT - RHA2145

Description

Join a company that loves transforming through technology and embraces diversity in all its forms! **Responsibilities and duties** Service delivery scope — Solution Architect (focus: High-level Solution Architecture derived from demand understanding documentation) 1\) Service objective Design the high-level solution architecture (HLD) for initiatives/products/epics based on demand understanding documentation, consolidating requirements, defining alternatives, and recommending a target solution—including its key components, integrations, flows, non-functional requirements, and risks—ensuring alignment between business and technical teams. 2\) Scope of work (primary responsibilities) 2\.1 Discovery and refinement based on demand * Analyze demand understanding documentation and consolidate context, objectives, stakeholders, assumptions, constraints, and dependencies. * Elicit and refine functional and non-functional requirements with business and technical teams where gaps or ambiguities exist (e.g., performance, availability, security, observability, scalability) \[1] \[2]. * Identify end-to-end scenarios and use cases (e.g., customer journey, business events, required integrations). 2\.2 Solution Architecture Design (HLD) * Propose the high-level “to\-be” architecture covering: o Macro view of components and responsibilities (bounded contexts/services/systems). o Key end-to-end flows (synchronous and/or asynchronous, as applicable) \[2]. o High-level data view (sources, movement, storage/consumption, where applicable) \[1]. * Define the appropriate architectural style per scenario (e.g., API\-led, event\-driven, batch, integrations via gateway/ESB/iPaaS, as applicable) \[2]. * Produce architecture artifacts and lead validation sessions with stakeholders (Architecture Review) \[1] \[2]. 2\.3 Integrations and contracts (solution-level view) * Map required integrations across systems/domains, indicating type (API/event/queue/file), responsibilities (producer/consumer), and coupling points \[2]. * Define solution-level contract guidelines (e.g., OpenAPI/AsyncAPI, versioning, compatibility, error handling policies), when within the initiative’s scope \[2]. * Consider high-level resilience requirements (e.g., retries, idempotency, DLQ, timeouts) as architectural drivers \[2]. 2\.4 Data, information, and compliance (where applicable) * Identify key data handled by the solution (relevant entities/events/datasets) and how it flows/where it resides at a high level \[1]. * Consider LGPD and sensitive data requirements in the design (minimization, retention/deletion, controls) at the architectural level \[1] \[2]. 2\.5 Evaluation of alternatives and architectural decisions * Evaluate solution options and trade\-offs (cost, complexity, risk, time\-to\-market, platform alignment) and recommend the target alternative \[1] \[2]. * Record relevant architectural decisions and justifications (ADRs), including impacts and consequences \[1] \[2]. 2\.6 Governance and cross-team alignment * Act as a convergence point among Product/Business, Engineering, Platform, Security, and Data to ensure shared understanding and consistent execution \[1] \[2]. * Participate in architecture rituals/comittees, reviews, and approvals (including ADRs) \[1] \[2]. * Suggest standards, templates, and checklists to improve repeatability and design quality (e.g., go\-live checklist for integrations, documentation standards) \[2]. 3\) Deliverables (artifacts) 3\.1 Solution Architecture (per initiative/epic) * HLD (High-Level Design) including: o Context and objectives o In-scope and out-of-scope items o Consolidated requirements (functional/non-functional) o Target architecture (to\-be) and as\-is view when needed o Key end-to-end flows o Dependencies, risks, and assumptions o High-level phased implementation plan (when applicable) * ADRs (Architecture Decision Records) documenting decisions and trade\-offs \[1] \[2]. 3\.2 Diagrams (high-level) * Context diagram (e.g., C4 Level 1/2) \[1] \[2]. * Component and integration diagram (macro view) \[1] \[2]. * Data flow diagram (DFD), when relevant \[1] \[2]. * Sequence diagram (UML) for critical integration flows (when necessary) \[2]. * High-level security/boundaries and control view (when applicable) \[1]. 3\.3 Inventories and maps (where applicable) * Interface map (inventory of solution integrations with minimal metadata such as owner, type, contract, SLA, criticality) \[2]. * Indication of high-level data map (sources, transformations, consumption) for data-oriented initiatives \[1]. * LGPD classification matrix (if required in context) \[1]. 4\) Working methodology (how the service will be delivered) * Discovery and alignment: understand demand, stakeholders, constraints, and current architecture (as\-is) \[1] \[2]. * Design and validation: propose to\-be alternatives and conduct review sessions with architecture and delivery teams \[1] \[2]. * Governance and oversight: checkpoints during implementation to ensure adherence to design and govern significant changes (including contract reviews, where applicable) \[2]. 5\) Acceptance criteria (suggested) * HLD approved in Architecture Review, with explicit and traceable requirements and NFRs linked to demand. * Critical decisions recorded in ADRs with documented trade\-offs. * Minimum diagrams and inventories updated (integrations/data, where applicable). * Risks, dependencies, and assumptions identified with clear action plans. If you tell me the type of initiatives (e.g., more digital/API-focused, more data/analytics-focused, or both) and whether there is a standard demand documentation template, I’ll tailor the scope to precisely reflect your workflow and deliverables. **Requirements and qualifications** **Mandatory:** PER CLIENT’S JOB DESCRIPTION ATTACHED FILE BACHELOR’S DEGREE — COMPLETED **Additional information** Want to learn more about us and join the team building the future? **\#VemSerSpreader** **Transforming the world with technology** We are nearly 2\.500 Spreaders, spread across 22 Brazilian states via Spread Anywhere, enabling us to work **100% remotely**, depending on the contract model. We are digital, hyperconnected, and wherever we are, we practice daily one of our core cultural values: \#collaboration. **Innovation to shape the future** Spread is an innovation company with 41 years of history, offering comprehensive technology and digital business solutions. Today, we offer a robust portfolio of services, including application development, Quality Assurance, IT Outsourcing, Talent on Demand, Artificial Intelligence solutions, and SAP and S/4HANA consulting and implementation. We adopt a customer-centric approach, where customer experience is paramount and guides our actions and strategies. This commitment is reflected in our NPS of 75 points—a metric placing us in the quality zone and confirming our clients’ trust and satisfaction. **Diversity, Equity & Inclusion** Here, diversity and inclusion are not just words—they are a genuine commitment. We strive to ensure every Spreader feels **valued, respected, and empowered** to reach their full potential. We recognize that true diversity goes beyond superficial aspects and encompasses a broad range of characteristics, including gender, ethnicity, sexual orientation, age, and abilities.