Jan Call Prep: Nue Enablement Content Developer
- Role: Enablement Content Developer, Toronto, CA$80-95K
- Interviewer: Jan, Head of Enablement
- Format: 45 minutes, likely video
- Jan’s team structure: Content (this role) upstream of Partner Enablement Lead (delivery) and Enablement Technical Support (Bogota)
- Her explicit bet: AI-driven content workflows, Claude is named in the posting
- Her audience: Implementation, services, and sales partners (not end customers)
- Your anchor sample: garyhills.dev/nue
Opening: First 90 Seconds
OPEN When she says “tell me about yourself” or equivalent.
“Thanks for making the time, Jan. Quick version: I am an instructional designer with nine years at VMware building enablement content for NSX, which is a complex enterprise software product that had to land with both technical implementers and business decision-makers. Since leaving VMware I have been consulting independently on SaaS customer education and AI-driven content workflows, which is what drew me to this role.
A few things about the way I work that seem relevant to what you are building. I think in reusable systems, not one-off artifacts. I use Claude daily as part of my content pipeline, with real validation gates. And I have a technical background that lets me go deep with product and engineering without needing translation.
I am genuinely interested in the content role specifically because of how you framed it: AI-leveraged, upstream of partner delivery, shipping against release cadence. That is the work I want to be doing. Happy to go wherever you want to take this.”
Notes. 90 seconds max. Avoid full career chronology. Three credibility claims: reusable systems, Claude with validation, technical depth. Last line hands her the mic.
Core Stories (condensed for fast recall)
🎯 AI WORKFLOW (InsightSoftware Power ON)
InsightSoftware needed two Rise 360 courses for Power ON, their Planning and Write-back tool for Power BI. 16 lessons across Admin and End User courses, 5-month estimate, 3-month deadline.
Compress the timeline by 40 percent without sacrificing accuracy, since learners were writing data back into live Power BI datasets.
Built a Claude-assisted workflow with four stages: drafting first-pass content from SME source material, restructuring it into learning objectives, writing knowledge checks, and converting SCORM XML for import into the target LMS. Every draft went through three validation gates: live Power ON testing, SME review, and a second-reviewer pass. Caught a renamed feature that would have shipped with the old terminology.
16 lessons shipped in 3 months instead of 5, with no drop in accuracy and faster reviews because objectives were locked early.
Claude accelerates drafting, but the leverage is only safe inside a workflow with real validation gates.
🎯 NUE BATTLE CARD (anchor for “walk me through something you built”)
Preparing for this conversation, I wanted to show not just that I can write enablement content, but that I understand where Nue’s GTM opportunity sits right now.
Build a sample battle card that AEs could actually use in a discovery call, in a format Nue’s partner channel could adopt and extend.
Identified the Salesforce CPQ End-of-Sale announcement as Nue’s biggest competitive opportunity. Built a field-neutral battle card with AE talk tracks, trap avoidance notes, a six-dimension comparison table, and sample proof points. Built it as a reusable template: same structure works for any competitive objection by swapping in the competitor, the strategic weakness, the three objection handlers, and the comparison dimensions.
A working sample at garyhills.dev/nue that demonstrates both the craft (battle card content) and the system (reusable template that scales across competitive situations).
The artifact is one battle card. The system is a template. That is the leverage behind “reusable templates and scalable content systems.”
🎯 RELEASE CADENCE (NSX 4.0)
NSX 4.0 major release at VMware. Content team had two weeks from code freeze to GA to ship updated certification curriculum, labs, and technical documentation aligned to the new release.
Land all release-aligned enablement content on or before GA, without cutting corners on lab accuracy.
Coordinated directly with the Product Manager on feature changes, breaking changes, and what needed new content versus what could be updated in place. Used VMware Cloud Foundation APIs to programmatically deploy and tear down hands-on lab environments, turning a multi-day manual lab build into a repeatable, automated workflow. That freed up time to focus on content accuracy and validation rather than infrastructure setup.
Content landed on time for GA. The API-driven lab deployment approach became the standard pattern for subsequent NSX releases, compressing lab build time for every release that followed.
Automating the infrastructure layer is what makes release cadence sustainable. Manual lab builds do not scale with a product release rhythm.
Behavioral Stories (from main STAR prep)
⭐ FAILURE / ACCOUNTABILITY
Early in my career as a network engineer, I made a production change outside of change control under pressure to move quickly, which resulted in a service outage.
Immediately acknowledged responsibility, informed my manager, focused on restoring service as quickly as possible, and clearly communicated root cause so other teams were not pulled into unnecessary troubleshooting.
Service restored quickly, issue contained.
Process is there to protect outcomes. I now prioritize structured approaches and validation, especially under pressure.
⭐ PUSHBACK / ALIGNMENT
Stakeholder wanted content at admin or expert level; actual learners needed a foundational, user-level experience.
Initiated a discussion around what success looked like and what the learner needed to do. Anchored the conversation in learner outcomes instead of content preference.
Team aligned on the appropriate level. Final course became more usable and effective.
Effective pushback is about reframing decisions around shared outcomes.
⭐ TRUST BUILDING
Joined a project where the client had low confidence due to inconsistent prior delivery.
Introduced clear timelines, checkpoints, early draft visibility, and tight feedback loops. Explicitly showed how feedback was incorporated.
Client became more engaged. Moved faster with fewer revisions.
Trust is built through consistent, transparent execution over time.
⭐ INFLUENCING WITHOUT AUTHORITY
SaaS training where the system was prone to user error, without direct authority over curriculum design.
Introduced a troubleshooting section with realistic failure scenarios based on hands-on testing. Framed as reducing learner frustration, not critiquing original design.
SMEs saw value immediately. Approach extended across additional modules.
Influence comes from identifying real friction and offering practical solutions.
⭐ INITIATIVE / GROWTH
At VMware, noticed recurring patterns where customers struggled with complex NSX concepts.
Started a blog breaking down complex topics into clear, simplified explanations.
Blog gained traction, led directly to a technical content role without formally applying.
Growth comes from creating value before being asked.
Handling Likely Concerns
PREP Three concerns Jan is most likely to raise. Do not memorize word-for-word. Know the shape of each answer.
❓ “I am worried you are not deep enough on CPQ or SaaS sales motions”
“Fair. My CPQ depth is what I have built in the last few weeks, including the battle card. What I bring is nine years of building enablement content for enterprise software with mixed audiences, which is the harder half of the problem. I ramp fast on domain, and I would expect to be conversational on Nue CPQ within a month and genuinely fluent in three.”
❓ “I am worried this is a level mismatch” (over-leveled)
“I am specifically looking for an IC role where the work is the work, not a management track. What you described in the posting is what I want to be building. I have had enough time at the Staff level at VMware to know I want to build things, not run meetings about building things.”
❓ “I am worried this is a level mismatch” (under-leveled)
“Hear you. Let me point to two things that demonstrate senior judgment. First, the battle card I built is a template, not an artifact. That template thinking is what makes a senior IC valuable. Second, at VMware I automated lab deployment via the Cloud Foundation API for NSX 4.0, which turned a two-week release scramble into a repeatable pattern. That kind of systems thinking is what I would bring here.”
❓ “Why full-time now after consulting?” (the leave-risk question)
“The reason I am looking at full-time SaaS enablement specifically is that consulting forces me to reset context every few months, which means I never get to go deep on one product, one set of partners, or one team. The work I want to be doing compounds over years, not sprints. That is only possible in a full-time role at a company where the product and the partners are worth investing in.”
Note to self: Do not say “tired of searching for work.” True but wrong framing. She hears “will leave the moment consulting market picks up.” The compounding framing lands better.
❓ “Walk me through something you built”
Default answer: the Nue battle card. 90 seconds.
“The battle card at garyhills.dev/nue. I built it because Nue’s biggest competitive opportunity right now is the Salesforce CPQ End-of-Sale window. AEs in that conversation need a talk track, a trap to avoid, and a comparison they can pull up in a discovery call. I built all three. But the more important thing is that I built it as a template: swap in the competitor, swap in the strategic weakness, swap in the three objection handlers, swap in the comparison dimensions. The artifact is one battle card. The system is a template that scales across any competitive situation at release pace.”
Questions to Ask Jan
Top Three
- The posting is explicit about AI-driven workflows. What has Nue tried so far, what has worked, and what has not? I want to understand whether you are building this from scratch or improving something that exists.
Opens the most interesting conversation. Shows you see AI as an engineering problem, not a buzzword.
- Content sits upstream of partner delivery and technical support. Where do you see the hand-off friction points in the first year, and what would make this role succeed inside that system?
Signals you have read all three of her postings and understand her team structure. Sharpest “I did my homework” question.
- Six months in, what does success look like for this role from your perspective?
Her answer tells you what she will actually measure, which is often different from the JD.
Backup Questions
- What is Nue’s release cadence, and how much lead time does Product give Enablement on feature releases?
Shows you think about shipping rhythm as structural.
- You used the phrase “reusable templates and scalable content systems” in the posting. What does that look like in practice at Nue today, and how much is already built versus something you want this role to build?
Pulls her language back at her. Tests whether she has a clear vision for the content engine.
- What kind of content does Nue’s GTM team wish existed today that does not?
Flips the dynamic. Her answer tells you what the team actually needs.
Avoid
- “Who are the reviewers and approvers in a typical content cycle?” (Too operational for first conversation)
- “What are the team’s OKRs?” (Too corporate-process)
- “When will I hear back?” (Sounds needy. Ask “what is the timeline?” instead)
Closing
CLOSE When she says “anything else?” or starts wrapping.
“One thing I want to leave you with. The pattern I keep seeing in enablement roles at SaaS companies your size is that the content person becomes the bottleneck for everything else the function wants to do. My whole approach is built around not being that bottleneck: Claude-assisted drafting with real validation, templates that scale, infrastructure that automates the parts humans do not need to touch. I built the battle card the way I did to show that thinking, not just the output.
Practical question: what are the next steps, and what timeline are you working to?
And one personal ask: if there is anything in my background you are uncertain about, I would rather hear it now than guess at it later.”
Note to self. The last line is the power move but only works if you can handle the answer. If she raises a concern, do not freeze. The three prep answers above cover the most likely ones.
Pre-Call Checklist
- ✅ LinkedIn profile updated (headline, About, employer field, Featured post)
- ✅ Battle card live at garyhills.dev/nue
- ✅ STAR prep page updated for Nue
- □ Re-read Jan’s JD one more time 30 minutes before call
- □ Have garyhills.dev/nue open in a browser tab during call
- □ Have this page open in another tab
- □ Water, notebook, pen within reach
- □ Camera angle and lighting checked
- □ Phone on silent
Closing Principles
- 90 seconds max on the open. Hand her the mic early.
- Name Claude specifically, not “AI.” She named Claude in the JD.
- Reusable systems, not one-off artifacts. Her language. Mirror it.
- Battle card is the anchor. If in doubt what to reference, reference it.
- Defensible beats impressive. No ERP. No 15 years of awareness training. Do not stretch.
- Ask her what concerns her. Surface the objections, do not let them sit.