Sanjaay Gowda T S
All company profiles

COMPANY CONTEXT / 51 IN THE STUDY LIST

Shell plc

EnergyUnited KingdomData scienceSystem design

Shell operates energy businesses spanning fuels, natural gas, power and related services.

Original company-context practice, not verified company interview questions. Use the business setting to explain technical choices clearly.

01 / PRACTICE IN CONTEXT

Two problems to reason through.

Clarify assumptions before reading the model answer. Discuss what would change with different constraints.

Original company-context practiceHard

Data science

Distinguish sensor drift from a process change

Shell plc · Concept

Original practice scenario: An energy-operations simulator reports rising pressure readings after a sensor replacement. How would you investigate before training an anomaly detector?

Read model answer

Separate instrumentation changes from changes in the measured process. A replacement can alter calibration, reporting frequency or units, so an apparent anomaly may describe the measurement system.

Work through it

  1. Build a timeline of installation, calibration, maintenance and operating conditions; preserve raw readings with device identity, units and event timestamps.
  2. Compare overlapping reference sensors and comparable operating regimes, examining missingness and sampling intervals before aggregating trends.
  3. Evaluate detectors on held-out time periods with known simulated incidents and maintenance transitions; report alert delay and false alerts separately.

Tradeoffs to discuss

  • Normalizing every device independently can conceal meaningful absolute limits; pooled models may overreact to harmless calibration differences.

Common pitfalls

  • Do not label all post-replacement changes as equipment faults.
  • Keep maintenance information available at prediction time rather than leaking later inspection outcomes.
Open full question
Original company-context practiceHard

System design

Reconstruct a hypothetical energy dispatch decision

Shell plc · Concept

Original practice scenario: Design an audit trail for a simulated power-dispatch planner whose forecasts and constraints can change after a recommendation is produced.

Read model answer

A replayable decision needs the inputs and rule versions used at that moment, not merely its final schedule. Later corrections should remain distinguishable from the original evidence.

Work through it

  1. Assign a decision identifier and retain immutable references to forecast snapshots, available capacity, constraint versions and optimization settings.
  2. Record proposed schedules, validation outcomes, overrides and their reasons; keep operational execution acknowledgements distinct from planning output.
  3. Replay archived scenarios in an isolated environment and compare constraint satisfaction and objective values, allowing documented numerical tolerances.

Tradeoffs to discuss

  • Full snapshots simplify replay but increase storage; immutable versioned references require reliable retention across dependent systems.

Common pitfalls

  • A current forecast must not silently replace the historical input.
  • Do not equate a feasible simulated schedule with permission to control physical equipment.
Open full question

02 / STRENGTHEN THE FOUNDATIONS

Related technical practice.

Browse company questions

03 / TEST AN APPROACH

Suggested coding exercises.

Exercises selected for these technical tracks. They are independent practice with visible tests and public solutions.

Study list: PwC Global Top 100 companies by market capitalisation, 2026 · 31 March 2026.

Keep learning beyond the interview.

Explore the Learning Hub