Yet, I:
- Help with hiring/marketing/leading scrum sessions (when the actual scrum master is ill)
- Conduct pentests
- Do the frontend and backend (what I was hired to do)
If they'd let me, I'd help with the writing efforts as well as my writing ability is better than that of the average developer, if I have to believe my grades on any report in any degree that I did (game studies, psychology and CS).
Most companies and teams are thrilled to have people who proactively seek to solve thorny issues. The difference with me is that most programmers are attracted to solving “problems” in a code base, which might add value but have arguable ROI. I’m rarely the person who advocates for a rewrite or tries to push some hot new technology. I’m almost always the engineer who asks the question “how can we apply what we’ve already written to this new sector” or “how do we change up this experience to cut onboarding time in half” etc.
My unique (well one of) internalized properties I have is having a keen eye for good problem to technology fit. Steve Jobs said it best with
“start with the experience and work backwards toward the technology”
In another words, it’s extremely valuable to be able to understand when you can re use an existing tool (in this case, existing code) to achieve the result, which is different from trying to shoehorn your existing code to fix/improve/add a feature to an existing problem space or product domain.
That’s the real key, to me, in a nutshell
(And why I almost never buy in on complete re writes)
The key, I've found, is figuring out the role that maximizes your strengths, and converting your current role into that (gradually) or finding a company that has a position that matches.
For example, I loved a lot of aspects of being a PM (leading the team, breaking down complicated tasks/releases, designing great UX) but am an engineer at heart. So I worked with my PM to take over responsibilities that leveraged those skills, and then I used that experience to get a new role where I'm able to do those same things to a greater degree (at a company now that combines typical tech lead + PM responsibilities into one).
What is your goal? I identify with the parent comment here, (the parent of that too) and feel like I've reached a point where the most obvious answer to your question (on leveraging strengths) is management.
If you can code, project manage, and communicate effectively with [non]tech people and don't mind the stress of dealing with other people's issues, then it might be up your alley.
Well based on the comment I replied to, you communicated that you did! Don't sell yourself short. Talk to your manager; is there opportunity at your current org to do the kind of work you are looking for? If not, look elsewhere; the challenge is communicating that you have the relevant experience (ideally with something to show at your current role (hence my previous comment)).
Instead I started freelancing, got a few clients, and eventually hired others to help me.
Looking back, when I impressed clients with my work I was regularly offered various forms of management responsibilities. I probably could have found other opportunities like that if I had pursued it.
If you demonstrate good results in one of the main skills required for a job and explain how you would build up the others, you might be surprised at who would hire you.
People who can do well in several areas and effectively manage projects or other people are always in short supply.
Being funny is one way to be like able
