Lecturer in Energy Systems

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. We have posting: includes Salary: Lecturer (Level B)- AUD $133,065 to $156,864 per annum + 17% superannuation. Employment type: Full-time. Appointment type: Fixed term, 2-year convertible tenure track. Location: Kensington – Sydney, Australia. Reporting line: This role reports to the Head of School and has no direct reports. Also includes "About You" which is basically qualifications/skills/experience. "About UNSW" is description of institution. "Skills And Experience" list. We need to map content to sections: About the role (maybe overview of role). Responsibilities (teaching, research, supervision, course admin, academic quality assurance, engage with industry, etc). Requirements/Qualifications/Skills: PhD, teaching experience, research track record, etc. Benefits: maybe superannuation, maternity leave, flexible work options, workplace adjustments, etc. Pay: salary range. Schedule: maybe full-time? Could be schedule: Full-time. But we should only include Schedule if posting actually states schedule details (like part-time, shift). It says Employment type: Full-time. That could be considered schedule. We'll include Schedule section with Full-time. We must not include placeholder text like "commensurate with experience". Not present. We must not include duplicated lines. We'll need to extract substantive info. Let's parse: - About the role: The School ... seeking a Lecturer for a teaching and research role in Electrical Energy Systems and Power Engineering. This role will help strengthen the School’s capabilities in power systems, high-voltage systems, system modelling, simulation and control, while supporting interdisciplinary research across telecommunications, control systems, signal processing and microelectronic systems. Alongside delivering high-quality teaching across undergraduate and postgraduate Electrical Engineering programs, you will supervise Honours and postgraduate project students and contribute to course administration and academic quality assurance. With established strengths across electrical engineering, telecommunications, signal processing, communications, energy systems, robotics and emerging technologies, UNSW offers an exceptional environment for academics seeking to advance their research profile, contribute to interdisciplinary initiatives and deliver outstanding teaching. You will undertake research that advances electrical energy systems and power engineering, engage with industry, government and interdisciplinary collaborators, and contribute to innovation, knowledge exchange and the development of the next generation of engineers and researchers. That's a good overview. - Responsibilities: Could be derived from same paragraph: delivering high-quality teaching, supervising Honours and postgraduate project students, contributing to course administration and academic quality assurance, undertaking research, engaging with industry/government/collaborators, contributing to innovation, knowledge exchange, development of next generation engineers. Also maybe "support interdisciplinary research across telecommunications, control systems, signal processing and microelectronic systems." Also "contribute to course administration and academic quality assurance." Also "support students from diverse backgrounds, contributing to equity, diversity and inclusion initiatives, building effective relationships across disciplines, and engaging with industry and professional networks." That's more about You but could be responsibilities. We'll separate. - Requirements/Qualifications/Skills: The posting includes "About You" and "Skills And Experience". We'll combine into Requirements (maybe qualifications) and Skills. But we need separate headings: Requirements, Qualifications, Skills. The instruction says use headings for those sections if content exists. We can decide to put qualifications under "Requirements" and skills under "Skills". Or we can have both. We need to preserve all substantive info; not invent. Let's extract: Qualifications: - PhD in Electrical Engineering or a related discipline, along with relevant work experience. - Proven commitment to proactively keeping up to date with discipline knowledge and developments. - Demonstrated experience and evidence in teaching and learning design, development and/or delivery at undergraduate and/or postgraduate levels in the area of power systems or electrical energy engineering, as well as across the broad field of Electrical Engineering. - Demonstrated track record in power systems research, along with outcomes of high quality and high impact. - Demonstrated evidence of research excellence as well as the capacity for research leadership. - Experience using and/or designing with educational technologies and online delivery methods. - Evidence of teaching effectiveness and passion for educational excellence (e.g. relevant discipline based curriculum design and development at a variety of levels and scales). - Demonstrated knowledge of industry or experience of work-integrated learning (desirable). - Evidence of ability to support and inspire students from diverse backgrounds and support student equity, diversity and inclusion initiatives. - A track record of significant involvement with the profession and/or industry. - High level communication skills and ability to network effectively and interact with a diverse range of students and staff. - Demonstrated ability to work in a team, collaborate across disciplines and build effective relationships. - Evidence of highly developed interpersonal and organisational skills. - An understanding of and commitment to UNSW’s aims, objectives and values in action, together with relevant policies and guidelines. - Knowledge of health and safety responsibilities and commitment to attending relevant health and safety training. Skills: - Possibly same as above but we can separate: teaching and learning design, educational technologies, communication, interpersonal, organisational, teamwork, collaboration, networking, industry experience, etc. But to avoid duplication, we could put all under "Skills And Experience" as a single section. However instruction says we can have Skills section. We'll create Skills section with bullet list of skills: teaching and learning design, educational technologies, communication, interpersonal, organisational, teamwork, collaboration, networking, industry experience, etc. But we must not repeat same content verbatim across sections; but we can split. Better: Use "Requirements" for mandatory qualifications (PhD, teaching experience, research track record, etc.) and "Skills" for desirable/soft skills (communication, interpersonal, organisational, teamwork, etc.). However the posting lumps many as "Demonstrated evidence". We'll just follow the posting: we can put all under "Requirements" and maybe not have Skills separate if it's redundant. But we need to decide. Given instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Skills into one section called "Requirements and Skills" but headings are fixed: we can only use the listed headings. We could omit Skills if content overlaps heavily with Requirements. But we need to preserve all info; we can put all under Requirements and omit Skills. That's acceptable because we are not required to include all headings; we include only those with real specific content. So we can have Requirements (covering qualifications and skills). Similarly Benefits: we have superannuation, 26 weeks maternity leave, flexible work options, workplace adjustments, etc. Pay: salary range. Schedule: Full-time. We also have location etc. Could be part of About the role or separate? Not required heading. We could include location in About the role paragraph. We must not include Job ID/requisition numbers as headings; we can drop them. We must remove boilerplate: EEO, legal, etc. The posting includes a lot of EEO statements at the end: "UNSW is committed to evolving a culture..." etc. That's boilerplate; we should remove. Also remove "For further information about our School, please visit - https://..." maybe keep as part of About UNSW? It's a link; but it's not boilerplate; it's substantive info about school. Could keep under About UNSW? But we don't have a heading for About UNSW; we could incorporate into About the role or maybe a separate section "About UNSW". Not in allowed headings. So we could incorporate that info into About the role or maybe drop? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info about UNSW being world-leading, etc. That is substantive. We can include it in About the role section (makes sense). Or we could create a separate section "About UNSW" but not allowed heading. So we incorporate. Similarly "Additional details about the specific responsibilities for this position can be found in the position description. This is available via JOBS@UNSW." That's a reference; maybe we can drop as it's not substantive detail. Application instructions: "To Apply Please click the “Apply Now” button..." etc. Remove. Contact info: remove. Applications close date: maybe we can keep as substantive? It's a deadline; could be considered metadata but not boilerplate. However instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. The closing date is minor metadata; we could fold into a short p maybe under About the role? But we could drop it as it's not essential to role description? The instruction says preserve ALL substantive information; is closing date substantive? Probably yes, it's important for applicants. But they said fold minor metadata into a short p or drop it. The closing date could be considered minor metadata. I'd include it in a short p maybe under About the role or separate? But we don't have a heading for "Application deadline". Could add a paragraph after About the role: "

