KBR Instrumentation Interview Prep

KBR Basic Engineering Interview Questions

& Model Answers
200 Questions - Instrumentation & Basic Engineering Focus

This document provides model answers and structured guidance for a KBR Basic Engineering (Instrumentation)
interview, covering engineering fundamentals, instrument and control valve selection, engineering
documentation, functional safety, vendor engineering, and behavioral/scenario-based questions. For Sections 7
and 8, tailor the frameworks provided with your own real project details.

1
 KBR Instrumentation Interview Prep

Section 1: Engineering Fundamentals & FEED

Q1. Explain the complete EPC project lifecycle from Concept to Commissioning.
The lifecycle runs: Feasibility/Conceptual Engineering (defines scope, technology selection, rough cost) →
FEED (Front End Engineering Design, defines process basis, layout, major equipment, cost estimate class 3) →
Detailed Engineering (issued-for-construction drawings, datasheets, MRs) → Procurement (vendor selection,
TBE, PO placement) → Construction (fabrication, installation) → Pre-commissioning (loop checks, punch
listing) → Commissioning and Start-up → Performance testing and handover to operations.

Q2. What is the difference between Conceptual Engineering, FEED, Basic Engineering, and Detailed
Engineering?
Conceptual Engineering establishes technology selection and order-of-magnitude cost. FEED (often used
interchangeably with Basic Engineering in EPC contracts) fixes the process design basis, PFDs/P&IDs, plot
plan, and major equipment specs to support an EPC bid or FID. Basic Engineering deepens this to produce
datasheets, specifications, and preliminary quantities discipline-by-discipline. Detailed Engineering then
produces fully IFC drawings, final datasheets, cable/loop drawings, and construction-ready documents.

Q3. What are the objectives of FEED?

FEED aims to freeze the process design basis, define plot plan and major equipment, establish instrument and
control philosophies, generate enough quantity and specification detail for an accurate (class 2/3) cost estimate,
identify long-lead items, and de-risk the project before committing to detailed engineering and construction.

Q4. What are the major instrumentation deliverables during FEED?

Key deliverables include the Instrument Design Basis/Philosophy, preliminary Instrument Index, I/O list
estimate, control system architecture and philosophy, control valve list, hook-up and installation standards,
cable/JB quantity estimates, alarm and SIS philosophies, and input to the overall FEED cost estimate and MDR.

Q5. Explain the Instrument Design Basis document.

The Design Basis captures the project-specific engineering premises: site/environmental conditions, area
classification, applicable codes and standards, units of measurement, signal types (4-20mA HART, Fieldbus),
power supply arrangements, and general philosophy for instrument selection - it is the reference document that
all subsequent instrument specifications must comply with.

Q6. Explain the Instrument Design Philosophy.

This document describes the overall approach to instrumentation and control for the project - preferred
measurement technologies by service, control system architecture (DCS/PLC/SIS split), redundancy
philosophy, cabling and marshalling strategy, and how instrumentation supports the plant's operability, safety,
and maintainability objectives.

Q7. What is an Instrument Design Criteria document?

It's a more granular technical standard that specifies the detailed selection rules and default choices for each
instrument type (e.g., transmitter accuracy class, minimum orifice beta ratio, thermowell insertion length rules),
used by engineers to make consistent selections without re-deriving criteria for every tag.

Q8. How do you estimate instrument quantities during FEED?

Quantities are estimated from the PFD/preliminary P&ID count of control loops, safety instrumented functions,
and utility metering points, benchmarked against similar completed projects (unit rates per equipment item or
per process unit), then adjusted for project-specific complexity, redundancy, and client philosophy.

2
 KBR Instrumentation Interview Prep

Q9. How do you estimate I/O counts?

I/O is estimated by multiplying the anticipated tag count by signal type (AI, AO, DI, DO) based on historical
ratios for similar process units, then adding margin (typically 10-20%) for spares and future expansion, and
cross-checking against package vendor I/O once package scope is known.

Q10. How do you estimate cable quantities?

Cable estimates are derived from instrument locations on the plot plan, junction box locations, and routing
distances measured on the layout, using typical cable-per-tag ratios (individual pair cables from field to JB,
multicore trunk cables from JB to marshalling), plus contingency for rerouting and derating.

Q11. How do you estimate junction box quantities?

JB quantities are based on plot area coverage, maximum cable run length limits, and typical JB capacity (e.g.,
24 or 32 pairs), grouping instruments by area/unit and hazardous area zone so each JB serves a practical cluster
of field devices within acceptable cable length and voltage drop limits.

Q12. How do you estimate marshalling cabinets and system cabinets?

These are sized from the total I/O count divided by I/O capacity per cabinet (accounting for redundancy and
spare philosophy), with system cabinets (DCS/PLC/SIS controllers) estimated separately based on controller
loading, redundancy requirements, and the client's cabinet standardization philosophy.

Q13. What assumptions are acceptable during Basic Engineering?

Acceptable assumptions include using vendor standard package I/O until package data is firm, applying
industry-typical accuracy/turndown for instruments not yet selected, assuming standard hook-up details, and
using generic cable/JB unit rates - provided all assumptions are documented and flagged for validation in
Detailed Engineering.

Q14. How do you control design changes between FEED and Detailed Engineering?
Through a formal Management of Change / Engineering Change Notice process: changes are logged, impact-
assessed across disciplines, approved by the project/client, and reflected in updated design basis documents,
with a change log maintained so cost and schedule impact is traceable.

Q15. How do you estimate engineering man-hours?

Man-hours are estimated using historical productivity norms (hours per document type - datasheet, drawing,
specification) multiplied by the deliverable count from the MDR, adjusted for project complexity, degree of
standardization, and discipline experience level, then reviewed against similar completed projects for
benchmarking.

Q16. How do you identify engineering risks during FEED?

Risks are identified through HAZID/HAZOP inputs, technology maturity reviews, long-lead equipment
assessment, interdisciplinary interface reviews, and lessons-learned from similar projects; each risk is logged in
a risk register with mitigation actions and an owner.

Q17. What are the responsibilities of an Instrument Engineer during Basic Engineering?
Responsibilities include preparing the Instrument Index, design basis/philosophy documents, instrument
datasheets, control valve sizing, hook-up standards, I/O and cable estimates, reviewing P&IDs from an
instrumentation perspective, coordinating with process/piping/electrical, and supporting HAZOP and cost
estimation.

Q18. How do you ensure consistency between engineering documents?

Consistency is maintained through a controlled Instrument Index as the master reference, standard document
templates, interdisciplinary check (IDC) cycles before issue, a single source of tag numbering, and periodic
squad checks or 3D model reviews that cross-verify P&IDs, datasheets, and layouts.

3
 KBR Instrumentation Interview Prep

