◆ Amazon DynamoDB

Store, retrieve, and manipulate data

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Amazon DynamoDB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFetch the user profile for 'user-123' from the 'users' DynamoDB table and update their…+
Fetch the user profile for 'user-123' from the 'users' DynamoDB table and update their 'lastLogin' attribute to the current timestamp. If the user doesn't exist, create a new entry with default values.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptWhen we retrieve customer order history, the queries are sometimes slow, especially for…+
When we retrieve customer order history, the queries are sometimes slow, especially for customers with many orders. Before we launch the new customer portal, refactor the data access patterns for order history in our NoSQL database. We need to ensure consistent, fast retrieval times, even for power users, so the portal feels snappy.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA critical end-of-quarter report failed because it couldn't retrieve all necessary data from…+
A critical report failed because it couldn't retrieve all necessary data from DynamoDB.
A critical end-of-quarter report failed because it couldn't retrieve all necessary data from our NoSQL database for yesterday. I'm afraid we've hit a read limit or there's a data corruption issue, but I can't tell if it's a capacity problem or a specific item that's missing. What's the fastest way to diagnose why the data wasn't fully retrieved without causing more disruption?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur DynamoDB queries often become performance bottlenecks as data scales, leading to customer…+
Our DynamoDB queries often become performance bottlenecks as data scales.
Our DynamoDB queries often become performance bottlenecks as data scales, leading to customer complaints and frantic optimizations. It feels like we're not designing our access patterns correctly from the start. What habit should we change to ensure our data models and query strategies are scalable and performant from day one, avoiding future crises?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Amazon DynamoDB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.