← Notion Interview Insights

Notion·Software Engineer·Onsite - Cross-functional / Panel·Senior

Senior
Apr 2026

Summary

A 30-minute cross-functional screen at Notion for a Data Engineer role, basically just one big collaboration question stretched across the whole call. Pretty focused, almost weirdly so.

Questions Asked (1)

Q1

Walk me through a project where you worked closely with a Data Science partner. How did you split responsibilities, keep communication going, and handle disagreements? What came out of it, and what would you change about how you two worked together if you did it again?

Cross-functional AlignmentConflict ResolutionStakeholder Management
Author's notes

This was basically the entire interview.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a project where you collaborated with a Data Science partner, and structure your answer using the STAR method. Focus on how you divided responsibilities based on strengths, maintained communication through regular syncs and shared tools, and resolved disagreements with data-driven discussions. Conclude with the project's impact and a specific lesson you'd apply next time.

Pro tip: Emphasize how you adapted your communication style to bridge the gap between engineering and data science—for example, by translating technical constraints into business terms or using shared metrics to align on goals. This shows you can collaborate effectively with diverse stakeholders.

1. Set the Context

Briefly describe the project, its goals, and why you needed a Data Science partner. Highlight the cross-functional nature and the expected impact.

2. Divide Responsibilities

Explain how you split work based on expertise: e.g., you handled engineering implementation, while your partner focused on model development and analysis. Mention any shared ownership areas.

3. Maintain Communication

Describe the communication cadence and tools you used (e.g., daily stand-ups, Slack, shared docs). Explain how you ensured alignment and addressed blockers quickly.

4. Resolve Disagreements

Provide a specific example of a disagreement, how you listened to each other's perspectives, and how you reached a resolution—ideally using data or experimentation.

5. Reflect on Outcomes and Improvements

Summarize the project's results and what you learned. Suggest one or two concrete changes you'd make to improve collaboration next time, such as earlier involvement or clearer success metrics.

Key Points to Mention

  • Clear role definition based on strengths (e.g., engineering vs. modeling)
  • Regular syncs and shared documentation to maintain alignment
  • Use of data or experiments to resolve disagreements objectively
  • Project impact (e.g., improved model accuracy, faster deployment, user growth)
  • A specific lesson learned and how you'd apply it to future collaborations
  • Adaptability in communication styles to bridge technical and non-technical gaps

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.