GPUs

Moving from Dagster to Nvidia

Sean Lopp
2025-01-10
Picture of a paulin oh no watch

Today marks my last day at Dagster Labs and Monday will be my first day at Nvidia. It is a bittersweet change. The team at Dagster is truly impressive, and I am proud of what we’ve accomplished over the last 2.5 years. This post serves to be a reminder for both of those:

Accomplishments

I think the best “artifact” of this work is the open source Dagster demo, and perhaps my capstone of “30 days of orchestration” video series.

Team

In no particular order:

Next

So why join Nvidia? Well its an opportunity that is super hard to pass up. Re-uniting with some old colleagues, learning about a transformative technology, remote + comp.

What is this transformative tech? As the past few posts and many gists have shown, I’ve started to wrap my head around LLMs. I don’t think they will replace programmers, but I do seem them as almost a new “type” of function that is incredibly powerful and I excited to see what they enable. If we are truly close to crossing the bridge to physical systems… that woulds be monumental. For now, I am excited to have a LOT to learn (both about these models and GPU computing in general.) I am also excited to see how I adjust to “public company comp” as well as a role that is less directly in the trenches.

Last year I wrote the following about sales engineering. I think it still holds true, but for now I’m curious to see what the next chapter holds with a less known role.

My team is hiring a sales engineer!

Which might lead you to ask, what the heck is sales engineering?

If your company has ever considered onboarding a new software vendor, they’ve talked to a sales engineer. That’s the person who demos the product, answers technical questions, leads any proof of concept, and usually helps kickstart an implementation.

Why would (or wouldn’t) you want to be this person?

I started my career writing software. I enjoyed it, actually I enjoyed it too much. I was sort of like a video gamer, I would say things like “I’ll be done in an hour” and then 5 hours later I’d still be pushing commits trying to get one more error unblocked. I came home late and grouchy. Sales engineering gave me the huge dose of human empathy and encounter I needed on a regular basis to be a more balanced person while still scratching that technical itch.

You could say other roles provide that balance: engineering management, product management, even consultants. I enjoy sales engineering because it is competitive. It also doesn’t suffer from “OKR ambiguity”. You close deals, the business does well, you make money. It’s beautiful in both its simplicity and its challenge. In a startup, you get to be remarkably in tune with the health of the business, that gives you incredible leverage but it can also be a bit scary. Like any sales role, sometimes it comes down to a bit of luck, and sometimes that bad luck means you lose deals outside of your control. You get to meet a lot of interesting people and learn about how different teams do their work; unlike a consultant you’re not stressed about making every hour billable. Sometimes you do have to deal with difficult customers. 

Why would you want to be at Dagster Labs?

Dagster is a Python data orchestrator. This means you get to play with Python, dbt, Spark, CICD systems like GitHub actions, and Kubernetes. It is a blast. Some sales engineering roles are not that technical. This one is. If you want to sell data tools instead of giving demos about martech, cookie tracking, and ad conversion - this is the place. The company has a lot of things going for it that other data tooling startups don’t: the product actually exists, users enjoy it, and we know how to sell it for money. The team is also incredible. I’ve worked with lots of smart people, what is unique about Dagster Labs is that every seat on the bus has a smart person in it. A really smart person. And none of them are jerks.

Citation

For attribution, please cite this work as

Lopp (2025, Jan. 10). Loppsided: GPUs. Retrieved from https://loppsided.blog/posts/gpus/

BibTeX citation

@misc{lopp2025gpus,
  author = {Lopp, Sean},
  title = {Loppsided: GPUs},
  url = {https://loppsided.blog/posts/gpus/},
  year = {2025}
}