How do I even describe my job now, in an interview?
Before, the pitch was a list. I know this language, I’ve built these kinds of systems, I did this at that company. It was about what you could sit down and write yourself.
Now a lot of that isn’t really what fills the day. Before, you’d get an idea or a requirement and the work was figuring out how to turn that into code. Now the work is explaining to the AI what you want and making sure it actually delivers that. You don’t really have to think about the code itself anymore.
So the old list doesn’t quite describe the job anymore. It describes a job that used to exist.
What replaces it isn’t another list, and it’s not obvious what it is either. It’s something closer to a role than a skillset: knowing what you actually want, explaining it to the AI in a way it can act on, catching fast when the outcome drifts from that, and knowing when what comes back is really what you wanted. It’s not about auditing the code underneath, it’s about steering the outcome, not the implementation.
And it has to happen fast. AI can now build far more than any one person could have built alone, so the bottleneck isn’t what gets built anymore, it’s how quickly and cheaply you can steer it to the right result. That speed is what people expect as the baseline now, and it’s also where the real edge over other people using the same AI actually is.
There’s still some of the old knowledge in there, things a developer just knows to flag, like security or auth, but that’s temporary color, not the core, the same way memory management or register allocation used to be core knowledge and is now background infrastructure most developers never think about. AI gets better at that every day, and that entire domain of expertise compresses into legacy knowledge. What doesn’t go away is being fast and precise at saying what you mean and steering toward the result you actually need. Push far enough down that road and human involvement shrinks down to pure intent, utility, and steering.
That’s maybe the harder thing to put into words in an interview, because there’s no clean noun for it the way there was for “I know Python.” It’s not a tool and it’s not really a technique. It’s something like: I used to be the one writing the code. Now I’m the one deciding whether what the AI delivers is actually the software I wanted.