AI policy for GTM engineer interviews

• 02 A funnel you own is leaking between acquisition and activation. What are the first three things you do? Whether the first reflex is diagnosis or tooling

  Follow up with

  • What would change your mind about where the leak is?
  • When would you conclude the targeting is wrong rather than the funnel?

  Strong answer

  A strong candidate treats the stated leak as somebody's hypothesis and starts by asking what it is based on. The first move is questions rather than actions: which segment is leaking, whether it has always leaked or started recently, and whether the activation event is instrumented well enough to say. They usually get to whether the people arriving were the right people at all, which moves the problem out of the funnel and into targeting.

  Weak answer

  A weak candidate accepts that the leak sits between acquisition and activation because the question said so, and answers with tools they would add: a session recorder, a warehouse, a dashboard. Nothing in the three moves would tell them the premise was wrong.

• 03 You are handed a cold-email domain that also needs to run the team's day-to-day mail. How do you set it up? Whether deliverability knowledge is operational or repeated

  Follow up with

  • What does the warmup ramp look like week by week?
  • At what daily volume per inbox does placement start to tilt?

  Strong answer

  A strong candidate stops on the premise, because a domain's MX records point at one provider and the setup as described does not exist. They separate the sending domain from the corporate one, usually a lookalike that redirects, and only then talk about authentication and the ramp. Ask for the ramp week by week and they give you weeks and numbers rather than a principle.

  Weak answer

  A weak candidate takes the premise at face value and starts configuring inboxes and warmup on the corporate domain. The conflict is sitting in the question, and reciting a sound warmup ramp on top of it does not make the domain safe to send from.

• 23 Your CRM says a campaign produced 40 opportunities. The attribution report says 12. Where do you look? Whether they reach for definitions before dashboards

  Follow up with

  • Which of the two would you take to the board, and why that one?
  • What would you write down so this stops recurring every quarter?

  Strong answer

  A strong candidate goes at the definitions before either system, because both numbers can be right under their own rules: which object counts as an opportunity, what window, first touch or multi-touch, how duplicates were merged. They will ask what the number is for before choosing which one to take to the board. A good answer ends with the rules written down where both teams read them, since this argument returns every quarter.

  Weak answer

  A weak candidate assumes one of the two systems is broken and starts checking the integration. A gap between 40 and 12 is wide enough to be a definition rather than a sync failure, and that possibility never gets raised.

• 24 A vendor returned garbage for yesterday's enrichment run and you need to re-run it. How do you do that without duplicating rows or paying for the same records twice? Whether re-running a job is routine for them or something to avoid

  Follow up with

  • What happens if the re-run dies halfway and you start it again?
  • How do you prove afterwards that the day is now correct?

  Strong answer

  A strong candidate replaces the affected day rather than appending to it, and makes the write idempotent on a stable key so running it twice lands the same rows. Ask what happens when the re-run dies halfway and the answer is that they start it again, which is the point of having built it that way. Expect a concrete check that the day is now right, usually a count plus a sample compared against what the vendor returned.

  Weak answer

  A weak candidate deletes rows by hand, or re-runs the job and plans to clean up the duplicates afterwards. The question names both costs it is protecting against, and paying the vendor a second time for records already bought does not come up.

• 25 A sequence that was replying at four percent drops below one in a week. Nothing about the copy changed. Walk me through it. Whether they reach for infrastructure or for rewriting

  Follow up with

  • What do you check before you touch the copy at all?
  • How would you tell a placement problem from a list problem?

  Strong answer

  A strong candidate uses the sentence about the copy, and treats copy as the last suspect precisely because it did not change. They go at delivery first: authentication, domain reputation, a seed test, and whatever else moved that week in volume, provider or list source. Expect them to hold the answer open, since an unchanged-copy collapse can be placement, a worse list, or a shift in who is being mailed, and a week is not long enough to have separated those.

  Weak answer

  A weak candidate starts rewriting subject lines, which the question rules out in advance by saying nothing about the copy changed. Or they blame list quality without first establishing whether the mail is arriving at all.

• 26 Inbound demo requests are reaching a rep 30 hours after they come in. The SLA is five minutes. Where do you look first? Whether they can decompose a routing path in order

  Follow up with

  • How do you tell a routing failure from an ownership failure?
  • What would you put in place so you knew the next time it slipped?

  Strong answer

  A strong candidate walks the path in order and says it out loud: form submission, record creation, assignment rule, queue, notification, whether a rep was awake. Thirty hours against a five minute target is a stop somewhere rather than slowness everywhere, and they are hunting for the step where the clock parks. What they want afterwards is a timestamp at each hop, so the next slip shows up as a number rather than as a complaint.

  Weak answer

  A weak candidate proposes a new routing tool, or decides the reps are ignoring their alerts, before knowing whether the lead reached one. The gap in the question is wide enough to locate precisely, and nothing in the answer would locate it.

• 27 You are four days into a test of a new outbound sequence, the variant is replying 30 percent better, and a VP wants it rolled out to the whole list on Monday. What do you say? Whether they can hold a line on evidence without stonewalling

  Follow up with

  • What had you agreed before the test started?
  • What would make you happy to call it early?

  Strong answer

  A strong candidate explains in plain language why a four-day read moves around, without leaning on the word significance, and goes to what was agreed before the test started, including the case where the answer is nothing. Then they give the VP a route: what they would need to see to call it on Monday, or a partial rollout that keeps the test alive. Expect them to say what would make them happy to call it early, because sometimes the gap is wide enough and the downside small enough.

  Weak answer

  A weak candidate concedes on the spot because a VP asked, or lectures about sample size and offers nothing the VP can act on. Either way the person who has to decide on Monday leaves with the options they walked in with.

• 28 A prospect receives four emails in one day from four different systems. How do you stop that happening again? Whether they fix the instance or the architecture

  Follow up with

  • Which system should own the decision to send, and why that one?
  • How would you make the next tool somebody buys inherit the rule?

  Strong answer

  A strong candidate reads four systems as the problem rather than four emails, and puts the decision to send behind one arbiter holding suppression and frequency for all of them. They will name which system that should be and why, usually the one every tool already syncs through. The harder half is the second follow-up, and a good answer says how the next tool somebody buys inherits the rule instead of routing around it.

  Weak answer

  A weak candidate turns off the offending campaign, or proposes a standing meeting between the teams that own the four systems. The question asks how it stops happening again, and a fifth system could be bought next month under either answer.

No question carries that tag.