Api Architect

Role & responsibilities

• API Architecture & Design: Define and maintain the end-to-end design covering service boundaries, contracts, data models, error semantics, and versioning strategies.
• Interface Landscape: Produce repeatable, reusable API patterns for inbound/outbound interfaces (data exchange, file push/pull, synchronous and asynchronous flows).
• Contract Standards: Own the OpenAPI specification approach, naming/payload conventions, backward-compatibility rules, and contract-first workflows.
• Large File Transfer Design: Define patterns for moving large payloads reliably (chunked/resumable transfers, streaming, signed URLs, checksums, restart on failure).
• Technical Trade-offs: Make architectural decisions between synchronous APIs, queue-backed asynchronous flows, and bulk file interfaces, documenting them via ADRs.
• Resilience & Scale: Design for high throughput and low latency, incorporating backpressure, circuit breaking, retries with idempotency, rate limiting, and timeout budgets.
• Reference Implementation: Set standards and prove them by writing reference services that engineering teams can follow and pattern-match against.

Preferred candidate profile

• Core Backend: Java, Spring Boot, Microservices, Spring Data / Hibernate.
• API & Web Services: Java REST API, REST Web Services using Spring MVC, OpenAPI Specs.
• Reactive & Advanced Spring: Project Reactor / WebFlux, Spring Cloud, Spring Batch.
• Architecture Concepts: API Security, Performance Tuning, Resiliency Patterns, Distributed Systems.

Soft Skills:

• Strong collaboration skills to partner effectively with client-side architects and engineering leads.
• Excellent technical documentation skills (ADRs, system design documents).