Business System Analyst

Not available for C2C engagements

Vendors marketing candidate will be blocked

Must be eligible for hire without work authorization sponsorship

Must Have:

Sitecore

Google Workspace

Jira

Description:

Analyze science, engineering, business and all other data processing problems for application to electronic data processing systems. A typical business systems analyst is responsible for analyzing user requirements, procedures and problems to automate or improve existing systems and review computer system capabilities, workflow and scheduling limitations.

-Gathers requirements from business units and translates those to programmers and developers.

-Prepares cost-benefit and return-on-investment analyses to aid in decisions on system implementation.

-Confers with clients regarding the nature of the information processing or computation needs.

-Coordinates and links the computer systems within an organization to increase compatibility and so information can be shared.

Skills/Experience:

-Verbal and written communication skills, problem solving skills, attention to detail and interpersonal skills.

-Basic ability to work independently and manage one’s time.

-Basic knowledge of design techniques and principles involved in production of drawings and models.

-Basic knowledge of computer software, such as Visual Basic, Java, SQL, etc.

Bachelor's degree in a technical field such as computer science, computer engineering or related field required. MBA or other related advanced degree preferred.

Additional Role Requirements

-Seeking a Business Analyst with both functional and technical expertise who can effectively partner with the Product Manager and business stakeholders.

-Responsible for facilitating requirements gathering sessions and documenting detailed functional requirements.

-Create, maintain, and update Business Requirements Documents (BRDs) for assigned features and initiatives.

-Partner closely with the Product Owner and development team to translate requirements into user stories and define clear acceptance criteria.

-Must be comfortable discussing and documenting both functional and non-functional requirements, including technical dependencies, integrations, performance considerations, and system impacts.

-Ability to independently drive requirement clarification, identify gaps, and proactively follow up with stakeholders to obtain needed information.

-Strong meeting facilitation skills with the ability to schedule and lead discussions with business partners, technical teams, and product leadership.

-Must be self-motivated and capable of working independently while managing multiple priorities in a fast-paced environment.

-Experience serving as the liaison between business and technical teams to ensure requirements are clearly understood and successfully delivered.