Software Developers

Does not pass

• Modify existing software to correct errors, adapt it to new hardware, or upgrade interfaces and improve performance.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it, and a failure is too expensive · 10.0% of the role's time · $23.9B

• Confer with systems analysts, engineers, programmers and others to design systems and to obtain information on project limitations and capabilities, performance requirements and interfaces.

  reason given most often: no existing check settles it · 8.9% of the role's time · $21.2B

• Analyze user needs and software requirements to determine feasibility of design within time and cost constraints.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it · 8.7% of the role's time · $20.8B

• Develop or direct software system testing or validation procedures, programming, or documentation.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it · 7.7% of the role's time · $18.4B · passed by Claude Sonnet · the models disagreed

• Design, develop and modify software systems, using scientific analysis and mathematical models to predict and measure outcomes and consequences of design.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it, and a failure is too expensive · 6.9% of the role's time · $16.5B

• Determine system performance standards.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it · 6.4% of the role's time · $15.2B

• Monitor functioning of equipment to ensure system operates in conformance with specifications.

  physical work, outside the screen · 6.3% of the role's time · $15.1B

• Analyze information to determine, recommend, and plan installation of a new system or modification of an existing system.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it · 5.5% of the role's time · $13.2B

• Consult with customers or other departments on project status, proposals, or technical issues, such as software system design or maintenance.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it · 5.3% of the role's time · $12.7B

• Prepare reports or correspondence concerning project specifications, activities, or status.

  reason given most often: no existing check settles it · 5.1% of the role's time · $12.2B · waiting on a check

• Supervise the work of programmers, technologists and technicians and other engineering and scientific personnel.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it · 4.9% of the role's time · $11.7B

• Confer with data processing or project managers to obtain information on limitations or capabilities for data processing projects.

  reason given most often: no existing check settles it · 4.5% of the role's time · $10.7B · waiting on a check

• Coordinate installation of software system.

  physical work, outside the screen · 3.5% of the role's time · $8.5B

• Obtain and evaluate information on factors such as reporting formats required, costs, or security needs to determine hardware configuration.

  reason given most often: nobody can tell quickly whether it worked, and no existing check settles it · 3.2% of the role's time · $7.7B

• Supervise and assign work to programmers, designers, technologists, technicians, or other engineering or scientific personnel.

  an accountable sign-off — stays with a person · 3.1% of the role's time · $7.3B

• Train users to use new or modified equipment.

  physical work, outside the screen · 2.4% of the role's time · $5.8B