Salesforce Developer Interview Preparation Fresher Edition

Salesforce Developer
Interview Preparation Guide
Fresher Edition — Everything you need to ace your first interview

☁️ Salesforce Fundamentals

Before diving into code, make sure you understand what Salesforce is and how it works conceptually.

• What is Salesforce and what is CRM (Customer Relationship Management)?

• Salesforce multi-tenant, metadata-driven architecture
• Salesforce editions — Developer, Sandbox, Production org types
• Sales Cloud, Service Cloud, Marketing Cloud — Cloud products:
• Standard vs Custom Objects — when to use each
• App, Tab, Object, Record, Field hierarchy

Data Modeling & Administration

Objects & Fields

• Standard vs Custom Objects
• Field types: Text, Number, Date, Picklist, Lookup, Formula, Roll-Up Summary
• Validation Rules and Formula Fields
• Record Types and Page Layouts

Relationships
• Lookup Relationship — loosely coupled, child can exist without parent
• Master-Detail Relationship — tightly coupled, roll-up summaries available
• Many-to-Many via Junction Object
• Self-Relationships and Hierarchical Relationships

Security & Sharing

• Profiles, Roles, Permission Sets — differences and use cases
• OWD (Org-Wide Defaults) — Private, Public Read Only, Public Read/Write
• Sharing Rules — criteria-based and ownership-based
• Manual Sharing and Apex Managed Sharing

Prepared for Fresher Salesforce Developer Interviews | Start at: [Link]

 Salesforce Developer Interview Preparation Fresher Edition

⚙️ Apex Programming

Apex is Salesforce's proprietary Java-like language. This is the most critical section for a developer
role.

Core Apex Concepts

• Apex syntax, data types, and primitive types
• Classes, Interfaces, Abstract Classes, Constructors
• Access modifiers: public, private, protected, global
• List, Set, Map — usage and differences Collections:
• Exception Handling — try/catch/finally, custom exceptions

SOQL & SOSL

• SOQL — Salesforce Object Query Language (queries records)
• SOSL — Salesforce Object Search Language (searches text across multiple objects)
• Aggregate functions: COUNT, SUM, AVG, GROUP BY
• Relationship queries — parent-to-child and child-to-parent
• When to use SOQL vs SOSL

Triggers
• Trigger events: before insert, before update, after insert, after update, before delete, after delete,
after undelete
• Trigger context variables: [Link], [Link], [Link], [Link]
• Trigger best practices — one trigger per object
• Trigger Handler pattern — separating logic from trigger file
• Bulkification — always handle 200 records, never hardcode single record logic

Governor Limits (Very Important!)

Governor Limits are strict runtime limits enforced by Salesforce in a multi-tenant

environment. Interviewers ALWAYS ask about this. Know the key limits by heart.

• 100 SOQL queries per transaction (synchronous)

• 150 DML statements per transaction
• 50,000 records returned by SOQL
• 10 MB heap size limit
• CPU time limit: 10,000 ms (synchronous), 60,000 ms (asynchronous)
• Never put SOQL or DML inside a for loop — this is a classic interview question!

Prepared for Fresher Salesforce Developer Interviews | Start at: [Link]

 Salesforce Developer Interview Preparation Fresher Edition
Asynchronous Apex
• Batch Apex — process large data volumes in chunks (up to 50M records)
• Schedulable Apex — schedule jobs to run at specific times
• Queueable Apex — chaining jobs, supports more complex types than Future methods
• Future Methods (@future) — lightweight async, no chaining

⚡ Lightning Web Components (LWC)

LWC is the modern UI framework for Salesforce. Expect heavy questioning on this topic —
it is the most in-demand skill for Salesforce developers in 2024 and beyond.

LWC Architecture
• Component files: .html (template), .js (controller), .css (styles), .[Link] (metadata)
• Shadow DOM — encapsulation of styles and markup
• Template directives: if:true, for:each, iterator

Decorators
• @api — exposes properties and methods to parent components (public)
• @track — reactive private property (tracks deep object changes)
• @wire — connects component to Apex methods or Lightning Data Service

