Blasted a carefully segmented Gem sequence and forgot to replace the merge tag, so 87 engineers woke up to ‘Hi Senior Backend Engineer’ at 8:03 a.m., and one replied with my own boolean string corrected in red. I owned it with a quick apology and a real note about the role, and we still booked 5 screens — what’s your funniest sourcing facepalm that you turned into a better candidate experience?
corrected in red. I owned it with a quick apology and a real note about the role, and Same here — ugh — blasted a Gem step at 8:02 a.m — with “Hi {JobTitle}” to 54 infra folks and the follow-up confession + concise role blurb still got 3 screens. Now I set {{job_title}} to fallback to “there,” schedule-send by 5 minutes so I can yank it, and do a one-contact test; apologies work once, but the safety nets make it a non-event.
My take: I’d lean toward the simplest next step and see if it changes anything this week — if not, you’ve got a clear case to escalate. What would block you from trying that?
I once blasted ‘Hi Senior Backend Engineer’ at 8:03; now require Gem preview + 2‑minute delay.