Technical Business/Product Analyst
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include only sections when posting has real specific content. Must preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience" etc. Also must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Benefits, Wage Data (salary range), Work Environment/Physical Demands, Travel, etc. Pay: salary range given $80,000 - $120,000. So we can include Pay section with that. Schedule: not explicitly given; maybe work environment mentions schedule? Not explicit schedule like hours. There's mention of ability to sit/stand up to 8 hours per day, but not schedule. There's mention of morning/evening syncs with offshore teams, but not a set schedule. Probably we should not create Schedule section unless posting actually states them. It does not give specific schedule like "Full-time, 40 hrs/week". So omit Schedule.
Benefits: they list health, dental, vision, life insurance, 401(k) with employer match, paid time off. So include Benefits.
Pay: include salary range.
About the role: we have overview paragraph about role. Could be "About the role". Use that heading.
Responsibilities: there is a "Key Responsibilities:" section with bullet points (though formatting weird). We'll extract responsibilities.
Qualifications: there is "Required Qualifications" and "Preferred". We'll combine maybe into Qualifications and Skills? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide where to put requirements vs qualifications vs skills. The posting has "Required Qualifications" and "Preferred". Also mentions skills like proficiency in writing user stories, SQL, understanding of API integrations, hands-on experience with UAT, comfortable with APIs, data workflows, configurable software platforms, strong working knowledge of tools such as Jira, Confluence, Figma, Postman, etc. Also ability to explain technical constraints, manage schedule, excellent communication. Those could go under Skills. Qualifications could be the years of experience, proven ability, Agile experience, etc. Requirements maybe similar to qualifications? But we need to follow instruction: include sections only when posting has real specific content. We can have Qualifications and Skills separate. Requirements maybe not needed if content overlaps. But we could put "Requirements" for the required qualifications (5+ years experience, proven ability, Agile, etc.) and "Skills" for technical skills (user stories, SQL, API, tools). However the posting lumps them together. We need to preserve all substantive info; we can split but must not lose info. Let's decide:
- About the role: overview paragraph.
- Responsibilities: list of responsibilities.
- Qualifications: required qualifications (5+ years experience, proven ability to manage client relationships, Agile/Scrum, etc.)
- Skills: specific technical skills (writing user stories, BRDs, process flows, functional specifications, SQL; understanding of API integrations and cloud-based data structures; hands-on experience with UAT coordination and test case development; comfortable working with APIs, data workflows, configurable software platforms (low-code/no-code a plus); strong working knowledge of tools such as Jira, Confluence, Figma, Postman, or similar; ability to explain technical constraints to non-technical clients and business goals and technical requirements to developers; ability to manage schedule for morning/evening syncs; excellent communication and stakeholder management.)
- Benefits: list.
- Pay: salary range.
We should not include Requirements section if we already have Qualifications and Skills. But the instruction list includes Requirements as possible heading; we can omit if not needed. However we must ensure we don't lose any content that would be considered "Requirements". The required qualifications are essentially requirements. So we could put them under Qualifications. That's fine.
We must not include filler like "commensurate with skill, education, experience, and working environment." That's in Pay section? Actually they wrote: "The starting salary will be commensurate with skill, education, experience, and working environment." That's filler; we should avoid including that phrase if possible. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have actual salary range; we can include that. But we should avoid including the commensurate phrase as it's filler. So in Pay section we can just put the salary range: $80,000 - $120,000. Possibly also mention that it's the salary range for this position. That's substantive.
We must remove boilerplate: EEO, Drug Free Workplace, Solicitation, etc. Also remove "Work Environment/Physical Demands", "Travel", "Local Candidates only Yes", etc. Those are not required headings but could be considered extra info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep substantive info like travel percentage, work environment, physical demands, local candidates, drug free workplace, etc. However those are not under the allowed headings list. But we could incorporate them into existing sections like About the role or maybe a separate section like "Additional Information". However the instruction says use headings only from the list; we should not create other headings. But we can embed that info in paragraphs under existing sections if appropriate. For example, travel percentage could go under Responsibilities? Not really. Could go under About the role as part of overview. Physical demands could go under About the role as well. The instruction: "Prefer a few substantive sections over many thin ones." So we could add a section like "Work Environment" but that's not in the allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit all substantive info into those sections. We can add paragraphs under About the role covering work environment, travel, physical demands, local candidates, drug free workplace, etc. That would preserve info.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove EEO statement, drug free workplace? Actually drug free workplace is not EEO; it's a policy. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Drug free workplace might be considered legal boilerplate; but it's substantive? It's a condition of employment. Might be considered boilerplate but maybe we should keep? The instruction says remove ... boilerplate. It's ambiguous. I'd err on side of removing drug free workplace statement as it's likely boilerplate. Similarly "Solicitation Please no solicitation..." is boilerplate. Remove.
Local Candidates only Yes: that's substantive about eligibility; we could keep.
Travel 25-35%: substantive.
Work environment/Physical Demands: substantive.
We'll embed those in About the role.
Now craft HTML.
Structure:
About the role
... overview plus work environment, travel, physical demands, local candidates.
Responsibilities
- ... each responsibility.
Qualifications
- ... required qualifications.
Skills
- ... skills.
Benefits
- ... benefits.
Pay
Salary range: $80,000 - $120,000.
We must not include Schedule section.
Now extract content.
About the role overview: "Overview We are looking for a Technical Business Analyst with 5+ years of experience to serve as the critical bridge between our enterprise clients and our internal development team. The Analyst will own the full lifecycle of client-facing feature delivery, from gathering and translating requirements through to testing, release, and post-deployment validation ensuring that client expectations are met with precision and on schedule. You will also work closely with offshore teams, requiring flexibility and strong communication practices to collaborate effectively across multiple time zones. Comfort with early morning or evening overlap windows, asynchronous workflows, and distributed team dynamics is essential to thriving in this role."
Add work environment: "Work Environment This job operates in a professional office environment and uses standard office equipment such as computers and phones." Physical demands: "Ability to sit/stand for up to 8 hours per day. Ability to move freely for up to 8 hours per day." Travel: "This role requires 25 - 35% travel to client sites, project locations, and occasional internal team meetings." Local Candidates only Yes: maybe phrase "Local candidates only." We'll include.
Combine into a paragraph or multiple paragraphs? Use for prose. Could have multiple
tags under the heading. That's fine.
Responsibilities: list from "Key Responsibilities:" bullet points. Let's extract each:
- Serve as the primary point of contact throughout the project and delivery lifecycle.
- Conduct discovery sessions, workshops, and interviews to elicit, document, and validate business and technical requirements.
- Translate complex client needs into clear functional specifications, user stories, and acceptance criteria for the development team.
- Manage client expectations proactively by communicating scope, timelines, constraints, and trade-offs with transparency.
- Work closely with developers, architects, and QA engineers to ensure requirements are well-understood and technically feasible.
- Participate in sprint planning, backlog grooming, and stand-ups; represent the voice of the client within Agile ceremonies.
- Identify and flag scope creep, technical blockers, and dependency risks early; propose solutions in collaboration with the dev team.
- Assist in configuring E2M2M® platform modules (e.g., Low-Code Form Builder, Workflow Builder, Dashboard Builder) to meet client specifications.
- Develop and execute test plans, test cases, and UAT (User Acceptance Testing) scripts aligned to client requirements.
- Coordinate and facilitate UAT sessions with client stakeholders, capturing feedback and driving resolution of issues.
- Validate that delivered functionality matches documented requirements before client sign-off.
- Maintain defect logs and track issues through to closure with the QA and development teams.
- Coordinate release readiness activities including client communications, training materials, and go-live checklists.
- Support deployment activities and monitor post-release stability in collaboration with the dev and support teams.
- Document release notes, configuration guides, and end-user documentation as needed.
- Conduct post release reviews with clients to confirm delivery success and capture lessons learned.
We'll put each as
- .
Qualifications (Required Qualifications):
- 5+ years of experience in a Business Analyst, Technical BA, or Product Analyst role within a SaaS, enterprise software, or technology services environment.
- Proven ability to manage client relationships and translate business needs into actionable technical requirements.
- Experience working within Agile/Scrum delivery frameworks.
- Proficiency in writing user stories, BRDs, process flows, and functional specifications and SQL.
- Understanding of API integrations and cloud-based data structures is a plus.
- Hands-on experience with UAT coordination and test case development.
- Comfortable working with APIs, data workflows, and configurable software platforms (low-code/no-code experience a plus).
- Strong working knowledge of tools such as Jira, Confluence, Figma, Postman, or similar.
- Exceptional ability to explain technical constraints to non technical clients and business goals and technical requirements to
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include only sections when posting has real specific content. Must preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience" etc. Also must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Benefits, Wage Data (salary range), Work Environment/Physical Demands, Travel, etc. Pay: salary range given $80,000 - $120,000. So we can include Pay section with that. Schedule: not explicitly given; maybe work environment mentions schedule? Not explicit schedule like hours. There's mention of ability to sit/stand up to 8 hours per day, but not schedule. There's mention of morning/evening syncs with offshore teams, but not a set schedule. Probably we should not create Schedule section unless posting actually states them. It does not give specific schedule like "Full-time, 40 hrs/week". So omit Schedule. Benefits: they list health, dental, vision, life insurance, 401(k) with employer match, paid time off. So include Benefits. Pay: include salary range. About the role: we have overview paragraph about role. Could be "About the role". Use that heading. Responsibilities: there is a "Key Responsibilities:" section with bullet points (though formatting weird). We'll extract responsibilities. Qualifications: there is "Required Qualifications" and "Preferred". We'll combine maybe into Qualifications and Skills? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide where to put requirements vs qualifications vs skills. The posting has "Required Qualifications" and "Preferred". Also mentions skills like proficiency in writing user stories, SQL, understanding of API integrations, hands-on experience with UAT, comfortable with APIs, data workflows, configurable software platforms, strong working knowledge of tools such as Jira, Confluence, Figma, Postman, etc. Also ability to explain technical constraints, manage schedule, excellent communication. Those could go under Skills. Qualifications could be the years of experience, proven ability, Agile experience, etc. Requirements maybe similar to qualifications? But we need to follow instruction: include sections only when posting has real specific content. We can have Qualifications and Skills separate. Requirements maybe not needed if content overlaps. But we could put "Requirements" for the required qualifications (5+ years experience, proven ability, Agile, etc.) and "Skills" for technical skills (user stories, SQL, API, tools). However the posting lumps them together. We need to preserve all substantive info; we can split but must not lose info. Let's decide: - About the role: overview paragraph. - Responsibilities: list of responsibilities. - Qualifications: required qualifications (5+ years experience, proven ability to manage client relationships, Agile/Scrum, etc.) - Skills: specific technical skills (writing user stories, BRDs, process flows, functional specifications, SQL; understanding of API integrations and cloud-based data structures; hands-on experience with UAT coordination and test case development; comfortable working with APIs, data workflows, configurable software platforms (low-code/no-code a plus); strong working knowledge of tools such as Jira, Confluence, Figma, Postman, or similar; ability to explain technical constraints to non-technical clients and business goals and technical requirements to developers; ability to manage schedule for morning/evening syncs; excellent communication and stakeholder management.) - Benefits: list. - Pay: salary range. We should not include Requirements section if we already have Qualifications and Skills. But the instruction list includes Requirements as possible heading; we can omit if not needed. However we must ensure we don't lose any content that would be considered "Requirements". The required qualifications are essentially requirements. So we could put them under Qualifications. That's fine. We must not include filler like "commensurate with skill, education, experience, and working environment." That's in Pay section? Actually they wrote: "The starting salary will be commensurate with skill, education, experience, and working environment." That's filler; we should avoid including that phrase if possible. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have actual salary range; we can include that. But we should avoid including the commensurate phrase as it's filler. So in Pay section we can just put the salary range: $80,000 - $120,000. Possibly also mention that it's the salary range for this position. That's substantive. We must remove boilerplate: EEO, Drug Free Workplace, Solicitation, etc. Also remove "Work Environment/Physical Demands", "Travel", "Local Candidates only Yes", etc. Those are not required headings but could be considered extra info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep substantive info like travel percentage, work environment, physical demands, local candidates, drug free workplace, etc. However those are not under the allowed headings list. But we could incorporate them into existing sections like About the role or maybe a separate section like "Additional Information". However the instruction says use headings only from the list; we should not create other headings. But we can embed that info in paragraphs under existing sections if appropriate. For example, travel percentage could go under Responsibilities? Not really. Could go under About the role as part of overview. Physical demands could go under About the role as well. The instruction: "Prefer a few substantive sections over many thin ones." So we could add a section like "Work Environment" but that's not in the allowed list. The allowed list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit all substantive info into those sections. We can add paragraphs under About the role covering work environment, travel, physical demands, local candidates, drug free workplace, etc. That would preserve info. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove EEO statement, drug free workplace? Actually drug free workplace is not EEO; it's a policy. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Drug free workplace might be considered legal boilerplate; but it's substantive? It's a condition of employment. Might be considered boilerplate but maybe we should keep? The instruction says remove ... boilerplate. It's ambiguous. I'd err on side of removing drug free workplace statement as it's likely boilerplate. Similarly "Solicitation Please no solicitation..." is boilerplate. Remove. Local Candidates only Yes: that's substantive about eligibility; we could keep. Travel 25-35%: substantive. Work environment/Physical Demands: substantive. We'll embed those in About the role. Now craft HTML. Structure:
About the role
... overview plus work environment, travel, physical demands, local candidates.
Responsibilities
- ... each responsibility.
Qualifications
- ... required qualifications.
Skills
- ... skills.
Benefits
- ... benefits.
Pay
Salary range: $80,000 - $120,000.
We must not include Schedule section. Now extract content. About the role overview: "Overview We are looking for a Technical Business Analyst with 5+ years of experience to serve as the critical bridge between our enterprise clients and our internal development team. The Analyst will own the full lifecycle of client-facing feature delivery, from gathering and translating requirements through to testing, release, and post-deployment validation ensuring that client expectations are met with precision and on schedule. You will also work closely with offshore teams, requiring flexibility and strong communication practices to collaborate effectively across multiple time zones. Comfort with early morning or evening overlap windows, asynchronous workflows, and distributed team dynamics is essential to thriving in this role." Add work environment: "Work Environment This job operates in a professional office environment and uses standard office equipment such as computers and phones." Physical demands: "Ability to sit/stand for up to 8 hours per day. Ability to move freely for up to 8 hours per day." Travel: "This role requires 25 - 35% travel to client sites, project locations, and occasional internal team meetings." Local Candidates only Yes: maybe phrase "Local candidates only." We'll include. Combine into a paragraph or multiple paragraphs? Usefor prose. Could have multiple
tags under the heading. That's fine. Responsibilities: list from "Key Responsibilities:" bullet points. Let's extract each: - Serve as the primary point of contact throughout the project and delivery lifecycle. - Conduct discovery sessions, workshops, and interviews to elicit, document, and validate business and technical requirements. - Translate complex client needs into clear functional specifications, user stories, and acceptance criteria for the development team. - Manage client expectations proactively by communicating scope, timelines, constraints, and trade-offs with transparency. - Work closely with developers, architects, and QA engineers to ensure requirements are well-understood and technically feasible. - Participate in sprint planning, backlog grooming, and stand-ups; represent the voice of the client within Agile ceremonies. - Identify and flag scope creep, technical blockers, and dependency risks early; propose solutions in collaboration with the dev team. - Assist in configuring E2M2M® platform modules (e.g., Low-Code Form Builder, Workflow Builder, Dashboard Builder) to meet client specifications. - Develop and execute test plans, test cases, and UAT (User Acceptance Testing) scripts aligned to client requirements. - Coordinate and facilitate UAT sessions with client stakeholders, capturing feedback and driving resolution of issues. - Validate that delivered functionality matches documented requirements before client sign-off. - Maintain defect logs and track issues through to closure with the QA and development teams. - Coordinate release readiness activities including client communications, training materials, and go-live checklists. - Support deployment activities and monitor post-release stability in collaboration with the dev and support teams. - Document release notes, configuration guides, and end-user documentation as needed. - Conduct post release reviews with clients to confirm delivery success and capture lessons learned. We'll put each as