◆ Amazon DynamoDB

Organize and maintain geospatial 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskImport the new Q3 store location data from the CSV file into the 'RetailLocations' table,…+
Import the new Q3 store location data from the CSV file into the 'RetailLocations' table, ensuring all latitude and longitude fields are correctly parsed and indexed for spatial queries by Tuesday.
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 I import this Q3 store location data, make sure it's optimized for future use. Validate…+
Before I import this Q3 store location data, make sure it's optimized for future use. Validate the accuracy of the coordinates against known regions, flag any entries with missing or malformed geospatial data, and ensure the indexing strategy supports efficient 'stores near me' queries for our mobile app users.
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 'find nearest stores' query for the mobile app is performing incredibly slowly, taking…+
A new geospatial query for finding nearby stores is performing terribly, and I don't know why.
The new 'find nearest stores' query for the mobile app is performing incredibly slowly, taking over 10 seconds for a single request. I've checked the basic indexes, but it's not improving. I'm afraid this will severely impact user experience and the marketing campaign launching next week. The product manager is pressing for a solution. What's the most common reason for poor performance in geospatial queries, and what specific optimizations or indexing strategies should I investigate first to improve its speed without a major re-architecture?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur geospatial queries consistently become performance bottlenecks as the number of store…+
Geospatial queries often become performance bottlenecks as our data grows.
Our geospatial queries consistently become performance bottlenecks as the number of store locations grows, leading to slow load times for users. This pattern costs us user engagement and requires reactive fixes. What habit should I change in how we design, index, or maintain our geospatial data to proactively ensure scalable performance as our dataset expands?
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.