Senior Business Analyst/Functional Lead
CGI · Lafayette, LA · 3 wk ago
Analyst$80k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate like EEO etc. Must preserve all substantive info.
We need to parse the posting.
Content:
- Position Description paragraph: "The ideal candidate for this position is a problem solver. As a Senior Business Analyst and Functional Lead, you are an experienced analyst proficient in requirements definition and development. You can build strong relationships with your clients and your team and can manage stakeholder expectations. Candidates who are extremely organized and thrive on making processes run efficiently will do well in this position. If you are looking for a place where you can grow your skills while working with a friendly, dynamic team, this is the role for you. This position is located in our Lafayette, LA office; however, a hybrid working model is acceptable."
That's about the role.
- "Your future duties and responsibilities" then list of responsibilities (bulleted). We'll put under Responsibilities.
- "Required Qualifications To Be Successful In This Role" then bullet list of qualifications.
- "Desired qualifications/non essential skills required: CSM certification desired but not required. Experience authoring SQL queries will strongly benefit a candidate." That's desired qualifications/skills.
- Then compensation: "CGI is required by law in some jurisdictions to include a reasonable estimate of the compensation range for this role. ... A reasonable estimate of the current range for this role in the U.S. is $79,600.00 $172,400.00." So Pay section.
- Benefits: "CGI Federal's benefits are offered to eligible professionals on their first day of employment to include: Competitive compensation Comprehensive insurance options Matching contributions through the 401(k) plan and the share purchase plan Paid time off for vacation, holidays, and sick time Paid parental leave Learning opportunities and tuition assistance Wellness and Well being programs". So Benefits.
- Schedule: Not explicitly mentioned. There's hybrid working model acceptable, location Lafayette LA. Could be schedule? Not explicit schedule like full-time, part-time. Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule specifics. So omit.
- Also there is some other text about ownership etc. That's more about company culture; could be part of About the role? Might be considered "About the role" or maybe "Company Overview". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put culture under About the role as prose.
- Also there is "CGI is unable to sponsor international hires for this position. US Citizenship required." That's a qualification/requirement. Should be under Requirements or Qualifications.
- Also "Experience working with JIRA and Confluence" is under Required Qualifications.
- Also "Knowledge of the full software development lifecycle" etc.
- Also "Ability to travel to client site in Washington, DC as needed".
- Also "Minimum 7 years work experience as a business analyst and/or functional lead".
- Also "Bachelor's degree in a business related field or information systems management preferred".
- Also "Strong analytical and writing skills", "Excellent communication skills", "Ability to work effectively within a team environment under tight timelines", "Ability to multi task and support multiple projects at once".
- Also "CSM certification desired but not required." and "Experience authoring SQL queries will strongly benefit a candidate." That's desired qualifications/skills.
We need to decide sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine required qualifications?), Qualifications (maybe same as Requirements?), Skills (maybe desired qualifications?), Benefits, Pay.
But we must not repeat similar content. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple of those. We need to decide which sections have content.
We have:
- About the role: intro paragraph + maybe location/hybrid.
- Responsibilities: list of duties.
- Requirements: maybe the mandatory qualifications (Bachelor's degree preferred, 7 years experience, ability to travel, US Citizenship required, no sponsorship, knowledge of SDLC, strong analytical/writing skills, excellent communication, teamwork, multitask, JIRA/Confluence). That seems like requirements.
- Qualifications: maybe the same as Requirements? Could be redundant. But we could treat Requirements as mandatory, Qualifications as preferred? However the posting lumps "Required Qualifications To Be Successful In This Role" then bullet list. Then "Desired qualifications/non essential skills required:" then bullet. So we could map Required Qualifications to Requirements section, and Desired qualifications to Skills section (or Qualifications). But we already have Skills heading. Could put desired qualifications under Skills.
Better: Use Requirements for mandatory qualifications, Skills for desired qualifications/non-essential skills.
Qualifications heading could be omitted if not needed. But we have both Requirements and Qualifications as possible headings; we can choose to use only those that have content. Since we have both mandatory and desired, we could use Requirements for mandatory, Skills for desired. Qualifications could be omitted.
But we also have "Bachelor's degree ... preferred" which is not mandatory but preferred; still could be under Requirements.
Let's structure:
.
Requirements list (mandatory):
From "Required Qualifications To Be Successful In This Role":
- Bachelor's degree in a business related field or information systems management preferred
- Minimum 7 years work experience as a business analyst and/or functional lead
- Ability to travel to client site in Washington, DC as needed
- Knowledge of the full software development lifecycle
- Strong analytical and writing skills
- Excellent communication skills
- Ability to work effectively within a team environment under tight timelines
- Ability to multi task and support multiple projects at once
- Experience working with JIRA and Confluence
- CGI is unable to sponsor international hires for this position.
- US Citizenship required.
Also maybe "Ability to travel to client site in Washington, DC as needed" is a requirement.
We should keep each as separate .
Skills list (desired/non-essential):
- CSM certification desired but not required.
- Experience authoring SQL queries will strongly benefit a candidate.
Also maybe "Experience authoring SQL queries will strongly benefit a candidate." That's a skill.
Benefits list:
- Competitive compensation
- Comprehensive insurance options
- Matching contributions through the 401(k) plan and the share purchase plan
- Paid time off for vacation, holidays, and sick time
- Paid parental leave
- Learning opportunities and tuition assistance
- Wellness and Well being programs
Pay: "A reasonable estimate of the current range for this role in the U.S. is $79,600.00 $172,400.00." Note there is a missing space between numbers; but we keep as is.
About the role paragraph: combine the intro and location/hybrid.
Intro: "The ideal candidate for this position is a problem solver. As a Senior Business Analyst and Functional Lead, you are an experienced analyst proficient in requirements definition and development. You can build strong relationships with your clients and your team and can manage stakeholder expectations. Candidates who are extremely organized and thrive on making processes run efficiently will do well in this position. If you are looking for a place where you can grow your skills while working with a friendly, dynamic team, this is the role for you. This position is located in our Lafayette, LA office; however, a hybrid working model is acceptable."
We should not include any boilerplate like EEO etc. Also remove the later sections about ownership etc. That's not required but could be considered part of About the role? It's more about company culture. The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that content too if it's substantive. However we must fit into allowed headings. The ownership paragraph could go under About the role as additional prose. But we must not create new headings. So we can append to About the role paragraph.
The ownership paragraph: "Together, as owners, let’s turn meaningful insights into action. Life at CGI is rooted in ownership, teamwork, respect and belonging. Here, you’ll reach your full potential because… You are invited to be an owner from day 1 as we work together to bring our Dream to life. That’s why we call ourselves CGI Partners rather than employees. We benefit from our collective success and actively shape our company’s strategy and direction. Your work creates value. You’ll develop innovative solutions and build relationships with teammates and clients while accessing global capabilities to scale your ideas, embrace new opportunities, and benefit from expansive industry and technology expertise. You’ll shape your career by joining a company built to grow and last. You’ll be supported by leaders who care about your health and well-being and provide you with opportunities to deepen your skills and broaden your horizons. Come join our team—one of the largest IT and business consulting services firms in the world."
That is substantive; we should include it. It's not boilerplate; it's about company culture. So we can include in About the role section after the initial paragraph.
We must not include EEO etc. The later part about EEO, accommodation, background investigation etc is boilerplate/legal; we should remove.
Thus final HTML:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate like EEO etc. Must preserve all substantive info.
We need to parse the posting.
Content:
- Position Description paragraph: "The ideal candidate for this position is a problem solver. As a Senior Business Analyst and Functional Lead, you are an experienced analyst proficient in requirements definition and development. You can build strong relationships with your clients and your team and can manage stakeholder expectations. Candidates who are extremely organized and thrive on making processes run efficiently will do well in this position. If you are looking for a place where you can grow your skills while working with a friendly, dynamic team, this is the role for you. This position is located in our Lafayette, LA office; however, a hybrid working model is acceptable."
That's about the role.
- "Your future duties and responsibilities" then list of responsibilities (bulleted). We'll put under Responsibilities.
- "Required Qualifications To Be Successful In This Role" then bullet list of qualifications.
- "Desired qualifications/non essential skills required: CSM certification desired but not required. Experience authoring SQL queries will strongly benefit a candidate." That's desired qualifications/skills.
- Then compensation: "CGI is required by law in some jurisdictions to include a reasonable estimate of the compensation range for this role. ... A reasonable estimate of the current range for this role in the U.S. is $79,600.00 $172,400.00." So Pay section.
- Benefits: "CGI Federal's benefits are offered to eligible professionals on their first day of employment to include: Competitive compensation Comprehensive insurance options Matching contributions through the 401(k) plan and the share purchase plan Paid time off for vacation, holidays, and sick time Paid parental leave Learning opportunities and tuition assistance Wellness and Well being programs". So Benefits.
- Schedule: Not explicitly mentioned. There's hybrid working model acceptable, location Lafayette LA. Could be schedule? Not explicit schedule like full-time, part-time. Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule specifics. So omit.
- Also there is some other text about ownership etc. That's more about company culture; could be part of About the role? Might be considered "About the role" or maybe "Company Overview". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put culture under About the role as prose.
- Also there is "CGI is unable to sponsor international hires for this position. US Citizenship required." That's a qualification/requirement. Should be under Requirements or Qualifications.
- Also "Experience working with JIRA and Confluence" is under Required Qualifications.
- Also "Knowledge of the full software development lifecycle" etc.
- Also "Ability to travel to client site in Washington, DC as needed".
- Also "Minimum 7 years work experience as a business analyst and/or functional lead".
- Also "Bachelor's degree in a business related field or information systems management preferred".
- Also "Strong analytical and writing skills", "Excellent communication skills", "Ability to work effectively within a team environment under tight timelines", "Ability to multi task and support multiple projects at once".
- Also "CSM certification desired but not required." and "Experience authoring SQL queries will strongly benefit a candidate." That's desired qualifications/skills.
We need to decide sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine required qualifications?), Qualifications (maybe same as Requirements?), Skills (maybe desired qualifications?), Benefits, Pay.
But we must not repeat similar content. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple of those. We need to decide which sections have content.
We have:
- About the role: intro paragraph + maybe location/hybrid.
- Responsibilities: list of duties.
- Requirements: maybe the mandatory qualifications (Bachelor's degree preferred, 7 years experience, ability to travel, US Citizenship required, no sponsorship, knowledge of SDLC, strong analytical/writing skills, excellent communication, teamwork, multitask, JIRA/Confluence). That seems like requirements.
- Qualifications: maybe the same as Requirements? Could be redundant. But we could treat Requirements as mandatory, Qualifications as preferred? However the posting lumps "Required Qualifications To Be Successful In This Role" then bullet list. Then "Desired qualifications/non essential skills required:" then bullet. So we could map Required Qualifications to Requirements section, and Desired qualifications to Skills section (or Qualifications). But we already have Skills heading. Could put desired qualifications under Skills.
Better: Use Requirements for mandatory qualifications, Skills for desired qualifications/non-essential skills.
Qualifications heading could be omitted if not needed. But we have both Requirements and Qualifications as possible headings; we can choose to use only those that have content. Since we have both mandatory and desired, we could use Requirements for mandatory, Skills for desired. Qualifications could be omitted.
But we also have "Bachelor's degree ... preferred" which is not mandatory but preferred; still could be under Requirements.
Let's structure:
About the role
... intro paragraph ...
Responsibilities
- ... each duty ...
Requirements
- ... mandatory qualifications ...
Skills
- ... desired qualifications/non-essential skills ...
Benefits
- ... benefits ...
Pay
... compensation range ...
We must not include Schedule. Now we need to extract each bullet precisely. Responsibilities list from text: "Organize the daily activities of a software development project team Translate client business needs into functional and technical requirements. Create detailed development tickets and track requirements through the development process. Interact with client during JAD sessions. Run daily scrums, organize sprints, and conduct all team agile ceremonies. Remove blockers so that the team can accomplish sprint goals. Interact with advanced business analysts and solution developers to communicate and validate requirements. Perform functional and integrated testing to test application functionality against client requirements Prepare and maintain project documentation and artifacts including analysis, reports and user documentation. Work with project managers, developers, and end users to ensure application designs meet business requirements. Assist in all phases of software systems programming applications. Evaluate new and existing software products. Author and prepare meeting minutes to be distributed to a variety of audiences Author user stories, test scripts, acceptance criteria, and other Agile deliverables" We need to ensure each asAbout the role
The ideal candidate for this position is a problem solver. As a Senior Business Analyst and Functional Lead, you are an experienced analyst proficient in requirements definition and development. You can build strong relationships with your clients and your team and can manage stakeholder expectations. Candidates who are extremely organized and thrive on making processes run efficiently will do well in this position. If you are looking for a place where you can grow your skills while working with a friendly, dynamic team, this is the role for you. This position is located in our Lafayette, LA office; however, a hybrid working model is acceptable.
Together, as owners, let’s turn meaningful insights into action. Life at CGI is rooted in ownership, teamwork, respect and belonging. Here, you’ll reach your full potential because… You are invited to be an owner from day 1 as we work together to bring our Dream to life. That’s why we call ourselves CGI Partners rather than employees. We benefit from our collective success and actively shape our company’s strategy and direction. Your work creates value. You