Lifecycle Hooks
• constructor() — called when component is created
• connectedCallback() — called when component is inserted into DOM
• renderedCallback() — called after every render
• disconnectedCallback() — called when component is removed from DOM

Communication Patterns
• pass data via @api properties Parent to Child:
• fire custom events with CustomEvent() Child to Parent:
• Lightning Message Service (LMS) or pubsub Unrelated Components:

Calling Apex from LWC

• Wire service — reactive, automatic calls when properties change
• Imperative Apex calls — called manually (in connectedCallback or event handlers)
• @AuraEnabled annotation required on Apex methods; cacheable=true for wire

Prepared for Fresher Salesforce Developer Interviews | Start at: [Link]

 Salesforce Developer Interview Preparation Fresher Edition

🌐 Visualforce (Basics)

Visualforce is the older UI framework. While LWC is the future, freshers may still be asked basic
Visualforce questions.

• VF pages and components — apex:page, apex:form, apex:inputField

• Standard Controller vs Custom Controller vs Controller Extension
• View State — what it is and why it matters for performance
• Rendering pages as PDF

🤖 Automation Tools (Declarative)

Flows
• Screen Flow — interactive, user-facing flows
• Record-Triggered Flow — replaces Workflow Rules and Process Builder
• Scheduled Flow — runs at defined time intervals
• Autolaunched Flow — called from Apex or other flows

When to Use What

• Use Flow first — Salesforce recommends declarative over code whenever possible
• Use Apex when logic is too complex, requires callouts, or needs precise DML control
• Process Builder — being phased out; migrate to Flow
• Workflow Rules — legacy, only for field updates and email alerts

🔗 Salesforce Integrations

• REST API — JSON-based, most commonly used; supports GET, POST, PATCH, DELETE
• SOAP API — XML-based, used for older enterprise integrations
• Connected Apps & OAuth 2.0 flow — how external apps authenticate
• Named Credentials — store endpoint + auth in one secure config
• Outbound Messages — SOAP-based push notifications
• Platform Events — event-driven architecture, pub/sub model
• Callouts from Apex — @future(callout=true) required for async callouts

🧪 Testing & Deployment

Apex Testing
• Minimum 75% code coverage required before deploying to Production
• @isTest annotation on test classes
Prepared for Fresher Salesforce Developer Interviews | Start at: [Link]
 Salesforce Developer Interview Preparation Fresher Edition
• [Link]() and [Link]() — reset governor limits for test scope
• Test data must be created in test class — no seeAllData=true in most cases
• Use TestDataFactory class for reusable test data
• [Link](), [Link](), [Link]()

Deployment
• Change Sets — declarative, point-and-click deployment between orgs
• Metadata API — used by IDEs (VS Code + Salesforce Extension Pack)
• Salesforce DX (SFDX) — modern CLI-based development and deployment
• Sandboxes — Developer, Developer Pro, Partial, Full sandbox types

🏅 Preparation Priority Guide

Priority Focus Area Topics

🔴 HIGH Apex & Triggers, LWC Governor Limits, SOQL

🟠 MEDIUM Data Modeling, Flows SOQL & SOSL queries

🟡 GOOD TO KNOW Integrations, VF Deployment, Testing

💡 Top Tips for Freshers

• Practice on a free Developer org — sign up at [Link]

• Complete the Platform Developer I trail on Trailhead before your interview
• Always bulkify your Apex code — never query or DML inside loops
• Know the difference between Lookup and Master-Detail cold
• Be ready to explain Governor Limits and why they exist in multi-tenant architecture
• Prepare to write a simple Apex trigger and a basic LWC component on a whiteboard
• Study real Salesforce interview questions on Glassdoor and Ambitionbox

Best Free Resource: Start at [Link] — it is 100% free, has hands-

on challenges, and earns you badges that impress interviewers. Aim for the Salesforce
Platform Developer I Superbadge before your interview.

Good luck! Preparation + Practice = Success 🚀

Prepared for Fresher Salesforce Developer Interviews | Start at: [Link]