There are different kinds of programmers I find. Some are more algorithmically / mathematically minded. Some are less skilled when it comes to writing the low-l

There are different kinds of programmers I find. Some are more algorithmically / mathematically minded. Some are less skilled when it comes to writing the low-level code, but great at architecting and building clean scalable solutions. Others are less interested in the tech generally and more product orientated -- they're just looking to build cool things that users enjoy using (often frontend devs). I think you first need to understand where your strengths and interests lie. I think I'm probably a bit like you in that I just like building stuff (used to love lego as a kid), but my math abilities and technical abilities are nothing that impressive. I'm a full-stack dev, but I find I'm definitely more useful on the frontend. I tend to be the dev who spends a lot of time tweaking buttons and making the general UX improvements that other devs don't care about or have less of an eye for. I think I've built some really cool things in my time even though many of them haven't been that technically challenging. On the other hand one of the best programmers I know has built some extremely technically challenging things that go way beyond my abilities, but his UI/UX is so bad that everything he builds is basically unusable by anyone but himself and he doesn't seem to think that's a problem. Do you you really feel you have nothing of value to offer as an engineer? Are there any type of problems that your team tend to come to you first for answers? I really believe that building a great product requires engineers of all different mindsets and skillsets -- I actually think this is a mistake a lot of companies make when hiring, you probably want some people who are bad "fits" for your team instead of looking for clones of your existing devs. There might even be an argument to make that sometimes great engineers are actually fairly bad engineers. I've worked with guys before who are excellent at documentation and communication but less strong technically. In my opinion they were still really valuable members of the team though, they just focused more on ensuring we had good dev docs, improving tooling and arranging dev meetings to discuss things like tech debt. I'm yet to meet a engineer with nothing to offer. It might just be that the company you're working for isn't making the best of your skillset. Some things to think about anyway...