Senior Integration Architect - RHA2146

Description

Join a company that loves transforming with technology and embraces diversity in all its forms! **Responsibilities and Duties** **Requirements and Qualifications** Integration Architect (focus: integration design and interface mapping) **2\) Scope of Work (Key Responsibilities)** **2\.1 Integration Architecture (Solution)** Gather and detail integration requirements with business stakeholders and technical teams (functional and non-functional). Define the appropriate integration style per scenario: synchronous (REST/gRPC), asynchronous (events/pub\-sub, queues), batch/file-based (SFTP, object storage), integration via ESB/iPaaS/API Gateway. Design end-to-end flows (request/response, events, compensations, retries, idempotency). Define architectural patterns: API\-led connectivity, event\-driven, saga/orchestration, choreography, anti\-corruption layer, strangler pattern (modernization), canonical model vs. point\-to\-point mapping (trade\-offs). Evaluate alternatives and recommend solutions based on cost, risk, time\-to\-market, and platform maturity. **2\.2 Interface Mapping and Integration Catalog** Build and maintain the Interface Map (integration inventory): source/destination systems, type (API/event/queue/file), contract (schema), version, owner, and SLA, criticality, dependencies, and consumers. Define taxonomy and naming standards: APIs (paths, resources), events (namespaces, topics), queues, and files. Produce and evolve living documentation (OpenAPI/AsyncAPI, runbooks, diagrams). **2\.3 Contract Design (APIs and Events)** Define contracts and guidelines: APIs: OpenAPI, versioning, backward compatibility, pagination, filters, error handling, rate limiting. Events: AsyncAPI/JSON Schema/Avro/Protobuf, schema versioning, compatibility, DLQ. Define integration rules: idempotency, deduplication, ordering, correlation (correlation\-id), distributed tracing, timeouts, retries, circuit breaker, backoff, bulkheads, error patterns and messaging. Define publication and consumption policies (event and API governance). **2\.4 Security and Compliance in Integrations** Define authentication and authorization standards: OAuth2/OIDC, mTLS, JWT, API Keys (where applicable), service\-to\-service. LGPD and sensitive data requirements: data minimization in payloads, masking, secure logging, retention. Define audit trails and evidence requirements. 2\.6 Architecture Governance and Team Enablement Conduct integration and contract architecture reviews. Create and maintain standards, templates, and checklists (API checklist, event checklist, security checklist). Collaborate with Platform teams (API Gateway, messaging, iPaaS/ESB) and Security. Mentoring and “office hours” for consumer/producer teams. **4\) Deliverables (Artifacts)** **4\.1 Integration Design (per initiative/epic)** HLD (High Level Design) of the integration (macro view, components, flows, NFRs). LLD (Low Level Design) when required: contracts, sequence, error handling rules, idempotency, retry/DLQ strategies. Diagrams: context (C4\), sequence (UML) for synchronous/asynchronous flows, data and integration flow, logical deployment (if applicable). ADRs (Architecture Decision Records) documenting decisions and trade\-offs. 4\.2 Catalog / Interface Map Inventory of APIs, events, and integrations with minimum metadata: owner, criticality, environments, endpoints/topics, versioning, consumers, dependencies, SLA/SLO, sensitive data. “System Interfaces” matrix per domain/product line. Rationalization roadmap (duplicate integrations, legacy systems, failure points). 4\.3 Contracts and Standards Reviewed/approved OpenAPI (APIs) and AsyncAPI (events) specifications. Versioning and compatibility guidelines. Security standards and headers/correlation\-id conventions. Readiness checklist (go\-live) for integrations. **5\) Execution Methodology (How the Service Is Delivered)** Discovery: understanding of business process, involved systems, SLAs, and risks. As\-is: mapping of existing interfaces, pain points, bottlenecks, and recurring incidents. To\-be: target integration design \+ alternatives and trade\-offs. Validation: sessions with Architecture, Security, Platform, and execution teams. Follow\-up: checkpoints during implementation (contract review, change governance). Continuous evolution: maintenance of interface map and standards. **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 through 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 the core values embedded in our culture: \#collaboration. **Innovation to Shape the Future** Spread is an innovation company with 41 years of history, delivering 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 our top priority and guides our actions and strategies. This commitment is reflected in our NPS of 75 points — placing us in the quality zone and demonstrating our customers’ 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 surface-level attributes and encompasses a broad range of characteristics, such as gender, ethnicity, sexual orientation, age, and abilities.