While SOQL (Salesforce Object Query Language) gets all the glory, SOSL (Salesforce Object Search Language) is the silent powerhouse of the Salesforce platform. When dealing with global searches, unstructured data, or massive text fields, SOQL will quickly hit a wall. That is where SOSL steps in.
In this article, we have compiled the ultimate list of 30 SOSL interview questions, starting from essential theory and moving straight into real-world, scenario-based coding challenges.
Foundation: Essential SOSL Theory Questions
1. What is SOSL and when should you use it over SOQL?
SOSL (Salesforce Object Search Language) is a programmatic way to perform text-based searches across multiple objects simultaneously using the Salesforce search index.
You should use SOSL instead of SOQL when:
- You don’t know exactly which object the data resides in (e.g., searching for a phone number across Accounts, Contacts, and Leads).
- You need to search against Long Text Area or Rich Text Area fields (SOQL cannot filter on these fields using the
LIKEoperator, but SOSL can). - You want to leverage the speed of the search index for partial word matching across large volumes of data.
2. What is the return type of a SOSL search in Apex?
Unlike SOQL, which returns a single “List<sObject>” , a SOSL query searches across multiple objects. Therefore, it returns a List of Lists of sObjects (List<List<SObject>>). The order of the lists in the result corresponds exactly to the order of the objects specified in the RETURNING clause.
3. What are the core Governor Limits for SOSL?
To prevent performance degradation on the search index, Salesforce enforces the following limits:
- Total number of SOSL queries: 20 per synchronous transaction (200 for asynchronous transactions).
- Total number of records returned: A single SOSL query can return a maximum of 2,000 records total across all objects.
4. A user wants to search for the word “Acme” across the entire database. Write the simplest SOSL query to achieve this.
FIND 'Acme'
(Note: Always remember the single quotes around the search term.
Also, while this is valid in the Query Editor, if you run this in Apex without a RETURNING clause, it will only return the IDs of the matched records.)*
5. We need to find the term “John” to locate a user, but we want the search to be highly optimized. How do you restrict the search index to ONLY look inside Email fields?
Use the "IN EMAIL FIELDS" search group.
IN ALL FIELDS is the default but executes slower if you only need emails.
FIND 'John' IN EMAIL FIELDS
6. Search for the term “Apple”, but I only want you to return Account and Contact records. For Accounts, return the Name and Industry. For Contacts, return the FirstName and LastName.
Be sure to place the fields you wish to return inside parentheses immediately following the object name.
FIND 'Apple' IN ALL FIELDS
RETURNING Account(Name, Industry), Contact(FirstName, LastName)
7. Wildcards: Find all records where a name starts with “Sam” or exactly matches “Samuel”. Ensure it catches “Sammy” as well.
Do not use % like you would in SOQL. SOSL uses * for multiple characters and ? for a single character.
FIND 'Sam* OR Samuel' IN NAME FIELDS
RETURNING Contact(Name, Email)
8. We need to search for the phrase “Cloud Computing”. How do you ensure SOSL searches for that exact phrase, rather than just records containing “Cloud” and “Computing” separately?
Simply typing FIND 'Cloud Computing' performs an implicit logical operation. To search for an exact phrase, you must wrap it in escaped double quotes inside the single quotes.
FIND '"Cloud Computing"' IN ALL FIELDS RETURNING Account(Name)
SOSL isn’t just about finding text , you can also filter the results exactly like you do in SOQL.
9. Search for “Acme”, return Account records, but ONLY return the Accounts if their Industry is ‘Technology’.
Do not place the WHERE clause outside of the RETURNING statement. In SOSL, filters are applied inside the object’s parenthesis.
FIND 'Acme' IN ALL FIELDS
RETURNING Account(Name, Industry WHERE Industry = 'Technology')
10. Search for “Test”. Return Opportunities, but order them by Amount from highest to lowest, and only return a maximum of 10 Opportunities.
Just like the WHERE clause, ORDER BY and LIMIT for a specific object must go inside its RETURNING block.
FIND 'Test' IN ALL FIELDS
RETURNING Opportunity(Name, Amount ORDER BY Amount DESC LIMIT 10)
11. Search for “Universal” across Accounts and Leads. How do you limit the ENTIRE SOSL query to only return 50 records total, regardless of the object?
Putting LIMIT 50 inside the parenthesis limits it per object. To limit the global results across all objects, place it at the very end of the query.
FIND 'Universal' IN ALL FIELDS
RETURNING Account(Name), Lead(Name)
LIMIT 50
12. You have a Custom Object called “Project__c”. Search for “Alpha” and return the “Project__c” Name and custom “Budget__c” field.
SOSL works natively on Custom Objects exactly as it does on Standard Objects.
FIND 'Alpha' IN ALL FIELDS
RETURNING Project__c(Name, Budget__c)
13. Search for “Acme”, but only return Account records that belong to the ‘Customer’ Record Type.
You can filter by Record Type Developer Name inside the object’s parenthesis to avoid hardcoding IDs.
FIND 'Acme' IN ALL FIELDS
RETURNING Account(Name WHERE RecordType.DeveloperName = 'Customer')
14. You are returning Accounts and Contacts. How do you sort Accounts by Name and Contacts by LastName?
The ORDER BY clause is applied independently inside each object’s returning parentheses.
FIND 'Acme' IN ALL FIELDS
RETURNING Account(Name ORDER BY Name), Contact(FirstName, LastName ORDER BY LastName)
15. Can you use “OFFSET” in SOSL to paginate search results?
Yes. However, unlike SOQL, the OFFSET clause in SOSL is placed at the very end of the query and applies to the entire global result set, not the individual objects.
FIND 'Test' IN ALL FIELDS
RETURNING Account(Name), Lead(Name)
LIMIT 20 OFFSET 20
16. You executed this query in Apex: “[FIND ‘Cloud’ RETURNING Account(Name), Contact(Name)]“. How do you extract the Accounts and Contacts into their own separate lists?
You must cast the elements from the List<List<sObject>> array. The index matches the exact order of the objects in the RETURNING clause.
List<List<SObject>> searchList = [FIND 'Cloud' RETURNING Account(Name), Contact(Name)];
Account[] searchAccounts = (Account[])searchList[0];
Contact[] searchContacts = (Contact[])searchList[1];
17. A user types a search term into an LWC component, which passes a String searchTerm to your Apex controller. Write the SOSL query using Apex bind variables.
Never use string concatenation, as it leaves your code vulnerable to SOSL Injection. Use the : bind variable syntax just like SOQL.
public static List<List<SObject>> performSearch(String searchTerm) {
return [FIND :searchTerm IN ALL FIELDS RETURNING Account(Name, Type)];
}
18. How do you execute a SOSL query when the objects or fields to return are constructed dynamically at runtime based on user selection?
Use the Search.query() method, passing in the dynamically constructed SOSL string.
String dynamicQuery = 'FIND \'Acme\' IN ALL FIELDS RETURNING Account(Name), Contact(Email)';
List<List<SObject>> results = Search.query(dynamicQuery);
19. What is SOSL Injection, and how do you prevent it if you are forced to use Dynamic SOSL (Search.query())?
SOSL Injection happens when a malicious user inputs unexpected characters (like single quotes) into a search bar to alter the underlying database query. You must always wrap the user input in String.escapeSingleQuotes().
String userInput = 'Acme';
String safeInput = String.escapeSingleQuotes(userInput);
String dynamicQuery = 'FIND \'' + safeInput + '\' IN ALL FIELDS RETURNING Account(Name)';
List<List<SObject>> results = Search.query(dynamicQuery);
20. Your Apex class searches for records, but the security review flagged your SOSL query because it bypasses Field-Level Security (FLS) and Object Permissions. How do you fix this natively in the query?
Append the WITH SECURITY_ENFORCED clause to the end of the query. This will automatically throw an exception if the running user lacks the proper permissions to view the objects or fields in the RETURNING clause.
FIND 'Secret' IN ALL FIELDS
RETURNING Opportunity(Name, Amount), Contact(Name, Email)
WITH SECURITY_ENFORCED
21. You need to search for a specific error code (“ERR-404”) inside a custom “Rich_Text_Log__c” field on the Case object. Why must you use SOSL instead of SOQL?
Salesforce does not allow you to use the = or LIKE operators in a SOQL WHERE clause on Long Text Area or Rich Text Area fields. If you attempt it, you will get a syntax error. SOSL, however, indexes these large text fields automatically, allowing you to easily search them:
FIND 'ERR-404' IN ALL FIELDS RETURNING Case(CaseNumber, Rich_Text_Log__c)
22. Can you use SOSL inside an Apex Trigger?
Yes, but it is highly discouraged and rarely the right architectural choice. SOSL counts against your governor limits (only 20 queries allowed per synchronous transaction). Furthermore, SOSL relies on the search index, which updates asynchronously. If a record was inserted in the previous line of code, the SOSL query in your trigger will likely not find it yet because the index hasn’t updated.
23. How do you search for multiple disjointed terms, for example, finding records that contain “Salesforce” AND “Implementation”, but not necessarily right next to each other?
Use the logical AND operator inside the search string. Do not use commas.
FIND 'Salesforce AND Implementation' IN ALL FIELDS RETURNING Account(Name)
24. A user searches for “Smith” but you want to ensure the results are tracked so the company can build analytics around what users are searching for in a custom community. How is this done?
Salesforce has a native feature for this. You can append WITH TRACKING to your SOSL query to log the search terms in the Salesforce Search Activity framework instead of building custom tracking objects.
FIND 'Smith' IN NAME FIELDS RETURNING Contact(Name) WITH TRACKING
25. What happens if a SOSL query matches 5,000 records across the database? Will it throw a Limit Exception?
No, Salesforce does not throw a Limit Exception in this scenario. It simply truncates the result set to the maximum limit (2,000 records total), distributed across the objects requested in your RETURNING clause.
26. You need to find a Contact by their exact, specific email address (e.g., john.doe@example.com). Should you use SOQL or SOSL?
Use SOQL. Since you know the exact object (Contact), the exact field (Email), and you want an exact match, a SOQL query (WHERE Email = 'john.doe@example.com') is significantly faster, utilizes the database index directly, and doesn’t count against your tight SOSL governor limits.
27. A user searches for a term inside a large Knowledge Article. How do you return a preview excerpt of the text surrounding their search term so they know contextually why it matched?
Use the WITH SNIPPET clause. This tells the search engine to return an excerpt of the matched field with the search term highlighted in <mark> HTML tags, which is perfect for building a custom search UI.
FIND 'Deployment' IN ALL FIELDS RETURNING KnowledgeArticleVersion(Title) WITH SNIPPET
28. Can you use a SOSL query inside the “Start” method of a Batch Apex class returning “Database.Querylocator()” ?
No. A Database.QueryLocator strictly only accepts SOQL queries. If you absolutely must process SOSL results asynchronously in a batch, you have to execute the SOSL query and return a custom Iterable<sObject> in the start method instead.
29. Does SOSL automatically enforce record-level sharing rules?
Yes, SOSL automatically enforces record-level sharing rules based on the running user, unless it is executed within an Apex class explicitly declared as without sharing. However, for Field-Level Security (FLS) to be respected, you still must use the WITH SECURITY_ENFORCED clause.
30. Can you use aggregate functions like “Count() or “Sum()” inside a SOSL query?
No. SOSL is purely a search language designed to find text matches across objects. It does not support aggregate functions or GROUP BY logic. If you need aggregations, you must use SOQL.
Triggerhours Pro-Tip
When an interviewer asks you a question about fetching data, your default instinct will always be SOQL.
Pause for a second.
Ask the interviewer: “Are we searching across multiple objects? Are we filtering on a Long Text Area field?”
If the answer to either of those is yes, pivot your answer to SOSL.
Explaining why you chose SOSL over SOQL demonstrates that you understand the platform’s underlying architecture, not just how to memorize syntax.
Keep practicing, and go crush that interview!
Got a tricky SOSL interview question you couldn’t solve? Drop it in the comments below and the Triggerhours community will help you out!
Author
Discover more from Trigger Hours
Subscribe to get the latest posts sent to your email.