Applications close: 11:50 pm (Sydney time) on Tuesday, 27 October 2026.

" That's fine. Similarly "As part of our recruitment process candidates may be required to undergo pre-employment screening..." that's boilerplate legal; remove. Now we need to output HTML fragment with sections:

About the role

,

... maybe multiple paragraphs,

• for lists. We need to decide where to put lists: Responsibilities, Requirements, Benefits, Pay, Schedule. Pay: we can have

  Pay

  Lecturer (Level B) – AUD $133,065 to $156,864 per annum + 17% superannuation.

  Schedule:

  Schedule

  Full-time.

  Benefits: we have superannuation (already in Pay), 26 weeks fully paid maternity or primary carers leave, flexible work options including working from home, workplace adjustments for people with disability, access to flexible work options, supportive environment for ECAs, etc. Also "UNSW provides 26 weeks of fully paid maternity or primary carers leave upon commencement of employment (subject to eligibility)." Also "UNSW provides workplace adjustments for people with disability, and access to flexible work options, including working from home, for eligible staff." Also "UNSW is committed to enhancing the experience of ECAs by providing a supportive and collegial work environment and a dedicated framework to deliver support services to assist their research, teaching, and career development." Also maybe "UNSW offers an exceptional environment for academics seeking to advance their research profile, contribute to interdisciplinary initiatives and deliver outstanding teaching." That's more about role. We'll list benefits as bullet points. Responsibilities: bullet list: delivering high-quality teaching across undergraduate and postgraduate Electrical Engineering programs; supervising Honours and postgraduate project students; contributing to course administration and academic quality assurance; undertaking research that advances electrical energy systems and power engineering; engaging with industry, government and interdisciplinary collaborators; contributing to innovation, knowledge exchange and development of next generation engineers and researchers; supporting interdisciplinary research across telecommunications, control systems, signal processing and microelectronic systems; supporting students from diverse backgrounds, contributing to equity, diversity and inclusion initiatives; building effective relationships across disciplines; engaging with industry and professional networks. Requirements: bullet list: PhD in Electrical Engineering or related discipline with relevant work experience; proven commitment to staying current with discipline knowledge; demonstrated experience in teaching and learning design, development and/or delivery at undergraduate/postgraduate levels in power systems/elect