About the role

We are looking for a Business Analyst to assess existing reporting and define a future-state reporting strategy and governance model across a broad stakeholder community.

The mandatory requirements are 4+ years of business analysis and requirements management experience, stakeholder interviews and requirements workshops, experience rationalizing a reporting portfolio, and an upper-intermediate English level.

Must haves

  • Strong business analysis and requirements-management experience of at least 4 years.
  • Demonstrated ability to conduct stakeholder interviews and facilitate requirements workshops.
  • Experience assessing and rationalizing an existing reporting or analytics portfolio.
  • Strong ability to translate complex business needs into structured business and functional requirements.
  • Experience developing process maps, requirements documentation, reporting inventories, and roadmaps.
  • Strong analytical skills with an ability to identify duplication, gaps, inconsistencies, and opportunities for simplification.
  • Ability to operate across business, technology, data, and risk stakeholders.
  • Excellent written and verbal communication skills, including the ability to communicate effectively with senior stakeholders.
  • Strong organizational skills and the ability to drive requirements through ambiguity and competing stakeholder priorities.
  • Upper-intermediate English level.

Nice to haves

  • Experience with management reporting, operational risk, technology risk, cybersecurity, vulnerability management, or other data-intensive operational environments.
  • Experience with BI and other reporting platforms and familiarity with data governance concepts.
  • Understanding of metric definitions, controls, data quality, lineage, and reporting governance.
  • Experience establishing sustainable reporting operating models rather than solely delivering individual reports.

What you will do

1. Current-State Reporting Assessment

  • Develop a comprehensive inventory of existing reports, dashboards, metrics, and related reporting artifacts.
  • Research historical reporting and prior requirements to understand the original business need, intended audience, and use cases.
  • Assess existing reporting for relevance, duplication, usability, consistency, and continued business value.
  • Identify reporting gaps as well as reports that may no longer serve a meaningful business purpose.
  • Develop recommendations to retain, enhance, consolidate, replace, or decommission existing reporting.

2. Stakeholder Engagement & Requirements Gathering

  • Identify the stakeholder groups and personas that consume, produce, or rely upon reporting.
  • Conduct structured interviews and working sessions to understand business objectives, reporting needs, pain points, decision-making requirements, and desired outcomes.
  • Translate stakeholder needs into well-defined business and functional requirements.
  • Reconcile competing or overlapping requirements across stakeholder groups and establish a consolidated view of reporting demand.
  • Maintain traceability between business needs, requirements, reports, metrics, and intended outcomes.

3. Future-State Reporting Strategy

  • Develop a target-state reporting portfolio based on stakeholder requirements and current-state findings.
  • Define which reports should be created to address unmet business needs.
  • Define which reports should be enhanced where existing reporting partially meets requirements.
  • Define which reports should be consolidated where multiple reports address similar requirements.
  • Define which reports should be retained where reporting remains effective and relevant.
  • Define which reports should be decommissioned where reporting is obsolete, duplicative, or no longer creates sufficient value.
  • Prioritize requirements based on business value, risk, stakeholder need, dependencies, and implementation considerations.
  • Develop a roadmap that sequences reporting changes and enables an orderly transition from the current to future state.

4. Reporting Governance & Lifecycle Management

  • Establish clear ownership and accountability for reports, metrics, data sources, and business requirements.
  • Define standards for requirements documentation, report definitions, business logic, data lineage and supporting metadata, where applicable.
  • Establish a sustainable process for managing changes to reports and reporting requirements.
  • Define periodic review cycles to reassess usage, relevance, accuracy, stakeholder needs, and opportunities for improvement.
  • Establish criteria and governance for report retirement so that the reporting portfolio does not continually grow without rationalization.
  • Maintain a reporting catalog that provides transparency into available reporting, ownership, purpose, audience, and status.

5. Continuous Improvement

  • Regularly engage stakeholders to determine whether reporting continues to support business and management decision-making.
  • Identify opportunities to improve reporting quality, usability, consistency, and efficiency.
  • Monitor changing business requirements and translate them into appropriate enhancements to the reporting portfolio.
  • Encourage movement away from redundant or manually intensive reporting toward standardized, sustainable solutions.
  • Use stakeholder feedback and reporting usage information, where available, to inform periodic portfolio reviews.

Perks

  • Growth without limits: build your skills through mentorship, internal TechTalks, challenging projects, and a dedicated annual learning budget
  • Competitive compensation: get recognition that reflects your skills and impact, with regular performance and compensation reviews
  • Flexibility: work 100% remotely with flexible hours that support focus, autonomy, and a healthy work rhythm
  • Meaningful, modern projects: build impactful products using modern technologies alongside global teams and leading brands
  • Collaborative culture: join a supportive environment with zero micromanagement where ideas are welcomed and contributions are recognized
  • Well-being & support: access local well-being programs and people-focused support tailored to your location

Didn’t find the perfect fit?

Subscribe to get notified about new roles that match your skills and interests.

Get role alerts

Hiring process timeline

We designed our hiring process to be fast, transparent, and convenient — so you always know what to expect and can move through the steps without unnecessary delays.

lightning-iconA quick note

After applying, keep an eye on your inbox — including your spam folder. Occasionally, emails from our hiring platform, LaunchPod, may land there.

1

Tell us about yourself

Submit a short application form.

2

Pass a quick test

Pass a 30’- 60’ test.

3

Record a short video

Introduce yourself on video to fast-track your application process.

4

Meet our team

Once you pass the video review, grab a spot on our calendar for a technical interview.

5

Get an offer

Welcome to AgileEngine!

FAQ

Have any questions?

What is the work format and schedule?

We are a remote-first company, so all our positions are remote. Schedules are flexible, but the main requirement is to have an overlap with your client’s schedule to ensure smooth collaboration. Specific details depend on the project and are discussed during the interview process.

What level of English is required?

We look for Upper-Intermediate (B2) proficiency or higher. Since you will be collaborating with international teams and global clients (including Fortune 500 companies), English is a part of your daily work.

Does AgileEngine provide work equipment?

It depends on your location. We provide equipment in Ukraine, Poland, Argentina, Colombia, Mexico, Brazil, Guatemala, Portugal, Spain, and India. In the USA, equipment is usually provided by the client; otherwise, you will be expected to use your own setup.

What opportunities for professional growth do you offer?

We support continuous growth through personalized development paths tailored to each expert. Also, you can expect:

  • An annual learning and development budget
  • Internal workshops, tech talks, and mentorship programs
  • Opportunities to switch projects or grow into new roles over time

What does a typical team look like, and what tools do you use?

Teams vary by project, but you’ll usually work with a mix of experts across different fields, along with a delivery or project manager who supports collaboration and onboarding.

For day-to-day work, teams commonly use tools like Jira and Google Workspace, along with communication platforms such as Google Chat. Depending on the client, you may also work with Slack, Confluence, Notion, or similar tools.

Need help?

Want more details? See full FAQ

If something doesn’t work or you have questions regarding your application process, drop us a line.

    Scroll to Top