1 min lesson
Generalize it into a primitive
For each case in "Generalize it into a primitive", name the signal and the response you would use.
Step 1 of 2
Generalize it into a primitive
The role wants durable infrastructure, not a one-off. The pricing-page flow is really a generic primitive - trigger → resolve → enrich → score → route → act → measure - and swapping the trigger and the action reuses everything in between.
Trigger: applies / hits a usage milestone.
Action: program invite + onboarding.
Same enrich → score → route spine.
Trigger: extension install or repo signal.
Action: community / docs nudge.
Reuse the scoring and routing core.
Trigger: partner-sourced lead.
Action: co-sell routing with walled data.
Same primitive, permissions tuned.
Close a whiteboard answer by collapsing your specific flow into the generic primitive and showing two other programs it serves by swapping only the trigger and action. That single move answers the unspoken question behind the whole loop - can this person build infrastructure that outlives one campaign - which is exactly what "GTM Engineer, not marketing ops" means.
Learn more
Optional practice