Skip to content
Slow Variables
Ask
Census · IT & software · occupation code 11-3021

Computer and Information Systems Managers

Every task in this role, whether it passes the census's structural hand-over screen, which models pass it, and why. It is a screen, not a claim about what AI can do: a task can pass and still be beyond the systems of the day. The stricter and looser rules re-vote every task, and small differences between roles are noise.

Passes the screen · 0 of 17 tasks

No task in this role passes the screen.

Does not pass

  • Provide users with technical support for computer problems.

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

  • Direct daily operations of department, analyzing workflow, establishing priorities, developing standards and setting deadlines.

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

  • Assign and review the work of systems analysts, programmers, and other computer-related workers.

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

  • Manage backup, security and user help systems.

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

  • Stay abreast of advances in technology.

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

  • Review project plans to plan and coordinate project activity.

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

  • Meet with department heads, managers, supervisors, vendors, and others, to solicit cooperation and resolve problems.

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

  • Prepare and review operational reports or project progress reports.

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

  • Evaluate the organization's technology use and needs and recommend improvements, such as hardware and software upgrades.

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

  • Recruit, hire, train and supervise staff, or participate in staffing decisions.

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

  • Develop and interpret organizational goals, policies, and procedures.

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

  • Consult with users, management, vendors, and technicians to assess computing needs and system requirements.

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

  • Develop computer information resources, providing for data security and control, strategic computing, and disaster recovery.

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

  • Review and approve all systems charts and programs prior to their implementation.

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

  • Control operational budget and expenditures.

    reason given most often: nobody can tell quickly whether it worked, and a failure is too expensive · 3.5% of the role's time · $4.3B

  • Purchase necessary equipment.

    reason given most often: nobody can tell quickly whether it worked · 2.7% of the role's time · $3.3B

  • Evaluate data processing proposals to assess project feasibility and requirements.

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

Where this role works