You can't do that, unless you can figure out how to make and file TWO resumes. Different ones, I mean.
Man, these data scientists are all pipe dreams.
Well, it is not rocket science to have more than one resume. You have one work history, but you will use more than one resume format to present it in different (but veritable) ways according to the situation.
See, you are supposed to have multiple versions of your resume (which are true and accurate of course) according to job postings or fields of concentration. If you have a varied work experience, or you are contemplating lateral moves, this is a must.
Consider the following situation I had to deal with recently. After doing some C++ (and other programming bestialities), I switched Java/JEE in the commercial. I did that for about 11 years at several small and large firms (Sony, Citicorp, Motorola, etc.).
Then switched back to C/C++, for embedded systems and communication technology (and a bit of hypervisor research) with a defense contractor. The opportunity was there, after doing e-commerce/enterprisey stuff for so long, this looked very interesting (and more engaging of my CS background) and the money was good, so why not I said.
Then just recently when I tried to go back to Java, and all of the sudden my resume was being sent to the garbage can and job agencies were not submitting me to Java openings I was well qualified for.
Why is that? Well, apparently since I did C/C++ for nearly 4 years (ZOMG! no Java in 4 years!) somehow I became a retard who wouldn't know how to code EJBs, access a database, run an ant or maven build script or put a fucking dynamic web page together. 11 years of Java experience (and 18 years of software engineering) meant shit. I mean seriously?
But such is the world of HR drones and employment middlemen. You can't live out of it, and you have to work with it (or cut through it) in any way possible (otherwise you end up with a shitty job as a neophyte.)
So what I did is that I kept multiple versions of my resume. For a C++ job, I highlighted my recent work describing it in appropriate detail right of the bat, with all the different projects and positions on the first page. This would be my "default" resume.
For a Java job, I would reduce all my C++ work to two lines and bring as much past Java work experience as possible on the first page. Why is that? To ensure the HR drones and staffing middle men would see all the right Java buzzwords on the first page.
There was/is no false information at all on my resumes. I simply omitted work I already did to stress another one. How fucked up is that, that you have to remove some of your recent work history just to get contemplated by human buzzword scanners?
In the end, it worked (sort of since I was able to get a Java position via personal reference and passing the necessary technical interviews.)
But regardless. One should always try to make her case directly to the technical people in charge of hiring. But this is a very rare (and blissful) event. More often than not, you will go through HR or a staffing agency.
That is the general case. And for that general case, you better have your work history in more than one resume format, stressing items according to the desired job position (without lying of course or claiming that you have done shit you have not, of course.)
Companies might be desiring software engineers. But in practice, by accident and plain stupidity, they don't hire for software engineers. They hire for savantism, for autonomous, one-trick-pony drones that operate precisely along the lines of magically selected buzzwords. 10+ years of X, 5+ years of Y and 8+ years of Z. Mix and shake.
Imagine if we were to hire carpenters like that:We seek a master carpenter with 10+ years of experience using a Husky hammer, 8+ years using a HDX philips screwdriver, and 12+ years using a Black & Decker circular saw. Oh, and the brands must be Husky, HDX and Black & Decker, otherwise you are a fucktard who doesn't know how to use a hammer, a screwdriver and a circular saw.
That's how companies hire software engineers in general, and if you are not prepared for that (by knowing how to present your work history in different ways), you will eventually get burned at some point.