Intern - Application Analyst (Financials Software)
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits
3. Use
for prose
4. Do NOT repeat the job title as a heading
5. Do NOT put Job ID/requisition numbers as headings
6. Preserve ALL substantive information
7. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
8. Include a section ONLY when there's real, specific content
9. Never emit a heading followed by filler/placeholder text
10. Output ONLY the HTML fragment
Let me identify the sections from the posting:
- Company Overview (prose) - could be "About the role" or "About the company"
- Position Overview (prose) - "About the role"
- Work Schedule (specific info) - "Schedule"
- Essential Functions (list) - "Responsibilities"
- Desired Job Experience (list) - "Requirements" or "Qualifications"
- NISC's Shared Values & Competencies (prose/list) - could be "About the company" or "Qualifications"
- Desired Education and/or Certification(s) (list) - "Qualifications"
- Minimum Physical Requirements (prose) - "Requirements"
- Disclaimer (boilerplate) - should be removed
I need to organize this logically. Let me structure:
1. About the role (Position Overview)
2. Schedule (Work Schedule)
3. Responsibilities (Essential Functions)
4. Requirements (Desired Job Experience + Minimum Physical Requirements)
5. Qualifications (Desired Education and/or Certification(s))
6. About the company (Company Overview + Shared Values)
Wait, the rules say to use specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use these standard headings where appropriate.
Let me map:
- Position Overview → About the role
- Work Schedule → Schedule
- Essential Functions → Responsibilities
- Desired Job Experience → Requirements (or Qualifications)
- Desired Education → Qualifications
- Company Overview + Shared Values → About the company (but "About the company" isn't in the standard list... the standard list has "About the role". I could use "About the role" for position overview and maybe include company info there or as a separate section. The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule" - so these are examples. I can use other relevant headings but should prefer these.
I think I'll use:
- About the role (for Position Overview)
- Schedule (for Work Schedule)
- Responsibilities (for Essential Functions)
- Requirements (for Desired Job Experience + Physical Requirements)
- Qualifications (for Desired Education)
- About the company (for Company Overview + Shared Values) - though not in the example list, it's substantive content
Actually, looking at the rules again: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." means these are examples. I can use other headings if needed. But I should prefer these standard ones.
Let me combine Company Overview and Shared Values into "About the company" or maybe fold into "About the role". But the company overview is quite substantial. I'll create an "About the company" section.
Now, let me write the HTML. I need to be careful:
- No /
- No markdown code fences
- Only the HTML fragment
- Use ,
,
-
Let me draft:
About the role
This position reports to an Application Analysis Team Lead and collaborates with application analysts, software developers, software engineers, quality assurance teams, and subject matter experts. The intern will gain hands-on experience supporting the analysis, design, testing, and enhancement of NISC's software solutions, with a primary focus on NISC's Financials Software product. This position offers exposure to business requirements analysis, software design processes, database structures, documentation, quality assurance practices, and cross-functional collaboration within an enterprise software environment. This position may also be exposed to data fixes including bug fixes or custom programming requests.
Schedule
Hybrid from the Mandan, ND office location. Minimum of working 3 days per week out of an office location and ability to work up to all 5 days a week from an office location. Current applications submitted will be under consideration for Summer 2027 (May - August).
Responsibilities
- Assists with researching, analyzing, and documenting software functionality and business requirements.
- Supports application analysts and development teams in evaluating software enhancements and change requests.
- Assists in the creation and maintenance of functional diagrams, workflow diagrams, and related documentation.
- Collaborates with technical teams to understand software design specifications, interfaces, and database structures.
- Participates in discussions regarding software enhancements and solution development.
- Follows established software development and analysis methodologies and procedures.
- Assists with quality assurance testing, including unit and system integration testing activities.
- Helps analyze business processes and software requirements to support application improvements.
- Participates in design reviews and team meetings to gain exposure to software development lifecycle processes.
- Assists with documentation and maintenance of information within Confluence and/or the iVUE Support tool.
- Supports internal teams in researching and resolving software-related issues.
- Performs other duties as assigned.
Requirements
- Strong interest in software analysis, business systems, and technology solutions.
- Familiarity with software development lifecycle concepts and methodologies.
- Basic understanding of databases and data structures.
- Strong analytical and problem-solving skills.
- Strong attention to detail and organizational skills.
- Excellent verbal and written communication skills.
- Experience with using agentic AI coding tools (Claude Code, Augment, Jetbrains Junie, Github Copilot, Cursor, OpenAI Codex).
- Ability to learn new technologies and business processes quickly.
- Ability to organize and prioritize multiple tasks.
- Ability to work independently as well as in a team environment.
- Ability to interact professionally and positively with internal and external contacts.
- Ability to adapt effectively to change.
- Proficiency with Microsoft Office applications.
- Commitment to NISC's Statement of Shared Values.
- High School diploma or equivalency required.
- Pursuing Bachelor's Degree in Computer Science, Information Technology, Management Information Systems, Computer Engineering, or a related technical field.
- Must be able to see and communicate; regularly required to maintain a stationary position, move, and operate computer keyboards or office equipment. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
Qualifications
Desired Education and/or Certification(s): High School diploma or equivalency required; Pursuing Bachelor's Degree in a Computer Science, Information Technology, Management Information Systems, Computer Engineering, or a related technical field.
Wait, I already included education in Requirements. The posting has "Desired Education and/or Certification(s)" as a separate section. I should keep it separate as Qualifications. But I also have "Desired Job Experience" which is more like requirements. Let me separate:
- Requirements: Desired Job Experience (skills, abilities, experience)
- Qualifications: Desired Education and/or Certification(s)
- Physical Requirements: Minimum Physical Requirements
But the rules say to prefer a few substantive sections over many thin ones. Physical requirements could go into Requirements. Education into Qualifications.
Let me restructure:
Requirements
- Strong interest in software analysis, business systems, and technology solutions.
- Familiarity with software development lifecycle concepts and methodologies.
- Basic understanding of databases and data structures.
- Strong analytical and problem-solving skills.
- Strong attention to detail and organizational skills.
- Excellent verbal and written communication skills.
- Experience with using agentic AI coding tools (Claude Code, Augment, Jetbrains Junie, Github Copilot, Cursor, OpenAI Codex).
- Ability to learn new technologies and business processes quickly.
- Ability to organize and prioritize multiple tasks.
- Ability to work independently as well as in a team environment.
- Ability to interact professionally and positively with internal and external contacts.
- Ability to adapt effectively to change.
- Proficiency with Microsoft Office applications.
- Commitment to NISC's Statement of Shared Values.
- High School diploma or equivalency required.
- Pursuing Bachelor's Degree in Computer Science, Information Technology, Management Information Systems, Computer Engineering, or a related technical field.
- Must be able to see and communicate; regularly required to maintain a stationary position, move, and operate computer keyboards or office equipment. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
But that's mixing experience, education, and physical. Maybe better to split:
Requirements
- Strong interest in software analysis, business systems, and technology solutions.
- Familiarity with software development lifecycle concepts and methodologies.
- Basic understanding of databases and data structures.
- Strong analytical and problem-solving skills.
- Strong attention to detail and organizational skills.
- Excellent verbal and written communication skills.
- Experience with using agentic AI coding tools (Claude Code, Augment, Jetbrains Junie, Github Copilot, Cursor, OpenAI Codex).
- Ability to learn new technologies and business processes quickly.
- Ability to organize and prioritize multiple tasks.
- Ability to work independently as well as in a team environment.
- Ability to interact professionally and positively with internal and external contacts.
- Ability to adapt effectively to change.
- Proficiency with Microsoft Office applications.
- Commitment to NISC's Statement of Shared Values.
Qualifications
- High School diploma or equivalency required.
- Pursuing Bachelor's Degree in Computer Science, Information Technology, Management Information Systems, Computer Engineering, or a related technical field.
Physical requirements
Must be able to see and communicate; regularly required to maintain a stationary position, move, and operate computer keyboards or office equipment. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
But "Physical requirements" isn't in the example list. The example list has "Requirements" and "Qualifications". I could fold physical into Requirements. Or make a "Requirements" section with sub-lists? But the rules say use - for lists. I think folding physical into Requirements is fine.
Actually, the posting has "Minimum Physical Requirements" as a separate section. I'll include it as a subsection under Requirements or as its own. Since the rules say "include a section ONLY when the posting has real, specific content for it", and physical requirements are specific, I could make it a section. But the heading should be from the example list or similar. "Requirements" covers it.
Let me check the example headings again: About the role,
for prose 4. Do NOT repeat the job title as a heading 5. Do NOT put Job ID/requisition numbers as headings 6. Preserve ALL substantive information 7. Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) 8. Include a section ONLY when there's real, specific content 9. Never emit a heading followed by filler/placeholder text 10. Output ONLY the HTML fragment Let me identify the sections from the posting: - Company Overview (prose) - could be "About the role" or "About the company" - Position Overview (prose) - "About the role" - Work Schedule (specific info) - "Schedule" - Essential Functions (list) - "Responsibilities" - Desired Job Experience (list) - "Requirements" or "Qualifications" - NISC's Shared Values & Competencies (prose/list) - could be "About the company" or "Qualifications" - Desired Education and/or Certification(s) (list) - "Qualifications" - Minimum Physical Requirements (prose) - "Requirements" - Disclaimer (boilerplate) - should be removed I need to organize this logically. Let me structure: 1. About the role (Position Overview) 2. Schedule (Work Schedule) 3. Responsibilities (Essential Functions) 4. Requirements (Desired Job Experience + Minimum Physical Requirements) 5. Qualifications (Desired Education and/or Certification(s)) 6. About the company (Company Overview + Shared Values) Wait, the rules say to use specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should use these standard headings where appropriate. Let me map: - Position Overview → About the role - Work Schedule → Schedule - Essential Functions → Responsibilities - Desired Job Experience → Requirements (or Qualifications) - Desired Education → Qualifications - Company Overview + Shared Values → About the company (but "About the company" isn't in the standard list... the standard list has "About the role". I could use "About the role" for position overview and maybe include company info there or as a separate section. The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule" - so these are examples. I can use other relevant headings but should prefer these. I think I'll use: - About the role (for Position Overview) - Schedule (for Work Schedule) - Responsibilities (for Essential Functions) - Requirements (for Desired Job Experience + Physical Requirements) - Qualifications (for Desired Education) - About the company (for Company Overview + Shared Values) - though not in the example list, it's substantive content Actually, looking at the rules again: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." means these are examples. I can use other headings if needed. But I should prefer these standard ones.
Let me combine Company Overview and Shared Values into "About the company" or maybe fold into "About the role". But the company overview is quite substantial. I'll create an "About the company" section.
Now, let me write the HTML. I need to be careful:
- No /
- No markdown code fences
- Only the HTML fragment
- Use ,
,
-
Let me draft:
About the role
This position reports to an Application Analysis Team Lead and collaborates with application analysts, software developers, software engineers, quality assurance teams, and subject matter experts. The intern will gain hands-on experience supporting the analysis, design, testing, and enhancement of NISC's software solutions, with a primary focus on NISC's Financials Software product. This position offers exposure to business requirements analysis, software design processes, database structures, documentation, quality assurance practices, and cross-functional collaboration within an enterprise software environment. This position may also be exposed to data fixes including bug fixes or custom programming requests.
Schedule
Hybrid from the Mandan, ND office location. Minimum of working 3 days per week out of an office location and ability to work up to all 5 days a week from an office location. Current applications submitted will be under consideration for Summer 2027 (May - August).
Responsibilities
- Assists with researching, analyzing, and documenting software functionality and business requirements.
- Supports application analysts and development teams in evaluating software enhancements and change requests.
- Assists in the creation and maintenance of functional diagrams, workflow diagrams, and related documentation.
- Collaborates with technical teams to understand software design specifications, interfaces, and database structures.
- Participates in discussions regarding software enhancements and solution development.
- Follows established software development and analysis methodologies and procedures.
- Assists with quality assurance testing, including unit and system integration testing activities.
- Helps analyze business processes and software requirements to support application improvements.
- Participates in design reviews and team meetings to gain exposure to software development lifecycle processes.
- Assists with documentation and maintenance of information within Confluence and/or the iVUE Support tool.
- Supports internal teams in researching and resolving software-related issues.
- Performs other duties as assigned.
Requirements
- Strong interest in software analysis, business systems, and technology solutions.
- Familiarity with software development lifecycle concepts and methodologies.
- Basic understanding of databases and data structures.
- Strong analytical and problem-solving skills.
- Strong attention to detail and organizational skills.
- Excellent verbal and written communication skills.
- Experience with using agentic AI coding tools (Claude Code, Augment, Jetbrains Junie, Github Copilot, Cursor, OpenAI Codex).
- Ability to learn new technologies and business processes quickly.
- Ability to organize and prioritize multiple tasks.
- Ability to work independently as well as in a team environment.
- Ability to interact professionally and positively with internal and external contacts.
- Ability to adapt effectively to change.
- Proficiency with Microsoft Office applications.
- Commitment to NISC's Statement of Shared Values.
- High School diploma or equivalency required.
- Pursuing Bachelor's Degree in Computer Science, Information Technology, Management Information Systems, Computer Engineering, or a related technical field.
- Must be able to see and communicate; regularly required to maintain a stationary position, move, and operate computer keyboards or office equipment. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
Qualifications
Desired Education and/or Certification(s): High School diploma or equivalency required; Pursuing Bachelor's Degree in a Computer Science, Information Technology, Management Information Systems, Computer Engineering, or a related technical field.
Wait, I already included education in Requirements. The posting has "Desired Education and/or Certification(s)" as a separate section. I should keep it separate as Qualifications. But I also have "Desired Job Experience" which is more like requirements. Let me separate: - Requirements: Desired Job Experience (skills, abilities, experience) - Qualifications: Desired Education and/or Certification(s) - Physical Requirements: Minimum Physical Requirements But the rules say to prefer a few substantive sections over many thin ones. Physical requirements could go into Requirements. Education into Qualifications. Let me restructure:Requirements
- Strong interest in software analysis, business systems, and technology solutions.
- Familiarity with software development lifecycle concepts and methodologies.
- Basic understanding of databases and data structures.
- Strong analytical and problem-solving skills.
- Strong attention to detail and organizational skills.
- Excellent verbal and written communication skills.
- Experience with using agentic AI coding tools (Claude Code, Augment, Jetbrains Junie, Github Copilot, Cursor, OpenAI Codex).
- Ability to learn new technologies and business processes quickly.
- Ability to organize and prioritize multiple tasks.
- Ability to work independently as well as in a team environment.
- Ability to interact professionally and positively with internal and external contacts.
- Ability to adapt effectively to change.
- Proficiency with Microsoft Office applications.
- Commitment to NISC's Statement of Shared Values.
- High School diploma or equivalency required.
- Pursuing Bachelor's Degree in Computer Science, Information Technology, Management Information Systems, Computer Engineering, or a related technical field.
- Must be able to see and communicate; regularly required to maintain a stationary position, move, and operate computer keyboards or office equipment. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
Requirements
- Strong interest in software analysis, business systems, and technology solutions.
- Familiarity with software development lifecycle concepts and methodologies.
- Basic understanding of databases and data structures.
- Strong analytical and problem-solving skills.
- Strong attention to detail and organizational skills.
- Excellent verbal and written communication skills.
- Experience with using agentic AI coding tools (Claude Code, Augment, Jetbrains Junie, Github Copilot, Cursor, OpenAI Codex).
- Ability to learn new technologies and business processes quickly.
- Ability to organize and prioritize multiple tasks.
- Ability to work independently as well as in a team environment.
- Ability to interact professionally and positively with internal and external contacts.
- Ability to adapt effectively to change.
- Proficiency with Microsoft Office applications.
- Commitment to NISC's Statement of Shared Values.
Qualifications
- High School diploma or equivalency required.
- Pursuing Bachelor's Degree in Computer Science, Information Technology, Management Information Systems, Computer Engineering, or a related technical field.
Physical requirements
Must be able to see and communicate; regularly required to maintain a stationary position, move, and operate computer keyboards or office equipment. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.
But "Physical requirements" isn't in the example list. The example list has "Requirements" and "Qualifications". I could fold physical into Requirements. Or make a "Requirements" section with sub-lists? But the rules say use- for lists. I think folding physical into Requirements is fine. Actually, the posting has "Minimum Physical Requirements" as a separate section. I'll include it as a subsection under Requirements or as its own. Since the rules say "include a section ONLY when the posting has real, specific content for it", and physical requirements are specific, I could make it a section. But the heading should be from the example list or similar. "Requirements" covers it. Let me check the example headings again: About the role,