IT Software Architect - .NET/Web

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs about Nelnet, mission, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, application instructions, cookie/navigation, duplicated lines. Also remove "Click here to learn more about our benefits: Benefits & Perks - Nelnet Inc." maybe considered boilerplate? It's a link to benefits; but we can keep benefits content. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should strip the EEO paragraph, the Drug Free, etc. Also remove the "Click here to learn more about our benefits: Benefits & Perks - Nelnet Inc." maybe considered navigation? It's a link; but it's part of benefits description. Might keep benefits list but remove that sentence. We need to include Pay section only if posting actually states them. It does: "Starting salary range for this role is $110k - 170k annually". So include Pay. Schedule: they mention hybrid work environment, standard hybrid schedule includes a 3/2 split, subject to change, location restrictions. So include Schedule. Benefits: they list benefits package includes medical, dental, vision, HSA and FSA, generous earned time off, 401K/student loan repayment, life insurance & AD&D insurance, employee assistance program, employee stock purchase program, tuition reimbursement, performance-based incentive pay, short- and long-term disability, and a robust wellness program. So include Benefits. Qualifications: they have EDUCATION and EXPERIENCE sections. Could combine into Qualifications. Or separate? The instruction: use headings for Qualifications, Skills, etc. We'll include Qualifications heading covering education and experience. Skills heading covering competencies. Responsibilities: they have a big list under JOB RESPONSIBILITIES. We'll put that under Responsibilities. About the role: The initial paragraphs describing Nelnet and the role overview: "We are looking for IT Software Architects who can work collaboratively..." plus description of role. That's suitable for About the role. We must not repeat job title as heading. So no heading for IT Software Architects. We must not put Job ID/requisition numbers as headings; none present. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep details like location restrictions, citizenship, security clearance, etc. Those could go under Requirements or Qualifications? Probably under Requirements (citizenship, clearance, location). We'll include them in Requirements or Qualifications. Since Qualifications already covers education/experience, maybe Requirements for citizenship/clearance/location. But we can also put them under Qualifications as part of qualifications. The instruction: prefer a few substantive sections over many thin ones. So we could combine education, experience, citizenship, clearance, location into Qualifications. But we also have Skills section for competencies. Responsibilities separate. About the role separate. Benefits, Pay, Schedule separate. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We must not include headings with filler like "commensurate with experience". Not present. Now craft HTML. We'll need

About the role

then

with the prose. We need to preserve all substantive info: The initial paragraph about Nelnet: "Nelnet is a diversified and innovative company committed to enriching lives through the power of service as a student loan servicer, professional services company, consumer loan originator and servicer, payments processor, renewable energy solutions, and K-12 and higher education expert. For over 40 years, Nelnet has been serving its customers, associates, and communities. The perks of working at Nelnet go beyond our benefits package. When you join the Nelnet team, you're part of a community invested in the success of each individual. That support comes through in our work, as we are united by our mission of creating opportunities for people where they live, learn, and work." Then the role description: "We are looking for IT Software Architects who can work collaboratively within IT Delivery and across Business Operational areas to help design and deliver pragmatic solutions based on business value and NDS IT technology direction. This role provides technical leadership to agile teams and is also expected to pull work from the product backlog periodically." We can combine into one or two paragraphs. Responsibilities: list each bullet from JOB RESPONSIBILITIES. We'll convert each sentence into

. Need to preserve all details. Let's extract responsibilities sentences: - Provides overarching architectural leadership across a portfolio of related applications, partnering with application architects, site reliability engineers, and delivery teams to maintain technical alignment and departmental consistency. - Establishes and sustains the overall architecture practice, design standards, reference patterns, and a shared design language, and captures decisions as Architecture Decision Records (ADRs) maintained in source control. - Serves as a consulting architect to delivery teams: reviews designs, facilitates architectural decisions, and guides teams toward pragmatic solutions rather than owning delivery for them. - Owns and continuously improves the developer experience, identifying and removing technology and process impediments at the team level so engineers can do their best work. - Builds bridges across organizational boundaries, aligning groups that plan, prioritize, and deliver work differently toward shared technical outcomes. - Develops durable partnerships with infrastructure and platform teams, understanding their priorities and constraints and aligning delivery and platform roadmaps so teams are unblocked rather than escalated around. - Leads adoption of AI-assisted engineering practices across development roles, serving as a power user, setting expectations for responsible use, and coaching teams on where AI adds leverage. - Drives cost optimization for both application and platform spend, making architectural trade-offs with total cost of ownership in view. - Identifies, quantifies, and sequences technical debt remediation and post-implementation cleanup as an explicit part of the delivery plan. - Provides architectural leadership during incident management and post-incident review, ensuring systemic causes are addressed at the design level. - Understands the business domain of products supported and the business drivers behind the work, so teams understand the “why” behind technical direction. - Ensures technology solution architecture and design principles are aligned with NDS IT Delivery technology direction. - Knowledgeable of all existing services, components and technologies to ensure maximum technology reuse. - Understands and exhibits skills to protect data, systems and networks and maintains secure, reliable, redundant, and accessible systems. - Independently identifies and pursues opportunities to improve solution architecture across the enterprise. - Engages with Agile teams to deliver high quality, working software solutions in alignment with team commitments. - Explores and pursues technical skills outside of current job family; actively seeks to remain technically current and increase expertise and abilities. - Strives to align personal passion and career desires with opportunities and company needs. - Works in concert with Solution Architects to drive Nelnet technology solution architecture. We'll keep them as list items. Qualifications: include education, experience, citizenship, clearance, location restrictions. Education: "BS / MS in Computer Science, Engineering, related discipline or equivalent experience" Experience: "Minimum 6 years of experience in software development with a strong expertise in at least one key competency. 2 to 3 years of experience as a technical or development leader with a demonstrated ability to deliver medium to large scale technology solutions." Citizenship & clearance: "US Citizenship and the ability to obtain a 6C Federal security clearance are required for this role." Location: "At this time, Nelnet is looking to hire candidates who live within 30 miles of the following locations: Lincoln, NE Centennial, CO Madison, WI Brownsville, TX" Also mention hybrid schedule: but that's schedule. We could combine location with schedule? But schedule separate. We'll put location under Qualifications maybe as part of requirements. But we have separate Schedule section for hybrid schedule details. So location can be in Qualifications. We'll create a

