Salesforce developer interview prep

Master SOQL & bulkified Apex triggers.

LeetCode-style challenges judged against thousands of mock Accounts, Contacts and Opportunities — with the governor limits that trip up real interviews.

Start solving Try a trigger challenge

query.soql

1SELECT Name, (SELECT LastName FROM Contacts)
2FROM Account
3WHERE Rating = 'Hot'
4  AND Id IN (SELECT AccountId FROM Opportunity
5             WHERE CloseDate = THIS_QUARTER)
6ORDER BY Name

Accepted3 / 3 tests · 1,200 rows · 4.1 ms

Today's problems

View daily page

Daily SOQL

Largest Opportunity per Account

SOQLHard

Nested SubqueryLIMITSemi-Join

Solve

Daily Trigger

Maintain Account Contact and Opportunity Counts

Apex TriggerHard

Apex TriggerBulkificationAggregate SOQLContact

Solve

Real SOQL, real Postgres

Your query is parsed, compiled to SQL and executed against a mocked Salesforce org — relationships, aggregates, semi-joins and date literals included.

Read the notes

Bulk triggers, 200 at a time

Trigger.new, Trigger.oldMap, before/after phases and 200-record chunking — just like the platform, against 500+ seeded rows.

Read the notes

Governor limits enforced

SOQL-in-a-loop? You'll hit “Too many SOQL queries: 101”. CPU, DML and query-row limits are all simulated.

Read the notes

Rolled back every time

Each test runs inside a throw-away schema and transaction that is rolled back — the database stays pristine.

Read the notes