Assistant Professor, School of Information Systems & Technology
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to parse the posting.
Key info:
- Position Rank and Title: Assistant Professor (but we should not repeat job title as heading; page already shows it, so we don't output a heading for title.)
- School/Department Name: School of Information Systems & Technology (SISTech)
- Compensation: Commensurate with qualifications, experience, and rank as established by the CSU Salary Schedule. Anticipated hiring academic year annual salary range: $134,520-$141,246. Faculty employee benefits are very competitive... See CSU Employee Benefits Summary for details.
- Target Start Date: August 17, 2027
- Application Deadline: October 1, 2026 (Applications accepted until filled or closed)
- Position Description: paragraphs.
- Required Qualifications: bullet list? It's a sentence: "A PhD in Management Information Systems, Information Science, Computer Information Systems, Computer Science, or related field, from an appropriately accredited institutionApplicant must be qualified as a scholarly academic (SA) according to AACSB standardsApplicants should demonstrate an awareness of and sensitivity to the educational goals of a socially and economically diverse student population as might have been gained in cross-cultural study, training, teaching, and other comparable experience."
- Preferred Qualifications: bullet list: "Priority will be given to candidates who possess one or more of the following: Ability to teach a variety of traditional IS coursesExpertise in Python, R, Data Analytics / Visualization, Project Management or Artificial Intelligence (AI)Collegial, cooperative and collaborative work styleStrong teamwork, communication, interpersonal skillsDemonstrated record of teaching, research, and service excellence"
- Key Responsibilities: bullet list.
- Other Duties: includes mandated reporter etc. This is boilerplate? It's legal/EEO? It's about mandated reporter, Clery Act, etc. According to instructions: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So "Other Duties" includes legal stuff (mandated reporter, Clery Act, etc.) Should be removed as boilerplate. Also "Application Procedure" is application instructions, remove. "Conditional Offer" also maybe legal? It's about employment contingency; likely considered boilerplate? Might be considered application instructions? It's about conditional offer, background checks. Probably remove as boilerplate/instructions.
- "San José State University: Silicon Valley's Public University ..." is boilerplate about university; remove.
- Equal Employment Statement: remove.
- Campus Security and Fire Safety Notification: remove.
Thus we keep: Position Description (maybe as About the role?), Required Qualifications, Preferred Qualifications (maybe Skills?), Key Responsibilities (Responsibilities), Compensation (Pay and Benefits?), Target Start Date (Schedule?), Application Deadline maybe part of Schedule? Actually schedule could be start date, maybe also include application deadline? But schedule section is for work schedule? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (position description), Responsibilities (key responsibilities), Requirements (maybe required qualifications?), Qualifications (maybe preferred qualifications?), Skills (maybe expertise list?), Benefits (benefits description), Pay (salary range), Schedule (target start date). We need to avoid filler like "commensurate with experience" etc. For Pay we have actual salary range: $134,520-$141,246. So we can include Pay section with that.
Benefits: "Faculty employee benefits are very competitive for the higher education sector. See the CSU Employee Benefits Summary for details about the CSU’s excellent benefits package." That's substantive enough? It's a bit generic but mentions competitive benefits and reference. It's not placeholder like "varies". It's okay.
Schedule: Target Start Date: August 17, 2027. That's specific.
Also maybe include Application Deadline? Not a schedule heading but could be part of About the role? Probably not needed.
We must not repeat job title as heading. So we start with About the role
then
About the role
thenwith position description paragraphs. We need to preserve all substantive information, not invent or summarize away detail. So we need to include the description text exactly as given (maybe trimmed of boilerplate). The position description includes multiple paragraphs. We'll combine them into
elements. Let's extract position description text: "The School of Information Systems & Technology at San José State University invites applications for an Assistant Professor of Information Systems position to begin August 2027. The successful candidate will be able to teach in our MIS curriculum which includes traditional core courses such as Systems Analysis & Design, Fundamentals of MIS, and Business Programming, as well as electives in emerging topics such as Data Analytics & Visualization and Artificial Intelligence (AI). They will also be able to engage actively in research on IS-related topics, demonstrated by conference presentations and peer-reviewed journal publications, and will be expected to support the school, the college, and the university through service activities. SISTech resides in the Lucas College and Graduate School of Business at SJSU. We prepare students to excel professionally and contribute to society through the undergraduate MIS concentration within the Bachelor of Science in Business Administration degree. Our program reflects IS best practices and provides students with the skills and hands-on experience they will need to succeed today and tomorrow. Our location in Silicon Valley provides both students and faculty with unparalleled opportunities to engage with leading technology firms. Our diverse school includes tenured / tenure track faculty who contribute meaningfully to academic literature and clinical faculty with years of experience at leading organizations in Silicon Valley. Consequently, our students are well-represented throughout the high-tech and non-tech industries locally and beyond. To learn more about our school, programs, and faculty, please visit our SISTech website . SISTech and San José State University value institutional excellence and are committed to advancing equity through research, teaching, and service. We enroll more than 40,000 students, many of whom are historically underserved; approximately 45% of our undergraduate students are first-generation college students and 38% are Pell Grant recipients. In addition, we are both a Hispanic Serving Institution (HSI) and an Asian American and Native American Pacific Islander Serving Institution (AANAPISI). SJSU aspires to create holistic learning environments that facilitate both individual and collective transformation. We seek teacher-scholars who cultivate inclusive, empowering spaces for mutual learning, skill-building, and knowledge exchange for all students. Our commitment to lifelong learning supports meaningful connections among faculty, staff, students, alumni, and the broader communities we serve. We invite all applicants to include a Statement of Institutional Excellence (or incorporate it into your cover letter) to share how your lived and professional experiences will contribute to the SJSU community—particularly in relation to student success. A guide to writing this statement can be found at SJSU Institutional Excellence Statement Guidelines ." We need to keep that. Remove the link text? It's okay to keep as plain text. Now Required Qualifications: It's a sentence but we can format as
- each requirement? The instruction: Use
- for any list of duties/requirements/benefits. So we should split into list items. The required qualifications are three items: PhD in ...; qualified as scholarly academic (SA) per AACSB; demonstrate awareness/sensitivity to diverse student population via cross-cultural experience.
We'll create
- for each.
Preferred Qualifications: list items: Ability to teach a variety of traditional IS courses; Expertise in Python, R, Data Analytics / Visualization, Project Management or AI; Collegial, cooperative and collaborative work style; Strong teamwork, communication, interpersonal skills; Demonstrated record of teaching, research, and service excellence.
We could put these under Skills or Qualifications. The instruction says we can have Qualifications and Skills sections. We'll decide: Qualifications section for required qualifications; Skills section for preferred qualifications (or maybe Preferred Qualifications under Qualifications). But we have both Required and Preferred. We could put Required under Requirements, Preferred under Skills. Or we could have Qualifications for required and Skills for preferred. Let's map:
- About the role: position description.
- Responsibilities: Key Responsibilities.
- Requirements: Required Qualifications.
- Qualifications: maybe Preferred Qualifications? But the heading "Qualifications" could be used for both required and preferred? However we already used Requirements for required. So we can use Qualifications for preferred qualifications.
- Skills: maybe we could list specific technical skills like Python, R, etc. But we already have them in preferred qualifications. Could also separate but not needed.
- Benefits: benefits description.
- Pay: salary range.
- Schedule: target start date.
We should not create sections with filler. Ensure each section has real content.
Now we need to output only HTML fragment.
Let's craft:
About the role
...position description...
Responsibilities
- Maintain ongoing research activity providing valued contributions relevant to the IS academic community, including peer-reviewed journal papers and conference proceedings.
- Deliver engaging, relevant, and timely learning experiences that contribute meaningfully to our students' professional readiness for high-impact careers in IS.
- Participate in shared governance, usually in department, college, and university committees and other service assignments.
- Organize classes within the university policy guidelines and use the Canvas Learning Management System (LMS).
- Demonstrate awareness and experience in understanding the needs of a student population of great diversity – in age, abilities, cultural background, ethnicity, religion, economic background, primary language, sexual orientation, gender identity, and academic preparation – through inclusive course materials, teaching strategies, and advisement.
Requirements
- A PhD in Management Information Systems, Information Science, Computer Information Systems, Computer Science, or related field, from an appropriately accredited institution.
- Applicant must be qualified as a scholarly academic (SA) according to AACSB standards.
- Applicants should demonstrate an awareness of and sensitivity to the educational goals of a socially and economically diverse student population as might have been gained in cross-cultural study, training, teaching, and other comparable experience.
Qualifications
- Ability to teach a variety of traditional IS courses.
- Expertise in Python, R, Data Analytics / Visualization, Project Management or Artificial Intelligence (AI).
- Collegial, cooperative and collaborative work style.
- Strong teamwork, communication, interpersonal skills.
- Demonstrated record of teaching, research, and service excellence.
Benefits
Faculty employee benefits are very competitive for the higher education sector. See the CSU Employee Benefits Summary for details about the CSU’s excellent benefits package.
Pay
Anticipated hiring academic year annual salary range: $134,520‑$141,246 (commensurate with qualifications, experience, and rank as established by the CSU Salary Schedule).
Schedule
Target start date: August 17, 2027.
We need to ensure we didn't include boilerplate like "Commencement with qualifications..." we included that in Pay paragraph but it's okay as it's part of salary description. It's not filler. Check for any duplicated lines: we removed application instructions, EEO, etc. Check for any placeholders: none
- for each.
Preferred Qualifications: list items: Ability to teach a variety of traditional IS courses; Expertise in Python, R, Data Analytics / Visualization, Project Management or AI; Collegial, cooperative and collaborative work style; Strong teamwork, communication, interpersonal skills; Demonstrated record of teaching, research, and service excellence.
We could put these under Skills or Qualifications. The instruction says we can have Qualifications and Skills sections. We'll decide: Qualifications section for required qualifications; Skills section for preferred qualifications (or maybe Preferred Qualifications under Qualifications). But we have both Required and Preferred. We could put Required under Requirements, Preferred under Skills. Or we could have Qualifications for required and Skills for preferred. Let's map:
- About the role: position description.
- Responsibilities: Key Responsibilities.
- Requirements: Required Qualifications.
- Qualifications: maybe Preferred Qualifications? But the heading "Qualifications" could be used for both required and preferred? However we already used Requirements for required. So we can use Qualifications for preferred qualifications.
- Skills: maybe we could list specific technical skills like Python, R, etc. But we already have them in preferred qualifications. Could also separate but not needed.
- Benefits: benefits description.
- Pay: salary range.
- Schedule: target start date.
We should not create sections with filler. Ensure each section has real content.
Now we need to output only HTML fragment.
Let's craft:
- for any list of duties/requirements/benefits. So we should split into list items. The required qualifications are three items: PhD in ...; qualified as scholarly academic (SA) per AACSB; demonstrate awareness/sensitivity to diverse student population via cross-cultural experience.
We'll create