for Qualifications containing sentences. Skills: list competencies. We need to extract the competencies list from the posting. It's long with repeated items. We need to preserve all substantive info but avoid duplication. The posting includes sections: COMPETENCIES – SKILLS/KNOWLEDGE/ABILITIES: then subheadings Architecture & Technical Practice, LEADERSHIP & INFLUENCE, STRONG TECHNICAL COMPETENCY IN THE FOLLOWING. There's repetition. We need to include all unique items. Let's parse: Under Architecture & Technical Practice: - Solid grounding in architecture practice that transfers across languages and platforms, organizing code and systems in a way that makes sense, integration patterns, and technology-agnostic design judgment. - Working depth in the predominant application stack: Microsoft .NET frameworks (C# and ASP.NET), Microsoft IIS, RESTful web services, service-based architecture, message-based processing, SQL Server and/or other relational databases, and full stack development. - Secure development practices; knowledge in the area of NIST compliance, ISSO2 strongly desired. - Source control and CI/CD practice (GitLab or equivalent), including managing architecture artifacts and ADRs as code. - Understanding of best practices, standards and methods to integrate applications within the organization and with external partners. - In-depth knowledge of the full software development lifecycle; with exposure to agile or iterative approaches to delivery preferred. - Working knowledge of developer experience practices ,build and deployment pipelines, local development setup, feedback loops, and the process friction that slows teams down. - Understanding of technical debt: how it accumulates, how to quantify it, and how to plan post-implementation cleanup. - Understanding of application and platform cost drivers, with the ability to optimize spend without compromising reliability. - Hands-on fluency with AI development tooling and a track record of driving adoption across engineering teams. - Collaboration tools including JIRA, Confluence and/or Microsoft Teams. - Understanding of best practices, standards and methods to integrate applications within the organization and with external partners. (duplicate) - Strong verbal and written communication skill; with the ability to communicate at all levels of the organization. - Ability to quickly learn new technologies and business functions. - Strong analytical skills to determine effective approaches to business solutions. Then LEADERSHIP & INFLUENCE: - Strong verbal and written communication skill; with the ability to communicate at all levels of the organization. (duplicate) - Lateral thinking, inspects and reframes the question before solving it, rather than resolving the immediate problem and moving on. - Builds trust and credibility across distributed groups and partner organizations; influences technical direction without direct authority. - Good understanding of how the business operates, with the ability to connect technical decisions to business outcomes. - Strong analytical skills to determine effective approaches to business solutions. (duplicate) Then STRONG TECHNICAL COMPETENCY IN THE FOLLOWING: - Microsoft .net frameworks C# and ASP .net - Microsoft IIS - Restful Web Services - Service Based Architecture - Message Based Processing - SQL Server and/or other relational databases - Microsoft Team Foundation Server (TFS) - Full Stack Development Experience - Secure Development Practices - Collaboration tools including JIRA, Confluence and/or Microsoft Teams We need to deduplicate. Let's compile unique items: - Solid grounding in architecture practice that transfers across languages and platforms, organizing code and systems in a way that makes sense, integration patterns, and technology-agnostic design judgment. - Working depth in the predominant application stack: Microsoft .NET frameworks (C# and ASP.NET), Microsoft IIS, RESTful web services, service-based architecture, message-based processing, SQL Server and/or other relational databases, and full stack development. - Secure development practices; knowledge in the area of NIST compliance, ISSO2 strongly desired. - Source control and CI/CD practice (GitLab or equivalent), including managing architecture artifacts and ADRs as code. - Understanding of best practices, standards and methods to integrate applications within the organization and with external partners. - In-depth knowledge of the full software development lifecycle; with exposure to agile