Do you actually like hard problems?
I spent years becoming the engineer people reached for. Now they still reach for me, but for different reasons.
(first published as a tweet: https://x.com/threepointone/status/2107387483184853153)
The thing I learned this year is that when engineers say they like working on “hard problems”, they actually don’t. What they like is puzzle solving, and having a repertoire of patterns that they can pattern match onto traditionally hard problems, usually involving databases or something with scale, etc. And they know that the industry used to pay you a lot for how deep and broad this repertoire was. Unfortunately, in 2026, well, you have a cheat code machine that has infinite breadth and depth for pattern matching. So the question is, do you actually like hard problems? Because there are now hard problems that are a complection of engineering, product, society, culture, politics, and they are fairly intractable, probably unsolvable! Because if you do want to work on those actually hard problems, there is so much money that people will pay you for it. But you’ll have to face that truth about yourself first.
addendum: I tweeted as I was reflecting over the last year. Incredibly productive year where I shipped a lot of things, but I did start feeling a little bit of emptiness. I think a lot of my personal identity came from the idea of being “that guy”, you know? If there was a hard problem or something ambitious or even something nebulous, management and people around me would be like, “let’s put Sunil on it” because I was that guy. And while I’m still the one they reach for, it’s not so much for the programming or the grinding anymore, but for a higher level of abstraction, of thinking, of approaching the problem.
But I do miss being “that guy” a lot.