Sign In

Case Taintor

Senior Director, Klarna Engineering Platform

Case Taintor is a Senior Director of Developer Services at Klarna, a prominent figure in the tech industry with extensive experience in software engineering and leadership.1

Education and Background

Case holds a Bachelor of Science in Computer Engineering from the University of Virginia, completed between 2002 and 2006.1 He further advanced his education by earning a Master of Science in Computer Science from The Johns Hopkins University in 2007-2008.1

Career Progression

Case Taintor's professional journey includes:

  1. Early career roles:

    • Computer Engineering Intern at the Naval Research Laboratory (2004)
    • Research Assistant at the University of Virginia (2005)
    • Software Engineer at Boeing (2006-2009)
  2. Mid-career experience:

    • Software Engineer and Independent Contractor at Rosetta Stone (2009)
    • ScrumMaster and Tech Lead for Rosetta Stone Manager (RSM)
  3. Klarna career:

    • Joined Klarna in 2012 as a Software Engineer Team Lead
    • Progressed through various roles including Software Architect and Acting Chief Architect
    • Currently serves as Senior Director of Developer Services12

Expertise and Contributions

At Klarna, Case has been instrumental in several key initiatives:

  • Developed and launched a consumer payment portal
  • Implemented a RESTful API for e-commerce partners
  • Led improvements in reporting capabilities and strategies to handle larger user volumes1

Case is known for his passion for work, dedication, and consistent production of quality software.3 He has also been involved in leading exercises for Klarna's peak season preparations, collaborating with networking and security teams.5

Personal Interests

Outside of his professional life, Case describes himself as an outdoor enthusiast and traveler4, indicating a well-rounded personality that extends beyond his technical expertise.

Highlights

May 25 · linkedin

We drop suppliers who lack an interest in Klarna’s long term success.

Metric cardinality is an often misunderstood limitation of most metric platforms. Each additional permutation of metric tags can blow up your observability budget and the most frustrating part of watching your money burn is knowing your supplier could help if they only cared about your long term success. Instead, many suppliers think (mistakenly) that their product is sooo good that you’ll happily continue to burn money for the pleasure of using their product. Unfortunately no product is that good. Eventually the lack of alignment on mutual success catches up to the supplier and boom goes the dynamite. Some of my proudest days at Klarna have been the days we turned off an expensive-yet-unused APM provider (2019) and when we stopped running a not-so-customer-focussed & extremely expensive log provider (2022). This has minimized my negotiations with companies that clearly felt short term gains were worth risking longer term benefits.

Maybe it’s a sign of the times but it’s intriguing to me that some companies are actually seeing this commitment to mutual and long term success as one of their differentiators. If only all of our suppliers understood this. Oh well. They’ll learn (hopefully by changing their habits but more likely they’ll learn the hard way). Smart investors understand that short term gains are fleeting while developing longer term, mutually beneficial customer relationships yield much better results (think Amazon and Spotify who lost money for many years before yielding positive results for investors).

Why did I think about this? I looked up tools to systematically deal with metric explosion and found at least one observability company seems to get it. I then prioritized discussing expanding our existing relationship with them and learning about their offering and roadmap. Truth is - we hadn’t looked at their full observability offering in four years, when it was quite immature. Today is different.

Refusing to provide transparency on metric waste is just one example of how observability suppliers find themselves with a great product yet customers who are still highly motivated to GTFO. Other practices I’ve seen: • Complicated billing schemes which tie us to pre-purchasing individual products, making us think twice about shifting our money to products with the same supplier that drive more value for us. • Billing schemes that make us pay list price for overages. I’m sorry, what? Again – I spend millions of dollars with you and you really want my first thought when we use more of your product is “man, we’re getting fleeced!”

Do you have any examples of observability companies whose corporate values, contract terms and products are designed for long term relationships? Feel free to drop them in the comments.

Mar 8 · linkedin

Observability is really coming into focus at Klarna and proving its value. Years ago there was only really one provider that gave global visibility for a company of our size. Building it ourselves was also incredibly challenging with poor results. But what happens when that one provider has a global outage?

It’s a different world today though. There are now a handful of providers that have proven to work for an environment of our size and complexity. Happy our continuing and improving investments over the past years in standardization give us the flexibility to more easily gain from these innovative providers while reducing vendor lock-in.

#standardization #observability

Related Questions

What are some of the key projects Case Taintor has led at Klarna?
How did Case Taintor's role evolve from Software Engineer to Senior Director?
What specific technologies or tools does Case Taintor specialize in?
Can you provide examples of Case Taintor's contributions at Boeing and Rosetta Stone?
What are the main challenges Case Taintor has faced in his career?
Case Taintor
Case Taintor, photo 1
Case Taintor, photo 2
Add to my network

Location

Greater Stockholm Metropolitan Area