Prompt engineering for beginners

You do not need API jargon on day one. You need a way to state the job, give the model enough context, check the result, and improve the ask. That loop is the skill. The company dojo exists to train that loop with runnable lessons, not slides about "being AI-native."

This page is a plain start. When you want the full map, open the curriculum. If you already know your job lane, jump to a role path after the basics below.

What prompt engineering means (without the fog)

A prompt is the instruction you give a model: a question, a brief, a pasted document plus a request, a series of messages in a chat.

Prompt engineering is the craft of shaping those instructions so the model produces something useful, checkable, and reusable. It includes:

• Writing a clear first ask
• Adding context and constraints
• Choosing a useful output format
• Revising when the draft is wrong
• Knowing when to stop trusting the model

It is not memorizing secret phrases. It is not pretending the model "understands" your company the way a coworker does. It is directing a fast, fluent tool that still invents when you leave gaps.

If you can write a good brief for a human contractor, you already have half the skill. The other half is learning where models fail and how to catch it.

Who this is for

• You use ChatGPT (or similar tools) at work and get uneven results
• You want a beginner path before advanced agent talk
• You care about shipping work, not collecting prompt screenshots

Who should skim and move on: people hunting for "one prompt that replaces my job." That is not what this guide, or PromptDojo, sells.

Your first mental model: the builder loop

Beginners improve fastest when they treat every chat as a small build:

1. State the deliverable. What object do you want out?
2. Supply context. What must the model know that is not public knowledge?
3. Set constraints. What must it avoid or leave blank?
4. Run. Generate a draft.
5. Inspect. What is wrong, thin, or invented?
6. Revise the ask. Fix the instruction; do not only complain in your head.
7. Save what worked. Keep the prompt for next time.

That loop is the same muscle the dojo trains in Chapter 00 and across the curriculum. Free start: preview. Full map: curriculum.

A beginner template you can steal today

Copy this and fill the brackets:

Goal: [deliverable in one sentence]

Context:
- [audience]
- [product / situation]
- [facts the model must use]
- [facts that are unknown: say "unknown"]

Constraints:
- Do not invent [metrics / names / citations]
- Tone: [direct / formal / plain]
- Length: [range]

Format:
- [bullets / sections / table / email]

First, ask one clarifying question only if a missing fact would make the draft unusable. Otherwise produce the draft.

Run it on a real task from your inbox. Then send one follow-up that names keep / cut / fix. That single revision message teaches more than ten tip articles.

Three beginner exercises (about an hour total)

Exercise 1: Rewrite a mushy ask (15 minutes)

Take a vague prompt you actually used last week. Rewrite it with Goal, Context, Constraints, Format. Compare drafts side by side. Note what still failed. That note is your curriculum for tomorrow.

Exercise 2: Force a format (15 minutes)

Same goal, three formats: paragraph, bullet checklist, table. Pick which shape you can edit fastest. Beginners often blame the model when the real issue is an unusable shape.

Exercise 3: Catch an invention (20 minutes)

Ask for a short market overview or "stats about" a niche you know. Highlight every number or name you did not provide. Delete or mark them [NEED SOURCE]. Build the habit of treating unsupported claims as drafts, not facts.

Writers and marketers: this invention-catching habit is central. The copywriter path and marketer path both route through builder skills you can use on real campaigns and drafts, not toy chat demos.

Jargon you can learn later (skip for now)

You will see these words online. You do not need them to start:

• Tokens: chunks of text the model processes. Useful later for cost and length limits.
• System prompt: hidden instructions some apps set before your message.
• Temperature: a setting that affects randomness in some APIs.
• RAG / fine-tuning / agents: advanced patterns. Learn them after the basic loop is solid.

PromptDojo's curriculum goes deep over 52 chapters. Beginners should not try to swallow the whole stack on day one. Take the free entry, then follow a role route.

How beginners should pick a path

Generic "prompt engineering course" language is everywhere. Work is not generic. Marketing briefs, support replies, code reviews, and SOPs need different context and different failure checks.

PromptDojo keeps a company dojo identity on purpose: one school, assigned by role.

Not sure? Open the paths hub, pick the closest role, and start Chapter 00 from preview. You can change routes later; the point is to practice on work that looks like yours.

Recommended first role CTA for most office beginners: if your work touches campaigns, messaging, or research, take the marketer path. If that is not you, pick the row above that matches your calendar.

What "good" looks like after a week of practice

You will not be a prompt celebrity. You should notice:

• Fewer scrap-and-restart chats
• Shorter editing time because format and constraints were set early
• A small personal library of prompts that actually ship
• Faster detection when the model invents a fact

You will still need judgment. Tools change. Policies change. Customer trust does not get outsourced to a chat window.

How PromptDojo fits (honest product map)

• Free: Public curriculum in the browser; Chapter 00 via preview with no card, no install, no signup.
• Depth: Curriculum lists 52 live chapters, 218 lessons, 1561 runnable steps. That depth is the product, not a PDF of tips.
• Solo paid: Plus adds saved progress, sync, and certificates ($12/mo or $99/yr on site pricing).
• Teams: Later track: role-assigned paths for groups, sales-led. Beginners usually start solo.

This guide does not invent case studies or ranking claims. It routes you into practice.

Beginner mistakes to avoid

• Collecting prompts instead of finishing one real task
• Pasting confidential data into tools you have not cleared with your company
• Publishing model-invented numbers or citations
• Jumping to "agents" before you can write a clear brief
• Treating a single viral tip as a system

Your next hour

1. Skim the curriculum map so you see the shape of the dojo.
2. Run Chapter 00 in the preview.
3. Choose one role path (default suggestion: marketer if it fits; otherwise pick from paths).
4. Save one improved prompt from a real work task before you close the tab.

Prompt engineering for beginners is not a mystique. It is clear asks, honest checks, and reps. The company dojo is built for those reps.