/Practice

The principal interview reels

The principal interview1 / 3
1 / 4

Context first

Before naming a technology, state the context: data per user, how long users stay offline, whether data is shared, the team’s skills and the deadline. The right answer depends on these, and saying so is itself the signal.

2 / 4

Options and criteria

Name at least two real options and the criteria you weighed: reliability, time to market, cost, team fit and how reversible the choice is. Interviewers want to see the comparison, not just the winner.

3 / 4

Decision and cost

Say what you chose and what you accepted as its cost, such as a concurrent settings change occasionally being overwritten. Then say which signal would make you revisit it, and that you recorded it as an architecture decision record.

Interview answer

Say it in the interview

I frame each decision with the context, at least two options, explicit criteria and the cost I accepted, then name the signal that would make me revisit it. Write each as an architecture decision record, so the reasoning outlives the meeting.

How principals talk about decisions
#interview
The principal interview2 / 3
1 / 4

Real question

Background sync is native work in every option, so the choice is really about the UI layer and how much logic you want to share. Framed that way, the trade-offs become clear.

2 / 4

When each wins

Native Kotlin and Swift suit media-heavy, regulated or platform-heavy apps. React Native suits content and form-driven apps built by a strong JavaScript team that needs speed. A Kotlin Multiplatform or Rust core with native UI suits large organisations with complex sync on both platforms.

3 / 4

Build or buy sync

PowerSync and ElectricSQL give Postgres-to-SQLite sync quickly. Firestore is fast to start but harder at scale. Build your own when sync is core to the product or compliance demands it; for a small product, buy.

Interview answer

Say it in the interview

Background sync is native in every option, so the real choice is the UI layer. I pick native for media-heavy or regulated apps, React Native for form-driven apps with a strong JavaScript team, and a shared Kotlin Multiplatform core for complex sync on both platforms.

Native, React Native or a shared core?
#interview
The principal interview3 / 3
1 / 4

Pick a real failure

Panels trust a story about something that broke more than a list of things that worked. Choose an incident you were close to: a retry storm, a failed migration or a gap in synced data.

2 / 4

Four beats

What users saw. What you found. What you changed, in code and in process. What the numbers looked like afterwards. Keep blame out of it and keep yourself in it.

3 / 4

An example

After an outage, every device retried at once and the API hit several times its normal load. We added full-jitter backoff, 429 with Retry-After, staggered push fan-out and a remote kill switch. The next outage recovered without a spike.

In practiceNo incident of your own? Describe a failure test you ran instead. Never invent one.
Interview answer

Say it in the interview

When we had a retry storm, I said what users saw, how we traced it to synchronised retries, the four changes we made, and that the next outage recovered without a spike. Four beats, numbers at the end, no blame, and my own role clear.

Telling an incident story
#interview