Salesforce SMTS Frontend Interview Experience

Overview

This article details the Salesforce Senior Member of Technical Staff (SMTS) frontend interview experience. The candidate applied directly through the Salesforce Career Site and received a recruiter callback within 3-4 days. The complete interview process consisted of six rounds, each designed to assess different aspects of frontend engineering expertise, from algorithmic problem-solving to system design and cultural fit.

Interview Process

The Salesforce SMTS interview process comprised six distinct rounds:

1. Online HackerRank Assessment (60 minutes)
2. Hiring Manager Round (45 minutes)
3. JavaScript, HTML, CSS & React Fundamentals (60 minutes)
4. System Design — Google Maps (60 minutes)
5. System Design — WhatsApp Web (60 minutes)
6. Culture Fit & Collaboration (60 minutes)

Technical Rounds

Round 1: HackerRank Assessment

The initial screening round consisted of two algorithmic problems. The first problem involved graph traversal or graph properties, testing understanding of algorithms like BFS, DFS, or connected components. The second problem required dynamic programming on strings, similar to longest common subsequence or edit distance problems.

Round 2: Hiring Manager Round

This 45-minute round combined behavioural discussion with technical depth. The manager discussed the candidate's current work, tech stack, and team dynamics. Technical questions included:

Performance Fundamentals:

• What is FPS (Frames Per Second) and why is it important?
• What type of animations should be avoided and why?

The candidate was expected to discuss avoiding properties that trigger layout/reflow (width, height, top, left), preferring GPU-accelerated properties like transform and opacity, and understanding the rendering pipeline: Layout → Paint → Composite.

Mini System Design:

• Design a "Send message" functionality for Slack

Canvas Performance:

• What is Canvas and why is it better for performance?

Key discussion points included Canvas rendering pixels directly without DOM overhead, suitability for complex visualisations and games, and trade-offs regarding accessibility.

Round 3: JavaScript, HTML, CSS & React Fundamentals

This comprehensive 60-minute round covered the entire frontend stack.

HTML & CSS Questions:

1. What is semantic HTML? Why use it instead of divs everywhere?