It is 6:40 pm, your manager has sent a three-line message that could mean four different things, a 30-page circular is waiting in your inbox, and the Excel export from the ERP has phone numbers in six different formats. You open ChatGPT or Gemini, type a quick request, and get an answer that sounds confident and is not quite right. Nothing is wrong with the tool. The request was too thin for it to work with. Prompt engineering is the skill of fixing that, and it is far more practical than the name suggests. Here are 11 real situations from Indian workplaces, each with a prompt you can copy, adapt and use today.
Four Habits That Fix Most Bad Prompts
You do not need a formula or a course to get better results. Four habits cover most of it.
- Say who you are and who the answer is for. "I am a team lead at a mid-sized NBFC writing to a senior manager" changes the tone and the content more than any clever wording.
- Paste the real material. The AI cannot see your inbox, your sheet or your policy. Give it the actual text, with confidential details removed.
- Describe what "done" looks like. Length, format, language, and what to leave out.
- Give it permission to say "I don't know." Tell it to write "not stated" when something is missing, and to ask you questions before it answers.
The difference is easy to see with a task almost everyone has.
Thin prompt:
Help me prepare for my interview.
Prompt with the four habits:
I am a fresher with a B.Com degree interviewing for an accounts executive role at a manufacturing company in Pune. Ask me one interview question at a time, wait for my answer, then give me feedback on it in two lines before the next question. Start easy and get harder. If my answer is vague, ask me a follow-up the way a real interviewer would.
The second one takes twenty seconds longer to write and turns the AI from a search engine into a practice partner.
The 11 Use Cases at a Glance
| # | Use case | Who gets the most from it |
| 1 | Decode a vague message before you reply | Anyone with a busy manager |
| 2 | Say no without damaging the relationship | Team leads, account managers |
| 3 | Turn a messy chat thread into decisions and owners | Project and operations teams |
| 4 | Write festival and offer messages in Hindi or Hinglish | Small businesses, marketers |
| 5 | Turn a long circular into a one-page brief | Finance, compliance, HR |
| 6 | Clean a messy Excel export | Sales ops, HR, accounts |
| 7 | Turn 200 customer comments into themes | Product, marketing, support |
| 8 | Build a one-page competitor battlecard | Sales and marketing |
| 9 | Turn a vague hiring request into a job description and scorecard | HR and recruiters |
| 10 | Practise the interview for the exact job you applied for | Job seekers |
| 11 | Prepare for a salary conversation | Anyone due a hike or switching jobs |
Write and Communicate
1. Decode a Vague Message Before You Reply
"Let's discuss the deck tomorrow." "This needs some more thought." "Can you look into this?" Indian workplaces run on messages like these, and answering the wrong version wastes a day.
My manager sent me this message: "[paste message]". Context: I am a [role] working on [project]. Give me three different things this could mean, ranked by how likely each is. For each one, write the single question I could ask to find out which it is. Then draft a short, polite reply that asks the best question without making me look unsure.
The useful part is the ranking and the single clarifying question. You are not asking the AI to read your manager's mind. You are asking it to show you the options so you can pick the right question.
2. Say No Without Damaging the Relationship
Scope creep, a last-minute request on a Friday, a client asking for a discount you cannot give. Saying no is a skill, and a first draft written in frustration usually sounds worse than you meant.
I need to decline this request: "[paste request]". I am a [role] and the other person is [client / senior manager / peer]. The real reason is [honest reason]. I want to keep the relationship warm and offer an alternative: [what you can do instead]. Write the reply in under 100 words. Do not apologise more than once and do not use phrases like "unfortunately, due to unavoidable circumstances."
Keep the honest reason in the prompt. Messages that hide the real reason tend to sound evasive, and the AI writes a better draft when it knows what is true.
3. Turn a Messy Chat Thread Into Decisions and Owners
A 90-message WhatsApp or Teams thread where six people argued about a launch date. Somewhere in it, a decision was made.
Below is a group chat about [topic]. Extract only these four things: (1) decisions that were actually agreed, (2) tasks with the name of the person who said they would do it, (3) questions still open, (4) anything where two people disagreed and it was never resolved. If a decision or owner is unclear, write "unclear" instead of choosing one. Chat: [paste chat, with phone numbers and sensitive details removed]
Item 4 is the one most people forget, and it is where projects usually go wrong later. Skim the original thread for any decision the AI marked "unclear" before you send the summary out.
4. Write Festival and Offer Messages in Hindi, Hinglish or a Regional Language
Textbook Hindi on a promotional WhatsApp message sounds like a government notice. Customers respond to the way they actually talk.
Write a WhatsApp message for [customers in a small town / young shoppers / senior citizens] announcing [offer] for Diwali. Language: Hinglish (Hindi written in English letters), friendly and simple, the way a local shopkeeper would say it. Under 50 words, one emoji at most, no all-caps. Give me three versions. Then give the same message in Devanagari script. Tell me if any phrase might sound too formal or confusing in this region.
For anything customer-facing, ask a native speaker to read it before it goes out. AI is stronger in some languages than others, and it can pick the wrong level of formality, for example "tum" instead of "aap", which matters a great deal to the person reading it.
Work With Documents and Data
5. Turn a Long Circular Into a One-Page Brief
A new RBI circular, a GST notification, a revised HR policy. You need to know what changed and who must do what, not how it is worded.
You are helping a [role] at a [type of company] in India. Below is a [circular / notification / policy]. Write a one-page brief with: what this is in two sentences; what is different from before; who in our company is affected; every date and deadline, quoted exactly as written; and what we need to do, with a suggested owner. Add a final section called "Needs a professional's opinion" for anything ambiguous. Use only what is in the text. If something is not stated, write "not stated." Text: [paste text]
Check every date, rupee amount and percentage against the original before the brief goes to anyone. A summary tells you where to read closely. It does not replace reading the clause that carries a penalty.
6. Clean a Messy Excel Export
Names in capitals and lowercase, phone numbers with and without +91, dates in dd-mm-yyyy and mm-dd-yyyy in the same column. Clean-up is dull work and a good job for AI, as long as you test the result.
I use Excel. Column A has customer names in mixed case with extra spaces, column B has phone numbers in formats like "98765 43210", "+91-9876543210" and "09876543210", and column C has dates that are a mix of dd-mm-yyyy and text. Give me formulas to put in columns D, E and F that: (D) clean the name to Proper Case with no extra spaces, (E) return only the 10-digit mobile number, and (F) return a proper date. Explain each formula in one line. Tell me what could still go wrong. Here are 8 sample rows: [paste rows]
Test the formulas on rows you can check by eye, and look for the failure everyone meets: a date like 04-05-2026 read as 5 April when it means 4 May. Ask the AI to list the cases it could not handle instead of assuming there are none.
7. Turn 200 Customer Comments Into Themes
Survey responses, app reviews, support tickets or exit interviews. Reading them all is slow, and skimming them tends to confirm what you already believed.
Below are [number] customer comments about [product or service]. Group them into at most 7 themes. For each theme give: a short name, how many comments fall under it, two representative quotes copied exactly, and one thing we could do about it. List the comments that did not fit any theme separately. Do not paraphrase the quotes. Comments: [paste comments, with names removed]
Two checks matter here. The counts can be wrong, so spot-check one theme by counting yourself. And read the "did not fit" list, because the single odd comment is sometimes the most useful one.
Sell, Hire and Support
8. Build a One-Page Competitor Battlecard
Before a sales call or a pitch, you want to know how you compare, without the usual marketing fluff.
I sell [product] to [type of buyer in India]. My main competitor is [company]. Below is text copied from their website and from my own product page. Using only this text, make a battlecard with: where they are stronger, where we are stronger, three questions to ask the buyer that bring out our strengths, and two objections the buyer may raise with a suggested reply. If the text does not give enough information to support a point, write "need to verify" next to it. Their page: [paste]. Our page: [paste].
"Using only this text" is the line that matters. Without it, AI fills the gaps with plausible facts about pricing and features that may be out of date or invented. Verify every claim about a competitor before you say it to a customer.
9. Turn a Vague Hiring Request Into a Job Description and Scorecard
A manager says "I need a good marketing person who can do everything." You need something a candidate can read and an interview panel can score fairly.
A hiring manager at a [size and type of company] in [city] has asked for: "[paste their request]". Ask me up to five questions you need answered to write a good job description. After I answer, write a job description with a two-line summary, six responsibilities, no more than five must-have skills, three nice-to-haves and the experience range. Then write an interview scorecard with five questions, what a strong answer looks like for each, and a 1 to 5 rating guide. Keep the language plain, inclusive and free of requirements not needed for the job.
Letting the AI interview you first produces a much sharper job description than asking for one cold. Cut anything the role does not truly need, because AI tends to inflate must-have lists, and check the title and pay band against your own company structure.
Grow Your Own Career
10. Practise the Interview for the Exact Job You Applied For
Generic "top 50 questions" lists do not prepare you for the conversation you will actually have. The job description does.
Here is the job description for a role I applied for: [paste JD]. Here is my resume: [paste resume, with phone number and address removed]. Act as the hiring manager for this role. First, tell me the three things on my resume you would probe hardest and why. Then ask me one question at a time, mixing questions about my experience with questions about this specific job. After each answer, give me honest feedback in three lines: what worked, what was weak, and a better version of one sentence. After 8 questions, summarise my strongest and weakest areas.
The feedback is only as honest as you let it be. Say "be critical" in the prompt, and answer out loud at least once, because a typed answer hides the pauses and filler words an interviewer notices.
11. Prepare for a Salary Conversation
Asking for a hike, or negotiating an offer, is easier when you have rehearsed what to say and what the other side might reply.
I am a [role] with [years] of experience at a [type of company] in [city]. I want to ask for a [hike / higher offer]. My current pay is [figure]. The number I have in mind is [figure], based on [reasons: market research, added responsibilities, results I delivered, such as a project that saved cost]. Write a three-minute talking script for the conversation with my manager, the three most likely objections they will raise with a calm reply to each, and a fallback ask if the answer is no, such as a review in three months with clear targets. Do not invent market data. Where a number would help, put [add market figure] and tell me where I can find it.
AI cannot know what your role pays in your city, and it should not guess. Fill the brackets with salary information you have actually checked, such as live job listings and what people in similar roles tell you.
One Checklist for All 11
Rather than repeat a warning under every example, here is the checklist to run before anything leaves your desk.
- Names, numbers, dates, quotes: check each against the source.
- Any calculation: redo it in Excel or a calculator. AI writes smooth sentences even when the arithmetic is wrong.
- Legal, tax, medical or policy decisions: treat the output as a reading aid, and have a qualified person confirm.
- Another language: have a native speaker read anything official or public.
- What you pasted: no customer details, Aadhaar or PAN numbers, salaries, unreleased results, confidential contracts, passwords or source code. Anonymise first ("Client A", rounded figures) and use your company's approved tool if it has one.
- Does it sound like you? If a colleague would not believe you wrote it, rewrite a few lines in your own words.
Where Prompt Engineering Shows Up in Real Job Listings
Everything above is a skill for the job you already have. There is also a job market for it, and the listings on Jobaaj this quarter show a pattern. These are titles we saw, not a full survey, and listings come and go.
- Entry level (0 to 1 years): titles such as AI Agent Prompt Engineer (Gurugram), Gen AI Prompt Writer (Chennai) and AI Prompt Engineering Intern (Pune). These roles are mostly about writing and testing prompts, reviewing AI output and fixing mistakes./
- Mid and senior level (4 to 9 years): titles such as LLM Prompt Engineering Senior Associate (Bengaluru), RAG and Prompt Engineering (Pune) and Prompt Engineer, AI Applications Lead (Bengaluru). Here prompting is combined with other skills: retrieval-based systems (RAG), evaluating model output, and building the product around it.
What the pattern says is that "prompt engineer" on its own is mostly an entry door. People who move up add something else: Python, data work, a domain such as finance or healthcare, or product ownership. If you want to test whether this path suits you, use cases 7 and 10 above are good starting points, because evaluating output and understanding a job description are exactly the skills these roles ask for.
Pick the use case that costs you the most time this week, run it on real work once, and save the prompt if it works. Most of these prompts will feel obvious within a month. The one you keep refining is the one that changes your day.
FAQs
It is writing instructions for an AI tool so the answer is useful the first or second time. You give it your role, the situation, the actual material, the format you want and the limits, instead of a one-line request.
No. Every use case above works in plain English. Coding becomes useful when you want to build AI into software or automate a workflow, but for emails, summaries, spreadsheets and interview practice, clear writing is the main skill.
All four handle the use cases above. Copilot fits teams on Microsoft 365, Gemini fits Google Workspace, and ChatGPT and Claude are general assistants many people use directly. Run the same prompt on two tools with a real task and compare, and check which tool your employer allows.
Not by default. Free public tools can handle data differently from enterprise versions, so read the terms and your company's AI policy. Never paste customer personal details, salaries, unreleased financials, confidential contracts or passwords, and anonymise anything you do share.
You cannot remove the risk, but you can cut it. Tell the AI to use only the text you give it, to write "not stated" when information is missing, and to ask questions when unsure. Then verify names, numbers and dates against the source yourself.


