Skip forward into hiring notes
RosterAcorn

3 duties that define a Wisconsin computer employee role

A Wisconsin computer employee role is defined by three duties: work on systems and programs based on design specifications, program work for machine operating systems, or a genuine combination of the two.

  • Design, develop, document, analyze, create, test, or modify systems and programs based on user or system design specifications
  • Design, document, test, create, or modify programs for machine operating systems
  • A real combination of duties from the two parts above
  • The definition is written in terms of the duties performed, not job titles
  • Remove operations, support, and hardware tasks from postings claiming this category

Wisconsin hiring managers do not get to invent this category. The state has written down which duties make a role a computer employee, and your job post either tracks that list or invites a misclassification fight.

The short version: write your software and systems postings around design and development of systems and programs, operating-system program work, or a genuine mix of both. Anything else sits outside the definition.

The wording you are matching comes from the Wisconsin Legislature's DWD 274.03, which carries the duties in section 274.04(15).

How Wisconsin describes the role

The rule defines the role by the duties performed, not by job title. It looks at what the person actually does all day. Your posting is the first written record of that.

The definition runs in three parts, each keyed to a specific activity. If your posting describes work that maps cleanly onto one of them, you are on solid ground. If it mixes support tasks, ticket triage, or hardware work into the description, you may have written something the rule does not cover.

That is the whole discipline of writing these posts: describe the work, then check the description against the state's language before you publish.

The three duties in plain words

Duty one: design, develop, document, analyze, create, test, or modify systems and programs

The state frames it as work done on computer systems or programs, including prototypes, grounded in user or system design specifications. You can read the full wording in the DWD 274.03 rule text.

Notice how many verbs are listed. Design, development, documentation, analysis, creation, testing, and modification all count. You do not need the whole list in your posting. You need enough of it that a reader can see the work is systematic, not scattered.

This duty also covers prototypes. If your role builds throwaway versions to prove a design, that is inside the fence.

The phrase "based on and related to user or system design specifications" is the anchor. Your posting should name the specifications. Ask whether the role works from written user or system design specifications, such as a design doc. Then say so.

A posting that reads "maintains applications" tells a reviewer nothing. A posting that says the person modifies programs to a design spec does real work for you.

Duty two: design, document, test, create, or modify programs for machine operating systems

The second duty is narrower and more specific. It targets program work on machine operating systems. The same rule page carries this wording: DWD 274.03.

Notice the verbs here are a shorter list than in duty one. Design, documentation, testing, creation, and modification. Analysis is not listed. Neither is prototyping.

This duty is for roles that touch the operating system itself. Kernel work, driver development, and other program work related to machine operating systems sit here.

If your posting describes an administrator who installs servers and applies patches, you are not describing this duty. You are describing operations. That is a different job post.

When a role sits at this level, say it plainly in the posting. Name the operating system family. Name the layer of the stack. Give the reviewer something to point at.

Duty three: a combination of duties from the earlier parts

The third duty is the combination clause. The state allows a role that blends duties described in the earlier paragraphs of the same subsection. You can see this in the DWD 274.03 text.

This is where mixed roles live. A person who both designs application features and modifies operating-system programs fits here. A full-stack role that spans system-level work and application-level work fits here too.

The combination has to be real. If your posting lists five duties and only one is program design, the combination clause will not rescue you. The core of the job still has to be inside the definition.

Write your posting so the mix is obvious. Put the qualifying duties first. Leave support tasks out of the posting.

Side-by-side on the three duties

Here is how the three duties compare when you put them next to each other.

DutyCovered activitiesWhere it lives in the rule
Systems and programsDesign, development, documentation, analysis, creation, testing, modification, and prototypes274.04(15)(b)
Operating-system programsDesign, documentation, testing, creation, modification274.04(15)(c)
Combination A mix of duties from the earlier parts274.04(15)(d)

All rows come from the Wisconsin Legislature's DWD 274.03 rule text.

What the federal hook means for your posting

The rule carries a note tying its interpretation to 29 USC 213(a)(17). You can read that note in the DWD 274.03 page.

Practically, this means the state expects its reading of the computer employee duties to line up with the federal treatment of the same category. Your job post should survive both readings.

That is a useful test when you draft. Write the duty list, then ask whether a federal reviewer would see the same shape. If the answer is yes, you have written a defensible post.

Draft from the duty wording in DWD 274.04(15), and keep the federal reference as a sanity check.

Hours worked and where the counting rules come from

The rule points to DWD 272.12 for how hours worked are interpreted under the chapter. That reference sits on the same DWD 274.03 page.

