who is Jamie?

I keep landing in roles that sit between deep technical detail and human outcomes.

I work 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 work in data platforms at Snowflake and DataStax. Customer-facing work is where technical depth and clear communication both matter: live conversations, partner enablement, and the points where a product earns or loses trust.

LinkedIn →

Behind that, I have spent years building training programs, career paths, and policy that actually help 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, advocating for changes customers and partners can feel rather than another slide deck.

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

In that same UK period I was Head of Web Development & Infrastructure at mendmyi, running a team of engineers spread across the globe. I kept projects on track while staying hands-on in the build: bespoke CMS work for stock control, an employee workflow portal, the customer-facing site, and private portals. That is where the management muscle got built, and it is the part I leaned on hardest when I became Cloudflare’s first Technical Trainer.

Before I moved into training, I spent two years as a Technical Support Engineer. Pure customer-facing work at the point of pain. It built empathy, technical curiosity, and troubleshooting across the stack, with a strong lean toward security. I moved into training because I was already doing it for colleagues.

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

After Cloudflare I joined Snowflake and built a grounding in modern data platforms: data lakes, Apache Iceberg, and the surrounding ecosystem. The same lens applied as always, how organizations adopt, connect, and run things in production, because that is what shows up in real customer conversations. Cloudflare had already tuned me to how the internet behaves end to end. That carried over into 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. The breadth of what I picked up earlier keeps paying off as I go deeper into Cassandra, DataStax Enterprise (DSE), Astra DB, and the wider portfolio, always with an eye on how those choices land when a customer is trying to ship. The through-line holds in customer-facing work most of all: enablement, advocacy, and the quality of the experience when it counts.

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

Reading individuals and meeting them where they are is one of my strongest skills, whether that is a teammate, a partner, or a customer on a bad day. I care about career growth and helping people see their own trajectory, not just finishing 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 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. The aim was structure without the mechanical feel, and new hires who were credible in front of customers and partners sooner.

×
Page views: …