Also been a hiring manager but not OP. I would honestly say they are more related than you think. If you can't fit a narrative to your architecture or what yo

Also been a hiring manager but not OP. I would honestly say they are more related than you think. If you can't fit a narrative to your architecture or what you're doing, it will be hard to understand. It's important to know the "story" of what you are building: where is the data going? Who is the user? If you come up with an architecture that is complicated, just keep working on it and editing, like writing, to make it make more sense. You need good editors / code reviewers on both sides, and they will make you a better reader and writer. If you struggle with writing skills (not all people are good at some particular language) I find being able to make a good picture is even more essential. I think one of the things to state is that it's not about writing something that sounds important. It's about writing something that people can understand. Don't get too stuck in the "art" part of it. At least for me, simplicity is beauty. Another way to try this is to sit down with someone and say "explain what this does" and then see what they come up with. Some people are really good at talking, but not writing. But being able to explain is almost as good, and sometimes more necessary than writing.