You'll need define the type and scope of the problems you like better. Most software development could be considered problem solving "user has problem x, let's

You'll need define the type and scope of the problems you like better. Most software development could be considered problem solving "user has problem x, let's solve it by coding y", even if you're just gluing frameworks together you're solving someone's problem. Other problems are more like bugs, in which case support developer might be more your speed. Support developer is a rarely seen job title these days but still very much exists. In my current role I'm somewhat on the support side and sometimes get some really gnarly bugs that require weeks and some creative approaches to solve. I love doing this because it's like being paid to solve fun puzzles, but other peoples definition of problem solving is to be creating my problems :)