If an AI answers a question perfectly, I'll go with it. But if my boss fires me for no longer being needed because of the AI, good luck to him and his new idiot employee.
Asking questions is part of the job. Answering questions is part of the job. Collaborating with other people is the most important part of the job.
Some junior technical folks early in their career might bristle at this: "my job is to write this code I'm writing, and anything else is a distraction", or something along those lines. It's hard to internalize that your job is actually making the company successful, not yourself, and that means making other people successful.
If you can't answer a human question from a colleague, as a human, then the natural conclusion is that you are unable or unwilling to do the job. Like, great, you can write (or generate) code, what about the other 90% of the job?
That's for their manager to judge. You can maybe share your opinion on the matter, and let them decide. Until then, collaboration is more important than your personal IC work, and usually more effective than 1 person working heads-down and another struggling.
Newer devs invariably discover that the "write the code" part of the job is just a small part of being an engineer, and less value-added than collaboration. Big successes are achieved when you make others successful, rather than isolating yourself and focusing only on your own work and your own success.
Also, if the response of AI is sufficient, what is the added value of you spending more time on it?