On-demand AWS data expertise

Most data teams we work with do not need a full project. They need a senior who knows the AWS data services in depth, for a specific question, and they need one now:

• -A query or a job got slow or expensive, and nobody on the team knows why.
• -A design decision has to be made this week: table format, partitioning, access model, engine.
• -An incident or a limit was hit in production, and the documentation does not cover your case.
• -The team is good but junior on one service, and needs someone to review and teach.

• You get a senior who builds, not a slide. We work in your account and your code, with your team.
• Short and scoped. Each request has a question, an expected outcome and a time box, so you know what you pay for.
• Everything is written down. Findings, decisions and fixes end up in your repository or your wiki, so the knowledge stays.
• We say when it is not worth it. If the answer is to change service or to leave things as they are, that is the answer.

1. 01

   The question

   A short call to frame the problem: what is happening, what you expected, what has been tried. We agree on the outcome and the time box.

2. 02

   Diagnosis

   We read the configuration, the query plans, the job metrics, the logs and the bill, in your account with read access first.

3. 03

   Fix or recommendation

   Depending on what you need: the fix applied with your team, or a written recommendation with the options and their trade-offs.

4. 04

   Handover

   A short write-up of what was found and changed, and a session with the team so the next similar issue is solved in-house.

5. 05

   On demand, as long as needed

   A one-off request, or a monthly block of days with a senior who already knows your platform.

• -A 30-minute call to describe the problem.
• -A time box and an expected outcome agreed before we start.
• -Diagnosis within days, then the fix or the written recommendation.