> What they didn't say was how impossible it was to get an interview when transitioning fields. It's tough to get a foot in the door. I managed a transition la

> What they didn't say was how impossible it was to get an interview when transitioning fields. It's tough to get a foot in the door. I managed a transition largely thanks to preferential hiring for veterans, but even there I had a CS degree and some prior tech experience before going into the military. The other problem is that "junior" really means "fresh out of college." Transitional resumes look weird and they get thrown out in favor of people doing the normal thing. > I was also told that people would look at my GitHub code Recruiters, probably not, but if I'm doing an in-person interview with you, I've definitely read your github page. Tip: I'm looking for a. high quality code, and b. a delivered product. What's high quality? Find code written by the best people (e.g. your standard library, a major framework) and aim to make your code look that good. What's a delivered product? It has thorough, well-written documentation, and I can install it with a single command. If you set up a demo on a website, that's obviously better.