API Architect Event-Driven Architecture (EDA)

What do we offer?

• Joining Grupo NS and participating in a technological project in the financial sector.
• Architecture and integration project with API and event technologies and platforms.
• 100% remote working modality (Spain).
• Collaborative working environment specialized in architecture and integration of technological solutions.
• Opportunity to participate in governance, security, and evolution initiatives for integration architectures.

At Grupo NS, a technology consultancy specializing in digital transformation projects, we are incorporating an API Architect to participate in a strategic project within the banking sector. The working modality is 100% remote from any province in Spain.

We are looking for a technical profile with experience in the design, definition, and governance of REST APIs and asynchronous architectures (Event-Driven Architecture), who will participate in the definition of standards, security policies, quality, and the lifecycle of APIs and events.

The selected person will collaborate in the evolution and governance of the integration ecosystem, ensuring the quality, traceability, security, and consistency of the integration solutions.

What will your duties be?

Design and definition of APIs and Event-Driven architectures

• Design, definition, and documentation of REST APIs and asynchronous APIs.
• Definition of contracts and specifications using Swagger/OpenAPI and AsyncAPI 2.x and 3.x.
• Modeling and definition of data schemas using Avro.
• Participation in event modeling through Event Storming.
• Definition of Event-Driven architectures, differentiating between events and commands, as well as orchestration and choreography patterns.
• Knowledge and application of SAGA patterns and compensation mechanisms.

API governance and quality

• Definition and maintenance of standards, policies, guides, and best practices for REST APIs and EDA architectures.
• Governance of the API and event lifecycle: versioning, documentation, monitoring, and obsolescence (deprecation).
• Management of API typologies, exposure layers, and usage policies.
• Creation, maintenance, and control of API and event catalogs and inventories by domain.
• Validation of definition quality through reports, metrics, and scoring systems.
• Development and maintenance of automatic validation mechanisms (linters).
• Integration of quality controls into CI/CD processes and automation.

Security and access control

• Definition and application of security policies for REST APIs and events.
• Management of authentication, authorization, and access control mechanisms.
• Application of standards and technologies such as OAuth 2.0, JWT, IAM Policies, and integration with Identity Providers (IdP).
• Management of ACLs, encryption, digital certificates, and mutual authentication via mTLS.
• Guarantee of traceability, auditing, and communication security.

Traceability and observability

• Definition of auditing and traceability mechanisms for APIs and events.
• Tracking of event lineage (Event Lineage).
• Collaboration in observability and monitoring initiatives for the integration ecosystem.