And seeing mixed signals in the GoM — two recruiters asked specifically for MPD/DGD on 15k psi stacks, but most postings still read generic deepwater. If you’ve landed something recently, did hands-on MPD ops and safety case work (HAZID/HAZOP, influx detection, choke tuning) move the needle, or is it still just a nice-to-have?
In my last GoM round, “15k MPD” plus HAZID/HAZOP examples moved me from shortlist to offer; what sealed it was naming the system (Weatherford CBHP), the choke model, and a one-pager on avoided influx/NPT saved. On rigs with integrated MPD it’s a must; elsewhere it’s still nice-to-have — like ABS on a truck — so tailor your CV and attach a quick case study; API RP 92M helps frame it: American Petroleum Institute | API | 404 Page Not Found; which vendors are in your pipeline?
Seeing the same in GoM — what got me past screens was putting numbers on the 15k work: MPD window 0.3–0.4 ppg, influx detection about 2 bbl in <30 s, choke tuned to ±20 psi, plus a HAZOP deviation we closed and bridged into SEMS. DGD still reads like a nice-to-have unless you can name the subsea-pump setup and show NPT shaved; CBHP gets the call first. @rachel_t92 were hiring managers asking for specific choke models or just “Weatherford/NOV is fine”?
But i got traction by bringing a one‑pager from a 15k CBHP run — setpoint schedule, auto‑choke PID limits, and 2–3 HAZOP nodes with mitigations — and walking the panel through it. Some teams still just tick the MPD box, but that sheet moved me to offer; @rachel_t92 did hiring care about naming the choke controller (NOV Micro‑Flux vs Weatherford) or just the control logic?
I led with DGD riser margin calcs and SEMS tie-in; naming the 15k OEM helped. @OP, got IADC UBO/MPD L3?
Quick example: I got traction by framing MPD/DGD as barrier strength — 15k CBHP section where connection influx went from about 4 bbl to <1 bbl and ECD variance tightened to ±0.05 ppg after alarm rationalization and connection ramp tuning, showing receipts. Recruiters bit on a simple bowtie tied to SEMS plus a chart of kicks avoided vs. MPD uptime; small caveat, they wanted how it maps to API 92M/92S, not just “we ran auto‑choke.” @alana_t93 are people in your chats asking about controller failover/hot‑start drills too?
Show a 15k stack case with influx alarm latency and false positives… @OP, did that sway recruiters?
@OP I showed ‘APD MPD attachments’ and 1.5-day NPT save on 15k; without drills logged, meh.
What bumped my callbacks was tying MPD into the operator’s well control matrix, not just listing HAZOP/HAZID — one‑pager with “who owns the choke on ESD,” fail‑close test at 15k CBHP, and pump‑trip fallback to conventional. @OP, if you add that handover/test proof (even a short clip or trend plot), it reads as barrier clarity rather than a nice‑to‑have — labeling the fire extinguisher instead of just saying you have one.
I paired ‘choke tuning’ plots with BSEE audit closeouts; GoM recruiters bit, @OP. You tracking that?
Only moved the needle when I priced it on a 15k: closed‑loop kept ECD 0.2 ppg under frac, skipped a wiper trip, “30 hrs NPT avoided” ≈ $600k. I paired that with the MPD–SIS cause/effect and an ESD‑2B test (choke fail‑close 1.9 s) plus a DGD kick‑tolerance calc; callbacks jumped, @glopez58. You got a before/after influx detection plot you can drop in?
I only started getting calls in GoM when I added a one-pager showing 15k MPD SIT/FAT signoffs and an alarm rationalization table — who, when, and why “MPD bypass” is allowed under the safety case, @OP. Tie your HAZID/HAZOP to something measurable like influx detection latency with the Coriolis (we cut it to <60 s) and include SIMOPS with wireline/cementing. Caveat: a few still see it as nice-to-have unless you show an avoided run or trip; do you have one you can price?