Salesforce Developer

Salesforce DeveloperLocation : ONSITELOCATION : MUMBAI AND BANGALOREResources 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 LWCExpertise in backend development using Apex, Flows, Async ApexUnderstanding of Database concepts: SOQL, SOSL and SQLHands-on experience in API integration using SOAP, REST API, graphqlExperience with ETL tools , Data migration, and Data governanceExperience with Apex Design Patterns, Integration Patterns and Apex testing frameworkFollow 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 structuresPreferred qualificationsGraduate degree in engineeringExperience developing with India stackExperience in fintech or banking domain---------------------------------------------------------------------------- Skill details. 1. Salesforce FundamentalsStrong understanding of Salesforce core architectureObjects (Standard vs Custom)Fields, relationships (Lookup, Master-Detail)Data model basics and record lifecycleAwareness of declarative vs programmatic capabilities and when to use each2. Salesforce Security ModelEnd-to-end understanding of Salesforce security layers, especially:Record visibility when a record is createdOrg-Wide Defaults (OWD) and their impactRole Hierarchy and how it enables upward data accessDifference between Profiles, Permission Sets, and Sharing RulesAbility to explain how Salesforce ensures that records are not visible to unauthorized users by default and how access is extended3. Apex TriggersClear distinction between:Before Triggers (before insert, before update)Use cases such as validation and field updatesAfter Triggers (after insert, after update)Use cases such as related record updates or integrationsUnderstanding of trigger context variables and best practices (bulkification, avoiding recursion)4. Platform Events / Event-Driven ArchitectureKnowledge of Platform Events and their use in decoupled, event-driven solutionsUnderstanding 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 methodAwareness that @wire is primarily read/reactive and updates typically require imperative Apex callsClear articulation of reactive vs imperative data handling6. Integrations ExperienceAbility to articulate hands-on integration experience, including:REST/SOAP API integrationsInbound vs outbound integrationsAuthentication mechanisms (OAuth, Named Credentials)Use of Apex callouts, Platform Events, or middlewareClarity on integration patterns and error handling approaches