I can't really answer your question, but I can give you my view as somebody who does a lot of technical hiring.
When you hire new people, first and foremost you want people who can get stuff done. This is a combination of skill and will. First, skill: Do you have the skills needed to get the job done? This can be technical skills, as well as things like people skills and ability to work as part of a team. Here it is really helpful to see demonstrated work output. Perhaps a little open source side project you did could demonstrate more than, say, a list of classes you took or your research output. If you can demonstrate an ability and interest to work with others, that's even better.
The second is will. Many PhDs (and I am one) start out suffering from the idea that they need to stick with their expertise. They expect to take their knowledge gained in grad school and apply it to real-world problems, and get paid doing it. It seems reasonable. But it's not how the world works. What you learned in grad school was how to solve open-ended, difficult problems, not a specific set of expertise. So you need to convey some flexibility and desire to work on broader problems. Nobody wants an elitist on their team who, say, refuses to program in anything other than some obscure Haskell variant. What people do want is a person who can solve open-ended, hard problems and without pigeonholing themselves.
The final point is that how you present yourself on your resume is crucial. You shouldn't lie (of course), but you can emphasize different things in order to communicate the above points to whomever is reading it. Good luck!