Jobs · Oregon

Slate Administrator

$66k–$79k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. Must not repeat job title as heading. Must not put Job ID etc as headings. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting and extract relevant content. Let's identify sections: - About the role: Could be position summary description: "The Slate Administrator is a key member..." etc. That's a prose description. - Responsibilities: The bullet list of duties: "Design, Develop, and Deploy CRM Solutions (40%)", "Slate Administration (30%)", "Slate Training (20%)", "Other Duties as Assigned (10%)" and sub-bullets. We'll need to format as
  • . - Requirements: Minimum qualifications? Could be "Minimum Qualifications From Classification" and "Additional Minimum Qualifications For This Position". Those are requirements. - Qualifications: Preferred qualifications? Could be "Preferred Qualifications". Also "Key Cultural Competencies" maybe part of qualifications/skills. - Skills: Could be skills like "Experience with Technolutions Slate", "SQL, XML, JSON", etc. - Benefits: The total compensation range and benefits statement: salary range, benefits description. - Schedule: Work Days/Hours: "On campus Monday-Friday, 8am-5pm. Up to one day remote, with the approval of the supervisor." We must not include sections with placeholder like "commensurate with experience". Not relevant. We must not include boilerplate like EEO, legal, application instructions, etc. So we must strip out: "Position Announcement Position Details Proposed Start Date", "Classification Title", "Working Title", "Department", "Position Number", "Representation", "Position FTE", "End date, if applicable", "Position Summary Brief Description of PSU/School/Dept" (the paragraph about PSU), maybe that's part of About the role? Actually the "Position Summary Brief Description of PSU/School/Dept" is a description of the university; we could include that as part of About the role? But it's generic about PSU; still substantive. We'll keep it. We must not include "Refer to our human resources pages..." etc. That's boilerplate? Might be considered generic but still part of description. Might keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The paragraph about PSU is not boilerplate; it's descriptive. Keep. We must not include "Position Summary The Slate Administrator is a key member..." That's also part of description. We must not include "In this role, you will regularly collaborate..." etc. That's responsibilities. We must not include "An overview of the job duties for this position is as follows:" maybe heading? We'll just incorporate. We must not include "Design, Develop, and Deploy CRM Solutions (40%):" etc. We must not include "This position is primarily on campus, with the option of working up to 1 day remotely per week." That's schedule. We must not include "Minimum Qualifications From Classification" etc. We must not include "Additional Minimum Qualifications For This Position" etc. We must not include "Preferred Qualifications" etc. We must not include "Key Cultural Competencies" etc. We must not include "Environmental Stewardship" etc. We must not include "Work Days/Hours" etc (but we need schedule). We must not include "Total Compensation Range & Benefits Statement" etc (we need pay and benefits). We must not include "You will need to pass a background check..." etc (maybe part of requirements? Could be considered requirement but it's boilerplate? It's a condition; maybe we keep as part of Requirements? It's not boilerplate exactly; it's a condition. Might keep under Requirements. We must not include "Application Instructions" etc. We must not include "Additional Information" etc. We must not include "Search Details" etc. We must not include "Posting Close Date", "Supplemental Questions", etc. Now we need to decide which sections to output. We have content for: - About the role: Could combine the PSU description and position summary. - Responsibilities: The detailed duties. - Requirements: Minimum qualifications (both from classification and additional) plus maybe background check, work authorization. - Qualifications: Preferred qualifications. - Skills: Could be extracted from preferred qualifications (experience with Slate, SQL, XML, JSON, HTML, CSS, JS, Higher Ed, etc). But we could also put those under Qualifications. The instruction says we can have Skills section; but we can also put skills under Qualifications. To avoid thin sections, we might combine Skills into Qualifications or Responsibilities. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications (including preferred qualifications and skills), Benefits, Pay, Schedule. That's 6 sections. But we need to ensure we don't create sections with placeholder text. All have real content. Now we need to format: - Use

    for section headings. - Use
    • for any list of duties/requirements/benefits. - Use

      for prose. We must not repeat job title as heading. We must not put Job ID etc as headings. We must output only HTML fragment. Let's craft. Section About the role: combine PSU description and position summary. Prose: We'll put two paragraphs maybe. Paragraph 1: PSU description. Paragraph 2: Position summary: "The Slate Administrator is a key member of the Customer Relations and Documents (CRDOC) Team in the Office of Information Technology (OIT) at Portland State University (PSU). In this position, you will be an Administrator of the Slate Customer Relationship Management (CRM) system." plus maybe the collaboration sentence. We'll keep. Section Responsibilities: We'll list the duties as bullet points. We have high-level categories with percentages and sub-bullets. We could produce a list: - Design, Develop, and Deploy CRM Solutions (40%): - In collaboration with campus partners, design, develop, and deploy solutions to meet departmental and institutional goals. - Maintain and update existing solutions to fix bugs or address changing business needs. - Develop solutions that meet security, privacy, and accessibility guidelines. - Create documentation of deployed solutions. - Slate Administration (30%): - Monitor and troubleshoot application issues and collaborate with PSU teams and vendors to resolve them. - Manage user access, permissions, and system configurations. - Design and implement application configuration changes to enable and enhance business processes. - Monitor system health, assess performance issues, and tune applications for optimal performance. - Monitor alerts and logs to ensure system stability. - Maintain data integrity and validation. - Document system settings and processes. - Maintain communication with users and other stakeholders to keep them informed of any planned or unplanned service downtimes. - Provide support in times of emergency and outside of standard office hours. - Slate Training (20%): - Provide Users, Coordinators, and Administrators with training, documentation, and best practices for Slate usage and development, including guidance on security, privacy, and accessibility. - Collaborate with University Marketing and Communications or other departments to ensure technical and functional training alignment. - Provide demonstrations and information for departments considering Slate to meet their needs. - Other Duties as Assigned (10%): - (No further detail given) maybe we can omit if no detail? But we need to preserve all substantive information; there is no detail beyond the label. Could we include a bullet "Other duties as assigned." That's substantive enough? It's a phrase. We'll include as a bullet. We'll need to nest lists? The instruction: Use

      • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep simple: each top-level bullet as
      • and inside we could use
        • for sub-items. That's okay. Section Requirements: Minimum qualifications. We have: From Classification: "This classification requires a basic foundation of knowledge and skills in systems analysis and related programming support functions generally obtained by a bachelor’s degree in computer science, or an equivalent amount of training and applied experience." Additional Minimum Qualifications For This Position: - Bachelor’s Degree or 4 years of a combination of comparable work experience, training, and/or education. - Demonstrated knowledge of application systems design, data modeling concepts, data analysis, and system administration. - Experience administering or configuring a Customer Relationship Management (CRM) system - Strong interpersonal skills and ability to communicate effectively, both verbally and written, with both technical and non-technical staff and with people from a diverse range of perspectives and backgrounds. - Ability to work in a fast-paced, production environment and to provide occasional evening and weekend support - Ability to work with sensitive/confidential information and to handle such information as required by Federal, State, and OIT regulations/policies Also background check and work authorization: "You will need to pass a background check and must be legally authorized to work in the United States, as our department is unable to sponsor any type of visa application or extensions." We'll include that as requirement. We'll format as
          • . Section Qualifications: Preferred qualifications and Key Cultural Competencies and Environmental Stewardship maybe. Preferred Qualifications list: - Experience with Technolutions Slate - Experience with SQL, XML, and JSON - Experience with HTML, CSS, and JavaScript - Experience working in Higher Education - Proven experience building and maintaining professional working relationships - Experience collaborating across a large organization to achieve shared goals and complete complex IT projects - Ability to produce accurate and reliable work within deadlines - Align with OIT’s Attributes for Success: Coaching, Communication, Emotional Intelligence, Proactive, Teamwork (we could list each as sub-bullets) Key Cultural Competencies list: - Creates an environment that acknowledges, encourages and celebrates differences. - Functions and communicates effectively and respectfully within the context of varying beliefs, behaviors, orientations, identities and cultural backgrounds. - Seeks opportunities to gain experience working and collaborating in diverse, multicultural, and inclusive settings with a willingness to change for continual improvement. - Adheres to all PSU policies including the policies on Prohibited Discrimination & Harassment and the Professional Standards of Conduct. Environmental Stewardship: - Contributes to a culture of environmental stewardship, practices resource conservation, and actively works toward achieving long-term sustainability goals. We could combine these under Qualifications. We'll output as
            • with maybe sub-lists for OIT Attributes. Section Benefits: The benefits statement: "PSU’s excellent benefits package includes 95% premium-paid healthcare; a generous retirement and vacation package; and reduced tuition rates for employees, spouses, or dependents at any of the Oregon Public Universities." Also mention Total Compensation Calculator etc but that's maybe extra. We'll keep the benefits description. Section Pay: The total compensation range: "The starting salary rate for this position is between $66,132 and $79,358 per year. The starting salary may be negotiable above this range; however, it is dependent upon the knowledge, experience, skills, and abilities of the chosen candidate, the budget of the hiring department, and approval from human resources." Section Schedule: Work Days/Hours: "On campus Monday-Friday, 8am-5pm. Up to one day remote, with the approval of the supervisor." Also mention "This position is primarily on campus, with the option of working up to 1 day remotely per week." That's same. We'll combine. Now we need to ensure we don't include any boilerplate like "Please visit the Total Compensation Calculator..." maybe that's extra but still substantive? It's a reference; could be considered part of benefits. Might keep

Similar jobs

Key Administrator

State of South CarolinaColumbia, SC· 4 mo ago
Information Technologyapply on governmentjobs.com

Core Administrator

Boise State UniversityBoise, ID· 2 wk ago
$61k–$75k/yrapply on apptrkr.com

AMOS Administrator

National AirlinesOrlando, FL· 3 mo ago
Information Technologyapply on recruiting.paylocity.com

Access Administrator

Frontline Consulting Services (FCS) IncWaukegan, IL· 1 wk ago
Information Technology$23–$24/hr

Administrator

Monarch Healthcare ManagementRoseville, MN· 3 mo ago
Information Technologyapply on jobs.apploi.com