# To get a better programming job, explain your problem-solving skills

DevFeed: [To get a better programming job, explain your problem-solving skills](<https://devfeed.tech/articles/to-get-a-better-programming-job-explain-your-problem-solving-skills-20991.md>)

Original publisher: [Read original article](<https://codewithoutrules.com/2020/05/18/job-search-skills/>)

Author: Itamar Turner-Trauring

Published: 2020-05-18T00:00:00Z

Content type: tutorial

Language: en

Sources: [Itamar Turner-Trauring](<https://devfeed.tech/sources/itamar-turner-trauring.md>)

Topics: [Programming](<https://devfeed.tech/topics/programming.md>), [coding](<https://devfeed.tech/topics/coding.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>)

Tags: [career](<https://devfeed.tech/tags/career.md>), [interviews](<https://devfeed.tech/tags/interviews.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [programming](<https://devfeed.tech/tags/programming.md>), [skills](<https://devfeed.tech/tags/skills.md>)

## AI overview

The article explains how software job candidates can communicate problem-solving ability instead of only listing technologies. It presents three levels--Finders, Solvers, and Implementers--and recommends using precise language and examples in resumes and interviews to show the level of contribution.

## Source excerpt

When you're looking for a new programming job, how do you explain your value? The usual approach is a long list of technologies, but this leaves out a critical skill: your ability to solve problems. If you can convey your level of skill at problem solving, you can get: More job offers. Jobs with technologies you don't know. A higher salary by getting slotted into a higher pay grade. Often just a few extra words can make a big difference in demonstrating your skills. Let's see how you can do it. Three levels of problem solving skills As I discussed elsewhere in more detail, problem solving comes in three stages, each approximately corresponding to a particular career stage (these names are due to Randall Koutnik): Staff or principal software engineers are Finders: they find new problems. Senior software engineers are Solvers: they solve already-identified problems. Junior software engineers are Implementers: they implement already-identified solutions. The earlier you are in the problem-solving process, the more productive you are, and therefore the more valuable as an employee. As a result, you need to communicate how advanced your skill is across these three levels to demonstrate your productivity. Everything from your resume to the stories you tell in interviews should communicate your level of skill. Explaining your skill level Explaining your skill level involves telling stories that use the correct words and sufficient information to demonstrate your skill. I'm going to use resumes as an example here, but you should ensure you do this in interviews as well--if you're practicing with a friend, make sure they're checking for this, it's easy to leave the information out. Consider the following entry from a resume: Moved deployment from manually-managed hosts to a new Kubernetes cluster. This experience entry uses an implementation-level verb: "moved". Similarly, "coded", "tested", "wrote", "fixed", "optimized"--these are all about implementation. And maybe it's impl