who is Jamie?

I keep landing in roles that sit between deep technical detail and human outcomes. The pattern is not accidental.

I work in the space where technical systems meet the people who use them, enablement, trusted advisor work, and customer-facing programs that hold up at scale. My career spans technical support, five-plus years as Cloudflare’s first Technical Trainer, and more recent time in data platforms at Snowflake and DataStax. Customer-facing work is where technical depth and human clarity both come into play, live conversations, partner enablement, and the moments where a product earns trust or loses it.

LinkedIn →

Behind that, I have spent many years building training programs, career paths, and policy that actually helps teams, so the people on the front line are set up to represent the product well. I still gravitate toward trusted advisor work on process and advocating for changes customers and partners can feel, not just a slide deck.

Running my own hosting and security company in the UK meant living in client-facing delivery: clear communication, scope, and follow-through when incidents do not wait. It still informs how I think about reliability, trust, and what “good service” feels like from the other side of the table.

Before I moved into training, I spent two years as a Technical Support Engineer, pure customer-facing work at the point of pain. That role trained empathy, technical curiosity, and troubleshooting across the stack, with a strong lean toward security. I moved into training because I was already helping colleagues, it wasn’t a leap, it was a continuation.

At Cloudflare, I was the first Technical Trainer and stayed in that space for over five years. I created and scaled programs, targeted launches, ongoing career paths, and technical leadership tracks, and spent a huge share of my time in the room with people who would go on to support or sell to customers: instructor-led training for internal teams and external partners across North America (NAMER), with partner and customer outcomes in mind.

After Cloudflare, I joined Snowflake, where I built a solid grounding in modern data platforms: data lakes, Apache Iceberg, and the surrounding ecosystem. The same lens applied, how organizations adopt, connect, and operate in production, because that is what shows up in real customer conversations. My time at Cloudflare had already tuned me to how the internet behaves end to end; that perspective carried through when learning how client connectivity, private networking (including VPCs), and the path from application to data plane shape how data is reached and governed.

I then moved to DataStax. During the hiring process, the company was acquired by IBM, a sharp reminder of how quickly the industry shifts. The breadth of what I learned earlier continues to pay off as I go deeper into Cassandra, DataStax Enterprise (DSE), Astra DB, and the wider DataStax portfolio, always with an eye on how those choices land when a customer is trying to ship. That through-line holds in customer-facing moments most of all, enablement, advocacy, and the quality of experience when it counts.

Across companies, the through-line has been the same: turn complex products into clarity that sticks, so colleagues, partners, and customers get straight answers and a steady experience.

Understanding individuals and meeting them where they are is one of my strongest levers, whether that is a teammate, a partner, or a customer on a tough day. I care about career growth and about helping people see their own trajectory clearly, not just completing a course.

Content that starts from real constraints ¶

I have owned wikis and runbooks, built LMS courses, and advised on policy for support and technical audiences. The content I shipped always started from real frontline constraints, the same questions that show up in tickets, calls, and partner sessions, not idealized process diagrams.

I keep learning in public: labs, hands-on material, and projects that raise the floor for the team, especially for people who will soon be customer- or partner-facing.

At Cloudflare, I ran the first months for new hires, expectations, schedules, and KPIs, so onboarding was structured without feeling mechanical, and so new hires were credible in front of customers and partners sooner.

×
Page views: …