Ctrl K
Frontend · Senior · System design

Leadership is proposing to split a large frontend into micro-frontends so that teams can release independently. How would you go about making this decision, and how would you design it?

~10 min by voice

How to approach it

The interviewer is checking the maturity of your architectural thinking: whether you first find the real problem and compare micro-frontends with cheaper options, and, if the decision is made, whether you can design it so that team independence doesn't turn into a distributed monolith and a degraded UX.

Have you seen this question in a real interview?
Answers0
Avg. score—
Strong—
Practiced0
Topics
Similar questionsHow do you organize CSS in a large application that several teams work on? What approaches have you tried, and what have you abandoned? SeniorРасскажите о значимом архитектурном решении, которое вы принимали или продвигали. Как вы к нему пришли и как оно себя показало? SeniorYou have a Spring Boot monolith that a team of thirty people has been developing for five years, and it's started slowing development down. How would you decide whether to split it into services or modularize it internally, and how would you carry out the changes? Senior

Answer by voice

The interviewer will ask this question and listen. Think out loud and ask for a hint if you need one. When you're done, pause or tap “That's my answer”. In about a minute, your score and the points you covered show up here.

Sign in to answer

Best with headphones · ~10 min