11 different careers — and it means something different in each. Data team for a Meteorology Technician is not data team for a Scientific Programmer. Below, the real task it carries in every job, with a ready AI prompt for each.
11careers do this work
4prompts that speak it
7attested by the job's own software
The data team, job by job
Same artifact, different stakes — each card is one career's real use of it, with its prompt.
Meteorology Technician — Collaborate with environmental data analysts
Coordinate with the river basin data team to merge their hydrology outputs with our precipitation grids, agree on variable definitions and temporal resolution, set a joint QA checklist, and schedule weekly syncs through the storm season.
Scientific Programmer — Collaborate with scientists and engineers
Coordinate a working session with Dr. Alvarez and the lead engineer to align our simulation code inputs with lab measurement formats, consolidate agreed data schemas, and push the finalized schema to the engineers and data team by Thursday.
Weather Forecaster — Collaborate with environmental data analysts
Coordinate with the environmental data team to merge their air-quality concentrations with our mesoscale output for the coastal domain, agree on shared variable names and timestamps, and produce a combined dataset and a short methodology note by Monday.
Youtube Space Educator — Collaborate with environmental data analysts
Coordinate with the environmental data team to merge their air quality and land-cover datasets with my temperature anomalies: list needed variable names and units, agree a shared NetCDF schema, set a delivery date of Monday so I can run the joint analysis by Wednesday, and confirm who will QA the merged file.
Every job keeps its own logs, files, records and schedules — and the same one can live in hundreds of jobs, meaning something different in each. The LLOS Work Atlas maps them from the evidence — the software each career is attested to use — never from imagination.