◆ Amazon DynamoDB

Create searchable indices for content

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a new Global Secondary Index on the 'orders' DynamoDB table. The index should be named…+
Create a new Global Secondary Index on the 'orders' DynamoDB table. The index should be named 'customer-id-index', with 'customerId' as the partition key and 'orderDate' as the sort key, projecting only 'orderId' and 'totalAmount'.
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 acceptBefore we launch the new search feature for product reviews, optimize the indexing strategy for…+
Before we launch the new search feature for product reviews, optimize the indexing strategy for our NoSQL database. Users need to quickly find reviews by product ID, star rating, and keywords. The current setup makes multi-attribute searches slow. Focus on creating efficient secondary indices that support these query patterns without excessive cost, so the search feels responsive.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new dashboard's search functionality for user activity is returning incomplete results,…+
The new dashboard's search functionality for user activity is returning incomplete results.
The new dashboard's search functionality for user activity is returning incomplete results, especially for older data. I'm afraid the secondary index isn't properly covering all attributes or it hasn't finished backfilling. I can't tell if the index definition is wrong or if it's just a propagation delay. What's the most likely problem, and how should I verify the index's integrity and completeness?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently have to rebuild or modify DynamoDB indices after discovering new query needs,…+
We frequently have to rebuild or modify DynamoDB indices after discovering new query needs.
We frequently have to rebuild or modify DynamoDB indices after discovering new query needs, which is disruptive and costly. It feels like we're not anticipating future access patterns during initial schema design. What habit should we change to better predict and design for evolving query requirements, making our indexing strategy more resilient and less prone to rework?
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.