Salesforce India-Style Machine Coding Round: Format, Tips & Practice Problems
Written and reviewed by Sahil Srivastav
CRM systems are rule-heavy: records have owners, teams have scopes, and automation must not fire twice. Rounds in the style of Salesforce India use those rules to grade a small, explainable service.
The practice content is original to Gronex and focuses on business invariants.
What a Salesforce India-style machine coding round looks like
Expect a record, assignment, or notification workflow with roles and a few automation rules. Deliver a runnable core and demonstrate both allowed and rejected actions.
The follow-up adds a tenant, ownership transfer, or repeated event. Make tenant and permission context explicit in every command.
Keep automation observable and idempotent; a huge rules engine is unnecessary in the time box.
How you’re evaluated
Tenant isolation
A record from one organisation cannot leak into another.
Permission correctness
Owner, role, and scope determine each action.
Idempotent automation
Repeated events do not send or apply the same effect twice.
Auditable changes
Important mutations leave a useful history.
Common mistakes that fail this round
- Treating tenant id as display metadata.
- Trusting caller-supplied ownership.
- Firing notifications before the state change is durable.
- Duplicating permission checks across handlers.
- Omitting audit events for administrative actions.
Quick tips for the room
- Pass tenant context explicitly.
- Centralise policy checks.
- Record event ids.
- Keep automation after the core mutation.
How to prepare
Build a tenant-scoped record service with one automation rule and an audit trail.
Practise the linked repositories as focused exercises in RBAC, notifications, and event replay.
Practice problems in the Salesforce India-style round format
Each is a real backend repository with a failing test suite — the same working-code standard the round applies. Open the brief and read the full problem, no signup required.
Multi-Tenant Configuration & Isolation
Tenant-scoped configuration without cross-tenant leakage.
Open the challenge →Notification Preference & Delivery
Idempotent, preference-aware delivery. Free to try.
Open the challenge →FAQ
Were these Salesforce India questions?
No. They are Gronex originals in the style of CRM rounds. Gronex is not affiliated with Salesforce.
Is multi-tenancy always required?
Only when the statement includes it; if present, treat isolation as a core invariant.
How should automation be tested?
Run the same event twice and assert one effect with a recorded event identity.
Should I build a rules DSL?
Use small policies first and discuss a DSL only if the stated extensions justify it.
Related
Gronex is not affiliated with, endorsed by, or sponsored by Salesforce India. All company names and trademarks belong to their respective owners. The problems on this page are Gronex originals written in the style of such interview rounds — not actual interview questions from Salesforce India.