Forward Deployed Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have:
- About the role: we have description of role, mission, etc. Could be "About the role" section.
- Responsibilities: we have "Key Responsibilities" bullet list.
- Requirements: we have "Required Skills and Experience" list.
- Qualifications: maybe overlapping with Required Skills? Could treat as Qualifications.
- Skills: maybe "Desired Competencies" list.
- Benefits: we have benefits list.
- Pay: we have compensation range.
- Schedule: not mentioned, so omit.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive info. Remove boilerplate: EEO, legal, accommodation, drug free, AI in hiring, privacy policy, etc. Also remove navigation/cookie etc. Not present.
We need to output only HTML fragment, no /, no markdown fences.
Structure: maybe not required but we can just output headings and content.
We need - for any list of duties/requirements/benefits. Use
for prose.
We must not create sections with filler like "commensurate with experience". Pay section we have actual range, so include.
Let's extract content.
About the role: The first paragraph(s) describing Nelnet and role. Let's craft a concise prose preserving info.
Original: "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. This role is the primary technical bridge between Nelnet’s GenAI delivery team and the higher education and SLED (state, local, and education) institutions it serves. The Forward Deployed Engineer works directly with client technical stakeholders to scope solutions built on the Gemini Enterprise Agent Platform (Google’s 2026 evolution of Vertex AI), translating requirements and technical compliance considerations into a scoped delivery backlog, and ensures the solutions being built map to real institutional needs rather than generic platform capabilities. This role works in partnership with an Engagement Manager, who owns the overall client relationship, contract and commercial terms, staffing, and engagement reporting to practice leadership. The Forward Deployed Engineer owns the technical relationship: solution scoping, delivery backlog, and technical risk. This division of labor differentiates Nelnet’s GenAI practice from a standard Google Cloud reseller relationship, pairing commercial accountability with deep Google Cloud technical and domain credibility rather than folding both into a single role."
We'll put that in
under About the role.
Responsibilities: list from "Key Responsibilities:" bullet points.
We need to capture each bullet.
Let's list:
- Technical Discovery & Solution Scoping
- Lead technical discovery with client stakeholders, translating institutional pain points into scoped, deliverable use cases on the Gemini Enterprise Agent Platform.
- Run requirements-gathering sessions to define technical scope, success criteria, and delivery timelines, in coordination with the Engagement Manager.
- Assess technical feasibility during the pre-sales cycle to help right-size proposed engagements; the Engagement Manager owns the commercial shape of the deal.
- Delivery Backlog & Technical Translation
- Build and maintain the delivery backlog, converting client requirements into clear, sequenced work for the GCP/Gemini Enterprise Engineer, Data Engineer, and AgentOps Engineer.
- Prioritize backlog items against client timelines, contract commitments, and technical dependencies.
- Serve as the connective layer between client-facing technical commitments and internal delivery capacity.
- Validate that delivered solutions meet the acceptance criteria defined during scoping, serving as the client-facing quality gate before an engagement is considered complete.
- Technical Compliance & Risk Surfacing
- Identify and surface technical and data compliance requirements specific to higher education and SLED environments (e.g., FERPA data handling, state data privacy statutes, accessibility requirements) early in the solution design process.
- Flag data governance, security, and technical risk to the Engagement Manager before it affects delivery timelines or client trust; contract-level and commercial compliance remain with the Engagement Manager and legal.
- Ensure solution designs account for institutional compliance obligations rather than retrofitting them after build.
- Domain Expertise & Trusted Advisory
- Bring credible, first-hand understanding of higher education or SLED operating environments to client conversations.
- Advise clients on realistic AI adoption paths given institutional constraints such as data readiness, system integration limits, and technical staff capacity.
- Build trust with client technical stakeholders as a peer, not just a vendor representative.
- Cross-Functional Collaboration
- Work closely with the GCP/Gemini Enterprise Engineer, Data Engineer, and AgentOps Engineer to ensure delivery plans are technically sound and achievable.
- Partner with the Engagement Manager, providing technical status, risks, and backlog visibility so the Engagement Manager can manage the overall client relationship and report to practice leadership.
- Partner with the SLED Account Executive and GTM lead to inform repeatable offerings based on field learnings.
We'll put each as
- under a
. Possibly group under headings? The instruction: Use - for any list of duties/requirements/benefits. So we can just have a single list? But better to keep each bullet as
- . Could also have nested? Probably just flat list.
Requirements: "Required Skills and Experience:" list.
Let's extract:
- Hands-on experience scoping and delivering GenAI/agentic AI solutions for enterprise or institutional clients — required.
- Direct experience with the Gemini Enterprise Agent Platform (Agent Builder, Model Garden, Workspace Studio, Gemini models) strongly preferred; candidates with deep GenAI delivery experience on other platforms (e.g., AWS Bedrock, Azure AI Foundry) who can ramp quickly on Google's stack will be considered.
- Working familiarity with cloud data, compute, and compliance concepts used in AI solution design (e.g., data warehousing, container/serverless compute, IAM, network security controls) sufficient to speak credibly to Google Cloud's specific implementations.
- Google Cloud certification preferred (Professional Cloud Architect or equivalent technical certification), demonstrating hands-on platform fluency; foundational/business-oriented certifications (e.g., Generative AI Leader) do not satisfy this preference.
- Experience in a client-facing technical role (solutions engineering, forward deployed engineering, technical consulting, or similar) delivering AI/ML solutions directly with enterprise or institutional clients.
- Higher education or SLED (state, local government, and K-12/education) domain experience strongly preferred.
- Demonstrated ability to translate ambiguous client requirements into a structured, sequenced delivery backlog.
- Familiarity with compliance and regulatory considerations relevant to education or public sector data (e.g., FERPA, state privacy law, procurement requirements).
- Strong written and verbal communication skills, including experience leading client discovery and requirements sessions.
- Ability to work cross-functionally with engineering teams to ensure delivery commitments are realistic and technically grounded.
- Comfortable operating in a paired delivery model with an Engagement Manager, owning technical scope and direction while deferring on commercial and account-relationship decisions.
We'll put as
- .
Qualifications: maybe we could treat Required Skills as Qualifications. But we have both Required Skills and Desired Competencies. Could map Required Skills to Qualifications, Desired Competencies to Skills. However the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have:
- Responsibilities: Key Responsibilities.
- Requirements: Required Skills and Experience.
- Qualifications: maybe we could include Google Cloud certification etc? But that's already in Required Skills. Could split: Required Skills as Requirements, and maybe "Higher education or SLED domain experience" as Qualifications? But that's also in Required Skills.
Better to follow typical: Requirements = mandatory skills; Qualifications = preferred/experience; Skills = desired competencies. But we have both required and preferred in Required Skills list. Could separate: Requirements = required items (mandatory). Qualifications = preferred items. Skills = Desired Competencies.
Let's parse Required Skills list for mandatory vs preferred.
Mandatory (required) items: "Hands-on experience scoping and delivering GenAI/agentic AI solutions for enterprise or institutional clients — required." That's mandatory.
"Experience in a client-facing technical role (solutions engineering, forward deployed engineering, technical consulting, or similar) delivering AI/ML solutions directly with enterprise or institutional clients." Not explicitly required but likely required.
"Demonstrated ability to translate ambiguous client requirements into a structured, sequenced delivery backlog." Probably required.
"Strong written and verbal communication skills, including experience leading client discovery and requirements sessions." Probably required.
"Ability to work cross-functionally with engineering teams to ensure delivery commitments are realistic and technically grounded." Probably required.
"Comfortable operating in a paired delivery model with an Engagement Manager, owning technical scope and direction while deferring on commercial and account-relationship decisions." Probably required.
Preferred items: Direct experience with Gemini Enterprise Agent Platform strongly preferred; Google Cloud certification preferred; Higher education or SLED domain experience strongly preferred; Working familiarity with cloud data, compute, compliance concepts; Familiarity with compliance and regulatory considerations.
Thus we can put mandatory in Requirements, preferred in Qualifications.
Skills: Desired Competencies list.
Let's extract Desired Competencies bullet points:
- Demonstrates sound judgment in ambiguous client situations involving incomplete information and competing priorities.
- Builds credibility quickly with both technical and non-technical stakeholders.
- Anticipates technical, compliance, and delivery risks before they surface, taking proactive action.
- Balances client advocacy with delivery feasibility and team capacity.
- Communicates complex technical concepts in terms non-technical stakeholders can act on.
- Navigates client-facing situations, including difficult conversations, with professionalism and confidence.
- Exercises influence across internal delivery teams without relying on positional authority.
- Demonstrates ownership of technical engagement outcomes from scoping through delivery.
- Works effectively in a paired model with an Engagement Manager, respecting the boundary between technical and commercial ownership.
- Seeks continuous improvement through client feedback and delivery retrospectives.
We'll put as
- under Skills.
Benefits: list from "Our benefits package includes ..." We'll extract items:
- 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,
- robust wellness program.
We'll make
- each.
Pay: compensation range: $140,000-$185,000 based on experience.
We'll put in
.
Schedule: none, omit.
Now produce HTML.
We need headings
for each section.
We'll output:
About the role
...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Skills
...
Benefits
...
Pay
$140,000-$185,000 based on experience
Make sure no extra whitespace issues.
Now craft the prose for About the role: combine the
for prose. We must not create sections with filler like "commensurate with experience". Pay section we have actual range, so include. Let's extract content. About the role: The first paragraph(s) describing Nelnet and role. Let's craft a concise prose preserving info. Original: "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. This role is the primary technical bridge between Nelnet’s GenAI delivery team and the higher education and SLED (state, local, and education) institutions it serves. The Forward Deployed Engineer works directly with client technical stakeholders to scope solutions built on the Gemini Enterprise Agent Platform (Google’s 2026 evolution of Vertex AI), translating requirements and technical compliance considerations into a scoped delivery backlog, and ensures the solutions being built map to real institutional needs rather than generic platform capabilities. This role works in partnership with an Engagement Manager, who owns the overall client relationship, contract and commercial terms, staffing, and engagement reporting to practice leadership. The Forward Deployed Engineer owns the technical relationship: solution scoping, delivery backlog, and technical risk. This division of labor differentiates Nelnet’s GenAI practice from a standard Google Cloud reseller relationship, pairing commercial accountability with deep Google Cloud technical and domain credibility rather than folding both into a single role." We'll put that in
under About the role. Responsibilities: list from "Key Responsibilities:" bullet points. We need to capture each bullet. Let's list: - Technical Discovery & Solution Scoping - Lead technical discovery with client stakeholders, translating institutional pain points into scoped, deliverable use cases on the Gemini Enterprise Agent Platform. - Run requirements-gathering sessions to define technical scope, success criteria, and delivery timelines, in coordination with the Engagement Manager. - Assess technical feasibility during the pre-sales cycle to help right-size proposed engagements; the Engagement Manager owns the commercial shape of the deal. - Delivery Backlog & Technical Translation - Build and maintain the delivery backlog, converting client requirements into clear, sequenced work for the GCP/Gemini Enterprise Engineer, Data Engineer, and AgentOps Engineer. - Prioritize backlog items against client timelines, contract commitments, and technical dependencies. - Serve as the connective layer between client-facing technical commitments and internal delivery capacity. - Validate that delivered solutions meet the acceptance criteria defined during scoping, serving as the client-facing quality gate before an engagement is considered complete. - Technical Compliance & Risk Surfacing - Identify and surface technical and data compliance requirements specific to higher education and SLED environments (e.g., FERPA data handling, state data privacy statutes, accessibility requirements) early in the solution design process. - Flag data governance, security, and technical risk to the Engagement Manager before it affects delivery timelines or client trust; contract-level and commercial compliance remain with the Engagement Manager and legal. - Ensure solution designs account for institutional compliance obligations rather than retrofitting them after build. - Domain Expertise & Trusted Advisory - Bring credible, first-hand understanding of higher education or SLED operating environments to client conversations. - Advise clients on realistic AI adoption paths given institutional constraints such as data readiness, system integration limits, and technical staff capacity. - Build trust with client technical stakeholders as a peer, not just a vendor representative. - Cross-Functional Collaboration - Work closely with the GCP/Gemini Enterprise Engineer, Data Engineer, and AgentOps Engineer to ensure delivery plans are technically sound and achievable. - Partner with the Engagement Manager, providing technical status, risks, and backlog visibility so the Engagement Manager can manage the overall client relationship and report to practice leadership. - Partner with the SLED Account Executive and GTM lead to inform repeatable offerings based on field learnings. We'll put each as
- . Possibly group under headings? The instruction: Use
- for any list of duties/requirements/benefits. So we can just have a single list? But better to keep each bullet as
- . Could also have nested? Probably just flat list.
Requirements: "Required Skills and Experience:" list.
Let's extract:
- Hands-on experience scoping and delivering GenAI/agentic AI solutions for enterprise or institutional clients — required.
- Direct experience with the Gemini Enterprise Agent Platform (Agent Builder, Model Garden, Workspace Studio, Gemini models) strongly preferred; candidates with deep GenAI delivery experience on other platforms (e.g., AWS Bedrock, Azure AI Foundry) who can ramp quickly on Google's stack will be considered.
- Working familiarity with cloud data, compute, and compliance concepts used in AI solution design (e.g., data warehousing, container/serverless compute, IAM, network security controls) sufficient to speak credibly to Google Cloud's specific implementations.
- Google Cloud certification preferred (Professional Cloud Architect or equivalent technical certification), demonstrating hands-on platform fluency; foundational/business-oriented certifications (e.g., Generative AI Leader) do not satisfy this preference.
- Experience in a client-facing technical role (solutions engineering, forward deployed engineering, technical consulting, or similar) delivering AI/ML solutions directly with enterprise or institutional clients.
- Higher education or SLED (state, local government, and K-12/education) domain experience strongly preferred.
- Demonstrated ability to translate ambiguous client requirements into a structured, sequenced delivery backlog.
- Familiarity with compliance and regulatory considerations relevant to education or public sector data (e.g., FERPA, state privacy law, procurement requirements).
- Strong written and verbal communication skills, including experience leading client discovery and requirements sessions.
- Ability to work cross-functionally with engineering teams to ensure delivery commitments are realistic and technically grounded.
- Comfortable operating in a paired delivery model with an Engagement Manager, owning technical scope and direction while deferring on commercial and account-relationship decisions.
We'll put as
- .
Qualifications: maybe we could treat Required Skills as Qualifications. But we have both Required Skills and Desired Competencies. Could map Required Skills to Qualifications, Desired Competencies to Skills. However the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have:
- Responsibilities: Key Responsibilities.
- Requirements: Required Skills and Experience.
- Qualifications: maybe we could include Google Cloud certification etc? But that's already in Required Skills. Could split: Required Skills as Requirements, and maybe "Higher education or SLED domain experience" as Qualifications? But that's also in Required Skills.
Better to follow typical: Requirements = mandatory skills; Qualifications = preferred/experience; Skills = desired competencies. But we have both required and preferred in Required Skills list. Could separate: Requirements = required items (mandatory). Qualifications = preferred items. Skills = Desired Competencies.
Let's parse Required Skills list for mandatory vs preferred.
Mandatory (required) items: "Hands-on experience scoping and delivering GenAI/agentic AI solutions for enterprise or institutional clients — required." That's mandatory.
"Experience in a client-facing technical role (solutions engineering, forward deployed engineering, technical consulting, or similar) delivering AI/ML solutions directly with enterprise or institutional clients." Not explicitly required but likely required.
"Demonstrated ability to translate ambiguous client requirements into a structured, sequenced delivery backlog." Probably required.
"Strong written and verbal communication skills, including experience leading client discovery and requirements sessions." Probably required.
"Ability to work cross-functionally with engineering teams to ensure delivery commitments are realistic and technically grounded." Probably required.
"Comfortable operating in a paired delivery model with an Engagement Manager, owning technical scope and direction while deferring on commercial and account-relationship decisions." Probably required.
Preferred items: Direct experience with Gemini Enterprise Agent Platform strongly preferred; Google Cloud certification preferred; Higher education or SLED domain experience strongly preferred; Working familiarity with cloud data, compute, compliance concepts; Familiarity with compliance and regulatory considerations.
Thus we can put mandatory in Requirements, preferred in Qualifications.
Skills: Desired Competencies list.
Let's extract Desired Competencies bullet points:
- Demonstrates sound judgment in ambiguous client situations involving incomplete information and competing priorities.
- Builds credibility quickly with both technical and non-technical stakeholders.
- Anticipates technical, compliance, and delivery risks before they surface, taking proactive action.
- Balances client advocacy with delivery feasibility and team capacity.
- Communicates complex technical concepts in terms non-technical stakeholders can act on.
- Navigates client-facing situations, including difficult conversations, with professionalism and confidence.
- Exercises influence across internal delivery teams without relying on positional authority.
- Demonstrates ownership of technical engagement outcomes from scoping through delivery.
- Works effectively in a paired model with an Engagement Manager, respecting the boundary between technical and commercial ownership.
- Seeks continuous improvement through client feedback and delivery retrospectives.
We'll put as
- under Skills.
Benefits: list from "Our benefits package includes ..." We'll extract items:
- 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,
- robust wellness program.
We'll make
- each.
Pay: compensation range: $140,000-$185,000 based on experience.
We'll put in
. Schedule: none, omit. Now produce HTML. We need headings
for each section. We'll output:
About the role
...
Responsibilities
- ... ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Pay
$140,000-$185,000 based on experience
Make sure no extra whitespace issues. Now craft the prose for About the role: combine the
- each.
Pay: compensation range: $140,000-$185,000 based on experience.
We'll put in
- under Skills.
Benefits: list from "Our benefits package includes ..." We'll extract items:
- 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,
- robust wellness program.
We'll make
- .
Qualifications: maybe we could treat Required Skills as Qualifications. But we have both Required Skills and Desired Competencies. Could map Required Skills to Qualifications, Desired Competencies to Skills. However the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have:
- Responsibilities: Key Responsibilities.
- Requirements: Required Skills and Experience.
- Qualifications: maybe we could include Google Cloud certification etc? But that's already in Required Skills. Could split: Required Skills as Requirements, and maybe "Higher education or SLED domain experience" as Qualifications? But that's also in Required Skills.
Better to follow typical: Requirements = mandatory skills; Qualifications = preferred/experience; Skills = desired competencies. But we have both required and preferred in Required Skills list. Could separate: Requirements = required items (mandatory). Qualifications = preferred items. Skills = Desired Competencies.
Let's parse Required Skills list for mandatory vs preferred.
Mandatory (required) items: "Hands-on experience scoping and delivering GenAI/agentic AI solutions for enterprise or institutional clients — required." That's mandatory.
"Experience in a client-facing technical role (solutions engineering, forward deployed engineering, technical consulting, or similar) delivering AI/ML solutions directly with enterprise or institutional clients." Not explicitly required but likely required.
"Demonstrated ability to translate ambiguous client requirements into a structured, sequenced delivery backlog." Probably required.
"Strong written and verbal communication skills, including experience leading client discovery and requirements sessions." Probably required.
"Ability to work cross-functionally with engineering teams to ensure delivery commitments are realistic and technically grounded." Probably required.
"Comfortable operating in a paired delivery model with an Engagement Manager, owning technical scope and direction while deferring on commercial and account-relationship decisions." Probably required.
Preferred items: Direct experience with Gemini Enterprise Agent Platform strongly preferred; Google Cloud certification preferred; Higher education or SLED domain experience strongly preferred; Working familiarity with cloud data, compute, compliance concepts; Familiarity with compliance and regulatory considerations.
Thus we can put mandatory in Requirements, preferred in Qualifications.
Skills: Desired Competencies list.
Let's extract Desired Competencies bullet points:
- Demonstrates sound judgment in ambiguous client situations involving incomplete information and competing priorities.
- Builds credibility quickly with both technical and non-technical stakeholders.
- Anticipates technical, compliance, and delivery risks before they surface, taking proactive action.
- Balances client advocacy with delivery feasibility and team capacity.
- Communicates complex technical concepts in terms non-technical stakeholders can act on.
- Navigates client-facing situations, including difficult conversations, with professionalism and confidence.
- Exercises influence across internal delivery teams without relying on positional authority.
- Demonstrates ownership of technical engagement outcomes from scoping through delivery.
- Works effectively in a paired model with an Engagement Manager, respecting the boundary between technical and commercial ownership.
- Seeks continuous improvement through client feedback and delivery retrospectives.
We'll put as