Software Engineer (Front-End/Full Stack, Mobile/Website/Core)
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info. Do not invent or summarize away detail. Avoid filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Compensation & Benefits with salary ranges and benefits list. So we can have Pay and Benefits sections. Schedule: Department Hours: Monday - Friday 8:30am-5:00pm ET. So we can have Schedule section. Also Work Arrangement info: onsite/hybrid/remote, location restrictions. That could go under About the role or maybe a separate section? Not required but we can include in About the role. Must not create sections with filler. So we need to decide which sections to include: About the role (general description), Responsibilities (Essential Duties and Responsibilities), Requirements (Job Requirements), Qualifications (maybe overlapping with Requirements? Could combine but we need separate if content). Skills (maybe from Competencies). Benefits (list). Pay (salary ranges). Schedule (department hours). Also maybe Work Arrangement could be part of About the role.
We must not repeat job title. Use
headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to ensure we only include sections that have real content. All of these have content.
We must not include boilerplate like EEO, disclaimer, etc. Remove those.
We must preserve all substantive info. So we need to extract the description paragraphs and bullet lists.
Let's parse the posting.
First paragraph: "The Software Engineer is responsible for the design, development, implementation, and lifecycle ownership of MSUFCU’s portfolio of software solutions. This can include various MSUFCU-owned websites, digital banking applications, core banking systems, financial mobile and web-based applications in partnership with Reseda Group, as well as other internal systems and applications. This position is a cross-functional role that works directly with the product team and other stakeholders to identify requirements and constraints, estimate timeframes, design user interfaces, define system designs, and collaboratively develops innovative solutions that align with strategic objectives. It includes writing robust, testable and well-documented code, including the development of automated tests to ensure high reliability, maintainability and quality while completing projects on time. This role also documents and communicates system designs and decisions, contributes to knowledge sharing across the team, and engages stakeholders through technical presentations and collaborative design discussions."
Then Work Arrangement paragraph: "Work Arrangement: This position is able to work onsite, hybrid, or remote (must reside within the states of Michigan or Illinois). To be considered for this role, candidate must currently reside, or have plans to reside upon hire, within the state of Michigan or Illinois as described above. Occasional travel on a quarterly basis to MSUFCU Headquarters (East Lansing, MI) may be needed. Department Hours: Monday - Friday 8:30am-5:00pm ET. An offer of employment with MSU Federal Credit Union and affiliates is contingent upon the agreed work arrangement (onsite/hybrid/remote) and work location. MSU Federal Credit Union may or may not be able to accommodate temporary or permanent changes to work arrangements or allow employment outside the city and/or state of residency in which the new hire resides at the time of offered employment."
Then Compensation & Benefits: "Compensation & Benefits: Salary Range:Associate Software Engineer - $70,000 - $85,000+ annually, depending on experience Software Engineer - $85,000 - $105,000+ annually, depending on experience 100% Company-Paid Health, Dental, Vision, Life, and Long-Term Disability PremiumsUp to 26 days of PTO within your first year, as well as Volunteer Time Off & 11 Paid Holidays401(k) with a company matchTuition ReimbursementUp to 12 Weeks of Paid Parental LeaveLearn more about our benefits here"
Then Essential Duties and Responsibilities: includes bullet-like sentences for Associate Software Engineer and Software Engineer.
Then Job Requirements: includes bullet-like sentences for Associate Software Engineer and Software Engineer.
Then Competencies: list of core competencies and functional competencies.
Then Physical Demands and Work Environment: some sentences.
Then Disclaimer etc to remove.
We need to output HTML with sections.
We need to decide what goes where.
About the role: likely the initial description plus work arrangement? Could include description of role and work arrangement. But we also have Schedule section for hours. So About the role could include the description of responsibilities at high level, plus maybe work arrangement (onsite/hybrid/remote) and location restrictions. But we also have Responsibilities section for detailed duties. So About the role could be a brief overview: the first paragraph plus maybe work arrangement? However we must not duplicate content. We can split: About the role: the first paragraph (role description). Work arrangement could be part of About the role or maybe a separate section but we don't have a heading for work arrangement; we could include it in About the role as a paragraph.
Responsibilities: the Essential Duties and Responsibilities content (both Associate and Software Engineer). We need to format as - for each duty. The text includes many sentences; we can break them into list items.
Requirements: Job Requirements content (Associate and Software Engineer). Also maybe include knowledge and familiarity list.
Qualifications: Could be education requirements? But we already have Requirements includes education. Qualifications could be things like "High School Diploma or Equivalent Required. Bachelor’s Degree Computer Science or in a related field or 3 years of experience in lieu of a degree". However that's also requirements. The distinction is fuzzy. But we need to include a Qualifications section if there is specific content. The posting has "Job Requirements:" which includes education, knowledge, etc. There's also "Competencies:" which could be considered Qualifications or Skills. We have Skills section for competencies. So Qualifications could be education and experience requirements. Let's put Qualifications: education and experience (the bullet points about HS diploma, degree, etc). Requirements: maybe the knowledge and familiarity list (technical skills). But the instruction says use sections as given; we must not invent sections. We have to decide what content goes where, but we must preserve all substantive info. We can allocate as:
- About the role: initial paragraph (role description) + maybe work arrangement? But we have Schedule separate for hours. Work arrangement (onsite/hybrid/remote, location) could go in About the role.
- Responsibilities: Essential Duties and Responsibilities (list items).
- Requirements: Job Requirements (knowledge and familiarity list, plus maybe the "All of Associate Software Engineer duties and responsibilities" etc). Actually Job Requirements includes both knowledge and familiarity and also "All of Associate Software Engineer knowledge, skills, and abilities." plus additional for Software Engineer. We'll put that in Requirements.
- Qualifications: Education and experience requirements (HS diploma, degree or experience). Could also include "Knowledge of credit union products and services..." but that seems more like qualifications for Software Engineer. However that is under Job Requirements for Software Engineer. Might be better to treat Qualifications as education/experience, and Requirements as technical knowledge/skills. But we need to avoid duplication.
- Skills: Competencies list (core and functional). Could also include technical skills from knowledge and familiarity? But we already put those in Requirements. So Skills will be the competencies.
- Benefits: list of benefits.
- Pay: salary ranges.
- Schedule: department hours.
We must not include filler like "depending on experience" is okay; it's specific. Not "commensurate with experience". It's okay.
We must not include boilerplate like "Learn more about our benefits here" - that's a link; we can drop that as it's navigation? It's not essential substantive info? It's a reference; we could drop as it's not substantive. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about our benefits here" is like a link; could be considered navigation. Safer to drop it.
Also "Up to 26 days of PTO within your first year, as well as Volunteer Time Off & 11 Paid Holidays" etc are benefits.
We need to format benefits as
- .
Pay: we need to include salary ranges. Could be
with the two lines.
Schedule:
Monday - Friday 8:30am-5:00pm ET.
Now we need to ensure we don't repeat content. Let's extract each piece.
About the role paragraph:
"The Software Engineer is responsible for the design, development, implementation, and lifecycle ownership of MSUFCU’s portfolio of software solutions. This can include various MSUFCU-owned websites, digital banking applications, core banking systems, financial mobile and web-based applications in partnership with Reseda Group, as well as other internal systems and applications. This position is a cross-functional role that works directly with the product team and other stakeholders to identify requirements and constraints, estimate timeframes, design user interfaces, define system designs, and collaboratively develops innovative solutions that align with strategic objectives. It includes writing robust, testable and well-documented code, including the development of automated tests to ensure high reliability, maintainability and quality while completing projects on time. This role also documents and communicates system designs and decisions, contributes to knowledge sharing across the team, and engages stakeholders through technical presentations and collaborative design discussions."
Work arrangement paragraph: "Work Arrangement: This position is able to work onsite, hybrid, or remote (must reside within the states of Michigan or Illinois). To be considered for this role, candidate must currently reside, or have plans to reside upon hire, within the state of Michigan or Illinois as described above. Occasional travel on a quarterly basis to MSUFCU Headquarters (East Lansing, MI) may be needed."
We could combine these two paragraphs in About the role.
Now Responsibilities: Essential Duties and Responsibilities section includes two sets: Associate Software Engineer duties and Software Engineer duties (which includes all Associate duties plus extra). We need to avoid duplication. We could list all duties for Software Engineer (which includes Associate duties). But we need to preserve all substantive info; we could list Associate duties then additional duties for Software Engineer. However that would duplicate the Associate duties. Better to list Software Engineer duties (which includes Associate duties) and note that Associate duties are subset. But we need to preserve the info that Associate duties are as described. Could list both but avoid duplication by listing Associate duties then extra for Software Engineer. That would repeat the Associate duties in the list for Software Engineer if we just copy them. To avoid duplication, we could list Associate duties as items, then for Software Engineer list additional items beyond Associate. However the posting says "Software Engineer - All of Associate Software Engineer duties and responsibilities." So we could note that.
Thus we can produce list items:
- Participate in the development and architecture of the credit union’s and Reseda Group’s software solutions through various tools, software, styles and programming languages; program and support front-end interactive elements as well as backend architecture to ensure the functionality, look, feel and organization of content.
- Participate in all phases of the Software Development Lifecycle (SDLC) including: analysis, design, testing, code review, deployment, and maintenance for all systems and applications maintained by the department.
- Troubleshoot technical problems and implement effective solutions.
- Assist with fixing any software or infrastructure problems that affect the digital solutions that the department supports.
- Create and help maintain technical documentation for programs and systems created and supported by the department.
- Collaboratively work with business units, technical teams, and third-party vendors to create project plans, technical specifications, software diagrams, and technical documentation
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info. Do not invent or summarize away detail. Avoid filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Compensation & Benefits with salary ranges and benefits list. So we can have Pay and Benefits sections. Schedule: Department Hours: Monday - Friday 8:30am-5:00pm ET. So we can have Schedule section. Also Work Arrangement info: onsite/hybrid/remote, location restrictions. That could go under About the role or maybe a separate section? Not required but we can include in About the role. Must not create sections with filler. So we need to decide which sections to include: About the role (general description), Responsibilities (Essential Duties and Responsibilities), Requirements (Job Requirements), Qualifications (maybe overlapping with Requirements? Could combine but we need separate if content). Skills (maybe from Competencies). Benefits (list). Pay (salary ranges). Schedule (department hours). Also maybe Work Arrangement could be part of About the role. We must not repeat job title. Use
headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to ensure we only include sections that have real content. All of these have content.
We must not include boilerplate like EEO, disclaimer, etc. Remove those.
We must preserve all substantive info. So we need to extract the description paragraphs and bullet lists.
Let's parse the posting.
First paragraph: "The Software Engineer is responsible for the design, development, implementation, and lifecycle ownership of MSUFCU’s portfolio of software solutions. This can include various MSUFCU-owned websites, digital banking applications, core banking systems, financial mobile and web-based applications in partnership with Reseda Group, as well as other internal systems and applications. This position is a cross-functional role that works directly with the product team and other stakeholders to identify requirements and constraints, estimate timeframes, design user interfaces, define system designs, and collaboratively develops innovative solutions that align with strategic objectives. It includes writing robust, testable and well-documented code, including the development of automated tests to ensure high reliability, maintainability and quality while completing projects on time. This role also documents and communicates system designs and decisions, contributes to knowledge sharing across the team, and engages stakeholders through technical presentations and collaborative design discussions."
Then Work Arrangement paragraph: "Work Arrangement: This position is able to work onsite, hybrid, or remote (must reside within the states of Michigan or Illinois). To be considered for this role, candidate must currently reside, or have plans to reside upon hire, within the state of Michigan or Illinois as described above. Occasional travel on a quarterly basis to MSUFCU Headquarters (East Lansing, MI) may be needed. Department Hours: Monday - Friday 8:30am-5:00pm ET. An offer of employment with MSU Federal Credit Union and affiliates is contingent upon the agreed work arrangement (onsite/hybrid/remote) and work location. MSU Federal Credit Union may or may not be able to accommodate temporary or permanent changes to work arrangements or allow employment outside the city and/or state of residency in which the new hire resides at the time of offered employment."
Then Compensation & Benefits: "Compensation & Benefits: Salary Range:Associate Software Engineer - $70,000 - $85,000+ annually, depending on experience Software Engineer - $85,000 - $105,000+ annually, depending on experience 100% Company-Paid Health, Dental, Vision, Life, and Long-Term Disability PremiumsUp to 26 days of PTO within your first year, as well as Volunteer Time Off & 11 Paid Holidays401(k) with a company matchTuition ReimbursementUp to 12 Weeks of Paid Parental LeaveLearn more about our benefits here"
Then Essential Duties and Responsibilities: includes bullet-like sentences for Associate Software Engineer and Software Engineer.
Then Job Requirements: includes bullet-like sentences for Associate Software Engineer and Software Engineer.
Then Competencies: list of core competencies and functional competencies.
Then Physical Demands and Work Environment: some sentences.
Then Disclaimer etc to remove.
We need to output HTML with sections.
We need to decide what goes where.
About the role: likely the initial description plus work arrangement? Could include description of role and work arrangement. But we also have Schedule section for hours. So About the role could include the description of responsibilities at high level, plus maybe work arrangement (onsite/hybrid/remote) and location restrictions. But we also have Responsibilities section for detailed duties. So About the role could be a brief overview: the first paragraph plus maybe work arrangement? However we must not duplicate content. We can split: About the role: the first paragraph (role description). Work arrangement could be part of About the role or maybe a separate section but we don't have a heading for work arrangement; we could include it in About the role as a paragraph.
Responsibilities: the Essential Duties and Responsibilities content (both Associate and Software Engineer). We need to format as - for each duty. The text includes many sentences; we can break them into list items.
Requirements: Job Requirements content (Associate and Software Engineer). Also maybe include knowledge and familiarity list.
Qualifications: Could be education requirements? But we already have Requirements includes education. Qualifications could be things like "High School Diploma or Equivalent Required. Bachelor’s Degree Computer Science or in a related field or 3 years of experience in lieu of a degree". However that's also requirements. The distinction is fuzzy. But we need to include a Qualifications section if there is specific content. The posting has "Job Requirements:" which includes education, knowledge, etc. There's also "Competencies:" which could be considered Qualifications or Skills. We have Skills section for competencies. So Qualifications could be education and experience requirements. Let's put Qualifications: education and experience (the bullet points about HS diploma, degree, etc). Requirements: maybe the knowledge and familiarity list (technical skills). But the instruction says use sections as given; we must not invent sections. We have to decide what content goes where, but we must preserve all substantive info. We can allocate as:
- About the role: initial paragraph (role description) + maybe work arrangement? But we have Schedule separate for hours. Work arrangement (onsite/hybrid/remote, location) could go in About the role.
- Responsibilities: Essential Duties and Responsibilities (list items).
- Requirements: Job Requirements (knowledge and familiarity list, plus maybe the "All of Associate Software Engineer duties and responsibilities" etc). Actually Job Requirements includes both knowledge and familiarity and also "All of Associate Software Engineer knowledge, skills, and abilities." plus additional for Software Engineer. We'll put that in Requirements.
- Qualifications: Education and experience requirements (HS diploma, degree or experience). Could also include "Knowledge of credit union products and services..." but that seems more like qualifications for Software Engineer. However that is under Job Requirements for Software Engineer. Might be better to treat Qualifications as education/experience, and Requirements as technical knowledge/skills. But we need to avoid duplication.
- Skills: Competencies list (core and functional). Could also include technical skills from knowledge and familiarity? But we already put those in Requirements. So Skills will be the competencies.
- Benefits: list of benefits.
- Pay: salary ranges.
- Schedule: department hours.
We must not include filler like "depending on experience" is okay; it's specific. Not "commensurate with experience". It's okay.
We must not include boilerplate like "Learn more about our benefits here" - that's a link; we can drop that as it's navigation? It's not essential substantive info? It's a reference; we could drop as it's not substantive. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about our benefits here" is like a link; could be considered navigation. Safer to drop it.
Also "Up to 26 days of PTO within your first year, as well as Volunteer Time Off & 11 Paid Holidays" etc are benefits.
We need to format benefits as
- .
Pay: we need to include salary ranges. Could be
with the two lines.
Schedule:
Monday - Friday 8:30am-5:00pm ET.
Now we need to ensure we don't repeat content. Let's extract each piece.
About the role paragraph:
"The Software Engineer is responsible for the design, development, implementation, and lifecycle ownership of MSUFCU’s portfolio of software solutions. This can include various MSUFCU-owned websites, digital banking applications, core banking systems, financial mobile and web-based applications in partnership with Reseda Group, as well as other internal systems and applications. This position is a cross-functional role that works directly with the product team and other stakeholders to identify requirements and constraints, estimate timeframes, design user interfaces, define system designs, and collaboratively develops innovative solutions that align with strategic objectives. It includes writing robust, testable and well-documented code, including the development of automated tests to ensure high reliability, maintainability and quality while completing projects on time. This role also documents and communicates system designs and decisions, contributes to knowledge sharing across the team, and engages stakeholders through technical presentations and collaborative design discussions."
Work arrangement paragraph: "Work Arrangement: This position is able to work onsite, hybrid, or remote (must reside within the states of Michigan or Illinois). To be considered for this role, candidate must currently reside, or have plans to reside upon hire, within the state of Michigan or Illinois as described above. Occasional travel on a quarterly basis to MSUFCU Headquarters (East Lansing, MI) may be needed."
We could combine these two paragraphs in About the role.
Now Responsibilities: Essential Duties and Responsibilities section includes two sets: Associate Software Engineer duties and Software Engineer duties (which includes all Associate duties plus extra). We need to avoid duplication. We could list all duties for Software Engineer (which includes Associate duties). But we need to preserve all substantive info; we could list Associate duties then additional duties for Software Engineer. However that would duplicate the Associate duties. Better to list Software Engineer duties (which includes Associate duties) and note that Associate duties are subset. But we need to preserve the info that Associate duties are as described. Could list both but avoid duplication by listing Associate duties then extra for Software Engineer. That would repeat the Associate duties in the list for Software Engineer if we just copy them. To avoid duplication, we could list Associate duties as items, then for Software Engineer list additional items beyond Associate. However the posting says "Software Engineer - All of Associate Software Engineer duties and responsibilities." So we could note that.
Thus we can produce list items:
- Participate in the development and architecture of the credit union’s and Reseda Group’s software solutions through various tools, software, styles and programming languages; program and support front-end interactive elements as well as backend architecture to ensure the functionality, look, feel and organization of content.
- Participate in all phases of the Software Development Lifecycle (SDLC) including: analysis, design, testing, code review, deployment, and maintenance for all systems and applications maintained by the department.
- Troubleshoot technical problems and implement effective solutions.
- Assist with fixing any software or infrastructure problems that affect the digital solutions that the department supports.
- Create and help maintain technical documentation for programs and systems created and supported by the department.
- Collaboratively work with business units, technical teams, and third-party vendors to create project plans, technical specifications, software diagrams, and technical documentation
- .
Pay: we need to include salary ranges. Could be
with the two lines. Schedule:
Monday - Friday 8:30am-5:00pm ET. Now we need to ensure we don't repeat content. Let's extract each piece. About the role paragraph: "The Software Engineer is responsible for the design, development, implementation, and lifecycle ownership of MSUFCU’s portfolio of software solutions. This can include various MSUFCU-owned websites, digital banking applications, core banking systems, financial mobile and web-based applications in partnership with Reseda Group, as well as other internal systems and applications. This position is a cross-functional role that works directly with the product team and other stakeholders to identify requirements and constraints, estimate timeframes, design user interfaces, define system designs, and collaboratively develops innovative solutions that align with strategic objectives. It includes writing robust, testable and well-documented code, including the development of automated tests to ensure high reliability, maintainability and quality while completing projects on time. This role also documents and communicates system designs and decisions, contributes to knowledge sharing across the team, and engages stakeholders through technical presentations and collaborative design discussions." Work arrangement paragraph: "Work Arrangement: This position is able to work onsite, hybrid, or remote (must reside within the states of Michigan or Illinois). To be considered for this role, candidate must currently reside, or have plans to reside upon hire, within the state of Michigan or Illinois as described above. Occasional travel on a quarterly basis to MSUFCU Headquarters (East Lansing, MI) may be needed." We could combine these two paragraphs in About the role. Now Responsibilities: Essential Duties and Responsibilities section includes two sets: Associate Software Engineer duties and Software Engineer duties (which includes all Associate duties plus extra). We need to avoid duplication. We could list all duties for Software Engineer (which includes Associate duties). But we need to preserve all substantive info; we could list Associate duties then additional duties for Software Engineer. However that would duplicate the Associate duties. Better to list Software Engineer duties (which includes Associate duties) and note that Associate duties are subset. But we need to preserve the info that Associate duties are as described. Could list both but avoid duplication by listing Associate duties then extra for Software Engineer. That would repeat the Associate duties in the list for Software Engineer if we just copy them. To avoid duplication, we could list Associate duties as items, then for Software Engineer list additional items beyond Associate. However the posting says "Software Engineer - All of Associate Software Engineer duties and responsibilities." So we could note that. Thus we can produce list items: - Participate in the development and architecture of the credit union’s and Reseda Group’s software solutions through various tools, software, styles and programming languages; program and support front-end interactive elements as well as backend architecture to ensure the functionality, look, feel and organization of content. - Participate in all phases of the Software Development Lifecycle (SDLC) including: analysis, design, testing, code review, deployment, and maintenance for all systems and applications maintained by the department. - Troubleshoot technical problems and implement effective solutions. - Assist with fixing any software or infrastructure problems that affect the digital solutions that the department supports. - Create and help maintain technical documentation for programs and systems created and supported by the department. - Collaboratively work with business units, technical teams, and third-party vendors to create project plans, technical specifications, software diagrams, and technical documentation