Q19. What multidisciplinary inputs are required before starting instrumentation engineering?
Instrumentation needs process data (P&IDs, heat and material balance, line lists), piping layout and line sizes,
electrical area classification and power availability, civil/structural plot plan, mechanical equipment data sheets,
and the overall control philosophy from the client.

Q20. How do you optimize instrumentation costs during FEED?

Cost optimization comes from standardizing instrument types and vendors, minimizing redundant
measurements, using package vendor I/O instead of duplicating field instruments, optimizing cable routing to
reduce cable length, and challenging unnecessarily conservative SIL/instrument specifications against actual
process risk.

Q21. How do you prepare a Master Deliverable Register (MDR)?

The MDR lists every document/drawing to be produced by discipline, with planned issue dates, revision status,
and responsible engineer; it's built from the project execution plan and scope of work, then used to track
engineering progress and man-hour expenditure throughout the project.

Q22. What is an Interdisciplinary Check (IDC)?

IDC is the formal review cycle where a document from one discipline is circulated to all affected disciplines for
comments before formal issue, ensuring that instrumentation, process, piping, electrical, and civil inputs are
aligned before a document is approved.

Q23. Explain Engineering Change Notice (ECN).

An ECN is a formal record raised when a design change is required after a document has been issued; it
captures the reason for change, scope impact, disciplines affected, and approval status, and drives revision of all
impacted documents.

Q24. Explain Management of Change (MOC).

MOC is the structured process (often broader than engineering, extending into operations) for evaluating,
approving, and implementing any change to a facility's design, procedures, or operating parameters, ensuring
safety, technical integrity, and documentation are maintained before the change is implemented.

Q25. What are the biggest challenges in Basic Engineering?

Common challenges include incomplete or evolving process data, tight schedule pressure to freeze design basis,
coordinating package vendor data before it's firm, managing multidisciplinary interfaces, and balancing
conservative safety margins against cost targets.

4
 KBR Instrumentation Interview Prep

Section 2: Process Understanding & Instrument Selection

Q26. What process information is required before selecting an instrument?
You need the fluid properties (phase, density, viscosity, corrosiveness), operating and design
pressure/temperature, flow range and turndown, line size, hazardous area classification, and the required
accuracy/response time dictated by the control or safety function.

Q27. How do you select a pressure transmitter?

Select based on process pressure range (with margin above operating max), fluid compatibility of wetted parts,
required accuracy, hazardous area certification, and whether a diaphragm seal is needed for viscous, corrosive,
or solidifying fluids; smart HART transmitters are the default for most modern services.

Q28. When do you use a DP transmitter?

DP transmitters are used for flow measurement across a primary element (orifice, venturi), for level
measurement via hydrostatic head especially in pressurized vessels, and for filter/strainer differential pressure
monitoring.

Q29. When should remote seals be used?

Remote seals (diaphragm seals with capillary) are used when the process fluid is viscous, crystallizing, highly
corrosive, contains solids, or at extreme temperature, to protect the transmitter from direct process contact while
still transmitting pressure accurately.

Q30. How do you select a temperature element?

Selection depends on temperature range, required accuracy, response time, and process conditions: RTDs for
accurate, stable, low-to-moderate temperature service; thermocouples for high temperature or where
ruggedness/small size matters more than absolute accuracy.

Q31. RTD vs Thermocouple.

RTDs offer better accuracy, stability, and linearity but have a narrower range (typically up to ~600°C) and
slower response; thermocouples cover much higher temperatures (up to ~1700°C depending on type), are more
rugged and cheaper, but less accurate and prone to drift over time.

Q32. How do you select a thermowell?

Thermowell selection considers process velocity (to avoid resonance/wake-induced vibration per ASME PTC
19.3), pressure/temperature rating, material compatibility, insertion length for adequate response, and a wake-
frequency calculation to ensure structural integrity at the design flow velocity.

Q33. How do you select a flow meter?

Selection depends on fluid type (liquid/gas/steam), cleanliness, conductivity, required accuracy and turndown,
line size, pressure drop allowance, and whether bidirectional or custody-transfer accuracy is needed - matching
these to the strengths of orifice, Coriolis, magnetic, ultrasonic, vortex, or turbine technology.

Q34. Coriolis vs Orifice Flow Meter.

Coriolis meters directly measure mass flow and density with very high accuracy and wide turndown but at
higher cost and with line-size/weight limitations; orifice meters are cheap, simple, and well-standardized (ISO
5167) but have limited turndown, cause permanent pressure loss, and only measure inferred volumetric/mass
flow via DP.

Q35. Magnetic vs Ultrasonic Flow Meter.

Magnetic flow meters require a conductive fluid but offer excellent accuracy with no pressure drop and no
moving parts; ultrasonic meters work on conductive or non-conductive fluids and can be clamp-on (non-
intrusive) but are more sensitive to flow profile disturbances and entrained gas/solids.
5
 KBR Instrumentation Interview Prep

Q36. Vortex vs Turbine Flow Meter.

Vortex meters have no moving parts, handle a wider range of fluids (liquid, gas, steam) and require less
maintenance, but have a lower turndown and need adequate straight-run and minimum Reynolds number;
turbine meters offer better accuracy at moderate turndown for clean fluids but have moving parts subject to
wear and bearing failure.

Q37. Radar vs Guided Wave Radar.

Non-contact radar sends a free-space microwave pulse and is preferred for clean, low-dielectric, or turbulent
surfaces; guided wave radar (GWR) sends the pulse along a probe and performs better with low dielectric
constant fluids, foam, or turbulence, since the signal is guided rather than free-space.

Q38. Radar vs Ultrasonic Level Measurement.

Radar is unaffected by vapor, temperature, and pressure variations and works in vacuum, making it suitable for
most process vessels; ultrasonic relies on sound through air/vapor space so is affected by vapor density,
temperature gradients, and pressure, limiting it mainly to atmospheric or low-pressure applications.

Q39. DP vs Radar Level Measurement.

DP level measurement is robust and low-cost but requires density compensation and can be affected by process
density changes; radar is largely independent of density/pressure/temperature and gives more direct, accurate
measurement, though it can struggle with very low dielectric fluids or heavy foam/turbulence without GWR.

Q40. Instrument selection for LPG storage tanks.

LPG service demands instruments rated for the storage pressure, with radar or servo gauges for accurate
custody-transfer level, redundant high-level switches for overfill protection, pressure transmitters for vapor
space monitoring, and all field instruments certified for the hazardous area with appropriate material
compatibility for LPG.

Q41. Instrument selection for LNG cryogenic tanks.

Cryogenic service (-162°C) requires instruments and thermowells rated for extreme low temperature, radar
level gauges with cryogenic-rated antennas, multi-point temperature sensors along the tank height for rollover
monitoring, and materials (stainless steel, specific elastomers) selected to remain ductile and sealed at
cryogenic temperatures.

