I was a web developer for a few years out of college, but I eventually realized I got much more pleasure out of helping my colleagues solve challenges in their own work (obscure bugs or browser compatibility issues) than building my own assigned pages and apps. I transitioned to technical product/developer support engineering which I've now done at two companies for a combined six years or so, and it's been great.
There's definitely more interaction with people, as your day-to-day work is more about helping people succeed than building things. But you still use a lot of the same skills you've built up in development work - especially if you've spent any time debugging code.
Whether this will appeal to you depends on what motivates you. For me, I really like feeling like I've made a difference and one of the most powerful ways to get that feeling is to solve a problem for someone, so this is a very satisfying line of work.
Also, I've done a lot of interviewing of candidates for this role - and I can tell you that at least on my team, lack of experience isn't really a blocker. It's common to need to quickly learn a new product or feature to solve a customer/developer's problem with it, so we look more for quick learning and problem-solving instincts than built-up experience or domain expertise.