I also have a free advice to entrepreneurs - since I'm working remotely as I don't live in the US, I have to be much better / work much harder than US developers, just so I can take home barely the minimum U.S. salary in this industry. I also don't get any equity. When that attitude changes, maybe I'll start giving a shit.
Points for honesty, but I'm wary of any dev who says that. How do you know what maintainable code is if you never stick around for the maintenance?
Subsequently my experience is that developers who have been in the same job for a very long time, have a higher chance of being totally clueless. And also generally not confident with new ideas, not aware of alternative ways of doing things, not exposed to the culture of the broader profession etc.
I am wary of any dev. You could go through this during the hiring process. Most programmers end up doing some maintenance even in new jobs.
But bottom line I suspect this hiring principal is essentially backwards.
Getting bored easily and professionalism are not mutually exclusive.
There are several universal things you can do to ensure maintainability, which are a no-brainer, but don't happen because of various compromises that have to do with time and money - like code-reviews, having no module with a single owner, automatic tests, up to date documents / stories, etc...
If you don't do any of that, it's a no-brainer again that the project will not be maintainable; but it can still be beaten into shape later if the original devs weren't totally insane :)