Q42. Instrument selection for separators.

Separators typically use DP or radar for interface and total level control, pressure transmitters for vessel
pressure control, and often require multiple level taps or a guided wave radar capable of detecting the oil-water
interface directly, plus high/low level switches for trip protection.

Q43. Instrument selection for reactors.

Reactors need accurate temperature profiling (multi-point thermocouples), reliable pressure and level
measurement often with redundancy for control and safety, and instruments selected for compatibility with
reactive, high-temperature, or high-pressure conditions, with SIS-grade devices where a runaway reaction risk
exists.

Q44. Instrument selection for slurry service.

Slurry service favors non-intrusive or non-clogging technologies: magnetic flow meters for conductive slurries,
nuclear or radar level for abrasive/viscous media, and pressure transmitters with flush diaphragm seals to avoid
impulse line plugging.

Q45. Instrument selection for corrosive fluids.

6
 KBR Instrumentation Interview Prep

Corrosive service requires wetted-part materials (Hastelloy, Monel, PTFE-lined, tantalum) selected per a
corrosion compatibility chart, diaphragm seals to isolate sensitive electronics, and increased
inspection/maintenance frequency built into the philosophy.

Q46. Instrument selection for sour gas service.

Sour (H2S-containing) service requires materials compliant with NACE MR0175/ISO 15156 to resist sulfide
stress cracking, careful selection of elastomers and seals, and instruments rated for the hazardous, toxic, and
often high-pressure environment.

Q47. How do you determine transmitter range?

Range is set so normal operating point falls around 50-75% of span, with the upper range limit covering the
maximum credible process excursion plus margin, while still meeting the required accuracy at the low end of
the operating range.

Q48. How do you determine transmitter accuracy?

Required accuracy is driven by the control loop or custody-transfer requirement; the selected transmitter's stated
accuracy (including reference accuracy, temperature effect, and static pressure effect for DP) must be verified
to meet or exceed that requirement across the full operating range.

Q49. Explain material compatibility and wetted parts selection.

Wetted parts (diaphragm, body, seals) must be chemically compatible with the process fluid at operating
temperature and concentration - checked against corrosion tables/vendor compatibility charts - to avoid material
degradation, leakage, or contamination over the design life.

Q50. What common mistakes are made during instrument selection?

Common mistakes include ignoring turndown/rangeability needs, underestimating fluid corrosiveness or solids
content, over-specifying accuracy beyond what the control loop needs (adding cost), neglecting hazardous area
certification, and selecting technology based on habit rather than actual process conditions.

7
 KBR Instrumentation Interview Prep

Section 3: Control Valve Engineering

Q51. Explain the control valve sizing process.
Sizing starts from process data (flow rate min/normal/max, upstream/downstream pressure, fluid properties) to
calculate required Cv using ISA/IEC equations, checking for cavitation/flashing/choked flow, then selecting a
valve size and characteristic that gives good rangeability with the valve operating between roughly 20-80%
travel at normal flow.

Q52. What process data are required for valve sizing?

Required data includes fluid type and phase, min/normal/max flow, upstream and downstream pressure at each
flow case, temperature, specific gravity/viscosity, vapor pressure and critical pressure (for cavitation/flashing
checks), and piping size/schedule.

Q53. What is Cv?

Cv (flow coefficient) is the number of US gallons per minute of 60°F water that will flow through a valve with
a 1 psi pressure drop; it quantifies the valve's flow capacity at a given opening and is the basis for sizing
calculations.

Q54. What is valve authority?

Valve authority is the ratio of pressure drop across the valve to the total system pressure drop; low authority
(valve drop is a small fraction of the total) causes the valve to behave non-linearly and lose effective
rangeability, so a minimum authority (often ~0.3-0.5) is targeted.

Q55. Explain equal percentage, linear, and quick-opening characteristics.

Linear characteristic gives flow directly proportional to travel, suited to constant-pressure-drop systems; equal
percentage gives equal percentage flow change per equal travel increment, compensating for systems where
available pressure drop varies with flow (most common for process control); quick-opening gives maximum
flow change at low travel, used for on-off or safety applications.

Q56. What is cavitation?

Cavitation occurs when the local pressure inside the valve drops below the fluid's vapor pressure (vapor bubbles
form) and then recovers above vapor pressure downstream, causing the bubbles to collapse violently -
producing noise, vibration, and erosion damage to the valve trim.

Q57. What is flashing?

Flashing occurs when the downstream pressure remains below the vapor pressure so the vapor bubbles formed
inside the valve do not collapse - the fluid partially vaporizes and stays as a two-phase mixture, causing high
velocity erosion damage downstream rather than the pitting typical of cavitation.

Q58. What is choked flow?

Choked flow is the condition where, for liquids, cavitation/flashing limits further flow increase despite
additional pressure drop, or for gases, the velocity reaches sonic conditions at the vena contracta - beyond this
point, increasing the pressure differential does not increase flow.

Q59. How do you minimize valve noise?

Noise is reduced through low-noise trim designs (multi-stage pressure let-down, multi-hole cages), limiting
fluid velocity, avoiding cavitation by proper sizing/anti-cavitation trim, and if needed downstream silencers or
pipe schedule/insulation changes to attenuate radiated noise.

Q60. What is anti-cavitation trim?

8
 KBR Instrumentation Interview Prep

Anti-cavitation trim breaks the total pressure drop into multiple stages so that no single stage drops pressure
below vapor pressure, preventing bubble formation and the resulting erosion damage that would occur with a
single-stage trim under the same overall pressure drop.

Q61. How do you select actuator size?

Actuator sizing is based on the torque or thrust required to stroke the valve against maximum differential
pressure (including seating/unseating force), with margin (commonly 25-50%) for friction, packing drag, and
any additional force from the fail-safe spring, then matched to available instrument air supply pressure.

Q62. Fail Open vs Fail Close vs Fail Last.

Fail Open (FO) drives the valve fully open on loss of signal/air (used where blocking flow is the hazard, e.g.,
cooling water); Fail Close (FC) drives it fully shut (used where continued flow is the hazard, e.g., feed to a
reactor); Fail Last (Fail-in-Place) holds the last position, used where neither extreme is safe, requiring a lock-up
valve/volume tank.

Q63. Pneumatic vs Electric actuators.

Pneumatic actuators are faster, simpler, inherently fail-safe with a spring return, and preferred in hazardous
areas without extra certification concerns; electric (motorized) actuators don't need an air supply and are more
precise for slow-acting or on-off duty but are typically fail-in-place unless fitted with a battery/backup, and cost
more for fail-safe action.

Q64. Smart positioners and their advantages.

