In my experience, knowing tech in a tech world is useful. Knowing tech in a non-tech world is a burden, because it implies a focus on something that doesn't mat

In my experience, knowing tech in a tech world is useful. Knowing tech in a non-tech world is a burden, because it implies a focus on something that doesn't matter. I was a developer for the first 4 years of my career, but I've spent the last couple years doing sales and marketing. It turns out a really enjoy them, and my technical background has been enormously helpful while working at a technical company. For me, my technical knowledge is now domain expertise: I understand what our customers have to put up with, and I understand why our solution [1] will help them. My day-to-day is decided non-technical, and I intend to spend fewer and fewer hours writing code. In short, I'm interested in working in technology forever. I'm interested in it as an industry, because I like the problems there, but not as a profession, because I don't like the altitude of problem-solving when you're the one writing the code. I don't know you well enough to tell you what to do, but it's worth separating what you enjoy day-to-day and what you enjoy about the mission of the place you work, and figuring out how much each one motivates you. I enjoy the day-to-day aspects of marketing and product marketing enough, but I love being part of a company that I feel solves a real problem using cool technology. My question for you: if you like explaining technology to people, is it because you like working on the story, or you like the personal connection?