God-Emperor of code? Alright.
Artifex maximus programmanorum? You do you buddy.
Most people just chose "senior developer".
When one of them walks in a meeting room with a new client, they'll introduce themselves with a job title that they make up on the spot and satisfies these criteria:
- make it sound like a legitimate job title
- make it sound as senior as you can credibly get away with
- make it sound unique to the client's industry or requirement
- obviously: don't say anything stupid that will have legal consequences like "CEO" or "General Counsel"
It's working really well for them. They're having a blast doing it, and clients get to feel special.
For example a client in the retail business will say things like: Oh, I can tell the agency is really taking my business extra serious. I can tell because they don't just have any old senior developer working on my project, but rather my project is handled directly by their "Senior Head of Retail".
Or if a client asks: "Can you make me a responsive website?" One of them might say: "Yes. In fact, do you know who the gentleman sitting to my left happens to be? He's our Responsive Designs Art Director in Residence".
At least it points our the absurd arbitrariness of titles in software development.
15 years working on business/safety-critical infrastructure? -> senior engineer
3 months javascript bootcamp, no degree, 2 years of work? -> senior engineer
But then there is the plethora of Chief Marketing Officer, Chief Information Officer, Chief Whatever Officer which are being created more or less ad hoc.