Smart positioners use a microprocessor to compare valve position feedback with the control signal, providing
tighter control accuracy, diagnostics (friction, hysteresis, travel deviation alarms), HART/Fieldbus
communication for remote configuration, and options like AutoTune, split range, and characterization without
physical adjustment.

Q65. Split-range control.

Split-range control uses a single controller output to drive two (or more) valves sequentially over different
portions of the signal range (e.g., 0-50% opens valve A, 50-100% opens valve B), commonly used for
heating/cooling or blending applications requiring two final control elements from one loop.

Q66. Valve stroking time.

Stroking time is the time for the valve to travel from fully closed to fully open (or vice versa); it's set by
process/safety requirements (fast for ESD trip valves, slower for smooth process control) and achieved by
selecting actuator size, air supply capacity, and appropriately sized solenoid/quick-exhaust valves.

Q67. Control valve diagnostics.

Modern smart positioners provide diagnostics such as valve signature (friction/hysteresis plots), travel deviation
alarms, partial stroke test results for ESD valves, and trend data that help detect trim wear, packing issues, or
actuator degradation before they cause a control or safety failure.

Q68. Seat leakage classes.

Seat leakage is classified per ANSI/FCI 70-2 (Class I-VI), with Class VI being metal or soft-seat bubble-tight
shutoff (very low allowable leakage), used where tight shutoff matters (e.g., ESD valves), while lower classes
are acceptable for standard throttling control valves.

Q69. Valve body material selection.

Body material is selected for pressure/temperature rating and fluid compatibility - carbon steel for general
service, stainless steel for corrosive or cryogenic service, and exotic alloys (Hastelloy, Monel, duplex) for
highly corrosive or sour service - in line with the piping material specification and NACE requirements where
applicable.

9
 KBR Instrumentation Interview Prep

Q70. IEC 60534 overview.

IEC 60534 is the international standard series for industrial process control valves, covering sizing equations
(60534-2-1), noise prediction, inherent flow characteristics, face-to-face dimensions, and testing procedures - it
is the primary reference basis for valve sizing calculations.

Q71. ISA 75 overview.

ISA 75 is the North American standard series (largely harmonized with IEC 60534) covering control valve
sizing equations, terminology, and test procedures, commonly referenced alongside or interchangeably with
IEC 60534 depending on project standards.

Q72. Control valve datasheet preparation.

The datasheet captures process conditions for each flow case, calculated Cv and valve size, body/trim material,
characteristic, actuator type and fail action, accessories (positioner, solenoid, limit switches), and
noise/cavitation check results - it is the key document issued to vendors for quotation and fabrication.

Q73. Control valve TBE.

Technical Bid Evaluation for control valves compares vendor quotations against the datasheet requirements -
verifying Cv/travel calculations, material compliance, noise levels, actuator sizing margin, accessories, and any
technical deviations - to recommend the technically and commercially compliant vendor.

Q74. Common control valve failures.

Typical failures include trim erosion/cavitation damage, packing leaks causing stem friction or emissions,
actuator diaphragm/seal failure, positioner calibration drift, and seat wear leading to excess leakage - most are
preventable with correct sizing, trim selection, and preventive maintenance.

Q75. Troubleshooting valve hunting.

Hunting (oscillation) is diagnosed by checking positioner tuning, excessive dead-band/friction in packing,
oversized valve operating near closed position, control loop tuning (too aggressive gain), or an unstable process
interaction - corrected by valve resizing, positioner retuning, or loop tuning adjustment.

10
 KBR Instrumentation Interview Prep

Section 4: Engineering Documents

Q76. Instrument Index.
The Instrument Index is the master list of every instrument tag with its type, service, P&ID reference, location,
and status - it is the controlling document that ties together datasheets, hook-ups, cable schedules, and I/O lists.

Q77. I/O List.

The I/O list maps every instrument signal to its DCS/PLC/SIS input or output channel, cabinet, marshalling
terminal, and signal type, forming the basis for system cabinet sizing and wiring/loop drawings.

Q78. Instrument Datasheets.

Datasheets specify the complete technical requirements for each instrument type - process conditions, range,
accuracy, materials, certification, and accessories - and serve as the technical basis for procurement and vendor
quotation.

Q79. Instrument Specifications.

Specifications define the project-wide general requirements for a category of instruments (e.g., general
instrument specification, control valve specification) that apply across all tags of that type, supplementing the
individual datasheets.

Q80. Instrument Location Plan.

This drawing shows the physical location of every field instrument on the plot plan, used for cable routing,
hook-up design, accessibility/maintenance review, and hazardous area verification.

Q81. Hook-up Drawings.

Hook-up drawings detail the mechanical installation of an instrument to the process (impulse tubing, valves,
fittings) and to its support/JB, standardized by instrument type and service to ensure consistent, code-compliant
installation across the project.

Q82. Loop Drawings.

Loop drawings show the complete signal path for a control loop, from field instrument through junction box,
marshalling, system I/O card, and any related control/interlock logic, used for testing, troubleshooting, and
commissioning.

Q83. Wiring Drawings.

Wiring drawings detail the physical terminal-to-terminal connections within panels, junction boxes, and
cabinets, complementing loop drawings by showing exact terminal numbers and cable cores.

Q84. Cable Schedule.

The cable schedule lists every instrument cable with its origin, destination, cable type/size, length, and routing
reference, used for procurement and installation planning.

Q85. Junction Box Schedule.

This document lists each JB with its location, the instruments/cables terminated in it, and its capacity
utilization, ensuring JBs are correctly sized and cable routing is properly allocated.

Q86. Cable Routing Philosophy.

This philosophy defines rules for cable tray segregation (power vs signal vs IS circuits), maximum fill, routing
through hazardous areas, and grounding/shielding practices to prevent electromagnetic interference and ensure
safe installation.

Q87. Instrument Installation Details.

11
 KBR Instrumentation Interview Prep

Standard installation details show generic mounting arrangements (e.g., transmitter mounting brackets,
thermowell installation, tubing supports) referenced by hook-up drawings to standardize construction across the
project.

Q88. Material Requisition (MR).

An MR is the technical package issued to procurement for a specific equipment or bulk material item,
containing datasheets, specifications, and drawings needed for vendors to quote and supply the item.

Q89. Technical Requisition (TR).

Similar to an MR, a TR bundles the technical scope and requirements for enquiry to vendors, sometimes used
interchangeably with MR depending on company terminology, focusing on the technical content needed for a
compliant bid.

Q90. Purchase Requisition (PR).

A PR is the commercial/procurement instruction, often incorporating the MR/TR technical package, that
authorizes purchasing to issue an enquiry or place an order with approved vendors.

Q91. Vendor Document Register.

The VDR (Vendor Document Register, sometimes distinct from Vendor Data Requirements) tracks the status,
revision, and due dates of every document a vendor is contractually required to submit, used to monitor vendor
engineering progress.

