Natalie Rodriguez-Jackson.
I get GTM, product, and engineering to say yes to the same thing, then build the process that makes it stick. I’m an operator at heart: I find the friction, fix the workflow, and make efficiency the default. Most recently, AI programs for Copilot at GitHub.
“Build the system so the right call is the easy call.”
I'm a
I started on the support queue, which taught me where processes break and who feels it first. Then I learned to write the code, and eventually moved into running the programs that connect GTM, product, and engineering. The thread through all of it: I can’t leave an inefficient workflow alone.
GitHub / Microsoft
Sr. Program Manager, Technical · CoreAI
Jersey City, NJ
ET / UTC−4
When to call me in.
I usually get pulled in at one of two moments: a process has stalled, or a big initiative needs several teams pulling in the same direction.
Untangle the process
I start with the teams doing the work and trace every handoff until I find where things stall. Then I redesign the flow, and when a manual step keeps tripping people up, I automate it myself.
Took a feedback SLA from 52% to 92%Line up GTM, product, and engineering
For launches and programs that cut across teams with competing priorities, I define who decides what, set a steady operating rhythm, and keep one plan everyone can see.
Aligned 25+ stakeholders on Model Gating for CopilotThe work, measured.
Nominated ARR
Tied to the High Priority Feedback system I built from scratch
SLA Attainment
After building the HPF automation suite
Priority Changes Shipped
In 18 months, through escalation paths I designed
Engaged Community Users
Monthly, after growing the GitHub community program
Enterprise Signals
Connected to product roadmaps through HPF
Issues Matched by AI
Processed live by Matchy Matchy, with human review
Stakeholders Aligned
Across Engineering, Product, and Legal for Model Gating
PMs Using Unwrap
After I scoped and launched it across GitHub and Microsoft
Program rigor, with engineering depth.
Program Management
Cross-org programs with clear owners, cadences, and decision records, including Model Gating for Microsoft Copilot.
AI Governance
The Limited Access Framework: restricted-capability access agreed across legal/CELA, Responsible AI, and engineering.
Voice of Customer
High Priority Feedback: automated triage and routing that lifted SLA attainment from 52% to 92%.
Engineering Depth
Former engineer in Rails, Python, and GraphQL. I build automations myself with GitHub Actions and LLMs.
Product Operations
Operating models, planning rhythms, tool stacks, and reporting that keep product teams moving.
Applied AI Tools
I prototype AI tools hands-on, like Matchy Matchy, which matches customer feedback to existing issues using Azure AI Search and MCP.
The details I obsess over.
Good operations are mostly invisible. These are the small things I pay attention to so the big things don’t break.
Earn adoption gradually
Pilot with one team, learn, then expand. People adopt a new process faster when it’s proven before it’s mandated.
Numbers people believe
If a dashboard doesn’t match what teams see day to day, nobody acts on it. I reconcile the data with reality first.
One vocabulary
Every program gets named owners and agreed definitions, so “launch” and “priority” mean the same thing to GTM, product, and engineering.
Simple on the surface
However complicated the system underneath, the steps people actually follow should fit on one page.
Plan for the exceptions
Urgent escalations, blocked approvals, orphaned handoffs. I map how things fail before I map how they should work.
Make invisible work visible
I look for the copy-pasting, chasing, and spreadsheet wrangling people do to keep things afloat, then remove it. I started in support, so I know where to look.
↓
Thinking out loud, and building in public.
When I'm not running programs.
Let's build something.
I’m open to roles in product, product and business operations, and program management. If your team needs GTM, product, and engineering working as one, I’d love to hear from you.