IT Asset Administrator
Dart Container · Mason, MI · 1 mo ago
Full-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "Help Drive Smarter Technology Investments" (intro), "What You'll Do" with subsections: Software Asset Lifecycle Management, License Compliance & Audit Readiness, Cost Optimization & Financial Analysis, Reporting, Analytics & Process Improvement. Then "What You'll Bring" with Required Qualifications and Preferred Qualifications. Then "What Success Looks Like". Then "Why Dart?" then "Overview:" then "Benefits:".
We need to use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those headings if applicable. But we can also use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those standard headings where appropriate. However the posting has different headings; we need to map content to those standard headings where possible, but preserve all substantive information. We should not invent sections; only include sections when posting has real specific content. So we need to decide which sections to include.
We have content about role description (What You'll Do) -> could map to Responsibilities. Qualifications -> Requirements/Qualifications. Skills maybe part of qualifications. Benefits -> Benefits section. Overview maybe not needed? Could be part of About the role? But we have "Overview:" describing company; could be part of About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it). So we can have an About the role
containing the introductory paragraph(s) about the role and company overview? But we need to preserve all substantive information. The overview about Dart (company description) is substantive; we could put it under About the role or maybe a separate section like "About Dart". But they only gave examples; we can still use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests to use those. Safer to map to those.
Thus we can have:
About the role
containing the introductory paragraph: "Help Drive Smarter Technology Investments Dart Container is seeking a detail-oriented and analytical IT Software Asset Administrator ..." plus maybe the overview about Dart? The overview about Dart is separate but could be included there as well. However we need to preserve all info; we can include overview in About the role.
Then Responsibilities
containing the bullet points from What You'll Do (the four subsections). We'll need to convert each bullet into - . The subheadings inside could be maybe or just part of li text. We'll keep them as part of li.
Then
Requirements
containing Required Qualifications (maybe also Preferred Qualifications? Could be under Skills? But we have both required and preferred. Could put Required under Requirements, Preferred under Skills? Or we could have Qualifications section for both required and preferred. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements for required qualifications, Qualifications for preferred? Or Skills for preferred? Let's think: Usually Requirements = required qualifications. Qualifications could be both? But we have separate Preferred Qualifications. Could put them under Qualifications as well, but we need to differentiate. Maybe we put Required under Requirements, Preferred under Qualifications. Or we could combine both under Requirements with note "Preferred". But better to follow examples: Requirements (required), Qualifications (preferred), Skills (maybe specific skills). However we have skills listed in required (Intermediate Microsoft Excel skills). Could put those under Skills.
Thus:
Requirements
for Required Qualifications (list). Use - .
Skills
for Intermediate Microsoft Excel skills etc. But those are already in required qualifications; we could still list them there. Might duplicate. Better to keep required qualifications as a list; we can include the Excel skills as part of that list. Then Skills section maybe not needed if no extra skills beyond those. But we could still include Skills for any specific technical skills like SAP experience (preferred). Actually SAP experience is under Preferred Qualifications. Could go under Skills.
Thus:
Qualifications
for Preferred Qualifications.
Skills
for maybe specific technical skills like SAP experience, etc. But we risk duplication.
Alternatively, we could have only Requirements (required) and Qualifications (preferred) and skip Skills. The instruction says we can include sections only when posting has real specific content. If we don't have distinct Skills content beyond what's already in qualifications, we could omit Skills.
We have Benefits section: we have benefits description. So Benefits
with list.
We have no explicit Pay or Schedule info, so we omit those.
We also have "What Success Looks Like" which could be maybe under Responsibilities? But it's separate; could be its own section maybe "Performance Expectations". Not in examples. Could we include as a separate heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." So maybe we can incorporate What Success Looks Like into Responsibilities or About the role. It's about outcomes; could be part of Responsibilities. We'll include it under Responsibilities as additional bullet points.
Similarly "Why Dart?" could be part of About the role.
Overview about Dart could be part of About the role.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits.
We need to ensure we don't include boilerplate like visa sponsorship, EEO, etc. Remove those lines.
We need to preserve all substantive information: that includes the visa sponsorship statement? It says "IT Software Asset Administrator Dart Container does not sponsor employment visas for this position. Applicants must be authorized to work in the United States without the need for current or future sponsorship." That's substantive? It's a requirement about work authorization. Should we keep? It's not boilerplate; it's a specific requirement. It could be placed under Requirements. We'll include it as a bullet.
Also location: "Location: Mason, MI (hybrid)" - that's substantive; could be under About the role or Responsibilities? Probably under About the role.
Company: Dart Container - we already have.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO paragraph, accommodation lines, etc.
Also remove the "Overview:" heading? We'll incorporate overview text.
We'll also remove the "Benefits:" heading but we will create Benefits section.
Now craft HTML.
We'll start with About the role
then a
containing the intro paragraphs: "Help Drive Smarter Technology Investments Dart Container is seeking a detail-oriented and analytical IT Software Asset Administrator to support the management of our enterprise software assets and licensing portfolio. In this role, you will oversee software asset lifecycle activities, ensure license compliance, support vendor audits, optimize software spend, and provide valuable insights that help the business make informed technology investment decisions. If you enjoy working at the intersection of technology, finance, vendor management, and data analysis, this is an excellent opportunity to play a key role in maximizing the value of Dart's technology investments." Then location: "Location: Mason, MI (hybrid)". Could be separate
or same.
Then maybe a
for overview: "Dart makes everyday products that give people the freedom to enjoy the food & drinks they love, wherever they are. From to-go containers and dinnerware to tamper-evident food packaging and even the red SOLO cup, Dart products have been keeping people on the go and having fun for 65 years. We’re a family-owned, family-focused company of 12,000 employees united by a shared set of values and dedicated to providing exceptional customer service. Headquartered in Mason, MI, with 30 locations in three countries, we’re proud of our ability to innovate, manufacture and lead the way with each new generation of quality products."
Now Responsibilities:
Responsibilities
then a with li for each bullet group. We'll break down the four main categories and include sub-bullets? We can just put each main category as a li with its description (including sub-bullets). Or we could nest ul inside li but not required. Simpler: each main category as li containing the description (including the sub-bullets separated by semicolons). We'll preserve the details.
Thus li: "Software Asset Lifecycle Management – Manage the full lifecycle of software assets, including requests, procurement, deployment, renewals, true-ups, and retirement activities; maintain accurate software entitlement, license, contract, warranty, and maintenance records; track software assets through designated asset management systems and repositories; ensure software lifecycle activities align with company policies, standards, and governance requirements."
Second li: "License Compliance & Audit Readiness – Monitor software license compliance and identify over-licensing, under-licensing, and audit risks; support internal and vendor-led software audits through entitlement validation and documentation management; analyze software deployments against contractual obligations and licensing rights; coordinate remediation activities to resolve licensing discrepancies and compliance concerns."
Third li: "Cost Optimization & Financial Analysis – Analyze software utilization, spend trends, and inventory data to identify cost-saving opportunities; recommend license reclamation, consolidation strategies, and alternative licensing models; support budgeting, forecasting, and renewal planning activities; identify trends in software spending and provide recommendations to improve efficiency and control costs."
Fourth li: "Reporting, Analytics & Process Improvement – Administer and maintain software and IT asset management tools; generate reports and dashboards related to software compliance, asset utilization, renewals, and spend; perform quantitative and qualitative analysis to support technology investment decisions; assist in developing and improving asset management policies, procedures, controls, and best practices; communicate software licensing requirements and lifecycle impacts to business stakeholders."
Then also include "What Success Looks Like" bullet points as additional li maybe under Responsibilities or separate? We'll add as li: "Accurate and audit-ready software asset records; improved software license compliance and reduced organizational risk; identification of software cost-optimization opportunities; effective management of renewals, contracts, and software inventory; trusted partnership with IT, Finance, Procurement, and business stakeholders."
Now Requirements: Requirements
then with li for each required qualification bullet.
List:
- Associate degree in Information Systems, Business Administration, Technology Management, or a related field.
- Experience with information gathering, financial analysis, reporting, or asset management activities.
- Understanding of software licensing, vendor contracts, renewals, entitlements, and usage rights.
- Knowledge of software asset management principles and lifecycle management processes.
- Experience investigating discrepancies, analyzing data, and resolving complex issues.
- Intermediate Microsoft Excel skills, including VLOOKUPs, pivot tables, charts, and reporting functions.
- Strong organizational skills with the ability to manage multiple priorities and maintain accurate records.
- Excellent verbal and written communication skills with strong attention to detail.
- Ability to maintain confidentiality, accuracy, and data integrity.
- Equivalent combination of experience will be considered.
- Must be authorized to work in the United States without the need for current or future sponsorship (visa sponsorship not provided).
We could combine the last as a separate bullet.
Now Qualifications (preferred
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those standard headings where appropriate. However the posting has different headings; we need to map content to those standard headings where possible, but preserve all substantive information. We should not invent sections; only include sections when posting has real specific content. So we need to decide which sections to include.
We have content about role description (What You'll Do) -> could map to Responsibilities. Qualifications -> Requirements/Qualifications. Skills maybe part of qualifications. Benefits -> Benefits section. Overview maybe not needed? Could be part of About the role? But we have "Overview:" describing company; could be part of About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it). So we can have an About the role
containing the introductory paragraph(s) about the role and company overview? But we need to preserve all substantive information. The overview about Dart (company description) is substantive; we could put it under About the role or maybe a separate section like "About Dart". But they only gave examples; we can still use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests to use those. Safer to map to those.
Thus we can have:
About the role
containing the introductory paragraph: "Help Drive Smarter Technology Investments Dart Container is seeking a detail-oriented and analytical IT Software Asset Administrator ..." plus maybe the overview about Dart? The overview about Dart is separate but could be included there as well. However we need to preserve all info; we can include overview in About the role.
Then Responsibilities
containing the bullet points from What You'll Do (the four subsections). We'll need to convert each bullet into - . The subheadings inside could be maybe or just part of li text. We'll keep them as part of li.
Then
Requirements
containing Required Qualifications (maybe also Preferred Qualifications? Could be under Skills? But we have both required and preferred. Could put Required under Requirements, Preferred under Skills? Or we could have Qualifications section for both required and preferred. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements for required qualifications, Qualifications for preferred? Or Skills for preferred? Let's think: Usually Requirements = required qualifications. Qualifications could be both? But we have separate Preferred Qualifications. Could put them under Qualifications as well, but we need to differentiate. Maybe we put Required under Requirements, Preferred under Qualifications. Or we could combine both under Requirements with note "Preferred". But better to follow examples: Requirements (required), Qualifications (preferred), Skills (maybe specific skills). However we have skills listed in required (Intermediate Microsoft Excel skills). Could put those under Skills.
Thus:
Requirements
for Required Qualifications (list). Use - .
Skills
for Intermediate Microsoft Excel skills etc. But those are already in required qualifications; we could still list them there. Might duplicate. Better to keep required qualifications as a list; we can include the Excel skills as part of that list. Then Skills section maybe not needed if no extra skills beyond those. But we could still include Skills for any specific technical skills like SAP experience (preferred). Actually SAP experience is under Preferred Qualifications. Could go under Skills.
Thus:
Qualifications
for Preferred Qualifications.
Skills
for maybe specific technical skills like SAP experience, etc. But we risk duplication.
Alternatively, we could have only Requirements (required) and Qualifications (preferred) and skip Skills. The instruction says we can include sections only when posting has real specific content. If we don't have distinct Skills content beyond what's already in qualifications, we could omit Skills.
We have Benefits section: we have benefits description. So Benefits
with list.
We have no explicit Pay or Schedule info, so we omit those.
We also have "What Success Looks Like" which could be maybe under Responsibilities? But it's separate; could be its own section maybe "Performance Expectations". Not in examples. Could we include as a separate heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." So maybe we can incorporate What Success Looks Like into Responsibilities or About the role. It's about outcomes; could be part of Responsibilities. We'll include it under Responsibilities as additional bullet points.
Similarly "Why Dart?" could be part of About the role.
Overview about Dart could be part of About the role.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits.
We need to ensure we don't include boilerplate like visa sponsorship, EEO, etc. Remove those lines.
We need to preserve all substantive information: that includes the visa sponsorship statement? It says "IT Software Asset Administrator Dart Container does not sponsor employment visas for this position. Applicants must be authorized to work in the United States without the need for current or future sponsorship." That's substantive? It's a requirement about work authorization. Should we keep? It's not boilerplate; it's a specific requirement. It could be placed under Requirements. We'll include it as a bullet.
Also location: "Location: Mason, MI (hybrid)" - that's substantive; could be under About the role or Responsibilities? Probably under About the role.
Company: Dart Container - we already have.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO paragraph, accommodation lines, etc.
Also remove the "Overview:" heading? We'll incorporate overview text.
We'll also remove the "Benefits:" heading but we will create Benefits section.
Now craft HTML.
We'll start with About the role
then a
containing the intro paragraphs: "Help Drive Smarter Technology Investments Dart Container is seeking a detail-oriented and analytical IT Software Asset Administrator to support the management of our enterprise software assets and licensing portfolio. In this role, you will oversee software asset lifecycle activities, ensure license compliance, support vendor audits, optimize software spend, and provide valuable insights that help the business make informed technology investment decisions. If you enjoy working at the intersection of technology, finance, vendor management, and data analysis, this is an excellent opportunity to play a key role in maximizing the value of Dart's technology investments." Then location: "Location: Mason, MI (hybrid)". Could be separate
or same.
Then maybe a
for overview: "Dart makes everyday products that give people the freedom to enjoy the food & drinks they love, wherever they are. From to-go containers and dinnerware to tamper-evident food packaging and even the red SOLO cup, Dart products have been keeping people on the go and having fun for 65 years. We’re a family-owned, family-focused company of 12,000 employees united by a shared set of values and dedicated to providing exceptional customer service. Headquartered in Mason, MI, with 30 locations in three countries, we’re proud of our ability to innovate, manufacture and lead the way with each new generation of quality products."
Now Responsibilities:
Responsibilities
then a with li for each bullet group. We'll break down the four main categories and include sub-bullets? We can just put each main category as a li with its description (including sub-bullets). Or we could nest ul inside li but not required. Simpler: each main category as li containing the description (including the sub-bullets separated by semicolons). We'll preserve the details.
Thus li: "Software Asset Lifecycle Management – Manage the full lifecycle of software assets, including requests, procurement, deployment, renewals, true-ups, and retirement activities; maintain accurate software entitlement, license, contract, warranty, and maintenance records; track software assets through designated asset management systems and repositories; ensure software lifecycle activities align with company policies, standards, and governance requirements."
Second li: "License Compliance & Audit Readiness – Monitor software license compliance and identify over-licensing, under-licensing, and audit risks; support internal and vendor-led software audits through entitlement validation and documentation management; analyze software deployments against contractual obligations and licensing rights; coordinate remediation activities to resolve licensing discrepancies and compliance concerns."
Third li: "Cost Optimization & Financial Analysis – Analyze software utilization, spend trends, and inventory data to identify cost-saving opportunities; recommend license reclamation, consolidation strategies, and alternative licensing models; support budgeting, forecasting, and renewal planning activities; identify trends in software spending and provide recommendations to improve efficiency and control costs."
Fourth li: "Reporting, Analytics & Process Improvement – Administer and maintain software and IT asset management tools; generate reports and dashboards related to software compliance, asset utilization, renewals, and spend; perform quantitative and qualitative analysis to support technology investment decisions; assist in developing and improving asset management policies, procedures, controls, and best practices; communicate software licensing requirements and lifecycle impacts to business stakeholders."
Then also include "What Success Looks Like" bullet points as additional li maybe under Responsibilities or separate? We'll add as li: "Accurate and audit-ready software asset records; improved software license compliance and reduced organizational risk; identification of software cost-optimization opportunities; effective management of renewals, contracts, and software inventory; trusted partnership with IT, Finance, Procurement, and business stakeholders."
Now Requirements: Requirements
then with li for each required qualification bullet.
List:
- Associate degree in Information Systems, Business Administration, Technology Management, or a related field.
- Experience with information gathering, financial analysis, reporting, or asset management activities.
- Understanding of software licensing, vendor contracts, renewals, entitlements, and usage rights.
- Knowledge of software asset management principles and lifecycle management processes.
- Experience investigating discrepancies, analyzing data, and resolving complex issues.
- Intermediate Microsoft Excel skills, including VLOOKUPs, pivot tables, charts, and reporting functions.
- Strong organizational skills with the ability to manage multiple priorities and maintain accurate records.
- Excellent verbal and written communication skills with strong attention to detail.
- Ability to maintain confidentiality, accuracy, and data integrity.
- Equivalent combination of experience will be considered.
- Must be authorized to work in the United States without the need for current or future sponsorship (visa sponsorship not provided).
We could combine the last as a separate bullet.
Now Qualifications (preferred
About the role
containing the introductory paragraph: "Help Drive Smarter Technology Investments Dart Container is seeking a detail-oriented and analytical IT Software Asset Administrator ..." plus maybe the overview about Dart? The overview about Dart is separate but could be included there as well. However we need to preserve all info; we can include overview in About the role. ThenResponsibilities
containing the bullet points from What You'll Do (the four subsections). We'll need to convert each bullet into- . The subheadings inside could be maybe or just part of li text. We'll keep them as part of li.
Then
Requirements
containing Required Qualifications (maybe also Preferred Qualifications? Could be under Skills? But we have both required and preferred. Could put Required under Requirements, Preferred under Skills? Or we could have Qualifications section for both required and preferred. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements for required qualifications, Qualifications for preferred? Or Skills for preferred? Let's think: Usually Requirements = required qualifications. Qualifications could be both? But we have separate Preferred Qualifications. Could put them under Qualifications as well, but we need to differentiate. Maybe we put Required under Requirements, Preferred under Qualifications. Or we could combine both under Requirements with note "Preferred". But better to follow examples: Requirements (required), Qualifications (preferred), Skills (maybe specific skills). However we have skills listed in required (Intermediate Microsoft Excel skills). Could put those under Skills. Thus:
Requirements
for Required Qualifications (list). Use- .
Skills
for Intermediate Microsoft Excel skills etc. But those are already in required qualifications; we could still list them there. Might duplicate. Better to keep required qualifications as a list; we can include the Excel skills as part of that list. Then Skills section maybe not needed if no extra skills beyond those. But we could still include Skills for any specific technical skills like SAP experience (preferred). Actually SAP experience is under Preferred Qualifications. Could go under Skills. Thus:Qualifications
for Preferred Qualifications.Skills
for maybe specific technical skills like SAP experience, etc. But we risk duplication. Alternatively, we could have only Requirements (required) and Qualifications (preferred) and skip Skills. The instruction says we can include sections only when posting has real specific content. If we don't have distinct Skills content beyond what's already in qualifications, we could omit Skills. We have Benefits section: we have benefits description. SoBenefits
with list. We have no explicit Pay or Schedule info, so we omit those. We also have "What Success Looks Like" which could be maybe under Responsibilities? But it's separate; could be its own section maybe "Performance Expectations". Not in examples. Could we include as a separate heading? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." So maybe we can incorporate What Success Looks Like into Responsibilities or About the role. It's about outcomes; could be part of Responsibilities. We'll include it under Responsibilities as additional bullet points. Similarly "Why Dart?" could be part of About the role. Overview about Dart could be part of About the role. Thus final sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits. We need to ensure we don't include boilerplate like visa sponsorship, EEO, etc. Remove those lines. We need to preserve all substantive information: that includes the visa sponsorship statement? It says "IT Software Asset Administrator Dart Container does not sponsor employment visas for this position. Applicants must be authorized to work in the United States without the need for current or future sponsorship." That's substantive? It's a requirement about work authorization. Should we keep? It's not boilerplate; it's a specific requirement. It could be placed under Requirements. We'll include it as a bullet. Also location: "Location: Mason, MI (hybrid)" - that's substantive; could be under About the role or Responsibilities? Probably under About the role. Company: Dart Container - we already have. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO paragraph, accommodation lines, etc. Also remove the "Overview:" heading? We'll incorporate overview text. We'll also remove the "Benefits:" heading but we will create Benefits section. Now craft HTML. We'll start with
About the role
then acontaining the intro paragraphs: "Help Drive Smarter Technology Investments Dart Container is seeking a detail-oriented and analytical IT Software Asset Administrator to support the management of our enterprise software assets and licensing portfolio. In this role, you will oversee software asset lifecycle activities, ensure license compliance, support vendor audits, optimize software spend, and provide valuable insights that help the business make informed technology investment decisions. If you enjoy working at the intersection of technology, finance, vendor management, and data analysis, this is an excellent opportunity to play a key role in maximizing the value of Dart's technology investments." Then location: "Location: Mason, MI (hybrid)". Could be separate
or same. Then maybe a
for overview: "Dart makes everyday products that give people the freedom to enjoy the food & drinks they love, wherever they are. From to-go containers and dinnerware to tamper-evident food packaging and even the red SOLO cup, Dart products have been keeping people on the go and having fun for 65 years. We’re a family-owned, family-focused company of 12,000 employees united by a shared set of values and dedicated to providing exceptional customer service. Headquartered in Mason, MI, with 30 locations in three countries, we’re proud of our ability to innovate, manufacture and lead the way with each new generation of quality products." Now Responsibilities:
Responsibilities
then a- with li for each bullet group. We'll break down the four main categories and include sub-bullets? We can just put each main category as a li with its description (including sub-bullets). Or we could nest ul inside li but not required. Simpler: each main category as li containing the description (including the sub-bullets separated by semicolons). We'll preserve the details.
Thus li: "Software Asset Lifecycle Management – Manage the full lifecycle of software assets, including requests, procurement, deployment, renewals, true-ups, and retirement activities; maintain accurate software entitlement, license, contract, warranty, and maintenance records; track software assets through designated asset management systems and repositories; ensure software lifecycle activities align with company policies, standards, and governance requirements."
Second li: "License Compliance & Audit Readiness – Monitor software license compliance and identify over-licensing, under-licensing, and audit risks; support internal and vendor-led software audits through entitlement validation and documentation management; analyze software deployments against contractual obligations and licensing rights; coordinate remediation activities to resolve licensing discrepancies and compliance concerns."
Third li: "Cost Optimization & Financial Analysis – Analyze software utilization, spend trends, and inventory data to identify cost-saving opportunities; recommend license reclamation, consolidation strategies, and alternative licensing models; support budgeting, forecasting, and renewal planning activities; identify trends in software spending and provide recommendations to improve efficiency and control costs."
Fourth li: "Reporting, Analytics & Process Improvement – Administer and maintain software and IT asset management tools; generate reports and dashboards related to software compliance, asset utilization, renewals, and spend; perform quantitative and qualitative analysis to support technology investment decisions; assist in developing and improving asset management policies, procedures, controls, and best practices; communicate software licensing requirements and lifecycle impacts to business stakeholders."
Then also include "What Success Looks Like" bullet points as additional li maybe under Responsibilities or separate? We'll add as li: "Accurate and audit-ready software asset records; improved software license compliance and reduced organizational risk; identification of software cost-optimization opportunities; effective management of renewals, contracts, and software inventory; trusted partnership with IT, Finance, Procurement, and business stakeholders."
Now Requirements:
Requirements
then- with li for each required qualification bullet.
List:
- Associate degree in Information Systems, Business Administration, Technology Management, or a related field.
- Experience with information gathering, financial analysis, reporting, or asset management activities.
- Understanding of software licensing, vendor contracts, renewals, entitlements, and usage rights.
- Knowledge of software asset management principles and lifecycle management processes.
- Experience investigating discrepancies, analyzing data, and resolving complex issues.
- Intermediate Microsoft Excel skills, including VLOOKUPs, pivot tables, charts, and reporting functions.
- Strong organizational skills with the ability to manage multiple priorities and maintain accurate records.
- Excellent verbal and written communication skills with strong attention to detail.
- Ability to maintain confidentiality, accuracy, and data integrity.
- Equivalent combination of experience will be considered.
- Must be authorized to work in the United States without the need for current or future sponsorship (visa sponsorship not provided).
We could combine the last as a separate bullet.
Now Qualifications (preferred
- .