Design a centralized metrics and logging pipeline — GitLab interview
Reported in GitLab European engineering loops. Observability architecture interview question for platform roles.
Interview atlas
Explore 11,575 curated Q&As across 124 employers — filter by career stage, round, or company.
Reported in GitLab European engineering loops. Observability architecture interview question for platform roles.
Reported in GitLab European engineering loops. Critical design topic focused on correctness under retries and failures.
Reported in GitLab European engineering loops. System design interview around indexing, ranking, and freshness.
Reported in GitLab European engineering loops. System design problem testing reliability, fan-out, and channel abstraction.
Reported in GitLab European engineering loops. Senior system design combining sharding, eviction, consistency, and observability.
Reported in GitLab European engineering loops. Infrastructure design question covering L4/L7 balancers and health checks.
Reported in GitLab European engineering loops. Caching patterns for system design and backend performance tuning.
Reported in GitLab European engineering loops. Mid-to-senior design spanning WebSockets, message storage, and presence.
Reported in Elastic European engineering loops. Often appears in enterprise and platform interviews at EU cloud and SaaS companies.
Reported in Elastic European engineering loops. Frequently asked at European fintechs dealing with PSD2 and AML controls.
Reported in Elastic European engineering loops. Object model design for template rendering and channel-specific formatting.
Reported in Elastic European engineering loops. System design topic around edge caching, invalidation, and latency.
Reported in Elastic European engineering loops. System design exercise emphasizing control plane and low-latency reads.
Reported in Elastic European engineering loops. Observability architecture interview question for platform roles.
Reported in Elastic European engineering loops. Critical design topic focused on correctness under retries and failures.