Engineering

Software Engineer Role Prompt

Make AI act as a software engineer — design, implementation, and testing trade-offs — instead of a generic assistant that writes whatever you ask.

Open in Role Prompt Generator

Overview

Ask an AI to "write some code" and you get code that runs; ask it to act as a software engineer and you get the reasoning that comes with it — the edge cases, the trade-offs, the maintenance cost. This generates a role prompt that fixes the AI as a senior software engineer: working-code-over-clever-code perspective, correctness and maintainability as decision criteria, and runnable examples over pseudo-code. Open it in the Role Prompt Generator to adjust the seniority level, industry, and focus areas.

How to use this resource

Open the example in the tool

It loads with realistic inputs already filled in.
Swap in your own details

Adjust the inputs and options to match your case.
Generate and copy

Produce the output and paste it where you need it.

Why This Works

A role fixes the AI's reasoning framework, so answers weigh correctness and maintainability, not just "does it run"
Seniority level changes behavior — a senior engineer flags second-order effects a junior would miss
Focus areas concentrate the model where it matters: system design and code quality

Best for

Pairing with AI on design and implementation
Getting trade-off-aware code, not just working code
Anchoring an assistant to engineering judgment

Not for

Reviewing a specific diff — use the Code Review Prompt Generator
Explaining existing code — use the Code Explanation Prompt

FAQ

How do I make an AI weigh maintainability instead of just writing working code?

The role fixes a reasoning framework the model reasons against. This prompt sets Decision criteria of Correctness, Simplicity, and Maintainability, and a perspective that 'Most cost lives in maintenance, not the first write', so answers weigh the next change's cost, not just whether it runs. Generate it, paste it into your assistant, and it holds the senior-engineer role for the conversation.

What can I customize in this software engineer role prompt?

Open it in the Role Prompt Generator to change seniority, industry, and focus areas. The sample ships as a '7+ years' senior engineer in 'Technology' with 'Focus areas for this session: System Design, Code Quality'; adjusting the seniority shifts behavior — a senior flags second-order effects a junior misses. You run the resulting prompt in your own AI chat.

Should I use this to review a specific pull request?

It is not built for diff review — this anchors an assistant to engineering judgment for design and implementation. It sets a general perspective and Output expectations like 'keep examples runnable, not pseudo-code', which suits pairing on a build. To review a specific diff use the Code Review Prompt Generator; to explain existing code, the Code Explanation Prompt.

Customize This Resource

Opens these inputs in Role Prompt Generator. Generate to get the full role prompt — then adjust level, style, and focus areas.

Open in Role Prompt Generator

Prompt Template

Copy it as-is, or use Open in Role Prompt Generator to load it pre-filled and customize it with your own context.

Role: Senior Software Engineer — Technology

You are a senior software engineer with 7+ years of experience in building and shipping production software — design, implementation, testing, and the trade-offs between them. You work primarily in Technology contexts.

Perspective — how you see problems:
- Working, readable code beats clever code — the next reader is the real user
- Most cost lives in maintenance, not the first write — optimize for change
- Every decision trades off correctness, simplicity, performance, and time

Responsibilities — what you own in this conversation:
- Turn a requirement into a design, then into code with the tests that prove it
- Name the edge cases and failure modes before they ship, not after
- Leave the codebase clearer than you found it — or say why you could not

Decision criteria — weigh every recommendation against:
- Correctness — does it handle the edge cases and failure paths, not just the happy path
- Simplicity — the least complex solution that meets the requirement
- Maintainability — what the next change will cost, and who pays it

Focus areas for this session: System Design, Code Quality.
Weight your attention toward these — go deeper here than anywhere else.

Working style:
- Prefer the executable answer over the theoretically optimal one — always name the first concrete step.
- Push back when the request itself is the problem — propose the better question.
- Mention the second-order effects a less experienced person would miss.
- Consider scalability and technical-debt implications alongside the immediate ask.

Instructions:
- Stay in this role for the entire conversation.
- If a request falls outside this role's expertise, say so rather than improvising an answer.
- Ground advice in the perspective and decision criteria above — they are your reasoning framework, not decoration.

Output expectations:
- Show the approach and the trade-off before the code; keep examples runnable, not pseudo-code.
- Call out the assumptions you made and the failure cases you did not handle.

More resources from Role Prompt Generator

Resource

Product Manager Role Prompt

A complete 'act as a product manager' role prompt — the perspective, responsibilities, and decision criteria a real PM brings, not just the job title.

Product

Resource

Startup Advisor Role Prompt

An expert startup advisor role prompt — stage-aware, capital-efficiency-minded, and built to name the riskiest assumption in any plan instead of cheering it on.

Operations

Resource

Authentication Strategy Prompt

Choose how users prove who they are — sessions vs tokens, passwords vs passwordless, SSO and MFA — decided on your real constraints, not the default tutorial.

Engineering

Resources that pair well

Resource

Bug Triage Assistant

Convert scattered bug notes, Slack messages, or user complaints into structured engineering tasks with reproduction steps, severity, and root cause hypothesis.

Engineering

Resource

Fix a Vague Prompt

'Make it good', 'be detailed', 'keep it interesting' — vague prompts get vague output. The fix is mechanical: replace every fuzzy word with a checkable instruction.

Prompt Engineering

Resource

Agent Task Template

A reusable AI agent task template with variables for objective, context, available tools, constraints, success criteria, failure handling, and output format.

AI Agents

Related tools

Tool

Role Prompt Generator

Generate expert role prompts — perspective, responsibilities, and decision criteria, not just "act as".

Prompt Builders

Projects that use this resource

Project

Build a Company Website with AI

The full path to a business website that holds together — plan the content, structure the site, design the components, write the page copy, then ship it as one coherent whole.

5 stages Websites

Project

Build a Marketplace with AI

The full path to a two-sided platform — define the buyer-and-seller requirements, model the data, design the API, build roles and permissions, wire integrations, design the UI, then test, secure, and ship it.

10 stages Software Development

Project

Build a CRM with AI

The full path to a CRM that fits your sales process — define the contacts, deals, and pipeline, model the data that ties them together, then build the roles, integrations, and pipeline UI, and ship.

9 stages Business Systems

Project

Build an E-commerce Store with AI

The full path to a store you own end to end — model the catalog and orders, design the storefront and checkout, add customer accounts and payments, then secure it, test it, and ship.

10 stages Commerce

Workflows that use this resource

Workflow

AI Agent Instruction Workflow

Instruct an AI agent that runs on its own without it wandering off — anchor it to a role, write the agent system prompt, then lay out the multi-step plan it works through.

3 steps 40–70 minutes

Workflow

AI UI & Component Design Workflow

Structure a UI so it stays consistent as it grows — inventory the screens, break them into reusable components, specify the component system and its rules, then review the structure for drift.

4 steps 40–70 minutes

Tip: Save time by exploring related resources and tools that integrate with this resource.