Theory: Role prompting (also called persona prompting) assigns the model a specific identity or professional stance before giving it the task.
Common Roles Used in Prompt Engineering:
- Senior Software Developer
- Data Scientist
- Medical Professional
- Financial Advisor
- Teacher or Trainer
- Business Consultant
- Research Analyst
Role prompting is especially useful for:
- Getting domain-appropriate rigor (a “senior structural engineer” will apply safety factors and code references that a generic assistant might skip)
- Getting a consistent lens across a long interaction (e.g., always evaluating for numerical stability)
- Getting critique/review-style output rather than generative output
EXAMPLE 1
Without Role Prompting: I want to import a csv file into a list. Write me a code that would do this.
With Role Prompting : Act as a Python Software Developer. You are cautious and like to handle all types of unforeseen problems. I want to import a csv file into a list. Write me a code that would do this
EXAMPLE 2
Without role prompting: Explain API security.
Output may be generic or basic.
With role prompting: Act as a Cybersecurity Expert. Explain API security risks and best practices.
Output will be more professional and detailed.
EXAMPLE 3
You are a senior control systems engineer reviewing a colleague’s PID controller design for a manufacturing conveyor system. You are known for being rigorous about stability margins and skeptical of tuning that “just works in simulation.”
The proposed controller has Kp = 4.5, Ki = 2.0, Kd = 0.8 for a plant with transfer function G(s) = 10 / (s² + 3s + 2).
Evaluate this design:
- Compute the closed-loop characteristic equation.
- Assess stability using the Routh-Hurwitz criterion.
- Identify any risk of oscillation or overshoot given these gains.
- Recommend specific gain adjustments if needed, with justification.
Write your response as you would in a design review memo.
The role does two things simultaneously: it sets tone (memo-style, skeptical) and evaluation criteria (stability margins, not just “does it converge”). Compare this to asking the same question with no role — you’ll typically get a flatter, more generic walkthrough with less critical framing.