As engineers, we take pride in solving problems. We optimize systems, debug code, design robust architectures, and think in terms of precision and logic. But there’s one skill that quietly makes or breaks everything — a skill often underestimated in technical circles: communication.
Yes, I’m talking about the good old art of expressing ideas clearly.
This blog is a reflection on how communication – especially in the age of AI and prompt engineering – is becoming a non-negotiable skill, and how my own experience as an engineer (and a former theatre student) shaped this realization.
The Engineering Mindset: Facts First, Communication Later?
Engineering teaches us to focus on accuracy, efficiency, and function. We’re trained to get things right. But when it comes to sharing what’s in our mind — whether in design discussions, stakeholder meetings, or team emails — we often falter.
Why?
Because we tend to think logic alone should be enough.
But here’s the truth: if others can’t understand what you built, why you built it, or how it works — then it doesn’t matter how brilliant it is. It’s not usable, not understandable, and not scalable.
Theatre Helped Me See This
Interestingly, I didn’t realize the value of communication in engineering through an engineering course. I learned it from theatre.
Under the guidance of Samrat Sanyal, director of Baranagar Drishyakabyo, I was trained to observe people — their emotions, body language, silences, and unspoken tension. I learned that what’s said is only half the message. How it’s said — and how it’s received — is everything.
It made me realize: in both theatre and engineering, the goal is to deliver an experience that works. And that demands clarity, empathy, and precision in expression.
Enter Prompt Engineering: Communication With AI
With AI tools like ChatGPT, GitHub Copilot, or Google’s Gemini entering our workspace, a new type of communication is now critical — prompt engineering.
Let’s be honest: AI is powerful, but it’s not telepathic. If you give vague, incomplete, or poorly structured instructions, AI gives vague results.
For example:
- Bad prompt: “Write about engine.”
- Good prompt: “Write a 500-word explanation on how an internal combustion engine works, including the four-stroke cycle, in simple language for high school students.”
See the difference? The second one is not just a prompt; it’s a well-structured technical requirement.
And that is the essence of prompt engineering: treating communication like a specification.
Lessons for Engineers
So what should we, as engineers, take away from this?
1. Communication is not a soft skill. It’s a core engineering skill.
Whether it’s talking to a teammate, writing a Jira ticket, creating documentation, or prompting an AI — clarity matters. Ambiguity costs time, money, and patience.
2. Prompt engineering is not magic. It’s structured thinking.
It forces you to ask:
- What do I want?
- What’s the context?
- How should the result look?
These are the same questions we ask during design and debugging. The only difference: now we are doing it through words.
3. Empathy helps engineers build better systems.
Understanding how people think — be it your colleague or your AI assistant — helps you design prompts, interfaces, and systems that actually work. Empathy leads to better collaboration, better UIs, and smarter automation.
Final Thoughts
In engineering, we often say: “Garbage in, garbage out.”
Well, the same applies to communication.
You can’t expect meaningful output — from humans or machines — if your input is unclear. Prompt engineering may sound technical, but it’s built on a foundation of clean, thoughtful communication.
So the next time you struggle to explain something, don’t just blame AI or your team.
Ask: “Did I communicate clearly?”
Because at the end of the day — whether it's code, a circuit, a chatbot, or a conversation — communication is the first line of execution.