Atlassian Business Analyst Interview Guide

Listen to understand underlying needs and constraints, facilitate discussion to find common ground, prioritize based on business value/urgency, escalate to decision-makers with data, document trade-offs. Show diplomatic negotiation skills and focus on business outcomes over individual preferences.

Functional describes what system should do (user logs in, generates report). Non-functional describes how system should perform (response time < 2 seconds, 99.9% uptime, security standards). Discuss testing approaches for each and why non-functional requirements are often overlooked.

Use "As a [role], I want [feature], so that [benefit]" format. Good acceptance criteria are specific, measurable, achievable, relevant, and testable (SMART). Include edge cases, error scenarios, and success metrics. Discuss INVEST principles for user stories.

Use STAR method. Show impact assessment (scope, timeline, cost), stakeholder communication, updating documentation, managing expectations, and ensuring team alignment. Discuss change control process and balancing flexibility with project stability.

Validate through prototypes/mockups, user acceptance testing, stakeholder reviews, traceability to business goals, and pilot programs. Discuss root cause analysis to ensure solving right problem. Cover measuring success metrics post-implementation.

Document current state (as-is process map), identify pain points through data and stakeholder feedback, analyze bottlenecks and waste, design future state (to-be process), calculate ROI, create implementation plan. Use frameworks like Lean, Six Sigma, or value stream mapping.

Discuss BPMN (Business Process Model and Notation) or flowcharts. Identify start/end points, activities, decision points, actors, and systems involved. Cover swim lanes for different departments/roles. Show understanding of different diagram types (high-level vs detailed, as-is vs to-be).

Document current state capabilities, define desired future state based on requirements, identify gaps in people/process/technology, prioritize gaps by impact and effort, develop action plan. Discuss root cause analysis and linking gaps to business objectives.

Define KPIs upfront - cycle time, error rate, cost per transaction, customer satisfaction, employee productivity. Establish baseline before changes, track during implementation, compare post-implementation. Discuss leading vs lagging indicators and balanced scorecard approach.

Analyze process maps, review data (wait times, queue lengths), conduct time studies, gather feedback from process participants. Use tools like value stream mapping, fishbone diagrams, Pareto analysis. Discuss Theory of Constraints and focusing on biggest bottleneck first.

Define business question, identify data sources, clean and validate data, perform exploratory analysis, apply statistical methods, visualize findings, derive insights, make recommendations. Discuss tools (Excel, SQL, Tableau) and ensuring data quality.

Understand executive information needs and decision-making, use clear hierarchy with KPIs prominent, provide context with trends and benchmarks, minimal clutter, interactive drill-downs, automated data refresh. Discuss design principles (minimal ink-to-data ratio, pre-attentive attributes).

Validate data sources, check for duplicates and nulls, cross-reference with known figures, use data profiling, document assumptions, implement data quality rules, reconcile across systems. Discuss impact of bad data on decisions and building trust in analysis.

Correlation shows association between variables, causation means one causes the other. Establish causality through controlled experiments, A/B testing, regression with controls, time-lagged analysis, or natural experiments. Give examples of spurious correlations.

Break down high-level requirements into detailed functional specs, create wireframes/mockups for UI, define data models, specify business rules, document integration points, provide use cases and user flows. Discuss collaboration with architects/developers and technical feasibility assessment.

Understand data flows between systems, map data fields, define integration architecture (API, ETL, messaging), address data transformation needs, handle error scenarios, ensure data consistency. Discuss real-time vs batch, and involving IT teams early.

Use case describes system behavior from user perspective. Include actor (bank customer), preconditions (valid card, sufficient funds), main flow (steps), alternative flows (insufficient funds, wrong PIN), postconditions (balance updated). Discuss when to use use cases vs user stories.

Create decision matrix with criteria (cost, timeline, technical feasibility, scalability, user experience, risk), score each option, involve stakeholders in weighting criteria, perform cost-benefit analysis, consider implementation complexity. Document rationale for recommendation.

BA facilitates refinement sessions, writes user stories with acceptance criteria, clarifies requirements during sprint, validates deliverables, gathers feedback. Discuss difference from traditional waterfall BA role, working in sprints, and continuous collaboration with team.

Document clear baseline scope, implement change control process, assess impact of changes (time, cost, quality), communicate trade-offs to stakeholders, prioritize changes, maintain requirements traceability. Show understanding of balancing flexibility with control.

Identify risks through brainstorming and lessons learned, assess probability and impact, prioritize with risk matrix, develop mitigation strategies, assign owners, monitor regularly. Discuss types of risks (technical, resource, dependency, business) and contingency planning.

Identify all costs (development, implementation, training, maintenance), quantify benefits (revenue increase, cost savings, efficiency gains), calculate ROI or NPV, consider timeframe and payback period, account for intangibles. Present with sensitivity analysis for assumptions.

Waterfall is sequential (requirements → design → build → test), Agile is iterative with incremental delivery. Use Waterfall for stable requirements, regulatory environments, fixed scope. Use Agile for evolving requirements, rapid delivery, user feedback loops. Discuss hybrid approaches.

Mention certifications (CBAP, PMI-PBA), professional organizations (IIBA), conferences, online courses, reading (BA Times, PM blogs), networking with peers, applying new techniques on projects. Show commitment to continuous learning.

Use STAR method with quantified impact. Show how you uncovered hidden issue through data analysis or requirements validation, presented findings with evidence, influenced stakeholders, and achieved measurable result. Demonstrate business acumen and value-add of BA role.

Analyze picking/packing process flow, identify bottlenecks using data (cycle time, error rates), benchmark against best practices, recommend automation opportunities, design improved workflow. Discuss Amazon's customer obsession and operational excellence principles.

Research seller pain points, conduct stakeholder interviews, define user stories with acceptance criteria, prioritize by impact, create mockups for key flows, specify integration with existing systems. Show understanding of two-sided marketplace dynamics.

Interview diverse user personas (remote workers, hybrid teams, enterprise admins), understand current workflow and pain points, analyze competitor features, create user stories, define success metrics. Discuss accessibility and enterprise security requirements.

Review metrics (CTR, conversion rate, CPC, Quality Score), segment by campaign/keyword/geography, identify underperforming areas, recommend bid adjustments, ad copy tests, keyword optimization. Discuss attribution and measurement challenges at Google scale.

Show comfort with transparency and direct communication. Explain how the feedback improved outcomes and your growth mindset in receiving critique.

Demonstrate genuine customer empathy. Show how you gathered customer insights, championed their needs internally, and the positive impact on the product or service.

Atlassian genuinely values sustainable work. Share how you set boundaries, prioritised effectively, and delivered great results without burnout.

Emphasise your contribution to team dynamics — how you facilitated collaboration, resolved conflicts, or helped teammates succeed alongside your own work.

Show proactive leadership. Explain the gap you identified, how you built support, and the tangible improvement. Atlassian values action over committees.

Discuss user research methods, empathy mapping, or how you use data to understand user needs. Show genuine curiosity about the people using your work.

Show you can disagree constructively and commit. Explain your reasoning, how you communicated it, and how you supported the final decision either way.

Be genuine and specific. Reference products you've used, features you admire, or the mission of unleashing the potential of every team. Generic enthusiasm won't land.

Atlassian's Team Anywhere policy is core to their identity. Share specific practices for async communication, documentation, and building trust across time zones.

Show creative problem-solving and willingness to experiment. Atlassian's ShipIt culture values novel approaches and learning from experiments.