Jobs · Purchasing · South Carolina

Software License Analyst (Procurement, Analyst)

The MIL Corporation · Charleston, SC · 1 mo ago
Purchasing$84k–$94k/yrFull-time
We need to output HTML fragment with sections only if real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: EEO, etc. Must keep substantive info: Clearance Required, Education Required, US Citizenship, Summary, Responsibilities, Required Qualifications, Desired Qualifications, Education (already), Clearance, Compensation (benefits and salary range), maybe Schedule? The posting says "This position currently requires an on-site schedule. Schedule is subject to change based on company/contract requirements." That's schedule info, but it's vague; we should include Schedule section only if real specific content. It says on-site schedule, subject to change. That's somewhat specific but not detailed. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule: on-site schedule, subject to change. So we can include Schedule section with that content. Benefits: they mention benefits in Compensation paragraph: health, life, disability, retirement, PTO, professional growth, tuition assistance. Also they say "Additional benefits and incentives may also apply". So we have benefits content. So we can include Benefits section. Pay: they give salary range $84k-$94k. So include Pay section. We must not include filler like "commensurate with experience". Not present. We must not duplicate lines. We need headings:

for each section: About the role? The summary could be "About the role" or "Summary". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We have Summary paragraph; we could label as "About the role". Responsibilities as heading. Required Qualifications as "Requirements" or "Qualifications". Desired Qualifications maybe as "Preferred Qualifications" but not in list; we could combine under Qualifications? But instruction: prefer few substantive sections over many thin ones. Could combine Required and Desired under Qualifications with subheadings? But we must use

for section headings only; we could have one Qualifications section and inside we can have