Q92. Vendor Data Requirement (VDR).

VDR specifies exactly which documents (drawings, calculations, certificates, manuals) a vendor must submit
and at what project milestones, ensuring the purchaser receives all data needed for engineering integration,
installation, and operation.

Q93. Technical Bid Evaluation (TBE).

TBE is the structured comparison of vendor quotations against the technical specification, identifying
compliance, deviations, and technical risk to recommend the most suitable vendor(s) for commercial
negotiation.

Q94. Vendor Drawing Review.

This is the formal review of vendor-submitted drawings/documents against the purchase specification, with
comments categorized (e.g., approved, approved with comments, revise and resubmit) and tracked to closure
before fabrication proceeds.

Q95. IFC vs IFA vs AFC document status.

IFA (Issued For Approval) is sent to the client for review/comment; IFC (Issued For Construction) is the
approved version released to the field for building; AFC (Approved For Construction) is essentially
synonymous with IFC in many companies' terminology, denoting the final approved construction revision.

Q96. How do you review P&IDs?

Instrumentation reviews P&IDs by verifying all instrument tags, control loops, and safety functions are
correctly shown with proper symbology, checking interlocks and alarm setpoints match the cause and effect
matrix, and confirming consistency with the Instrument Index and control philosophy.

Q97. How do you review Instrument Location Drawings?

Review checks that instrument locations comply with hazardous area classification, are accessible for
maintenance and calibration, avoid clashes with piping/structural steel, respect minimum cable routing
distances, and are consistent with the 3D model and hook-up standards.

12
 KBR Instrumentation Interview Prep

Q98. How do you manage document revisions?

Revisions are managed through a controlled document management system with unique revision numbers, a
revision history log describing changes, formal IDC/approval cycles for each revision, and superseded
documents clearly marked to prevent use of outdated information.

Q99. How do you close IDC comments?

Each comment is logged with an owner and response, discussed and resolved (accepted, rejected with
justification, or partially incorporated) in a comment resolution sheet or meeting, and the revised document is
reissued showing all comments addressed before final approval.

Q100. How do you ensure document consistency?

Consistency is ensured by anchoring all documents to the single Instrument Index and tag numbering system,
using standard templates, running interdisciplinary checks before issue, and periodically auditing
datasheets/drawings/P&IDs against each other and the 3D model.

13
 KBR Instrumentation Interview Prep

Section 5: Functional Safety & Control Systems

Q101. Explain SIL.
Safety Integrity Level (SIL 1-4) quantifies the required risk reduction of a Safety Instrumented Function, based
on target failure measures (PFDavg for low-demand mode); higher SIL means lower tolerable probability of
failure on demand and typically requires more rigorous architecture, redundancy, and proof testing.

Q102. Explain IEC 61511.

IEC 61511 is the process-industry-specific standard for Safety Instrumented Systems, covering the full safety
lifecycle - hazard/risk assessment, SIL determination, SIS design, installation, and operation/maintenance -
applied by end users and EPCs in place of the more generic IEC 61508 for process applications.

Q103. Explain IEC 61508.

IEC 61508 is the generic functional safety standard for electrical/electronic/programmable electronic safety-
related systems across all industries, defining the overall safety lifecycle and providing the underlying
requirements that sector-specific standards like IEC 61511 (process) build upon; it's mainly used by
manufacturers to certify SIS components.

Q104. Explain HAZOP.

HAZOP (Hazard and Operability study) is a systematic, team-based review of a process design using
guidewords (more, less, no, reverse, etc.) applied to process parameters at each node to identify deviations, their
causes and consequences, and required safeguards.

Q105. Explain LOPA.

Layer of Protection Analysis is a semi-quantitative risk assessment method, typically following HAZOP, that
credits independent protection layers against a specific hazardous scenario to determine whether existing
safeguards reduce risk to an acceptable level, and if not, what SIL is required for an additional SIF.

Q106. Explain SIF.

A Safety Instrumented Function is a specific safety function (sensor, logic solver, final element) implemented
to achieve or maintain a safe state for a specific hazardous event, with a target SIL derived from LOPA or risk
graph analysis.

Q107. Explain Cause & Effect Matrix.

The C&E matrix tabulates process causes (alarms, trips, field conditions) against the resulting effects (valve
closures, pump trips, alarms) in a grid format, providing an unambiguous specification for the
shutdown/interlock logic to be implemented in the control/safety system.

Q108. Explain Shutdown Philosophy.

The Shutdown Philosophy defines the hierarchy of shutdown levels (e.g., unit shutdown, total plant shutdown,
emergency shutdown), the causes that trigger each level, and the sequence/timing of actions to bring the plant to
a safe state in a controlled manner.

Q109. Explain Fire & Gas Philosophy.

This document defines the fire and gas detection strategy - detector types and coverage/voting logic, mapping
studies for optimal placement, and the mitigative actions (alarms, deluge activation, ESD) triggered by
confirmed detection, separate from the process ESD system.

Q110. Explain Proof Testing.

Proof testing is periodic functional testing of a SIF to detect dangerous undetected failures that wouldn't be
caught by online diagnostics, restoring the system to an as-good-as-new state; test interval and coverage
directly affect the calculated PFDavg and hence achieved SIL.
14
 KBR Instrumentation Interview Prep

Q111. Explain SIS Architecture.

SIS architecture describes how sensors, logic solver, and final elements are configured (e.g., 1oo1, 1oo2, 2oo3
voting) to achieve the required SIL, balancing safety (spurious trip avoidance) against availability, per IEC
61511 requirements.

Q112. Explain DCS Architecture.

A Distributed Control System architecture consists of redundant controllers, I/O modules, operator
workstations, engineering stations, and a redundant plant network, distributing control processing across the
plant while providing centralized operator visibility and control.

Q113. Explain PLC Architecture.

A PLC architecture typically has a central processor, I/O racks (local and/or remote), and a communication
network to HMI/SCADA or DCS; PLCs are often used for package unit control or simpler discrete/sequential
logic compared to a full DCS.

Q114. Explain ICSS.

An Integrated Control and Safety System combines DCS (process control), SIS (safety), and often F&G and
other subsystems on a common but functionally segregated platform/network, simplifying operator interface
while maintaining independence between control and safety functions.

Q115. Explain ESD.

Emergency Shutdown is the safety system function that automatically (or manually) brings the plant or a
section of it to a safe state in response to a detected hazardous condition, isolating energy/material sources and
activating protective devices.

Q116. Explain F&G.

Fire & Gas systems detect fire, smoke, or combustible/toxic gas releases using dedicated detectors and voting
logic, then initiate mitigative actions (alarms, deluge, ESD) to protect personnel and assets, operating
independently from but interfaced with the ESD system.

Q117. Controller redundancy.

