smallcase powers investing products used across broker platforms, so its engineering interviews emphasize system design for market-data and order-flow systems that must stay correct during volatile trading hours.
Expect questions on handling bursty read traffic, integrating with multiple broker APIs, and keeping portfolios consistent across rebalances. The loop typically runs 4 to 5 rounds; interviewers want you to reason about scale, consistency, and third-party API failure rather than reciting patterns. SDE total pay varies widely by level, commonly in roughly the 15 to 35 LPA band including ESOPs, with senior roles higher.
About smallcase
smallcase is a Bengaluru investment platform that lets retail investors buy and manage thematic stock and ETF baskets. It integrates with all major Indian brokers via APIs.
Recruiter screen: background, motivation, and salary expectations (30 min)
Coding round: 1 to 2 medium-hard DSA problems
Technical round: DSA plus code quality and design fundamentals
System design round: market-data or order-flow architecture at scale
Hiring manager and culture round: ownership, fit, and compensation discussion
Coding Round (60 min)
1 to 2 medium-hard DSA problems as a filter.
Technical Round (60 min)
A harder problem plus discussion of code quality, edge cases, and backend fundamentals.
System Design Round (60 min)
Design a market-data or order-flow system. Follow-ups cover bursty read scaling, multi-broker API integration, idempotent orders, and consistency across portfolio rebalances. Name your caches, TTLs, and degradation strategy.
Hiring Manager / Culture Round (45 min)
Past ownership stories, team fit, and a compensation and level discussion.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe typical smallcase recruitment process has 5 stages: Recruiter screen: background, motivation, and salary expectations (30 min) → Coding round: 1 to 2 medium-hard DSA problems → Technical round: DSA plus code quality and design fundamentals → System design round: market-data or order-flow architecture at scale → Hiring manager and culture round: ownership, fit, and compensation discussion.
smallcase typically conducts 4 interview rounds: Coding Round (60 min): 1 to 2 medium-hard DSA problems as a filter.; Technical Round (60 min): A harder problem plus discussion of code quality, edge cases, and backend fundamentals.; System Design Round (60 min): Design a market-data or order-flow system. Follow-ups cover bursty read scaling, multi-broker API integration, idempotent orders, and consistency across portfolio rebalances. Name your caches, TTLs, and degradation strategy.; Hiring Manager / Culture Round (45 min): Past ownership stories, team fit, and a compensation and level discussion..
HireStepX recommends the Market-scale design framework for this type of interview: Clarify read vs write load, then broker-API integration and idempotency, then consistency across rebalances, then caching and graceful degradation.
To answer this question well, HireStepX recommends the Market-scale design approach: Clarify read vs write load, then broker-API integration and idempotency, then consistency across rebalances, then caching and graceful degradation. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Market-scale design approach: Clarify read vs write load, then broker-API integration and idempotency, then consistency across rebalances, then caching and graceful degradation. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Market-scale design approach: Clarify read vs write load, then broker-API integration and idempotency, then consistency across rebalances, then caching and graceful degradation. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Market-scale design approach: Clarify read vs write load, then broker-API integration and idempotency, then consistency across rebalances, then caching and graceful degradation. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Market-scale design approach: Clarify read vs write load, then broker-API integration and idempotency, then consistency across rebalances, then caching and graceful degradation. Ground your answer in a specific real example from your own experience.