For a hiring manager, the practical point is simple. The way hours are counted under this chapter is not left to your posting's wording. It follows the hours-worked rules the state already has.

Write your posting to describe the work honestly. Do not engineer the language to squeeze an hours-counting outcome. The counting rules will apply regardless.

If you need detail on how specific shifts are treated, ask the Wisconsin Department of Workforce Development directly.

When a labor agreement changes the picture

There is a waiver path. Where a collectively bargained agreement exists, the department may consider a written application from labor and management to waive or modify the chapter's requirements. The basis is practical difficulty or unnecessary hardship in complying. You can read this provision at DWD 274.08.

This matters if you are hiring into a union shop. The application comes from labor and management together. You cannot file alone.

For most non-union Wisconsin tech teams, this path will not apply. It is worth knowing it exists so you do not assume the chapter is rigid in every case.

If you are in a bargained environment and the duties do not fit neatly, raise it with your labor partner early. The waiver process expects a written case about hardship, not a casual request.

Writing the posting itself

You now have the three duties. The next job is turning them into a posting a reviewer can check.

Start with the duty you are claiming. Put it in the first paragraph of the responsibilities section. Do not bury it under a paragraph about culture and perks.

Then name the specifications the work runs from. User or system design specifications are the language the state uses. If your role works from written specs, say that. If it works from an architecture review, say that.

Keep the verbs aligned. If you claim duty one, use verbs from that list. If you claim duty two, use its list. Mixed verbs across duties belong only where you are claiming the combination.

Strip out anything that pulls the reader away from program work. Hardware shipping, license renewals, and on-call ticket triage do not belong in a post that is trying to establish this category.

If a real duty does not fit, write a different posting for it. Two honest posts beat one vague one.

Illustrative example: a role that fits, and one that does not

Consider a Wisconsin employer hiring a mid-level developer. The role takes a written design spec, builds features against it, tests them, documents the changes, and ships a prototype for review. On alternate weeks, the person modifies a system-level program to keep it compatible with a kernel update.

That posting claims duty one for the feature work and duty two for the system-level work. Together, duty three covers the blend. The responsibilities section should show both shapes, in that order, with the specs named in the first paragraph.

Now change one fact. Suppose the same person only installs servers, rotates credentials, and closes tickets. None of the three duties describe that job. Write a separate posting for it, and do not borrow language from this one to make it look closer.

The test is always the same: can a reviewer point from a sentence in your posting to a duty in the rule. If yes, keep the sentence. If not, cut it or move it.

Checklist before you publish

Before the post goes live, run it through these checks.

  • Name the duty you are claiming in the first paragraph of the responsibilities list.
  • Use verbs that come from that duty's list, not a mix pulled from all three.
  • Say what specifications the work is based on and related to, so the anchor is visible.
  • Remove duties that are operations, support, or hardware work.
  • If you are claiming the combination clause, make both shapes visible.
  • If a collectively bargained agreement covers the role, flag the waiver path to your labor partner before publishing.

Each check takes a minute. Skipping one is how a posting drifts away from the rule it needs to match.

For the wider shape of a defensible posting, see Job description parts in 6 standard sections and Check 4 duty tests before you write a salaried offer.

Before you publish today

Open your current posting, put the duty you are claiming in the first line of the responsibilities section, name the design specifications the work runs from, and delete any operations, support, or hardware lines. For a job post that reads cleanly before this edit, see Job ad mistakes: 3 fixes to make before you publish.

FAQ

Does the job title matter? No. The rule reads the duties, not the label. A posting titled "Software Engineer" that describes ticket triage fails the same way a posting titled "Support Lead" that describes design-spec program work succeeds.

Can I list both duty one and duty two even if one is rare? Yes, if both genuinely apply. The combination clause exists for blended roles. The blend has to be real, and both shapes need to be visible in the responsibilities section.

What if part of the role falls outside all three duties? Split the posting. Put the qualifying work in one post and the non-qualifying work in another. Do not mix them and hope the qualifying duties carry the rest.

Where do I get a ruling on a specific role? Ask the Wisconsin Department of Workforce Development. The rule page carries the duties, the federal hook, the hours-worked cross-reference, and the waiver path.

Does the waiver path apply to a non-union team? The provision applies where a collectively bargained agreement exists. Outside a bargained environment, plan your posting to fit the duties as written.

How much of the duty list do I need in the posting? Enough that a reviewer can see the work matches. You do not need every verb. You need the specification anchor, the right verbs, and a clean separation from non-qualifying work.

Sources