Controller redundancy (typically 1oo2 hot-standby) ensures no single controller failure causes loss of control or
safety function - the standby controller continuously synchronizes with the primary and takes over bumplessly
on detected failure.

Q118. Network redundancy.

Redundant control network paths (e.g., dual fiber rings or switches) ensure continued communication between
controllers, I/O, and workstations if one network path or switch fails, preventing loss of view or loss of control.

Q119. Remote I/O.

Remote I/O places I/O modules physically close to the field devices (in remote cabinets or junction rooms)
rather than centrally, reducing cable length and cost while communicating back to the controller over a
redundant network/fieldbus link.

Q120. Marshalling philosophy.

Marshalling philosophy defines how field cables are terminated and organized before connection to system I/O
- conventional marshalling racks, or increasingly, electronic/software-configurable marshalling that removes
the need for physical marshalling and simplifies late I/O changes.

Q121. HART protocol.

15
 KBR Instrumentation Interview Prep

HART (Highway Addressable Remote Transducer) superimposes a digital signal on the standard 4-20mA
analog loop, allowing remote configuration, diagnostics, and secondary process variables to be read without
disturbing the primary analog signal.

Q122. Modbus communication.

Modbus is a simple, widely supported serial or Ethernet-based master/slave communication protocol commonly
used to integrate package PLCs, analyzers, or third-party devices with the DCS/PLC where full fieldbus
integration isn't required.

Q123. Foundation Fieldbus.

Foundation Fieldbus is a fully digital, two-way, multi-drop communication protocol allowing multiple devices
on one segment with function-block-based control that can execute in the field device itself, reducing wiring
and enabling advanced diagnostics compared to conventional 4-20mA.

Q124. Profibus.
Profibus (PA for process automation, DP for factory automation) is a digital fieldbus protocol similar in intent
to Foundation Fieldbus, popular particularly in Europe, supporting multi-drop wiring and diagnostics with a
different underlying communication and function block structure.

Q125. Ethernet/IP.
Ethernet/IP is an industrial Ethernet-based protocol (using the Common Industrial Protocol) mainly used in
discrete/factory automation and increasingly for high-speed integration of package units and system-to-system
communication in process plants.

Q126. Time synchronization in control systems.

Time sync (via NTP/GPS/IRIG-B) ensures all controllers, historians, and event/alarm records share a common
accurate timestamp, which is essential for sequence-of-events analysis after a trip or incident across multiple
systems.

Q127. Cybersecurity considerations for ICSS.

Cybersecurity follows a defense-in-depth approach per IEC 62443 - network segmentation/zones and conduits,
firewalls between IT/OT and between DCS/SIS, restricted USB/remote access, patch management, and
independence of the SIS from the DCS network to prevent a single cyber event compromising both.

Q128. Alarm management philosophy.

The alarm philosophy (per ISA 18.2/EEMUA 191) defines alarm priority classification, rationalization criteria,
setpoint rules to avoid nuisance/duplicate alarms, and target alarm rates for operators, ensuring alarms are
meaningful and actionable rather than overwhelming.

Q129. Difference between alarm and trip.

An alarm notifies the operator of an abnormal condition requiring action but takes no automatic action itself; a
trip (interlock) is an automatic action taken by the control/safety system (e.g., closing a valve, stopping a pump)
independent of operator intervention, usually to prevent escalation to a hazardous event.

Q130. Alarm rationalization.

Alarm rationalization is the systematic review of every configured alarm against documented rationale (cause,
consequence, corrective action, and time to respond) to eliminate nuisance, duplicate, or low-value alarms and
ensure each remaining alarm is necessary and actionable.

16
 KBR Instrumentation Interview Prep

Section 6: Vendor Engineering & Project Coordination

Q131. Explain Technical Bid Evaluation.
TBE is a line-by-line comparison of vendor offers against the technical specification/datasheet, flagging
deviations and technical risks, and providing a recommendation to the project (often via a compliance matrix)
before commercial negotiation proceeds.

Q132. Explain Commercial Bid Evaluation.

Commercial Bid Evaluation (led by procurement, with technical input) compares price, delivery schedule,
payment terms, and commercial conditions across technically acceptable bids to select the vendor offering best
overall value.

Q133. Vendor document review procedure.

Vendor documents are logged against the VDR, reviewed within a defined turnaround (e.g., 10-15 working
days), commented using standard status codes, and tracked to closure with re-submittal cycles until fully
approved, all recorded in the vendor document register.

Q134. Vendor deviations.

Deviations are vendor-proposed departures from the specification, submitted with technical justification; the
project engineer evaluates the impact on performance, safety, interchangeability, and cost, then accepts, rejects,
or negotiates a compromise, documenting the decision.

Q135. Package vendor integration.

Integration involves obtaining the package vendor's instrument list, P&IDs, and I/O requirements early,
aligning their control philosophy and communication protocol (Modbus/hardwired) with the plant DCS/PLC,
and coordinating FAT/interface testing before shipment.

Q136. FAT procedure.

Factory Acceptance Testing verifies the system/package (hardware, software, I/O, logic) functions correctly at
the vendor's works, following an approved test procedure covering point-to-point I/O checks, logic/interlock
simulation, and HMI functionality, witnessed by the client/EPC before shipment.

Q137. SAT procedure.

Site Acceptance Testing repeats key functional checks after installation on site, confirming the system operates
correctly in its actual environment with real field wiring and interconnections, as a precursor to commissioning.

Q138. Vendor inspection.

Inspection involves witnessing or reviewing vendor manufacturing/testing (e.g., calibration certificates,
hydrostatic tests, material certificates) at defined inspection hold points per the project's inspection and test
plan, to verify compliance before dispatch.

Q139. Package P&ID review.

Package P&IDs are reviewed to confirm the vendor's internal process matches the interface conditions (battery
limit flows/pressures), that instrumentation and safety devices meet the project's control philosophy, and that
tagging/numbering aligns with the plant's overall Instrument Index.

Q140. Vendor calculations review.

Calculations (relief valve sizing, control valve sizing, structural, electrical load) submitted by vendors are
checked for correct input data, methodology, and code compliance, ensuring the vendor's design basis matches
the project's actual operating conditions.

Q141. Coordination with Process discipline.

17
 KBR Instrumentation Interview Prep

Instrumentation relies on Process for accurate PFDs, heat and material balances, and control philosophy;
regular coordination ensures process data changes are promptly reflected in instrument selection, control valve
sizing, and SIS requirements.

Q142. Coordination with Piping discipline.

Coordination ensures instrument tapping points, line sizes for flow elements, valve orientation, and support
requirements are compatible with the piping layout and isometrics, avoiding clashes and ensuring correct
installation per hook-up standards.

Q143. Coordination with Electrical discipline.

