Interview Prep
General Questions
Tell me about yourself
I began my IT journey in 2017, had to drop out in due to financial difficulties,
but because I had passion for this field and felt like I could excel in it, I had
to get a job so that I can be able to pay for my fees… I went back to do my diploma
in Information Technology in 2021 and graduated In record time in May 2023. So
from 2017 I was in between jobs where I got exposed to different working
environments.
With nearly five years of diverse experience across multiple industries, I have
honed a strong ability to adapt to different work environments. I began my career
in customer service, gaining valuable insights in both call center and retail
settings. This foundation helped me develop a solid understanding of end-user
needs, which I now leverage in my work as a Salesforce developer.
Over time, I transitioned into Salesforce development, where I’ve built strong
technical expertise. I specialize in creating and customizing Salesforce
applications to align with business requirements, ensuring that solutions are both
effective and user-friendly.
My experience in high-pressure roles—such as managing a Security Control Room
Operation in a 24/7 environment—has instilled a keen attention to detail and the
ability to perform effectively with minimal supervision.
How do you feel about salesforce
If I had feelings, I’d say I enjoy the dynamic nature of Salesforce and its
constant evolution. Salesforce is a platform that connects people, data, and
processes, and I find it fascinating how it empowers businesses to solve real-world
problems in innovative ways. A few things I particularly enjoy about Salesforce:
1. Empowering Automation:
Salesforce is all about making processes more efficient, and I enjoy how powerful
tools like Flows, Process Builder, and Apex allow users and developers to automate
complex business workflows. The ability to automate routine tasks, trigger
notifications, and streamline approval processes makes it so impactful for
organizations.
2. Customization & Flexibility:
Salesforce's ability to be customized—from its user interface (through Lightning
components) to business logic (via Apex and flows)—is something that stands out. No
two Salesforce implementations are exactly the same, and the flexibility to tailor
solutions to fit unique business needs is both challenging and rewarding.
3. Data-Driven Insights:
The platform’s powerful reporting, dashboarding, and analytics features,
particularly with Einstein Analytics, allow businesses to turn data into actionable
insights. I love how these tools enable organizations to make smarter decisions
based on real-time data.
4. Focus on Innovation:
Salesforce is always innovating. The frequent releases (Spring, Summer, Winter)
bring exciting new features like Einstein AI, Blockchain, and MuleSoft
integrations. It's fascinating how Salesforce continuously enhances its platform to
stay ahead of industry trends, like cloud computing, artificial intelligence, and
low-code/no-code development.
Where do you see salesforce
Salesforce is an incredibly versatile, scalable, and innovative platform, and it’s
only getting better. I see it evolving into an even more powerful tool that uses
AI, automation, and deeper integrations to help businesses work smarter and faster.
Its future will likely be characterized by low-code development, AI-powered
decision-making, and a more connected ecosystem, making it a central hub for both
internal and external business processes.
Salesforce is already at the forefront of the digital transformation revolution,
and I expect it to continue to lead the way in empowering businesses to deliver
outstanding customer experiences, drive efficiency, and stay ahead in an
increasingly connected world.
What were the challenges you faced with Salesforce…
Complexity in Building Advanced Flows
Challenge: While Salesforce Flow (especially Screen Flows and Record-Triggered
Flows) is powerful, building complex flows that handle intricate business logic or
multiple conditional paths can be challenging. This often leads to flows becoming
difficult to maintain or debug.
Example: A flow with many decision elements, loops, or nested conditions might
become overly complicated, making it hard to understand or troubleshoot.
Solution: Keep flows as simple as possible. Break complex flows into smaller sub-
flows or processes. Use Flow Builder’s documentation and annotations to document
logic, and organize elements to make them easy to follow. Whenever possible, avoid
nesting decision elements too deeply.
So I learnt that with careful planning, following best practices, and using the
right tools (such as Flow Debugger, Platform Events, and Apex), many of these
challenges can be mitigated.
Tell us about the projects you worked on
Millbank FX is a foreign exchange (FX) service provider that is based in UK, it
specializes in helping businesses and individuals manage international payments and
currency exchange. It offers solutions that simplify the process of sending and
receiving money across borders. These solutions are designed to be more efficient
and cost-effective compared to traditional bank services. Millbank FX aims to
deliver competitive exchange rates, reduce transaction costs, and provide a range
of tools for managing global cash flows.
Millbank FX Project: Trade Creation Form
• Introduction: “At Millbank FX, I worked on a Salesforce project to
simplify their trade creation process.”
• Objective: “The goal was to help traders create and verify trades more
easily while ensuring accuracy.”
• My Role:
• “I built a Trade Creation Form using Lightning Web Components, where
traders could input details like currency pairs, trade types, and exchange rates.”
• “I handled backend processes using Apex, including submitting trade
data and verifying it with liquidity providers.”
•
• Result: “This system reduced errors, sped up trade processing, and made
it easier for teams to collaborate.”
2. Echelon Dynamics Project: React Bootstrap Website
Echelon Dynamics, a Salesforce implementation firm dedicated to delivering growth-
focused and cost-effective CRM solutions that transform businesses while driving
efficiency.
• Introduction: “At Echelon Dynamics, I developed a responsive website
using React and Bootstrap.”
• Objective: “The aim was to create a modern, easy-to-use site that
showcased their services.”
• My Role:
• “I created key components like a navbar that adjusted for different
screen sizes and a hero section featuring their logo and key service images.”
• “I integrated assets for platforms like Google Cloud, Salesforce, and
Microsoft, aligning them with the website’s design.”
• “I ensured everything was properly spaced and visually appealing,
optimizing it for both desktop and mobile.”
• Result: “This enhanced their brand’s online presence and gave their
clients a polished, professional interface.”
Closing Summary
• “These projects taught me how to deliver solutions tailored to business
needs, whether it’s through creating seamless user experiences or developing robust
backend logic. I’m confident these skills will help me contribute effectively to
your team.”
Apex and LWC What it is:
Using Apex for business logic and LWC for the frontend allows Salesforce
developers to build powerful, scalable applications that are both data-driven and
user-friendly. Apex handles the heavy lifting of business processes and data
management, while LWC ensures a modern, interactive user experience, making this
combination ideal for Salesforce development. In simple terms Apex is used for
business logic and lwc for frontend.
What conflicts did you face and how did you resolve it?
One of the junior developers had a challenge with his feature and did inform any of
us until last minute. Lack of communication led a to misunderstandings and delays.
However he eventually approached one of us.
Try to understand why the communication didn’t happen. Was the person unaware of
the need for help? Was the issue something they felt they could solve
independently? Did they not realize that help was available? Understanding the root
cause is key to resolving the situation. He just wanted to tackle this issue on his
own and when he realised that is not working, he asked for help and as a team we
were happy to help where we can and that made the team stronger , enabled us to be
aware that we can ask for help from others if we need clarification on certain
things. Effective communication, especially in a collaborative environment like
Salesforce development, is key to avoiding bottlenecks and ensuring the team is
working towards the same goal.
The team consisted with how many people?
In the project I did it had a team of 6 people, a tech lead , 2 senior dev, 3
junior developers…
Interview prep..
Tech Questions
What are governor Limits?
Governor limits in Salesforce are runtime limits enforced by the platform to ensure
efficient resource usage and to prevent any single process or transaction from
consuming too many system resources. These limits help maintain the stability and
scalability of Salesforce, particularly in a multi-tenant environment where many
different organizations share the same infrastructure.
Governor limits apply to different types of operations in Salesforce, such as Apex
code execution, database queries, DML operations, and API calls. The limits are in
place to ensure that no single user or organization monopolizes the shared
resources.
Apex Execution Limits: CPU time: Maximum allowed CPU time (in milliseconds) for
synchronous and asynchronous Apex transactions.
DML Limits: Number of DML operations per transaction: Salesforce limits how many
DML operations (insert, update, delete, undelete) can be performed in a single
transaction.
What is a successful integration in development?
To ensure integration is properly developed, tested, and deployed. It is essential
that aspects of Salesforce development are crucial to ensure a high-quality
solution.
Triggers Must Have at Least 1% Test Coverage
In Salesforce, triggers are pieces of Apex code that execute in response to
specific events like insertions, updates, deletes, or undeletes on Salesforce
objects. For your trigger code to be successfully deployed to Production,
Salesforce requires that at least 1% of the trigger code is covered by test
methods.
Salesforce requires that at least 70% of your Apex test classes have code coverage
before you can deploy the code to Production. This rule is enforced for all types
of Apex code, including triggers, classes, and other components of your
integration.
What is the difference between Programmatic and declarative?
In Salesforce, programmatic and declarative approaches refer to two distinct
methods for implementing solutions, automating processes, and customizing the
platform. Both approaches have their place in Salesforce development, and each
comes with its own set of advantages and use cases.
Programmatic Approach
The programmatic approach involves writing custom code (usually in Apex,
Visualforce, Lightning Web Components (LWC), or JavaScript) to implement business
logic, handle complex processes, and build custom functionality that cannot be
easily achieved through declarative tools. Essentially, programmatic development
refers to building custom solutions through code.
Declarative Approach
The declarative approach refers to using Salesforce's built-in, point-and-click
tools to build functionality without writing any code. It’s typically used for
business users, admins, and consultants to automate processes, manage data, and
configure the system in a way that meets business requirements without the need for
custom programming.
Apex triggers are used to perform custom actions before or after certain events
occur on Salesforce records. There are two main types of triggers based on when
they are executed in the Salesforce transaction lifecycle:
Before Triggers
• Description: Before triggers are executed before a record is saved to
the database (i.e., before an insert, update, or delete operation is committed to
the database).
• Use Case: These triggers are primarily used when you need to validate,
modify, or prepare the data before it's saved to Salesforce.
After Triggers
• Description: After triggers are executed after a record has been saved
to the database (i.e., after insert, update, or delete operations are committed).
• Use Case: These triggers are used when you need to perform actions that
require the record to already be saved to the database, such as updating related
records, sending notifications, or logging information.
• Both before and after triggers are subject to Salesforce governor
limits, such as the maximum number of DML operations or SOQL queries.
What are Relationship custom objects?
In Salesforce, relationships between objects define how records in different
objects relate to one another.
A Lookup Relationship is a one-to-one relationship where one object can reference
another. The referencing object (child) contains a field that links to a record in
the referenced object (parent). This relationship is optional, meaning the child
record does not necessarily need to have a parent.
A Master-Detail Relationship is a stronger relationship where one object (the
child) is tightly bound to another object (the parent). In this relationship, the
child record depends on the parent record for its existence, meaning the child
cannot exist without the parent.
What are the different types of Flows in Salesforce, and when would you use each
one?
Screen Flow:
• When to Use: For user-interactive processes, where users need to input
data through screens (e.g., surveys, data collection, wizards).
• Example: Collecting information from a user to create a new record.
1. Record-Triggered Flow:
• When to Use: Automatically triggers when a record is created, updated,
or deleted (e.g., automatically updating related records).
• Example: Updating an Account when a related Contact is updated.
2. Scheduled Flow:
• When to Use: To run flows at a specific time or on a recurring
schedule, like batch jobs (e.g., sending reminders or running reports).
• Example: Sending a weekly email summary to a manager every Monday at 8
AM.
3. Autolaunched Flow:
• When to Use: Runs in the background without user interaction, triggered
by another process (e.g., another flow, a button, or an Apex class).
• Example: Automatically creating tasks after a record is updated.
4. Platform Event-Triggered Flow:
• When to Use: To trigger flows based on platform events (real-time
events from external systems).
• Example: Listening to an event from an external system to trigger a
flow in Salesforce.
Each type of flow is used based on how you want the flow to interact with users or
other Salesforce processes.
Technical Competence: The ability to create and manage complex flows, following
best practices for design and functionality.
Problem-Solving: Knowing when and how to use different types of flows (like Screen
Flows, Record-Triggered Flows) based on the problem you're solving.
Optimization & Efficiency: Ensuring flows run efficiently, avoid hitting Salesforce
limits (governor limits), and can process large sets of data without performance
issues.
Integration Expertise: Experience using Salesforce Flows to connect with external
systems or services via tools like Apex, Platform Events, or HTTP callouts.
User-Centric Design: Creating easy-to-use flows with simple screens and ensuring
data is entered and processed correctly.
Testing & Troubleshooting: Ability to test, debug, and fix any issues in flows,
ensuring they work smoothly in production without errors.
What are apex best practices?
Bulkify Your Code
Why: Salesforce has governor limits (like the number of records processed in a
transaction). Always design your code to handle multiple records at once.
How: Use collections (lists, sets, maps) to process records in bulk and avoid SOQL
or DML inside loops.
Avoid SOQL and DML in Loops
Why: Running SOQL queries or DML operations inside loops can easily hit governor
limits.
How: Collect records outside the loop and process them in bulk.
Use Custom Settings and Custom Metadata for Configuration
Why: Storing configuration data directly in Apex code is inefficient and hard to
manage. Use custom settings or custom metadata types for this.
How: Fetch configuration values from custom settings or metadata, reducing the need
to hardcode values.
Handle Exceptions Properly
Why: Proper error handling ensures that your code doesn't fail silently, and you
can debug issues effectively.
How: Use try-catch blocks and create meaningful error messages.
Test Your Code
Why: Salesforce requires at least 75% test coverage for deployment, but more
importantly, tests help ensure your code works as expected.
How: Write unit tests that cover positive, negative, and edge cases, and use
@isTest annotation to write test methods.
By following these Apex best practices, you’ll write more efficient, maintainable,
and scalable code that is easier to debug, test, and deploy in Salesforce
environments.
What is SOQL ?
(Salesforce Object Query Language)
SOQL is Salesforce's query language used to retrieve data from Salesforce's
database (objects and records). It’s similar to SQL (Structured Query Language) but
specifically tailored for Salesforce’s data model.
Key Points:
• Purpose: To query and retrieve records from Salesforce objects.
• Syntax: Similar to SQL but focused on Salesforce's objects and fields.
• Main Use: Fetch records based on certain conditions or filters.
What is DML ?
(Data Manipulation Language)
DML is used in Salesforce to perform operations on records, such as inserting,
updating, deleting, or undeleting records in the Salesforce database.
Key Points:
• Purpose: To modify data in Salesforce objects (create, update, delete).
• Main Use: Perform CRUD (Create, Read, Update, Delete) operations on
Salesforce records.
• Syntax: Uses DML operations to manipulate record
SOSL (Salesforce Object Search Language)
SOSL is a search language used in Salesforce to perform text searches across
multiple objects in the Salesforce database. Unlike SOQL, which is used to retrieve
records based on specified fields and conditions, SOSL is used for searching
specific terms or text across multiple objects and fields.
Key Points:
• Purpose: Used to search for records across multiple objects (such as
Accounts, Contacts, Opportunities) based on keywords or phrases.
• Main Use: Efficient when you don't know where a piece of information
(like a name or email) is located and want to search multiple objects and fields.
• Syntax: Similar to SOQL, but more focused on text-based searches.
When to Use SOSL:
• When you need to search across multiple objects (e.g., Account,
Contact, Opportunity) for a keyword or phrase.
• When you are looking for text-based matches (e.g., matching names,
emails, phone numbers, etc.) across different fields.
• Ideal for global searches or when you don’t know exactly where the
information is stored.
Salesforce Clouds Salesforce Clouds:
• Sales Cloud: I can explain how to configure and optimize the Sales
Cloud for your organization's sales processes.
• Service Cloud: I can guide you through configuring the Service Cloud to
support customer service operations, including case management and knowledge base.
• Marketing Cloud: I can help you set up Marketing Cloud for personalized
customer communication and marketing automation.
• Community Cloud: I can explain how to set up communities for
collaboration with partners, customers, and employees.