Banner Technical Consultant IV

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. The posting includes duties, skills, education, location, pay rate, contract length, benefits. Also includes some responsibilities etc. We need to parse content: - About the role: The first paragraph describing role: "As a member of the Banner technical team, the Senior Consultant uses advanced technical expertise, superior programming skills, and deep knowledge of customer business challenges to provide outstanding consulting and technical services to the client's Managed Services client community. This role focuses on implementing, extending, integrating, and supporting modern the client's Platform and Banner solutions, including Ethos Integration, Banner Extensibility, Client Experience Experience, Data Connect, Intelligent Processes, Forms, and Banner applications. The work ranges from software troubleshooting and break/fix support to full application development and solution implementation, spanning application development, integrations, extensibility, reporting, and technical consulting. This is a customer-facing lead position that requires strong consulting, technical leadership, and communication skills. In addition, the successful candidate will be responsible for providing project leadership, needs assessment, solution architecture, integration services, and developing strong working relationships with clients while promoting best practices across the client's technology ecosystem." That's about role. - Responsibilities: The bullet list under Skills? Actually there is a "Skills" heading then bullet list of duties. The bullet list includes many responsibilities. Could treat those as Responsibilities. The "Skills" heading appears but the bullet list is actually responsibilities/skills. The posting has "Skills• Provide creative technical leadership..." etc. So we need to separate Skills section maybe for technical skills? But the bullet list includes both responsibilities and skills. However the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. So we need to decide which content goes where. We have: - About the role: prose paragraph. - Responsibilities: Could be the bullet list items (the long list). Could also include some of the duties described earlier (implementing, extending, etc). But we can treat bullet list as Responsibilities. - Requirements: Education section: "Bachelor's Degree, Certification and Experience 7 years of Banner integrations/solid understanding of data structures and Banner Ethos, Rest APIs Ellucian Forms, and Ellucian Intelligent processes Experience on building Integrations Inbound/Outbound, Event Driven, and Serverless APIs for its usage with Intelligent Processes , Forms and Experience Custom cards Development of Experience Custom Card and Experience Implementation (SSO, Personas, Baseline Cards set up etc) PostgreSQL Insights - Nice to have Ethos Integration, Business Process API Custom Spec APIs Schema Designer Conversion of existing PLSQL custom jobs/integrations to SaaS Compatible Ellucian platforms and Solutions" That's a block of text; we can treat as Requirements (or Qualifications). The instruction says we can have Requirements and Qualifications sections; we need to decide based on content. The education block includes both degree and experience; could be Requirements. Qualifications could be certifications? Not present. Might combine. - Skills: Could be the bullet list? But we already used bullet list for Responsibilities. However the bullet list is labeled "Skills". The instruction says we should include a section only when posting has real specific content for it. The posting has a "Skills" heading followed by bullet list. So we should create a Skills section with that bullet list. Thus we need to split: About the role (prose), Responsibilities (maybe from earlier description? but we already used bullet list for Skills). Actually we could treat the bullet list as Skills, and Responsibilities could be derived from the earlier prose about role? But the instruction says use

  • for any list of duties/requirements/benefits. The bullet list is a list of duties/skills. So we need to decide which heading to use for that list. Since the heading in the posting is "Skills", we should follow that and make a Skills section with
    • . Then we need Responsibilities maybe from the earlier prose? But we could also not include Responsibilities if we don't have distinct list; but we could still include Responsibilities as a section with prose derived from the role description? However the role description already covers responsibilities. Might be redundant but okay. Better: Use About the role (prose from first paragraph). Use Responsibilities (maybe we can extract from the bullet list but re-label as Responsibilities? But the heading "Skills" is explicit; we should respect that as Skills section. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using Skills heading even if the posting uses that. So we will have Skills section with bullet list. Then we need Requirements: maybe the education/experience block. Could also include location? Location is not a requirement but could be included in About the role? Probably not needed. We'll put Requirements as the education/experience block. Qualifications: maybe we don't have separate qualifications beyond requirements; could omit. Benefits: The posting includes "Health, dental, vision, 401k (provided minimum eligibility hours are met)". That's benefits. Pay: "Pay Rate: $95 - $106/Hour W-2 Only (based on Education/Experience)". That's pay. Schedule: "Location: Reston, VA (Remote with ET/CT hours)" and "Contract: 3-6months". That could be schedule? Actually schedule could be remote hours ET/CT. Could treat as Schedule: Remote with ET/CT hours, Contract length 3-6 months. We'll include Schedule section with that info. We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information. Ensure we don't lose any details. Let's extract each piece precisely. About the role paragraph: Let's copy exactly: "As a member of the Banner technical team, the Senior Consultant uses advanced technical expertise, superior programming skills, and deep knowledge of customer business challenges to provide outstanding consulting and technical services to the client's Managed Services client community. This role focuses on implementing, extending, integrating, and supporting modern the client's Platform and Banner solutions, including Ethos Integration, Banner Extensibility, Client Experience Experience, Data Connect, Intelligent Processes, Forms, and Banner applications. The work ranges from software troubleshooting and break/fix support to full application development and solution implementation, spanning application development, integrations, extensibility, reporting, and technical consulting. This is a customer-facing lead position that requires strong consulting, technical leadership, and communication skills. In addition, the successful candidate will be responsible for providing project leadership, needs assessment, solution architecture, integration services, and developing strong working relationships with clients while promoting best practices across the client's technology ecosystem." Note there is a typo: "modern the client's Platform". We'll keep as is. Responsibilities: Could we extract from the bullet list? But we already using bullet list for Skills. Maybe we can treat Responsibilities as the same bullet list but rename? However we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Responsibilities and Skills into one section? But we have headings list; we could choose to have only About the role, Requirements, Benefits, Pay, Schedule, and maybe Skills. But we need to include Responsibilities if we have content. Could we treat the bullet list as Responsibilities and not have Skills? But the bullet list is labeled Skills; but we could still treat as Responsibilities and omit Skills heading. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require us to use all; we can omit sections lacking real specific content. The bullet list is definitely specific content; we need to place it somewhere. If we omit Skills heading, we could put it under Responsibilities. That would be acceptable because the content is duties/responsibilities. The heading "Skills" in the posting is just a label; we can reinterpret. The instruction says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to match exactly. So we can choose Responsibilities for the bullet list. Thus we will have: - About the role (prose) - Responsibilities (bullet list) - Requirements (education/experience) - Benefits (health, dental, vision, 401k) - Pay (pay rate) - Schedule (location remote ET/CT, contract 3-6 months) We will not include Qualifications. Now we need to format. Responsibilities bullet list: extract each bullet from the "Skills• ..." line. The bullet list appears as a continuous string after "Skills•". Let's split by the bullet points which start with a capital letter after a bullet? The text: "Skills• Provide creative technical leadership to design and develop solutions that address customer business and technical challenges.• Lead technical discussions around the implementation and adoption of the client's Platform capabilities and modern Banner solutions.• Facilitate business process review sessions and application prototyping while providing recommendations aligned with best practices.• Consult with clients to prototype, refine, test, and debug applications, integrations, and platform extensions.• Apply design and programming skills across multiple application tiers to develop, enhance, and support applications, integrations, interfaces, reports, custom APIs, and automation processes.• Design, implement, and support integrations using Ethos Integration, Ethos Data Connect, REST APIs, GraphQL, Serverless APIs, and event-driven architecture where appropriate.• Develop Banner Extensibility solutions that satisfy customer business requirements while following upgrade-safe best practices.• Configure and implement the client Platform solutions including Experience, Ethos, Intelligent Processes, Forms, and related technologies.• Provide high-quality technical consultation and support for the client's Banner and Platform products, including Banner Extensibility, Ethos, Experience, Self-Service Banner, Data Connect, Intelligent Processes, and related solutions.• Assist customers with extensions and enhancements that satisfy business needs beyond standard product functionality while leveraging the client's Platform capabilities whenever possible.• Drive customer adoption of innovative the client's technologies and modernization initiatives.• Troubleshoot issues across Banner modules and Platform services, identifying root causes and implementing effective solutions.• Prepare technical documentation related to requirements, specifications, integrations, reporting, interfaces, extensions, and custom applications.• Develop installation, operational, and support documentation for customer solutions.• Implement proof-of-concepts and technical solutions that best align with customer objectives.• Ensure customer satisfaction throughout project delivery and support engagements.• Mentor and train less experienced consultants while reviewing technical deliverables and promoting development best practices.• Assist with effort estimation and solution planning for customer projects and enhancements" We need to split each bullet after the "•" symbol. We'll produce

      • for each. Now Requirements block: "EducationBachelor's Degree, Certification and Experience7 years of Banner integrations/solid understanding of data structures and Banner Ethos, Rest APIsEllucian Forms, and Ellucian Intelligent processesExperience on building Integrations Inbound/Outbound, Event Driven, and Serverless APIs for its usage with Intelligent Processes , Forms and Experience Custom cardsDevelopment of Experience Custom Card and Experience Implementation (SSO, Personas, Baseline Cards set up etc)PostgreSQLInsights - Nice to haveEthos Integration, Business Process APICustom Spec APIsSchema DesignerConversion of existing PLSQL custom jobs/integrations to SaaS Compatible Ellucian platforms and Solutions" We need to parse into readable sentences. It seems missing spaces. We'll add spaces where appropriate. Let's rewrite: Education: Bachelor's Degree, Certification and Experience 7 years of Banner integrations/solid understanding of data structures