Electrical coordination covers power supply requirements for instruments/panels, area classification alignment,
cable tray/routing segregation, and earthing/lightning protection interfaces between the two disciplines.

Q144. Coordination with Mechanical discipline.

Mechanical (equipment/rotating machinery) coordination covers vibration monitoring, instrument connections
on package skids, and integration of vendor-supplied instrumentation with the plant control system.

Q145. Coordination with Civil discipline.

Civil coordination addresses instrument support structures, cable trench/duct routing, foundation loads for field-
mounted panels, and building layout for control rooms/marshalling cabinets.

Q146. Coordination with Control Systems team.

This covers aligning the I/O list, cabinet layout, and system architecture with the instrumentation design,
ensuring the DCS/PLC/SIS configuration matches the field device list and control philosophy.

Q147. Participation in model reviews.

Instrumentation reviews the 3D model to verify field instrument accessibility, correct location relative to
piping/structures, adequate maintenance clearance, and consistency with the Instrument Location Drawing.

Q148. Participation in HAZOP.

The Instrument Engineer participates as a core team member, providing input on instrument reliability,
proposing additional safeguards (alarms, trips) where deviations are identified, and capturing action items
affecting the instrumentation design.

Q149. Participation in SIL review.

The Instrument Engineer supports the SIL determination workshop (risk graph or LOPA) by providing failure
rate data, proposed SIF architecture, and ensures the resulting SIL requirement is reflected in the SIS design and
datasheets.

Q150. Participation in client meetings.

This involves presenting engineering progress, resolving open technical queries, clarifying design intent, and
capturing client comments/action items for incorporation into the design and schedule.

Q151. Managing engineering interfaces.

Interfaces are managed through an Interface Register that tracks data exchange points between disciplines,
contractors, or the client, with clear ownership and due dates to prevent gaps or conflicting assumptions.

Q152. Engineering progress monitoring.

Progress is tracked against the MDR with weighted percentage completion per document type, compared to the
planned S-curve, with corrective actions taken when man-hour burn or deliverable issue rate falls behind
schedule.

18
 KBR Instrumentation Interview Prep

Q153. Engineering quality control.

QC is achieved through IDC, squad checks, checking/approval hierarchy (originator-checker-approver), and
adherence to project procedures and standards, supported by periodic internal audits.

Q154. Managing long-lead items.

Long-lead items (e.g., large control valves, analyzers, SIS logic solvers) are identified early in FEED,
specifications frozen ahead of the rest of the package, and enquiries issued early to protect the overall project
schedule.

Q155. Engineering schedule recovery.

Recovery involves identifying the critical path deliverables causing delay, reprioritizing resources, running
documents in parallel where dependencies allow, and negotiating scope/format simplifications with the client to
regain lost time without compromising technical integrity.

19
 KBR Instrumentation Interview Prep

Section 7: Real Project Experience (Guidance + Model Framework)

These are personal/behavioral questions - the interviewer wants YOUR real project story using the STAR method
(Situation, Task, Action, Result). Below is a model framework and the key technical points to weave in for each,
which you should replace with your own actual project details.

Q156. Describe your role in your latest FEED project.

Frame around: which unit/facility, your specific scope (e.g., led instrument datasheets and control valve sizing
for a gas processing train), the team size/structure you worked within, and one concrete deliverable you owned
end-to-end. Close with the outcome (on-time issue, cost saving, client commendation).

Q157. Describe your biggest instrumentation challenge.

Pick a genuine technical difficulty (e.g., selecting level measurement for a high-turbulence, foaming interface
separator), explain why standard solutions didn't work, the analysis/trials you did, and the resolution and its
impact on the project.

Q158. Explain a difficult instrument selection decision.

Describe a case with competing constraints (cost vs reliability vs client standard), how you gathered data,
consulted vendors/other disciplines, and justified the final choice with a clear technical rationale.

Q159. Describe a successful cost optimization.

Quantify it: e.g., 'standardized transmitter models across a unit to reduce spare parts inventory, saving X% on
procurement cost' - explain the trade-off analysis you did to confirm it didn't compromise performance or
safety.

Q160. Explain a vendor deviation you accepted.

Show your evaluation process: the deviation requested, why you assessed it as low-risk or even beneficial
(proven alternative design, no impact on interchangeability/performance), and how you documented the
acceptance.

Q161. Explain a vendor deviation you rejected.

Show sound judgment: a deviation that would have compromised safety, interchangeability, or code
compliance, your technical justification for rejecting it, and how you communicated this constructively to the
vendor and project.

Q162. Describe a difficult client comment.

Pick a comment that initially seemed to conflict with good engineering practice or schedule; explain how you
investigated, presented options with trade-offs, and reached an agreed resolution that satisfied the client's real
concern.

Q163. Describe a disagreement with the Process team.

Focus on a data or philosophy disagreement (e.g., disputed turndown requirement), how you resolved it through
data-driven discussion rather than escalation, and the final agreed basis.

Q164. Describe a disagreement with the Piping team.

A common example: instrument tap location conflicting with pipe support or insulation; describe how you
collaborated on the 3D model to reach a mutually workable solution without compromising instrument
accessibility or accuracy.

Q165. Explain your role during HAZOP.

Describe your preparation (reviewing P&IDs beforehand), your active participation flagging instrumentation-
related causes/safeguards, and how you tracked and closed out actions assigned to instrumentation afterward.

20
 KBR Instrumentation Interview Prep

Q166. Explain your role during SIL assessment.

Describe providing input on proposed SIF architecture and instrument reliability data, and how the workshop's
SIL determination fed directly into your SIS datasheets and vendor specifications.

Q167. Explain your role during design reviews.

Describe presenting your discipline's design status, defending key decisions under scrutiny from other
disciplines/client, and incorporating valid review comments into the next revision.

Q168. Explain your role during model reviews.

Describe walking through the 3D model checking instrument accessibility, clash avoidance, and correct routing,
and raising/closing action items collaboratively with piping and civil.

Q169. Describe a project that ran behind schedule.

Explain the root cause objectively (e.g., late process data, client scope change), without blame, and pivot
quickly to the recovery actions you personally drove.

Q170. How did you recover engineering progress?

Describe concrete levers used: reprioritizing critical-path deliverables, adding resources selectively, running
parallel reviews, and negotiating simplified documentation where acceptable to the client.

Q171. Describe your experience leading junior engineers.

Describe mentoring approach: reviewing their work with constructive feedback, delegating increasingly
complex tasks, and a specific example of a junior engineer's growth under your guidance.

Q172. Describe your experience reviewing vendor documents.

Describe your systematic review approach against the datasheet/specification, an example of a significant
vendor error you caught, and how it prevented a downstream problem.

Q173. Describe your experience reviewing TBEs.