describing required and desired. However we need to preserve all substantive info; we can list required and desired as separate

    maybe. But we need to keep headings only for sections; we can have a single Qualifications

    and then inside we can have two

    or

      for required and desired. That's acceptable. We also have Education and Clearance as separate items; they could be part of Qualifications or separate sections. The instruction list includes Qualifications, Skills, Benefits, Pay, Schedule. Education and Clearance could be part of Qualifications. But we could also make separate sections if they have content. However they'd be thin; maybe combine. We have "Clearance Required: Ability to Obtain a Top Secret", "Education Required: BA/BS", "US Citizenship: Required". Those are metadata; we could put them in a short

      under a section like "Key Requirements". But we must not create headings for minor metadata. So we can include them in a paragraph after summary maybe. We need to output only HTML fragment. Let's structure:

      About the role

      Summary paragraph.

      Responsibilities

      • ...
      • ...

      Qualifications

      Required: ... list as

        maybe.

        Preferred: ... list as

          maybe.

          But we need to preserve all details. Could embed required and desired as separate
            under Qualifications. We also need Benefits, Pay, Schedule sections. Benefits: list health, life, disability, retirement plans, paid time off, professional growth, tuition assistance. Could be
              . Pay: salary range $84,000 - $94,000 per year. Schedule: on-site schedule, subject to change. We must not include boilerplate like EEO etc. Let's extract responsibilities list from text: - Manage the organization’s software license portfolio, including license inventory, assignments, utilization, renewals, costs, and contractual entitlements. - Maintain accurate records of software products, license quantities and types, assigned users, renewal dates, costs, and entitlement information. - Administer vendor licensing portals and manage license assignments, removals, transfers, and other day-to-day licensing activities. - Provide first-line support for software licensing and access issues, coordinating with vendors and technical teams to resolve more complex issues. - Monitor software usage and license utilization to identify unused, underutilized, duplicative, or unnecessary licenses and recommend appropriate actions. - Analyze licensing and utilization data to identify opportunities for cost savings, optimization, consolidation, and license reductions. - Evaluate new software requests against existing enterprise capabilities and identify opportunities to leverage current products before acquiring new solutions. - Maintain working knowledge of the capabilities, licensing models, and primary use cases of software products across the organization’s portfolio. - Partner with business and technical stakeholders to identify overlapping software capabilities and support rationalization, standardization, and consolidation efforts. - Support software renewal planning and forecasting by providing procurement teams with accurate license quantities, utilization data, requirements, and renewal recommendations. - Coordinate with software vendors regarding licensing models, product changes, renewals, account administration, and licensing-related issues. - Track software agreements, entitlements, and licensing terms to support contractual and licensing compliance. - Develop and maintain software portfolio reports, dashboards, inventories, and metrics to provide visibility into utilization, costs, renewals, and portfolio trends. - Develop, document, and standardize software license management processes, procedures, and best practices to improve consistency and efficiency. - Monitor changes in vendor licensing models, product offerings, and software capabilities and assess potential impacts to cost, compliance, and the organization’s software portfolio. - Travel 0-10% Required Qualifications Note: The "Travel 0-10%" appears before Required Qualifications heading; it's a responsibility? It's a separate line. We'll include as a responsibility bullet. Now Required Qualifications list: - 3+ years of experience in software asset management, IT asset management, software licensing, enterprise application management, or a related field. - Experience managing enterprise software licenses throughout the license lifecycle. - Experience administering software licensing/vendor portals and managing user license assignments. - Strong understanding of software licensing models, entitlements, subscriptions, renewals, and utilization. - Ability to evaluate software capabilities and identify overlapping or redundant tools within an enterprise environment. - Strong analytical skills with experience analyzing licensing, utilization, and cost data. - Advanced proficiency with Microsoft Excel and experience maintaining software inventories, reports, or dashboards. - Ability to troubleshoot software licensing and access issues and coordinate resolution with vendors and technical teams. Desired Qualifications list: - Experience with Software Asset Management (SAM) or IT Asset Management (ITAM) programs and tools. - Experience managing enterprise SaaS, cloud, developer, collaboration, and productivity software. - Familiarity with products/platforms such as Microsoft, Atlassian/Jira, Adobe, ServiceNow, AWS, Azure, or similar enterprise technologies. - Experience with software portfolio rationalization, application rationalization, or enterprise software consolidation. - Experience supporting software procurement and renewal activities within a federal environment. - Familiarity with federal IT, cybersecurity, and software compliance requirements. - SAM, ITAM, ITIL, FinOps, or related certification is a plus. Education: BA/BS (already in Required? Actually Education separate). We'll include in Qualifications maybe. Clearance: Ability to obtain Top Secret clearance. US Citizenship: Required. We could include those as bullet points under Qualifications as well. But we need to avoid too thin sections. Perhaps we make a section "Key Requirements" with those items. But instruction: Prefer a few substantive sections over many thin ones. So maybe we have sections: About the role, Responsibilities, Qualifications (including required, preferred, education, clearance, citizenship), Benefits, Pay, Schedule. That's 6 sections. Now we need to ensure we don't repeat job title. Not needed. Now produce HTML. We'll need to escape any HTML special characters? Not needed. Let's craft.

              About the role

              The MIL Corporation seeks a Software License Analyst (Procurement, Analyst) to support a Federal Government client at our Charleston, SC location. The Software License Analyst will be responsible for the lifecycle management and administration of the organization’s enterprise software portfolio, including license inventory, utilization, assignments, renewals, vendor coordination, compliance, and portfolio optimization. This role will serve as a central resource for understanding the organization’s existing software capabilities and licensing environment. The Software License Analyst will partner with technical teams, business stakeholders, procurement personnel, and vendors to maximize the use of existing software investments, identify redundant or underutilized products, support software consolidation efforts, and ensure licenses are appropriately assigned and managed throughout their lifecycle. This position currently requires an on-site schedule. Schedule is subject to change based on company/contract requirements.

              But note we already have Schedule section later; we might not need to repeat schedule in About the role. However the summary includes schedule mention; we could keep it but it's okay. However we might duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that sentence somewhere. If we move schedule to its own section, we could still keep it in About the role but that would duplicate. Better to keep schedule mention only in Schedule section and remove from About the role. But then we lose that sentence from summary? The summary originally didn't include schedule; schedule was separate paragraph after responsibilities. Actually the text: "This position currently requires an on-site schedule. Schedule is subject to change based on company/contract requirements." That's after responsibilities before Required Qualifications. So we can treat that as schedule info, not part of summary. So we should not include it in About the role. So About the role will be just the summary paragraph before responsibilities. Let's extract summary: "The MIL Corporation seeks a Software License Analyst (Procurement, Analyst) to support a Federal Government client at our Charleston, SC location. The Software License Analyst will be responsible for the lifecycle management and administration of the organization’s enterprise software portfolio, including license inventory, utilization, assignments, renewals, vendor coordination, compliance, and portfolio optimization. This role will serve as a central resource for understanding the organization’s existing software capabilities and licensing environment. The Software License Analyst will partner with technical teams, business stakeholders, procurement personnel, and vendors to maximize the use of existing software investments, identify redundant or underutilized products, support software consolidation efforts, and ensure licenses are appropriately assigned and managed throughout their lifecycle." That's the summary. Now Responsibilities as above. Now Qualifications section: We'll include required, preferred, education, clearance, citizenship. We can structure as:

              Qualifications

              Required:

                ...

              Preferred:

                ...

              Education: BA/BS

              Clearance: Ability to obtain Top Secret clearance

              Citizenship: US Citizenship required

              That preserves all. Now Benefits section: We need to extract benefits: health, life, disability, and retirement plans, paid time off, opportunities for professional growth and tuition assistance. Also "Additional benefits and incentives may also apply". We'll list the known ones.

              Benefits

              • Health insurance
              • Life insurance
              • Disability insurance
              • Retirement plans
              • Paid time off
              • Professional growth opportunities
              • Tuition assistance
              We could also mention that additional benefits may apply. Now Pay section:

              Pay

              Projected compensation range: $84,000 - $94,000 per year

Similar jobs

Software Analyst

USTMeridian, ID· 4 days ago
$75k–$113k/yrapply on usource.ripplehire.com

Software Analyst

Weatherbie Capital, LLCNew York, NY· 3 mo ago
Engineering$225k/yrapply on ats.rippling.com

Software Analyst

i-Link SolutionsAlbany, NY· 3 mo ago
Engineeringapply on www1.jobdiva.com

Software Business Analyst

UL SolutionsFremont, CA· 2 wk ago
Analyst$85k–$110k/yrapply on fa-eups-saasfaprod1.fa.ocs.oraclecloud.com