Make performance claims useful to the person buying the computer. You will measure what the system accomplishes, what it costs and how reliably it works.
Not open yet: Pilot expansion
This work starts when that stage arrives, so there is no application to submit today and we will not pretend otherwise. What is written below is what the role is for and what would make somebody right for it, published early on purpose so you can decide whether it is worth watching.
The work
Build representative task suites covering inference, retrieval, training and integrations. Record model version, quality, context, precision, memory and device conditions. Measure latency distributions, wall energy and completed-task cost alongside raw throughput.
The milestone
In your first 90 days, publish a repeatable baseline and a comparison that another engineer can reproduce on the same configuration.
Evidence
Bring experimental design, systems measurement and clear technical writing. Be able to identify cherry-picked workloads and distinguish measurement noise from a meaningful change.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Design a fair comparison between two devices when their fastest available model configurations have different quality.