Salesforce Developer

Salesforce Developer

Location : ONSITE

LOCATION : MUMBAI AND BANGALORE

Resources should have banking domain experience.

1. Salesforce development Engineer (1 - 3 Years)

2. Salesforce development Engineer (3 - 5 Years)

3. Salesforce development Engineer (5 - 8 Years)

Job description.

----------------------------------------------------------------------------

Technical Skills

Strong hands-on frontend development using JavaScript and LWC

Expertise in backend development using Apex, Flows, Async Apex

Understanding of Database concepts: SOQL, SOSL and SQL

Hands-on experience in API integration using SOAP, REST API, graphql

Experience with ETL tools , Data migration, and Data governance

Experience with Apex Design Patterns, Integration Patterns and Apex testing framework

Follow agile, iterative execution model using CI-CD tools like Azure Devops, gitlab, bitbucket

Should have worked with at least one programming language - Java, python, c++ and have good understanding of data structures

Preferred qualifications

Graduate degree in engineering

Experience developing with India stack

Experience in fintech or banking domain

----------------------------------------------------------------------------

Skill details.

1. Salesforce Fundamentals

Strong understanding of Salesforce core architecture

Objects (Standard vs Custom)

Fields, relationships (Lookup, Master-Detail)

Data model basics and record lifecycle

Awareness of declarative vs programmatic capabilities and when to use each

2. Salesforce Security Model

End-to-end understanding of Salesforce security layers, especially

Record visibility when a record is created

Org-Wide Defaults (OWD) and their impact

Role Hierarchy and how it enables upward data access

Difference between Profiles, Permission Sets, and Sharing Rules

Ability to explain how Salesforce ensures that records are not visible to unauthorized users by default and how access is extended

3. Apex Triggers

Clear distinction between

Before Triggers (before insert, before update)

Use cases such as validation and field updates

After Triggers (after insert, after update)

Use cases such as related record updates or integrations

Understanding of trigger context variables and best practices (bulkification, avoiding recursion)

4. Platform Events / Event-Driven Architecture

Knowledge of Platform Events and their use in decoupled, event-driven solutions

Understanding of real-time or near real-time notification use cases (e.g., UI alerts, pop-up style notifications)

Ability to position Platform Events versus alternatives (Streaming API, Change Data Capture)

5. Lightning Data Access (Wire Method)

Understanding of the @wire mechanism in Lightning Web Components (LWC)

Discussion point

Whether records (e.g., AppX records) can be updated using the wire method

Awareness that @wire is primarily read/reactive and updates typically require imperative Apex calls

Clear articulation of reactive vs imperative data handling

6. Integrations Experience

Ability to articulate hands-on integration experience, including

REST/SOAP API integrations

Inbound vs outbound integrations

Authentication mechanisms (OAuth, Named Credentials)

Use of Apex callouts, Platform Events, or middleware

Clarity on integration patterns and error handling approaches