Describe how you built or reviewed a compliance matrix, identified deviations, and provided a clear technical
recommendation that supported the commercial decision.

Q174. Explain a challenging control valve application.

A strong example: severe service (high pressure drop across multiple stages, cavitation risk) requiring anti-
cavitation trim and noise calculations - describe the sizing iteration and vendor collaboration.

Q175. Explain a difficult level measurement application.

A strong example: interface level in an emulsion-prone separator - describe why standard DP/radar struggled
and how you arrived at a workable solution (e.g., GWR with signal processing, or nucleonic backup).

Q176. Describe your experience with cryogenic projects.

If applicable, describe specific cryogenic instrumentation challenges you handled (material selection,
thermowell design, tank gauging) - if you lack direct experience, be honest and pivot to transferable experience
with extreme-service instrumentation.

Q177. Describe your experience with LNG or gas processing projects.

Describe specific units you've worked on, key instrumentation systems involved (custody transfer metering,
boil-off gas control, etc.), and your contribution to those projects.

Q178. Describe your experience with modular or package systems.

21
 KBR Instrumentation Interview Prep

Describe coordinating package vendor I/O and control philosophy integration, a specific interface challenge
you resolved, and lessons learned about early vendor engagement.

Q179. What is your biggest engineering achievement?

Choose one achievement with measurable impact (cost, schedule, safety, or quality) and briefly walk through
your specific contribution using STAR structure.

Q180. What engineering lesson has had the greatest impact on your career?
Pick a genuine lesson (e.g., 'always validate vendor package data early rather than assuming it will match
assumptions') and explain how it changed your subsequent working practice.

22
 KBR Instrumentation Interview Prep

Section 8: Scenario-Based & Leadership Questions

Q181. The client rejects your instrument selection. How do you respond?
Understand the client's specific concern, review the technical basis for your original selection, present
data/alternatives objectively, and reach a documented agreement - escalating only if there is a genuine safety or
code-compliance conflict.

Q182. Process conditions change after FEED approval. What documents need revision?
Revisit the Design Basis, Instrument Index, affected datasheets, control valve sizing, SIL/SIF calculations if the
change affects risk, and any P&IDs or hook-ups impacted - all managed through a formal MOC/ECN.

Q183. How would you reduce instrumentation cost by 10% without affecting safety?
Target non-safety-critical areas first: standardize vendors/models to cut spares cost, eliminate redundant non-
critical measurements, optimize cable routing/JB placement, and negotiate bulk procurement - leaving SIL-
rated safety instrumentation untouched.

Q184. A vendor cannot meet the project specification. What is your approach?
Evaluate the specific gap's technical impact, explore whether a documented deviation is acceptable, negotiate
an alternative compliant vendor if not, and escalate to the project only if schedule or cost is materially affected.

Q185. A control valve is oversized. How would you solve the problem?
Confirm the actual operating flow range against original sizing assumptions, consider re-trimming or resizing
the valve/trim, or apply a smaller valve with reduced Cv, checking authority and rangeability are restored
across the real operating range.

Q186. A package PLC uses an unsupported communication protocol. What would you do?
Evaluate options: request the vendor add a supported protocol/gateway, insert a protocol converter, or fall back
to hardwired I/O for critical signals - weighing cost, schedule, and reliability of each option before deciding.

Q187. During FAT, an analog input is not updating. What checks would you perform?
Check field simulator signal source and wiring, verify the I/O card channel and terminal assignment, confirm
database point configuration/scaling in the system, and check for a blown fuse or open circuit - working
systematically from signal source to display.

Q188. During commissioning, a transmitter reads incorrectly. How would you troubleshoot?
Verify zero/span calibration, check for impulse line blockage or trapped air/liquid, confirm wiring polarity and
loop resistance, cross-check against a calibrated reference, and inspect for process conditions outside the
transmitter's rated range.

Q189. During HAZOP, a new shutdown function is added. What deliverables must be updated?
Update the Cause & Effect Matrix, SIS logic/datasheets, Instrument Index, relevant P&ID, and if it introduces a
new SIF, run a SIL determination and update the SIS architecture accordingly.

Q190. A SIL requirement changes from SIL 1 to SIL 2. What engineering changes are required?
Reassess the SIF architecture (voting, redundancy), re-select instruments/logic solver/final elements with
appropriate SFF and certified SIL capability, update proof test intervals and PFDavg calculations, and revise all
related datasheets and SRS documentation.

Q191. How do you prioritize multiple critical deliverables?

23
 KBR Instrumentation Interview Prep

Prioritize based on critical-path impact to the overall schedule, dependency on other disciplines waiting for
your output, and any client/contractual milestone commitments, communicating trade-offs transparently to the
project team.

Q192. How do you manage engineering under schedule pressure?

Focus resources on critical-path items, use standard/proven designs to avoid rework, increase review frequency
to catch errors early rather than late, and maintain clear communication with the project on realistic timelines.

Q193. How do you mentor junior engineers?

Provide clear task context and expectations, review work with specific constructive feedback rather than just
corrections, progressively increase responsibility, and encourage them to understand the 'why' behind design
decisions, not just the 'how'.

Q194. How do you resolve conflicts within the engineering team?

Address disagreements early through direct, respectful discussion focused on technical facts, involve a neutral
third party (lead/discipline manager) if needed, and ensure the resolution is documented so it doesn't resurface.

Q195. How do you handle conflicting client and project requirements?

Clarify the underlying driver behind each requirement, look for a technical solution that satisfies both, and if a
genuine conflict remains, present the trade-offs clearly to project management/client for a documented decision.

Q196. If appointed Lead Instrument Engineer tomorrow, what would be your first priorities?
Review the current Instrument Index and MDR status, identify any open technical risks or overdue vendor
documents, meet the team to understand workload and blockers, and align with other discipline leads on
upcoming interface milestones.

Q197. What technical improvements would you introduce to the instrumentation team?
Examples: greater use of smart positioner diagnostics for predictive maintenance, standardized digital datasheet
templates to reduce errors, earlier vendor engagement for package I/O, and structured lessons-learned capture at
project close-out.

Q198. Why do you want to join KBR?

Reference KBR's strong track record in EPC/technology-led projects (e.g., LNG, sustainable technologies,
government/defense engineering), the opportunity to work on complex, high-value projects, and alignment with
your own career growth toward broader engineering leadership.

Q199. Why should KBR hire you?

Summarize your relevant technical depth (instrument selection, control valves, SIS), demonstrated project
delivery record, and collaborative approach across disciplines - tailored to the specific role you're interviewing
for.

Q200. What value will you bring to KBR's Basic Engineering team?
Emphasize your ability to produce accurate, cost-optimized FEED deliverables quickly, strong interdisciplinary
coordination skills, and a track record of catching design issues early - directly supporting KBR's reputation for
quality FEED work.

24