IT Softwaree Engineer - Data

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. First paragraph: description about Nelnet, mission, etc. That's "About the role"? Actually "About the role" could be a summary of the role. The posting includes: "This role owns the data foundation underpinning Nelnet’s GenAI solutions for higher education and SLED clients. The Data Engineer builds and maintains the data pipelines, classification, and governance framework required to make client data safely and reliably usable by agentic AI solutions built on the Gemini Enterprise Agent Platform. Operating within Nelnet’s GenAI delivery team, this role translates the Forward Deployed Engineer’s scoped requirements into production data pipelines on Google Cloud, working closely with the GCP/Gemini Enterprise Engineer to ensure data is structured, classified, and access-controlled appropriately for AI use. Given the sensitivity of student and institutional data, this role plays a central part in surfacing data-level compliance risk — such as FERPA — before it reaches production." That's a good description for About the role. Then we have sections: Compensation range: $115,000-$135,000 based on experience. That's Pay. Then we have bullet-like paragraphs: "Data Pipeline Engineering Design, build, and maintain data pipelines using BigQuery and Dataflow (or Cloud Composer/Apache Airflow) to ingest, transform, and serve client data for GenAI use cases.Build and maintain ELT/ETL processes for batch ingestion of client source system data (SIS, ERP, casework systems) into Google Cloud analytics and RAG data stores — distinct from the live, real-time system access the GCP/Gemini Enterprise Engineer builds for agent tool use.Monitor pipeline reliability, performance, and cost, optimizing BigQuery usage and Dataflow jobs as engagements scale." That's responsibilities. Then "Data Classification & AI Readiness Classify and tag client data using Dataplex and Cloud Data Loss Prevention (DLP) to identify sensitive and regulated data, such as FERPA-protected student records, prior to AI use.Define and enforce data access controls and governance policies appropriate for higher education and SLED data sensitivity.Assess and document data readiness for AI use cases, flagging gaps in quality, completeness, or governance to the Forward Deployed Engineer." Also responsibilities. Then "Data Architecture & Integration Design data models and schemas that support both current client use cases and reusable, repeatable data patterns across engagements.Partner with client technical teams to understand source system constraints and negotiate data access and extraction approaches.Maintain technical documentation of data flows, schemas, and classification decisions for internal reuse and audit purposes." Responsibilities. Then "Delivery Execution & Quality Execute against the delivery backlog owned by the Forward Deployed Engineer, providing technical estimates and flagging data-related delivery risks.Partner with the GCP/Gemini Enterprise Engineer to ensure data pipelines feed agentic solutions with the structure and freshness required.Conduct data quality reviews and testing to maintain reliability standards across the practice." Responsibilities. Then "Cross-Functional Collaboration Partner with the GCP/Gemini Enterprise Engineer on data structure and access needed for agentic solutions and retrieval-augmented generation (RAG) pipelines.Partner with the AgentOps Engineer on infrastructure, security, and environment management for data systems.Provide technical input to the Forward Deployed Engineer and Engagement Manager on data-related scope, risk, and timeline." Responsibilities. Then "EDUCATION: Bachelor’s degree in related field or equivalent work experience EXPERIENCE: Hands-on experience building data pipelines and ELT/ETL processes for analytics or GenAI use cases on a major cloud data platform (e.g., BigQuery, Snowflake, Redshift, Synapse) — required. Direct experience with BigQuery and Dataflow (or Cloud Composer/Apache Airflow) strongly preferred; candidates with strong GenAI/AI-adjacent data engineering experience on other platforms who can ramp quickly on Google Cloud will be considered.Experience with data governance and classification tooling for identifying and managing sensitive or regulated data (e.g., Google Cloud Dataplex and Cloud DLP, or equivalent tools such as Collibra, Alation, AWS Macie); direct experience with Google's tools strongly preferred.Working knowledge of cloud storage, messaging, and access-control concepts (e.g., Cloud Storage/S3, Pub/Sub/SNS/SQS, IAM) sufficient to ramp quickly on Google Cloud's specific implementations.Google Cloud certification preferred (Professional Data Engineer), demonstrating hands-on technical fluency; foundational/business-oriented certifications do not satisfy this preference.Strong SQL skills and experience with Python for pipeline development and data transformation.Familiarity with data privacy and compliance considerations relevant to education or public sector data (e.g., FERPA, state privacy law).Experience partnering with client or partner technical teams to extract and integrate data from legacy or third-party systems (SIS, ERP, casework systems).Ability to work from a scoped backlog and translate technical requirements from the Forward Deployed Engineer into working data pipelines." That's Requirements/Qualifications. Then "Desired Competencies: Demonstrates strong technical judgment in structuring data for both immediate client use and long-term reuse.Identifies data quality, access, and compliance risks proactively before they affect delivery or client trust.Communicates technical data considerations clearly to non-technical stakeholders and the Forward Deployed Engineer.Builds for reuse, translating one-off client data work into repeatable technical assets.Takes ownership of data reliability and quality from ingestion through AI consumption.Collaborates effectively with GCP/Gemini Enterprise Engineering and AgentOps counterparts.Maintains composure and problem-solving focus when data quality or access blockers threaten delivery timelines.Seeks continuous learning given the fast-evolving nature of the Google Cloud data and AI platform." That could be Skills or Competencies. Then "COMPETENCIES – SKILLS/KNOWLEDGE/ABILITIES: Proficient in SQL development (complex queries, stored procedures, user defined functions) and performance tuning Strong knowledge of the full software development lifecycle with exposure to agile or iterative approaches to delivery preferred. Proficient in ETL design and development in at least one tool, such as SSIS Basic knowledge of C#.net for SSIS scripting Understanding of RDBMS principles Knowledge of Agile Data base design and modeling experience, preferred JIRA/TFS experience, preferred Netezza, Postgres SQL experience would be helpful Analytical and problem solving skills Ability to maintain high level of confidentiality Must demonstrate a high level of professionalism, positive attitude, and demeanor Accepts responsibility Passionate about delivering working software Ability to adapt and maintain stress tolerance in a rapidly changing environment Ability to work on a distributed team in a virtual environmental and remain motivated and productive Strong verbal and written communication skills Ability to obtain a security clearance" That's Skills. Then benefits: "Our 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." That's Benefits. We have Pay: compensation range. Schedule: not mentioned. So we should not include Schedule section. We also have About the role (maybe also a brief company overview). The first paragraph about Nelnet could be considered "About the company" but we need About the role. We could combine the company description with role description? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to decide which sections to include based on content. We have: - About the role: we have a description of the role (the paragraph about owning data foundation, building pipelines, etc). Could also include the mission statement? Probably just role description. - Responsibilities: we have multiple bullet-like sections: Data Pipeline Engineering, Data Classification & AI Readiness, Data Architecture & Integration, Delivery Execution & Quality, Cross-Functional Collaboration. We'll combine into a single Responsibilities section with

