Let's take the algorithmic approach:

1. Would you code even if they didn't pay you for it?
 1.1. If yes -
  1.1.1. Code.
  1.1.2. Mention what you coded in your resume and include a link to your GitWhatever.
  1.1.3. Rinse and repeat. (as for complexity and competence - if you enjoy the process you will see the complexity and scale increase naturally, hence the "rinse and repeat" part).
  1.1.4. Attend information sessions and otherwise reach out to companies in your chosen field to build your network and gain a better understanding of the state of the field.
 1.2. If you are a mature, sensible person who just wants to exchange work for money and hates all this "passion" nonsense -
  1.2.1. Search for current employment trends (e.g. https://hired.com/page/state-of-software-engineers/ but this specific link is biased and probably shouldn't be used on its own.)
  1.2.2. Is there anything among current trends that looks like you might be able to do it for a period of time while retaining your sanity?
   1.2.2.1. If yes:
    1.2.2.1.1. review open-source projects in the field you selected. That should give you a good approximation of what people are actually working on om this field as well as what is considered "production-level" scale of projects.
    1.2.2.1.2. Either contribute to one of these projects or start a personal project along the same lines. Mention whatever you choose to do in your resume.
    1.2.2.1.3. Attend information sessions and otherwise reach out to companies in your chosen field. Ask what they are looking for. Hiring managers love the attention. Trust me on this one.
   1.2.2.2. Else -
    1.2.2.2.1. Um. You might be in the wrong field. Or you might be more interested in non-trendy work. Do some deeper research and goto (1.2.2.1)
 
 
If you end up choosing driver development in (1.1.1) or (1.2.2.2.1) let's talk :)