◆ Statistics

What a r programmer
really does.

20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.

20evidenced tasks
37,200in the US (2025)
$140,300median pay / year
6systems it runs on
This is what one task looks like here
Examine computer hardware
Inspect the workstation fleet listed in the maintenance log, record se…4 sources agree

The shape of the day

tap a movement to see its tasks

Which one is you, right now?

Pick the moment · no score, no sign-up
Which moment is you right now?
Whichever you pick, the task behind it opens below.

The work, task by task

20 tasks
Hands on the work13
Examine computer hardware+
Inspect the workstation fleet listed in the maintenance log, record serial numbers, RAM and disk capacities, note any physical damage, update each machine's maintenance record, and email technicians and Claire in support with the updated summary by Thursday.
escojdonetwiki4 agree
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Consult with users and management+
Hold joint sessions with Helen in product and Raj in support to gather their pain points with current hardware lifecycles, capture three highest-priority issues, propose two mitigations each, and email proposed next steps and timeline by Monday morning.
jdonet2 agree
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Evaluate project plans for feasibility+
Review the new project plan for deploying 120 workstations, verify power, cooling and spare-parts assumptions, estimate realistic service windows and staffing, mark any infeasible items and send my feasibility notes to project lead Omar by Friday noon.
jdonet2 agree
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Create new computing languages and tools+
Prototype a small interpreter and a testing harness to parse our device log format, add functions to normalise timestamps and error codes, run it on last quarter's logs, and share the prototype and results with the development team on Wednesday.
jdwiki2 agree
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Replace damaged components and parts+
Create the maintenance report and update the parts-replacement log after swapping the failed network card and two capacitors, note serial numbers, test results, customer contact details, warranty claims started, and schedule follow-up visit for Friday morning.
esco
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Participate in multidisciplinary projects+
Join the multidisciplinary team meeting on Thursday, bring the diagnostic scripts, the recent maintenance log for the signal processors, and explain how my data-cleaning workflow ties hardware specs to customer repair histories so engineers and clinicians can agree next steps.
jdonet2 agree
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Collaborate with scientists and engineers+
Work with Dr. Morales and Sam from hardware to reproduce the sensor calibration issue: share the analysis notebook, the subset of repair tickets showing voltage anomalies, and propose two experimental runs engineers can reproduce next week.
jdwiki2 agree
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Formulate mathematical models of problems+
Draft a compact mathematical model by Friday that links failure rate to operating temperature and maintenance interval, include assumptions, fitted parameters from last year's repair dataset, and a small R script to simulate expected uptime under three maintenance schedules.
jdwiki2 agree
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
Grow the practice4
Watch and assess3

What the work runs on

named inside the evidenced tasks
8 tasksApache Sparkprocesses and aggregates large sets of diagnostic logs and test results quickly
5 tasksApache Kafkastreams and collects real-time feedback from multiple stakeholders and channels for synthesis
4 tasksApache Airfloworchestrates review workflows and schedules automated reminders for policy review steps
3 tasksAmazon Elastic Compute Cloud EC2models capacity and performance scenarios for planned deployments to validate infrastructure assumptions
2 tasksApache Hadoopstores and processes large historical log sets used to test and iterate new parsing tools
1 taskAnsiblequeries inventories and gathers hardware facts across many machines for bookkeeping

The same task, four heights

this page is height one
ExecuteDo today's task, with fewer mistakesyou are here → ImproveMake it easy for the next person to acceptin the atlas → DecideWork out the right move when it is unclearin the atlas → BecomeLearn the pattern so it stops coming backin the atlas →

Can AI actually do this job?

the honest answer

It can

where it genuinely helps
  • Explain the theory behind the work
  • Draft, tidy and structure your writing
  • Rehearse a hard conversation before you have it
  • Build a study plan that fits your gaps

It cannot

where it stops, completely
  • Be in the room where a r programmer actually works
  • Carry the responsibility when the call is wrong — that weight stays yours
  • Notice what no one wrote down: the hesitation, the thing left unsaid
  • Live with the outcome

What the work pays

two countries, two different measures

United States

this exact occupation · BLS 2025
  • $140,300 a year — the middle: half earn more, half earn less
  • The lowest tenth earn near $82,200; the top tenth near $230,630
  • 37,200 people employed in this occupation

India

the occupation GROUP, not this job · PLFS via ILOSTAT 2025
  • ₹16,825 a month — the median for Craft and related trades workers, the group this work sits in
  • India publishes pay by broad occupation group, so this covers many jobs besides this one. It is a shape, not a salary.
read this carefullyThese two numbers are not comparable and must not be converted into each other. One is a yearly figure for this job alone; the other is a monthly figure for a whole family of jobs. What travels between them is the pattern, not the amount: experience lifts pay almost everywhere.

Where the evidence lives

open any of it yourself

Close to this work

12 nearby
StatisticsForecasting Analyst26 evidenced tasks StatisticsExperimentation Scientist26 evidenced tasks StatisticsProcess Improvement Analyst25 evidenced tasks km/h RPMStatisticsMeasurement Analyst25 evidenced tasks StatisticsData Labeling Lead23 evidenced tasks StatisticsFreelance Data Consultant23 evidenced tasks StatisticsSas Programmer22 evidenced tasks StatisticsActuary21 evidenced tasks

Questions people actually ask

You’ll split time between writing R code to clean and analyze data, and meetings with users or managers to clarify questions. Expect blocks of 2–3 hours doing data wrangling, visualization, or statistical modelling, then short syncs to keep projects aligned.

You’ll also run and monitor jobs in systems like Apache Airflow (scheduling), Apache Spark or Hadoop (big-data processing), and review results with scientists or engineers to refine models or reports.

Don’t paste confidential data into public AI chat tools. Use AI locally (an LLM hosted on your EC2 instance) or enterprise tools that keep data inside your network. Document what the tool did and keep human review for statistical outputs.

Use AI to suggest code patterns or summarize logs from Airflow/Spark, but validate models, code, and results yourself. Treat AI outputs as draft, not final.

Technical: solid R programming, experience with Spark and Airflow, and basic cloud skills on EC2. Know how to monitor jobs, debug failed Spark tasks, and profile R code with real data.

People skills: clear consulting with users and management, writing reproducible reports for scientists, and coordinating tasks across teams. You’ll often explain model results, help set performance standards, and guide deployment decisions.