Software Developer III Grade 14
Space Coast Credit Union · Melbourne, FL · 3 wk ago
Hybrid$114k–$121k/yrFull-time
We need to output HTML fragment with headings for sections present: About the role? Actually they have "Why Join SCCU?" which is like Benefits? But we need to follow rules: Use
for sections present: About the role? Actually they have "Why Join SCCU?" which is like Benefits? But we need to follow rules: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have:
- About the role: The description: "As a Software Developer III, you will be responsible for the designs, codes, and develops new financial applications or web based systems and/or modifies existing core financial application systems and web based systems." Also mention contract-to-hire 6 month. Also "Why Join SCCU?" includes Member-Focused Mission, Flexible Schedule Options, Career Growth. That could be Benefits? But we have separate Benefits section later.
- Responsibilities: list of duties.
- Requirements: list of experience and skills.
- Qualifications? Not separate; maybe combine with Requirements.
- Skills: front-end developer skills etc.
- Pay: compensation range.
- Benefits: list of benefits.
- Schedule: work schedule.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: legal statements, EEO, etc. Also remove duplicated lines.
We need to preserve all substantive info.
Let's extract content.
From posting:
Intro: At Space Coast Credit Union (SCCU), our members are at the heart of everything we do. Since 1951, we’ve been committed to delivering financial services founded on integrity and a people-first philosophy. This position is a 6 month contract-to-hire. As a Software Developer III, you will be responsible for the designs, codes, and develops new financial applications or web based systems and/or modifies existing core financial application systems and web based systems.
Why Join SCCU? Member-Focused Mission: Be part of a not-for-profit organization that reinvests in its members.Flexible Schedule OptionsCareer Growth: We prioritize internal promotions and offer on-the-job training.
Software Developer III Key Responsibilities (list):
- Responds to end user trouble calls to resolve routine application software problems or assist with hardware issues remotely when possible.
- Routes calls as needs for more non-routine questions.
- Track tickets in an incident management system to properly identify problem and resolution for a shared knowledge base or escalate and assign as needed for higher level support.
- Designs, develops, tests, and integrates moderately complex internal and external core and web applications, services, and sites, including maintenance, upgrades, and troubleshooting in order to fulfill business needs.
- Assists in determining cost and schedule of various software projects using current and proven software engineering
- Provides tier III technical support for staff on internal and external core and web applications and systems.
- Confers with vendors, other IT team members, users, and department managers to determine requirements for new or modified software and hardware.
- Tests new hardware and software configurations for usability and proper function, including cross-browser functional capability.
- Develops web security safeguards and technologies.
- Consistently meets assigned project deadlines and goals.
- Reviews, analyzes, and modifies the application systems including encoding, testing, debugging, and documentation.
- Analyzes and resolves problems associated with application systems.
- Detects, diagnoses, and reports related problems.
Software Developer III Requirements:
- 5 to 8 years prior experience with software analysis, design, development, testing, debugging, integration, deployment, support and documentation of core and web based systems following the software development lifecycle, or combination of applicable experience, education, and training which provides the knowledge and skills needed to perform job duties.
- Front-end Developer skills: Front-end web development, React, JavaScript, CSS, JQuery, SASS, Bootstrap, and WCMS platforms.
- Familiarity with .Net, Visual Studio, Azure DevOps Server, C#, SQL Server and/or other relational databases, Node.JS, experience with client-server concepts, object-oriented programming, web services, and Waterfall/Agile development methodologies.
Software Developer III Compensation: $113,900.00 - $120,628.00
SCCU Benefits:
- Health & Wellness: Medical, dental, and vision insurance, plus an Employee Assistance Program.
- Financial Perks: 401(k) match (5%), HSA match, and SCCU-paid insurance (short/long-term disability, life insurance).
- Education Support: Tuition reimbursement after one year of service.
- Generous Time Off: 20+ days of PTO, birthday PTO, and 11 federal holidays.
- Exclusive Discounts: Lower rates on loans, credit cards, and no fee SCCU accounts!
Work Schedule: Monday – Friday: 8:00 a.m. - 5:00 p.m.
About SCCU (description): Since 1951, Space Coast Credit Union (SCCU) has proudly served our community, growing to over 685,000 members and managing $9 billion in assets. With 67 branches spanning Florida’s east coast, we are the third-largest credit union in the state. In 2025, we expanded into Orange County to better serve the growing East Orlando market. As a not-for-profit financial institution, SCCU is dedicated to putting our members first. Unlike traditional banks, we return profits to our members through better rates, lower fees, and enhanced services. While we offer the same financial products—like checking, savings, and loans—our focus remains on empowering our members and supporting their financial well-being. With local decision-making and a commitment to exceptional service, we strive to make a meaningful difference in the lives of those we serve. At SCCU, we also prioritize our team members by fostering a supportive and collaborative environment that encourages career growth and development. As we continue to grow, we are seeking talented, member-focused professionals to join our team and help deliver innovative financial solutions and outstanding service.
Legal boilerplate after that should be removed.
Now we need to decide sections.
We have:
- About the role: Could combine intro and "Why Join SCCU?" maybe as About the role. But we have separate "Why Join SCCU?" which includes Member-Focused Mission, Flexible Schedule Options, Career Growth. Those could be Benefits? Actually they are more about why join, could be considered Benefits or About the role. However we already have Benefits section for concrete benefits. The "Why Join SCCU?" includes Member-Focused Mission (not a tangible benefit), Flexible Schedule Options (maybe schedule), Career Growth (maybe benefits). But we have separate Schedule section later. So we could treat "Why Join SCCU?" as part of About the role or maybe as a separate section like "Why Join SCCU?" but not in allowed headings list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Probably we should map content to those headings. So we can have:
About the role
with intro paragraph: At Space Coast Credit Union (SCCU), our members are at the heart... This position is a 6 month contract-to-hire. As a Software Developer III, you will be responsible for the designs, codes, and develops new financial applications or web based systems and/or modifies existing core financial application systems and web based systems.
Maybe also include "Why Join SCCU?" content? Could be part of About the role or Benefits. But we have Benefits separate; we could put Member-Focused Mission, Career Growth as part of Benefits? But they are not typical benefits like health insurance. However they are still benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Why Join SCCU? into Benefits section as bullet points? But Benefits already has list. Could add those as additional bullet points under Benefits. However the Benefits section currently has specific items; we could add "Member-Focused Mission: Be part of a not-for-profit organization that reinvests in its members." and "Career Growth: We prioritize internal promotions and offer on-the-job training." and "Flexible Schedule Options" maybe goes to Schedule.
But we have separate Schedule section later. So Flexible Schedule Options could be mentioned there.
Thus we can treat About the role as just the intro and role description. Responsibilities as list. Requirements as list (maybe split into Requirements and Skills? But we have Skills heading allowed. Could separate front-end developer skills as Skills, and other familiarity as Requirements? But the posting lumps them together under Requirements. However we can still create Skills section for front-end developer skills, and Requirements for experience and other familiarity. That would be more specific and not thin? Might be okay.
But we need to avoid creating sections with filler. We have concrete content for each.
Let's plan sections:
- About the role: intro paragraph.
- Responsibilities: - list.
- Requirements: 5 to 8 years experience ... plus familiarity with .Net, Visual Studio, Azure DevOps Server, C#, SQL Server, Node.JS, client-server concepts, OOP, web services, Waterfall/Agile.
- Skills: Front-end Developer skills: Front-end web development, React, JavaScript, CSS, JQuery, SASS, Bootstrap, WCMS platforms.
- Pay: compensation range.
- Benefits: list of benefits (Health & Wellness, Financial Perks, Education Support, Generous Time Off, Exclusive Discounts). Also maybe include Member-Focused Mission and Career Growth? Could add as bullet points.
- Schedule: Monday – Friday: 8:00 a.m. - 5:00 p.m.
We should not include About SCCU description? That's more about company; could be part of About the role? But we already have About the role; maybe we can add a second paragraph about SCCU under About the role? However About the role is supposed to be about the role, not company. But we could add a separate section like "About SCCU" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It might be okay to add other headings if needed, but better to stick to allowed ones. The About SCCU description is substantive; we could incorporate it into About the role as a second paragraph describing the organization. That seems okay: About the role can include both role and company overview.
Thus About the role will have two paragraphs: first about the role and contract, second about SCCU.
Now we need to ensure we don't repeat job title as heading. We'll not.
We must not include boilerplate like legal statements, EEO, etc. Remove duplicated lines.
Now produce HTML fragment.
Let's craft.
About the role
At Space Coast Credit Union (SCCU), our members are at the heart of everything we do. Since 1951, we’ve been committed to delivering financial services founded on integrity and a people-first philosophy. This position is a 6 month contract-to-hire. As a Software Developer III, you will be responsible for the designs, codes, and develops new financial applications or web based systems and/or modifies existing core financial application systems and web based systems.
SCCU has grown to over 685,000 members and manages $9 billion in assets, with 67 branches across Florida’s east coast and a recent expansion into Orange County. As a not-for-profit financial institution, SCCU returns profits to members through better rates, lower fees, and enhanced services, while fostering a supportive, collaborative environment that encourages career growth and development.
Responsibilities
- Responds to end user trouble calls to resolve routine application software problems or assist with hardware issues remotely when possible.
- Routes calls as needed for more non‑routine questions.
- Tracks tickets in an incident management system to properly identify problem and resolution for a shared knowledge
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Probably we should map content to those headings. So we can have:
About the role
with intro paragraph: At Space Coast Credit Union (SCCU), our members are at the heart... This position is a 6 month contract-to-hire. As a Software Developer III, you will be responsible for the designs, codes, and develops new financial applications or web based systems and/or modifies existing core financial application systems and web based systems.
Maybe also include "Why Join SCCU?" content? Could be part of About the role or Benefits. But we have Benefits separate; we could put Member-Focused Mission, Career Growth as part of Benefits? But they are not typical benefits like health insurance. However they are still benefits. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Why Join SCCU? into Benefits section as bullet points? But Benefits already has list. Could add those as additional bullet points under Benefits. However the Benefits section currently has specific items; we could add "Member-Focused Mission: Be part of a not-for-profit organization that reinvests in its members." and "Career Growth: We prioritize internal promotions and offer on-the-job training." and "Flexible Schedule Options" maybe goes to Schedule.
But we have separate Schedule section later. So Flexible Schedule Options could be mentioned there.
Thus we can treat About the role as just the intro and role description. Responsibilities as list. Requirements as list (maybe split into Requirements and Skills? But we have Skills heading allowed. Could separate front-end developer skills as Skills, and other familiarity as Requirements? But the posting lumps them together under Requirements. However we can still create Skills section for front-end developer skills, and Requirements for experience and other familiarity. That would be more specific and not thin? Might be okay.
But we need to avoid creating sections with filler. We have concrete content for each.
Let's plan sections:
- About the role: intro paragraph.
- Responsibilities: - list.
- Requirements: 5 to 8 years experience ... plus familiarity with .Net, Visual Studio, Azure DevOps Server, C#, SQL Server, Node.JS, client-server concepts, OOP, web services, Waterfall/Agile.
- Skills: Front-end Developer skills: Front-end web development, React, JavaScript, CSS, JQuery, SASS, Bootstrap, WCMS platforms.
- Pay: compensation range.
- Benefits: list of benefits (Health & Wellness, Financial Perks, Education Support, Generous Time Off, Exclusive Discounts). Also maybe include Member-Focused Mission and Career Growth? Could add as bullet points.
- Schedule: Monday – Friday: 8:00 a.m. - 5:00 p.m.
We should not include About SCCU description? That's more about company; could be part of About the role? But we already have About the role; maybe we can add a second paragraph about SCCU under About the role? However About the role is supposed to be about the role, not company. But we could add a separate section like "About SCCU" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It might be okay to add other headings if needed, but better to stick to allowed ones. The About SCCU description is substantive; we could incorporate it into About the role as a second paragraph describing the organization. That seems okay: About the role can include both role and company overview.
Thus About the role will have two paragraphs: first about the role and contract, second about SCCU.
Now we need to ensure we don't repeat job title as heading. We'll not.
We must not include boilerplate like legal statements, EEO, etc. Remove duplicated lines.
Now produce HTML fragment.
Let's craft.
About the role
At Space Coast Credit Union (SCCU), our members are at the heart of everything we do. Since 1951, we’ve been committed to delivering financial services founded on integrity and a people-first philosophy. This position is a 6 month contract-to-hire. As a Software Developer III, you will be responsible for the designs, codes, and develops new financial applications or web based systems and/or modifies existing core financial application systems and web based systems.
SCCU has grown to over 685,000 members and manages $9 billion in assets, with 67 branches across Florida’s east coast and a recent expansion into Orange County. As a not-for-profit financial institution, SCCU returns profits to members through better rates, lower fees, and enhanced services, while fostering a supportive, collaborative environment that encourages career growth and development.
Responsibilities
- Responds to end user trouble calls to resolve routine application software problems or assist with hardware issues remotely when possible.
- Routes calls as needed for more non‑routine questions.
- Tracks tickets in an incident management system to properly identify problem and resolution for a shared knowledge
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It might be okay to add other headings if needed, but better to stick to allowed ones. The About SCCU description is substantive; we could incorporate it into About the role as a second paragraph describing the organization. That seems okay: About the role can include both role and company overview.
Thus About the role will have two paragraphs: first about the role and contract, second about SCCU.
Now we need to ensure we don't repeat job title as heading. We'll not.
We must not include boilerplate like legal statements, EEO, etc. Remove duplicated lines.
Now produce HTML fragment.
Let's craft.
About the role
At Space Coast Credit Union (SCCU), our members are at the heart of everything we do. Since 1951, we’ve been committed to delivering financial services founded on integrity and a people-first philosophy. This position is a 6 month contract-to-hire. As a Software Developer III, you will be responsible for the designs, codes, and develops new financial applications or web based systems and/or modifies existing core financial application systems and web based systems.
SCCU has grown to over 685,000 members and manages $9 billion in assets, with 67 branches across Florida’s east coast and a recent expansion into Orange County. As a not-for-profit financial institution, SCCU returns profits to members through better rates, lower fees, and enhanced services, while fostering a supportive, collaborative environment that encourages career growth and development.
Responsibilities
- Responds to end user trouble calls to resolve routine application software problems or assist with hardware issues remotely when possible.
- Routes calls as needed for more non‑routine questions.
- Tracks tickets in an incident management system to properly identify problem and resolution for a shared knowledge