So, getting back to the topic...

I noticed that the PTB is apparently expecting someone to move to Tennessee. Umm, that's an immediate no-go.

Lemme tell you what I have to deal with  as a hiring management type, when it comes to software devs and engineers...

Some advice: 

* Drop the relocation/onsite demand if you have one, or at least make it clear you will hire for hybrid/remote work. Software devs/engineers can easily expect to work 100% remote these days. A quick browse through LinkedIn or any of the job sites show a demand for software devs where the majority of  companies hiring offer 100% remote work - and half of the rest offer hybrid work environments if they're in a major tech hub (West Coast examples: Silly Valley, Portland Metro, Seattle.) If you expect a dev to come into the office every day, let alone -move- to BFE, Tennessee, just for a job? Well, I got really bad news for you, unless you're scary-lucky, or you get someone who doesn't really know what they're doing.

* Hope you're offering enough. You may want to put up a range so nobody gets their time wasted. For a decent developer that close to the metal (C/C++ is a lot closer to it than Python), expect to shell out a range of at least $180k-250k/yr DOE (it can go way higher out here on this coast - a FAANG engineer can rake in up to $320k or more DOE.) 

* May want to make a couple of changes... Change "Primary Software" to "Primary Languages", so an applicant who knows what they're doing doesn't immediately think that you don't know what you're talking about.  Try something like this:

Primary Language: C/C++
Secondary Languages: Python, Visual C++

*  XCode is an IDE, not a language, and "GPU Rendering" is a concept, not a software package. 

* UX/UI and back-end should have clear and constant communication (and a Lead should be doing that), but the phrase "Working closely with QA and other engineers to ensure a great user experience" is clunky, and leads to confusion about who has UX responsibility. Clarify that, so that you can set better expectations for the Lead (and more importantly, his team) as being Front-End, Back-End, or Full-Stack (assuming Full-Stack since you likely have a small team like DAZ does - this leads me to...)  

* Given the small shop, you're likely Full-Stack. Many devs tend to differentiate these days between front-end/UI and back-end. May want to mention the range that the lead can expect to cover.

I got other nitpicks, but I don't really want to go into the weeds (and while I'm not directly competing with you for devs since I'm in Java/React/NodeJS for the most part these days, I'm not one to pull up the kimono all the way, y'dig? ;) ) 

Good luck...