LSEG Platform interview questions

Three of the questions

1. Walk me through how you'd design and build an observability platform where Cribl sits as the routing and normalisation backbone, moving telemetry from multiple sources to destinations like Datadog and BigPanda. How would you structure the pipelines and packs so logic stays standardised across teams and signal types?
   Technical depth · from the posting: “Cribl is the routing and normalisation backbone of our telemetry pipeline, and engineers in this role will spend significant time designing, building, and evolving Cribl pipelines”
2. Say the LOCP platform you support starts showing intermittent latency spikes in production only during peak trading hours, but staging tests look fine. Walk me through how you'd troubleshoot this, using the observability stack you'd have in place.
   Scenarios & troubleshooting · from the posting: “Apply Site Reliability Engineering (SRE) principles to improve platform reliability, scalability, performance, and operational effectiveness”
3. This team values working 'backwards from developer and business needs' to build platforms that make engineering teams more effective. Tell me about a time you built something that nobody asked for but turned out to be exactly what they needed.
   Behavioural · from the posting: “Customer Driven Work backwards from developer and business needs. Build platforms that make engineering teams more effective.”