Original practice scenario inspired by Siemens Aktiengesellschaft's public business context; this is not a reported interview question or a description of its internal systems. A fictional industrial device fleet includes old firmware that cannot update immediately. A new telemetry message adds optional units and a quality flag. Describe a parser and rollout strategy that keeps old data understandable.
Read model answer +
Version the message meaning as well as its bytes. Optional fields need documented defaults that preserve the interpretation of old messages, especially when measurement units and quality affect downstream decisions.
Work through it
Define required identifiers, sequence numbers, supported versions, and unknown-field behavior. Reject malformed values with explicit diagnostics rather than guessing units.
Add fixtures from each supported firmware generation and test missing optional fields, reordered fields, duplicate messages, and unsupported versions.
Deploy readers before writers when possible, monitor rejected-version counts, and retain raw messages with parser version for replay. Use an explicit migration for incompatible semantics.
Tradeoffs to discuss
Tolerant parsing helps forward compatibility but can hide producer defects. Distinguish harmless extra fields from changes that alter measurement interpretation.
Common pitfalls
A numeric field without units may be ambiguous.
Treating missing quality as good can make old or incomplete measurements appear validated.
Original practice scenario inspired by Siemens Aktiengesellschaft's public business context; this is not a reported interview question or a description of its internal systems. A synthetic industrial dashboard shows a gradual rise in one sensor's readings. Production conditions and maintenance schedules also changed. How would you investigate whether the sensor is drifting?
Read model answer +
A trend in readings does not by itself distinguish an instrument problem from a real process change. Use reference measurements, operating context, and maintenance events to compare competing explanations.
Work through it
Check units, calibration history, sampling frequency, and missingness. Plot the sensor alongside related measurements under comparable operating regimes.
Compare residuals against a trusted reference or a model fitted on stable periods, while keeping evaluation periods separate. Inspect changes around maintenance and equipment replacement.
Quantify uncertainty and investigate flagged periods with domain operators. Set an alert rule with persistence and review criteria rather than automatically recalibrating from the trend alone.
Tradeoffs to discuss
Reference instruments add cost, and model residuals can also drift when the process changes. Combining independent evidence is stronger than one statistical test.
Common pitfalls
Normalizing every period independently can erase genuine drift.
Correlated sensors sharing the same failure mode are not independent confirmation.
