Colleague Technical Consultant - United States Remote
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. We have content: About Ellucian (company overview) maybe not needed? The instruction says we can include sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "About The Opportunity" which is like role description. Could map to "About the role". Also "What You Will Bring" is requirements/qualifications. Also "Desired Ellucian & Partner Product Experience:" and "Desired Experience & Knowledge:" could be qualifications/skills. Also "What makes #Ellucianlife" is benefits. So we can have sections: About the role (maybe combine About Ellucian and About The Opportunity?), Responsibilities (maybe from "Where you will make an impact"), Requirements/Qualifications (What You Will Bring + Desired...), Skills (maybe technical skills list), Benefits (What makes #Ellucianlife). No Pay or Schedule info present, so omit those sections.
We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting.
We need to format using headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what constitutes a list. Many bullet-like sentences separated by periods. We can convert each sentence into
- if they are list items. The instruction: Use
- for any list of duties/requirements/benefits. So we need to identify lists.
Let's extract sections:
1. About the role: Could include "About Ellucian" company description and "About The Opportunity". But "About Ellucian" is company overview, not role. Might be better to put under "About the role" a brief description of the role and maybe company context. However we must not invent headings; we can include "About the role" heading and put the content from "About The Opportunity" plus maybe company description as prose. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have heading About the role.
We'll put under About the role: combine the paragraphs from "About Ellucian" and "About The Opportunity". But "About Ellucian" is generic company info; still substantive. We'll keep it.
We need to use
for prose. So we can have a
containing the combined text (maybe two paragraphs). Or we could split into multiple
elements. Probably each paragraph separate
.
2. Responsibilities: from "Where you will make an impact". Those are bullet-like sentences: "Meet regularly (typically weekly) with each customer to maintain open communication." etc. We'll make a
- list.
3. Requirements / Qualifications: from "What You Will Bring". That's a list of items each starting with bold? Actually they are sentences: "A minimum of 3-5 years of Ellucian product technical experience working in a customer-facing role within an Ellucian software environment", "Hands-on experience providing technical support for Colleague", etc. We'll make a
- list.
Also "Desired Ellucian & Partner Product Experience:" and "Desired Experience & Knowledge:" are additional desired qualifications; could be part of same list or separate. We could combine them under Requirements as well, but maybe better to have a separate "Qualifications" section for required and desired? The instruction allows sections like Requirements, Qualifications, Skills. We could have Requirements for mandatory, Qualifications for desired, Skills for technical skills. But we need to avoid thin sections. Let's think.
We have many items: mandatory experience, hands-on experience, patching/upgrading, SSO, Ethos Integration, Colleague architecture, UniData admin, MS SQL DBA, SQL/T-SQL, Shell scripting, customer service focus, initiative, independent work. Then desired: Colleague ODS, reporting tools, Ellucian Analytics admin, Ellucian Workflow, Ethos Identity Services, Ellucian CRM Recruit or Microsoft Dynamics. Desired Experience & Knowledge: Microsoft certifications, AWS certifications, Linux or Windows Server admin, project management/team leadership.
We could have a section "Requirements" for the mandatory items, and "Qualifications" for desired items. Or we could have "Skills" for technical skills list (like SSO, Ethos Integration, UniData, SQL, Shell scripting). But the instruction says prefer a few substantive sections over many thin ones. So maybe combine all into one "Requirements" section (including both mandatory and desired) as a list. That would be substantive.
But we also have "What makes #Ellucianlife" benefits list. That's definitely a Benefits section.
Thus we can have:
- About the role (prose)
- Responsibilities (list)
- Requirements (list) (including both mandatory and desired)
- Benefits (list)
We need to ensure we don't create empty sections.
Now we need to format lists properly: each item as
- . Ensure we preserve all details exactly as in posting, no omission.
Let's extract the exact text.
About Ellucian paragraph:
"Ellucian powers innovation for higher education, partnering with approximately 3,000 customers across 50 countries, serving more than 21 million students. Ellucian's AI-powered platform, trained on the richest dataset available in higher education, drives efficiency, personalized experiences, and strengthened engagement for all students, faculty and staff. Fueled by decades of experience with a singular focus on the unique needs of learning institutions, the Ellucian platform features best-in-class SaaS capabilities and delivers insights needed now and into the future. These solutions and services span the entire student lifecycle, including data-rich tools for student recruitment, enrollment, and retention to workforce analytics, fundraising, and alumni engagement. Ellucian's innovative solutions, vast ecosystem of partners and user community of more than 45,000 provides best practices leading to greater institutional success and achieving better student outcomes."
About The Opportunity paragraph:
"Ellucian is seeking a talented individual that has strong technical, hands-on, working knowledge of Colleague technical - Consultant role that is looking for an opportunity to continue learning and helping Ellucian customers. This role provides personalized, on-going guidance and support for Colleague technical customer business operations post-implementation, enabling customers to maximize value from their solutions. The role also works closely with the customer by building a relationship with their points of contact, understanding their business needs, troubleshooting and resolving operational issues, and assessing the customer’s current use of and knowledge of the Ellucian solution. To be successful in the role, you must possess strong knowledge of Colleague application and system administration, have current hands-on experience managing, installing, and updating Colleague applications, and have an overall understanding of Ellucian’s broad portfolio of solutions. Knowledge and current hands-on experience of Ethos Integration, ILP, and DataConnect in addition to Colleague system administration is a plus."
Note there is a slight grammatical oddity: "Colleague technical - Consultant role". We'll keep as is.
Now Responsibilities (Where you will make an impact):
List items:
- Meet regularly (typically weekly) with each customer to maintain open communication.
- Work with customer to gain an understanding of their goals, priorities, processes and challenges related to the supported applications.
- Provide guidance and assist with reviewing, planning and deploying changes and new functionality.
- Work with customers to review and modernize existing business processes, troubleshoot and resolve operational issues, provide direction on how to implement new modules or functionality in Colleague, and provide proactive communications about new functionality or defects.
- Conduct knowledge sharing sessions in response to specific customer needs.
- Promote customer usage of Ellucian resources such as the Solution Center, product documentation and Communities.
Now Requirements (What You Will Bring):
List items:
- A minimum of 3-5 years of Ellucian product technical experience working in a customer-facing role within an Ellucian software environment
- Hands-on experience providing technical support for Colleague
- In depth experience patching and upgrading Colleague and technical administration of Colleague and related technology in the Colleague ecosystem
- Single Sign-on Configuration/Support (SSO) including CAS and SAML2 protocols
- Ellucian Ethos Integration configuration and administration
- Colleague architecture and data layers
- UniData administration, operation and maintenance
- Microsoft SQL Server database administration (DBA)
- SQL & Microsoft T-SQL
- Shell scripting
- A strong focus on customer service
- Taking initiative and delivering on commitments to customers
- Working independently on many concurrent activities
Now Desired Ellucian & Partner Product Experience:
List items:
- Colleague Operational Data Store (ODS)
- reporting tools such as Entrinsik Informer or SAP Business Objects
- Ellucian Analytics administration
- Ellucian Workflow
- Ethos Identity Services
- Ellucian CRM Recruit or Microsoft Dynamics
Now Desired Experience & Knowledge:
List items:
- Microsoft certifications (MCSA, MCSE)
- Amazon Web Services (AWS) certifications
- Linux or Microsoft Windows Server administration
- project management or team leadership
Now Benefits (What makes #Ellucianlife):
List items:
- Comprehensive health coverage: medical, dental, and vision
- Flexible time off
- Thrive Flex Lifestyle Account (LSA) that allows you to contribute towards your health, financial or learning interests
- 401k w/ match & BrightPlan - to help you save for the future
- Parental Leave
- 5 charitable days to support the community that supports us
- Telemedicine
- Wellness
- Headspace Care (mental health)
- Wellbeats (virtual fitness classes)
- RethinkCare & Wellthy– caregiver support
- Diversity and inclusion programs which provide access to internal employee resource groups
- Employee referral bonuses to encourage the addition of great new people to the team
- We Foster a learning culture with:
- Education Assistance Program
- Professional development opportunities
- LinkedIn Learning
Note the last bullet includes a colon and sub-items. We could keep as a single
- with sublist? The instruction: Use
- for any list of duties/requirements/benefits. For benefits, we have a list; the last item includes a colon and sub-items. We could either keep as one
- containing the text "We Foster a learning culture with: Education Assistance Program Professional development opportunities LinkedIn Learning". Or we could make a nested list. But to keep simple, we can keep as one
- with the text as is.
We must preserve ALL substantive information; not invent or summarize away detail. So we need to keep the exact phrasing.
Now we need to output HTML fragment only, no markdown fences.
We'll structure:
About the role
Ellucian powers innovation for higher education, partnering with approximately 3,000 customers across 50 countries, serving more than 21 million students. Ellucian's AI-powered platform, trained on the richest dataset available in higher education, drives efficiency, personalized experiences, and strengthened engagement for all students, faculty and staff. Fueled by decades of experience with a singular focus on the unique needs of learning institutions, the Ellucian platform features best-in-class SaaS capabilities and delivers insights needed now and into the future. These solutions and services span the entire student lifecycle, including data-rich tools for student recruitment, enrollment, and retention to workforce analytics, fundraising, and alumni engagement. Ellucian's innovative solutions, vast ecosystem of partners and user community of more than 45,000 provides best practices
- for any list of duties/requirements/benefits, and
for prose. We need to decide what constitutes a list. Many bullet-like sentences separated by periods. We can convert each sentence into
- if they are list items. The instruction: Use
- for any list of duties/requirements/benefits. So we need to identify lists.
Let's extract sections:
1. About the role: Could include "About Ellucian" company description and "About The Opportunity". But "About Ellucian" is company overview, not role. Might be better to put under "About the role" a brief description of the role and maybe company context. However we must not invent headings; we can include "About the role" heading and put the content from "About The Opportunity" plus maybe company description as prose. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have heading About the role.
We'll put under About the role: combine the paragraphs from "About Ellucian" and "About The Opportunity". But "About Ellucian" is generic company info; still substantive. We'll keep it.
We need to use
for prose. So we can have a
containing the combined text (maybe two paragraphs). Or we could split into multiple
elements. Probably each paragraph separate
. 2. Responsibilities: from "Where you will make an impact". Those are bullet-like sentences: "Meet regularly (typically weekly) with each customer to maintain open communication." etc. We'll make a
- list.
3. Requirements / Qualifications: from "What You Will Bring". That's a list of items each starting with bold? Actually they are sentences: "A minimum of 3-5 years of Ellucian product technical experience working in a customer-facing role within an Ellucian software environment", "Hands-on experience providing technical support for Colleague", etc. We'll make a
- list. Also "Desired Ellucian & Partner Product Experience:" and "Desired Experience & Knowledge:" are additional desired qualifications; could be part of same list or separate. We could combine them under Requirements as well, but maybe better to have a separate "Qualifications" section for required and desired? The instruction allows sections like Requirements, Qualifications, Skills. We could have Requirements for mandatory, Qualifications for desired, Skills for technical skills. But we need to avoid thin sections. Let's think. We have many items: mandatory experience, hands-on experience, patching/upgrading, SSO, Ethos Integration, Colleague architecture, UniData admin, MS SQL DBA, SQL/T-SQL, Shell scripting, customer service focus, initiative, independent work. Then desired: Colleague ODS, reporting tools, Ellucian Analytics admin, Ellucian Workflow, Ethos Identity Services, Ellucian CRM Recruit or Microsoft Dynamics. Desired Experience & Knowledge: Microsoft certifications, AWS certifications, Linux or Windows Server admin, project management/team leadership. We could have a section "Requirements" for the mandatory items, and "Qualifications" for desired items. Or we could have "Skills" for technical skills list (like SSO, Ethos Integration, UniData, SQL, Shell scripting). But the instruction says prefer a few substantive sections over many thin ones. So maybe combine all into one "Requirements" section (including both mandatory and desired) as a list. That would be substantive. But we also have "What makes #Ellucianlife" benefits list. That's definitely a Benefits section. Thus we can have: - About the role (prose) - Responsibilities (list) - Requirements (list) (including both mandatory and desired) - Benefits (list) We need to ensure we don't create empty sections. Now we need to format lists properly: each item as
- . Ensure we preserve all details exactly as in posting, no omission. Let's extract the exact text. About Ellucian paragraph: "Ellucian powers innovation for higher education, partnering with approximately 3,000 customers across 50 countries, serving more than 21 million students. Ellucian's AI-powered platform, trained on the richest dataset available in higher education, drives efficiency, personalized experiences, and strengthened engagement for all students, faculty and staff. Fueled by decades of experience with a singular focus on the unique needs of learning institutions, the Ellucian platform features best-in-class SaaS capabilities and delivers insights needed now and into the future. These solutions and services span the entire student lifecycle, including data-rich tools for student recruitment, enrollment, and retention to workforce analytics, fundraising, and alumni engagement. Ellucian's innovative solutions, vast ecosystem of partners and user community of more than 45,000 provides best practices leading to greater institutional success and achieving better student outcomes." About The Opportunity paragraph: "Ellucian is seeking a talented individual that has strong technical, hands-on, working knowledge of Colleague technical - Consultant role that is looking for an opportunity to continue learning and helping Ellucian customers. This role provides personalized, on-going guidance and support for Colleague technical customer business operations post-implementation, enabling customers to maximize value from their solutions. The role also works closely with the customer by building a relationship with their points of contact, understanding their business needs, troubleshooting and resolving operational issues, and assessing the customer’s current use of and knowledge of the Ellucian solution. To be successful in the role, you must possess strong knowledge of Colleague application and system administration, have current hands-on experience managing, installing, and updating Colleague applications, and have an overall understanding of Ellucian’s broad portfolio of solutions. Knowledge and current hands-on experience of Ethos Integration, ILP, and DataConnect in addition to Colleague system administration is a plus." Note there is a slight grammatical oddity: "Colleague technical - Consultant role". We'll keep as is. Now Responsibilities (Where you will make an impact): List items: - Meet regularly (typically weekly) with each customer to maintain open communication. - Work with customer to gain an understanding of their goals, priorities, processes and challenges related to the supported applications. - Provide guidance and assist with reviewing, planning and deploying changes and new functionality. - Work with customers to review and modernize existing business processes, troubleshoot and resolve operational issues, provide direction on how to implement new modules or functionality in Colleague, and provide proactive communications about new functionality or defects. - Conduct knowledge sharing sessions in response to specific customer needs. - Promote customer usage of Ellucian resources such as the Solution Center, product documentation and Communities. Now Requirements (What You Will Bring): List items: - A minimum of 3-5 years of Ellucian product technical experience working in a customer-facing role within an Ellucian software environment - Hands-on experience providing technical support for Colleague - In depth experience patching and upgrading Colleague and technical administration of Colleague and related technology in the Colleague ecosystem - Single Sign-on Configuration/Support (SSO) including CAS and SAML2 protocols - Ellucian Ethos Integration configuration and administration - Colleague architecture and data layers - UniData administration, operation and maintenance - Microsoft SQL Server database administration (DBA) - SQL & Microsoft T-SQL - Shell scripting - A strong focus on customer service - Taking initiative and delivering on commitments to customers - Working independently on many concurrent activities Now Desired Ellucian & Partner Product Experience: List items: - Colleague Operational Data Store (ODS) - reporting tools such as Entrinsik Informer or SAP Business Objects - Ellucian Analytics administration - Ellucian Workflow - Ethos Identity Services - Ellucian CRM Recruit or Microsoft Dynamics Now Desired Experience & Knowledge: List items: - Microsoft certifications (MCSA, MCSE) - Amazon Web Services (AWS) certifications - Linux or Microsoft Windows Server administration - project management or team leadership Now Benefits (What makes #Ellucianlife): List items: - Comprehensive health coverage: medical, dental, and vision - Flexible time off - Thrive Flex Lifestyle Account (LSA) that allows you to contribute towards your health, financial or learning interests - 401k w/ match & BrightPlan - to help you save for the future - Parental Leave - 5 charitable days to support the community that supports us - Telemedicine - Wellness - Headspace Care (mental health) - Wellbeats (virtual fitness classes) - RethinkCare & Wellthy– caregiver support - Diversity and inclusion programs which provide access to internal employee resource groups - Employee referral bonuses to encourage the addition of great new people to the team - We Foster a learning culture with: - Education Assistance Program - Professional development opportunities - LinkedIn Learning Note the last bullet includes a colon and sub-items. We could keep as a single
- with sublist? The instruction: Use
- for any list of duties/requirements/benefits. For benefits, we have a list; the last item includes a colon and sub-items. We could either keep as one
- containing the text "We Foster a learning culture with: Education Assistance Program Professional development opportunities LinkedIn Learning". Or we could make a nested list. But to keep simple, we can keep as one
- with the text as is.
We must preserve ALL substantive information; not invent or summarize away detail. So we need to keep the exact phrasing.
Now we need to output HTML fragment only, no markdown fences.
We'll structure:
About the role
Ellucian powers innovation for higher education, partnering with approximately 3,000 customers across 50 countries, serving more than 21 million students. Ellucian's AI-powered platform, trained on the richest dataset available in higher education, drives efficiency, personalized experiences, and strengthened engagement for all students, faculty and staff. Fueled by decades of experience with a singular focus on the unique needs of learning institutions, the Ellucian platform features best-in-class SaaS capabilities and delivers insights needed now and into the future. These solutions and services span the entire student lifecycle, including data-rich tools for student recruitment, enrollment, and retention to workforce analytics, fundraising, and alumni engagement. Ellucian's innovative solutions, vast ecosystem of partners and user community of more than 45,000 provides best practices
- list.
3. Requirements / Qualifications: from "What You Will Bring". That's a list of items each starting with bold? Actually they are sentences: "A minimum of 3-5 years of Ellucian product technical experience working in a customer-facing role within an Ellucian software environment", "Hands-on experience providing technical support for Colleague", etc. We'll make a
- for any list of duties/requirements/benefits. So we need to identify lists.
Let's extract sections:
1. About the role: Could include "About Ellucian" company description and "About The Opportunity". But "About Ellucian" is company overview, not role. Might be better to put under "About the role" a brief description of the role and maybe company context. However we must not invent headings; we can include "About the role" heading and put the content from "About The Opportunity" plus maybe company description as prose. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have heading About the role.
We'll put under About the role: combine the paragraphs from "About Ellucian" and "About The Opportunity". But "About Ellucian" is generic company info; still substantive. We'll keep it.
We need to use