Your work. Your records.

Workplace Records for Software Developers

A software workplace concern can be difficult to explain when requirements, deadlines and review responsibilities change during a project. A dated account of your assigned work and the decisions affecting it helps separate the employment issue from a technical disagreement. Use records you may retain and leave source code, credentials and customer data in their authorized systems.

Call now(800) 800-5555

Free initial case evaluation. Representation depends on work state and case eligibility. This guide explains record preparation; it does not determine whether a legal claim exists.

A record map for your role

What to organize first

  1. Assignment and scope timeline

    Note your responsibility, the communicated deadline and dated changes to scope or dependencies. Mark estimates and uncertain dates clearly.

  2. Review and escalation messages

    Identify permitted correspondence showing what you asked, whom you asked and the response. Describe restricted engineering records without exporting them.

  3. Availability and time records

    Organize your own relevant schedule, scheduled availability assignment, time entries and pay statements by period, with any correction request alongside them.

  4. Employment decisions and feedback

    Keep your own performance feedback and HR communications together with the project events they refer to, separating quotations from recollection.

Start with the work you actually do

Research, design, and develop computer and network software or specialized utility programs. Analyze user needs and develop software solutions, applying principles and techniques of computer science, engineering, and mathematical analysis. Update software or enhance existing software capabilities. May work with computer hardware engineers to integrate hardware and software systems, and develop specifications and performance requirements. May maintain databases within an application area, working individually or coordinating database development as part of a team.

O*NET classifies this occupation as Software Developers (15-1252.00). Its description covers a typical occupation, not every workplace or individual job. It does not establish employee status, overtime eligibility or employer misconduct.

  • Analyze user needs and software requirements to determine feasibility of design within time and cost constraints.Source task 21662 · updated 08/2025
  • Develop or direct software system testing or validation procedures, programming, or documentation.Source task 21669 · updated 08/2025
  • Confer with systems analysts, engineers, programmers and others to design systems and to obtain information on project limitations and capabilities, performance requirements and interfaces.Source task 21664 · updated 08/2025

A reference point for your pay records

May 2025 wage estimates by state

Compare your pay records with published BLS estimates for Software Developers (SOC 15-1252). These describe an occupation across employers. They are not a required pay rate, an overtime calculation, or evidence of discrimination or unpaid wages.

Select your work state to see its published pay range. No personal pay information is requested or sent.

The 25th and 75th percentiles mark the middle half of the estimated wage distribution; the median is its midpoint. Actual pay can differ with experience, employer, location and duties. Hourly and annual figures are shown as published, without converting one into the other.

All published state estimates for this occupation
BLS OEWS, May 2025, SOC 15-1252. Selected service states only.
StateHourly 25thHourly medianHourly 75thAnnual median
Alabama$41.82$58.91$74.18$122,540
AlaskaNot publishedNot publishedNot publishedNot published
Arizona$49.19$62.35$76.77$129,690
Arkansas$39.18$50.23$61.41$104,490
Connecticut$50.84$64.48$80.02$134,120
Delaware$54.62$63.95$79.15$133,020
Florida$49.02$62.97$79.23$130,980
Georgia$49.72$62.99$78.00$131,010
Hawaii$39.82$59.64$82.20$124,040
Idaho$45.07$63.26$77.20$131,590
Indiana$40.22$50.92$65.21$105,920
Iowa$45.96$55.24$65.91$114,890
Kansas$41.57$54.53$65.63$113,420
Kentucky$44.21$52.41$65.43$109,010
Louisiana$39.87$49.42$59.01$102,800
Maine$47.69$59.19$78.44$123,120
Michigan$46.78$60.37$67.35$125,570
Minnesota$48.88$62.52$75.36$130,050
Mississippi$33.67$45.83$61.33$95,330
Missouri$46.89$60.64$74.52$126,120
Montana$45.58$58.65$81.34$121,990
Nebraska$43.75$53.32$65.19$110,900
New Hampshire$51.56$67.17$80.71$139,720
New Mexico$46.01$59.86$76.15$124,520
New York$61.13$79.89$98.82$166,180
North Carolina$50.25$64.76$79.21$134,710
North Dakota$37.92$50.77$60.82$105,600
Ohio$46.25$54.85$65.14$114,090
Oklahoma$45.37$56.78$66.80$118,100
Pennsylvania$47.40$60.84$76.15$126,550
Rhode Island$48.86$62.78$74.06$130,590
South Dakota$38.37$46.30$58.26$96,310
Tennessee$43.63$58.86$66.77$122,430
Texas$49.69$63.54$78.14$132,150
Utah$48.33$61.93$77.20$128,810
Vermont$49.43$60.23$80.10$125,280
Virginia$51.25$65.61$82.26$136,460
West Virginia$39.76$58.18$68.56$121,000
Wisconsin$46.99$58.97$66.63$122,660
Wyoming$48.34$55.37$73.60$115,170

“Not published” preserves unavailable or suppressed source cells. “Above reporting limit” preserves a top-coded source value without inventing a number. A missing state estimate does not establish service eligibility. The data describe wage and salary employment; they do not measure self-employment income.

Source: BLS May 2025 state workbook · OEWS tables · BLS technical notes. Use your own schedule, pay statement and compensation terms to identify the question you want reviewed.

Reconstruct the assignment and its changes

Start with the project or feature in general terms, your responsibility and the deadline communicated to you. Note when scope, staffing, acceptance criteria or dependencies changed and who communicated each change. Distinguish a plan from a release or completed task. If the concern involves a missed milestone, record the blockers you reported and the responses without treating an estimate as proof of what happened.

Explain review and escalation decisions

Describe the sequence of a relevant design discussion, test result or review request. Identify who could approve the work and whether you sought clarification or escalated a concern. Keep the focus on your own interactions and employment events. Avoid exporting repositories, private issue histories, production logs or security findings; identify the kind of record that exists and discuss permitted handling with the reviewer.

Keep work patterns separate from system activity

Your own schedules, time entries, pay statements and messages about availability may help explain the periods involved. Record a relevant scheduled availability assignment or after-hours request with its date and your response. A commit timestamp or login by itself may not explain the hours worked, the task performed or who directed it, so describe any uncertainty instead of treating system activity as a complete time record.

How the occupation source is used

The selected O*NET 31.0 tasks concern analyzing user needs, developing testing and documentation procedures, and discussing design constraints with colleagues. These task records are dated August 2025. They provide occupational context for this editorial guide, not a conclusion about a particular project, overtime eligibility, employee status or the strength of a workplace claim.

Choose your next step

Review the workplace retaliation guide, unpaid wages guide, or discrimination guide if those concerns fit your experience. A job title alone does not establish a claim.

Call now(800) 800-5555
Current service-state coverage

AK, AL, AR, AZ, CT, DE, FL, GA, HI, IA, ID, IN, KS, KY, LA, ME, MI, MN, MO, MS, MT, NC, ND, NE, NH, NM, NY, OH, OK, PA, RI, SD, TN, TX, UT, VA, VT, WI, WV, WY. Eligibility is evaluated individually; this list does not promise representation.

Explore state resources

Sources and editorial notes

Guide updated 2026-10-15. Occupation description and selected tasks: O*NET occupation profile, database 31.0. Individual task update dates are shown above; they can predate the database release.

This guide uses O*NET 31.0 data from the U.S. Department of Labor, Employment and Training Administration, developed by the National Center for O*NET Development. YesLawyer selected occupational tasks and added workplace-record guidance; O*NET does not endorse this guide.

Creative Commons Attribution 4.0 · Source database. The checklist and preparation sections are YesLawyer editorial guidance, not O*NET legal advice.