Covers the end to end concepts and practices for connecting systems using application programming interfaces and integration middleware. Candidates should understand REST and HTTP fundamentals, webhooks versus polling, API authentication and authorization patterns, request and response formats, rate limiting, versioning, and reading API documentation. Include practical skills for building and troubleshooting integrations: data mapping and transformation, schema mapping, message formats, error handling and retry strategies, idempotency, logging and monitoring, and ensuring data consistency across synchronous and asynchronous flows. Also includes integration tooling and middleware platforms, real time versus batch synchronization, designing for partial failures and back pressure, and frontend concerns such as async data fetching, loading and error states, pagination, optimistic updates, and race condition mitigation.
HardTechnical
0 practiced
You're defining SLOs and SLAs for an integration product used by enterprise customers. How would you choose service level indicators, set error budgets, negotiate SLA terms with legal/sales, define escalation paths, and measure customer impact when a breach occurs? Include considerations for multi-tenant differentiation.
HardTechnical
0 practiced
A customer requires transmission and storage of PII via integrations for 7 years fulfilling GDPR and other privacy constraints. Design an end-to-end architecture covering encryption in transit and at rest, key management, access control, audit logging, data minimization, retention policies, right-to-erasure, and how to keep aggregated historical financial records intact when deletion is requested.
HardTechnical
0 practiced
A near-real-time synchronization pipeline using Kafka shows intermittent consumer lag and duplicate processing. Describe a thorough troubleshooting plan: which metrics/logs to inspect (consumer lag, GC pauses, partition imbalance), possible root causes (slow consumers, broker issues, rebalances), and concrete remediation steps to stop duplicates and reduce lag.
EasyTechnical
0 practiced
Explain the fundamentals of REST and HTTP and how they differ in practice. In your answer, cover REST constraints (statelessness, uniform interface, cacheability), common HTTP methods and their intended semantics (GET, POST, PUT, DELETE, PATCH), how HTTP status codes influence client behavior, and an example of when REST constraints might be relaxed for pragmatic reasons.
EasyTechnical
0 practiced
In Python, implement a function parse_pagination_params(query_params: dict) -> dict that normalizes cursor-based pagination parameters from HTTP query strings. Requirements: return a dict with keys 'cursor' (str|None), 'limit' (int default 50, max 100), and 'direction' ('forward'|'backward', default 'forward'). Validate inputs and raise a ValueError for invalid values.
Unlock Full Question Bank
Get access to hundreds of API Integration and System Connectivity interview questions and detailed answers.
