latitudeclub

Value · Positioning and proof · lesson 1.1 open

From task to result

Why listing technologies does not sell and how to rewrite what you do in terms of problem, result, and client.

Promise: you walk away with a description of your work that someone who hires in your field understands in 10 seconds (the examples in this lesson come from data engineering; swap in your own field's).

Why it matters

Hiring managers do not buy Spark. They buy a report that used to take weeks and now takes hours, a cloud bill that dropped, data that stopped breaking in the middle of the night. Technology is the how. Senior positioning begins with the what and the for whom.

Three layers

LayerQuestionWeak exampleStrong example
Technologywith what?"Spark, Databricks, Airflow"still exists, but comes last
Problemwhat was stuck?"built pipelines""the experiments report relied on manual spreadsheets"
Resultwhat changed?"improved performance""from weeks to hours", "98% less data read per run"

Results need a rounded, truthful number. If you do not have a number, estimate using a method (before/after execution time, volume read, cost) and declare the estimate as an estimate.

The 10-second test

Show your description to someone who hires in your field. Within 10 seconds, that person should be able to answer: what kind of problem does this person help with and what was the effect? If they answer "with Spark", rewrite it.

Do this now

Take your last three projects. For each one, write on a single line: Problem → Action → Result (with a number). Keep the level of abstraction from lesson 0.4.

Common mistakes

Checklist

Checked on 05/10/2026. Educational content; tax and legal: confirm with a professional.