• items. - Requirements: maybe education and experience combined? The posting separates EDUCATION and EXPERIENCE. Could be Requirements. - Qualifications: maybe the Desired Competencies? Or we could treat Requirements as education+experience, Qualifications as desired competencies? But we need to avoid thin sections. Perhaps combine education+experience+desired competencies into Requirements? But we also have Skills section separate. Better: Use Requirements for education+experience. Use Qualifications for desired competencies? Or maybe Skills for the technical skills list (SQL, etc). The posting has "COMPETENCIES – SKILLS/KNOWLEDGE/ABILITIES:" which is clearly Skills. Thus: - About the role: role description paragraph. - Responsibilities: list of duty areas. - Requirements: Education + Experience (maybe combine). - Qualifications: Desired Competencies (maybe we could call it Qualifications). But we already have Skills separate. - Skills: the technical skills list. - Benefits: benefits paragraph. - Pay: compensation range. We should not include Schedule. We must not repeat job title. Not include metadata like Job ID. We must remove boilerplate: EEO, legal, accommodation, drug free, AI hiring notice, privacy policy, etc. Also remove "Click here to learn more about our benefits: Benefits & Perks - Nelnet Inc." (that's a link). Remove that. We must preserve all substantive information. So we need to include all the details from responsibilities, requirements, qualifications, skills, benefits, pay. We need to format as HTML fragment only. Let's extract each piece precisely. About the role: The paragraph starting "This role owns the data foundation underpinning Nelnet’s GenAI solutions for higher education and SLED clients." Continue until "...surfacing data-level compliance risk — such as FERPA — before it reaches production." That's the role description. We could also include the earlier company description? That is about Nelnet, not the role. The instruction says "About the role" heading. So we should not include company overview unless it's part of role description. The first paragraph about Nelnet is generic company info; could be considered "About the company" but not requested. We could omit it to avoid filler. However, we must preserve ALL substantive information; does that include company overview? It's substantive but not about the role. The instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't explicitly say we must include company overview. But "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should keep all substantive info from the posting, which includes the company overview. However, we have no heading for "About the company". We could include it as a

  before the first heading? The instruction says output ONLY the HTML fragment, no /. It didn't forbid having a leading paragraph before headings. It said use

  for section headings (e.g. About the role, Responsibilities, etc). It didn't say we cannot have other

  outside sections. So we could include a brief intro paragraph about Nelnet before the About the role heading. That would preserve the info. Thus: start with a

  containing the company overview: "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