Free · takes a minute · your resume fills your profile
CoreHRx never asks candidates for money. If anyone does, .
Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Position: Salesforce Technical Lead (RCA)
Experience: 10+ years
Location: Chennai / Pune / Hyderabad / Bangalore
Shift: UK Shift
Experience: 10+ years overall
Interviews: 3 Interview rounds.
Roles and Responsibilities:
You lead the build. You turn the approved design into working Revenue Cloud Advanced configuration, own technical quality, and deployments, and run the offshore developers and tester day to day.
You build the hardest parts yourself: pricing procedures, the region decision table and the rules that depend on it.
Translate the solution design into technical specifications and a sprint build plan across three sprints.
Configure Product Catalog Management: products, attributes, classifications, bundles and kits, and product selling models.
Build pricing: price books, cost book, pricing procedures, decision tables, tiered pricing, price waterfall, and line and blended margin with target-margin pricing.
Build the region decision table and the qualification, category and configuration rules that enforce regional eligibility in browse, search and kits.
Configure approval rules with alerts and aging reminders, quote types, orders, contracts, subscriptions and renewals.
Build document templates for the quote, including annotated site photos from the photo capture package.
Lead the Field Service extension build with the Sr. Developer: quote or order to work order, and line item mapping.
Write Flow first; write Apex or Lightning Web Components only where configuration cannot meet the need, with test classes and bulk-safe code.
Own environments, source control, CI/CD, data loads (two trial loads and one production load) and all deployments.
Review code and configuration, resolve defects in SIT and UAT, lead cutover and stay through hypercare.
Required Qualification:
Hands-on build of at least one Revenue Cloud Advanced (Revenue Lifecycle Management) project, or deep Salesforce CPQ build experience plus RCA delivery exposure.
Strong skills in RCA pricing procedures, decision tables, context definitions, product configurator rules, and advanced approvals.
Strong Flow, Apex and Lightning Web Component skills, with a declarative-first habit.
Working knowledge of Salesforce Field Service data model and automation: work orders, work order line items, work types.
Experience with Salesforce DevOps: source-driven development, Git, a CI/CD tool (Copado, Gearset or Salesforce CLI pipelines) and sandbox strategy.
Data loading at volume with Data Loader or similar, including catalog and price book data.
Experience leading a small offshore team and reporting status to an onshore architect.
Certifications:
Salesforce Platform Developer I
Salesforce Revenue Cloud or CPQ certification
Salesforce Platform Developer II - preferred
Salesforce Field Service Consultant (preferred)
Desired Qualifications:
Salesforce document generation (OmniStudio Document Generation) experience.
AppExchange package configuration such as SharinPix.
SAML single sign-on set-up.
Use of AI-assisted build tools for Apex, Flow and metadata.
Most IT Jobs posts in Bangalore ask for 3–6 years of experience (41% of 5032 that say).
From live job posts on CoreHRx, updated 19 Nov 2026. Skill figures count posts that list their skills; salary figures only posts that show a salary.
The post does not state the pay. As an estimate, comparable posts on CoreHRx advertise ₹13L – ₹25L a year (typical for IT Jobs in Bangalore, 256 posts).
The post asks for 10 Yrs experience.
In Bangalore.
It is a full time job.
Interview preparation · 60 questions
This guide is for freshers and working developers in India who use Git every day and now have to explain it in an interview: campus hires, engineers at service companies moving to product teams, and leads who review pull requests. It has 60 questions in three levels. Easy covers the staging area, commits, branches, merges and remotes. Medium covers what goes wrong at work: rebasing, conflicts, reset versus revert, lost commits, rejected and forced pushes. Hard covers Git internals, branching strategies, protected branches, merge queues, large repositories and GitHub Actions security. Every command output shown comes from running Git 2.43 on small practice repositories. Run the commands in a scratch repository of your own, then take the mock test.
Questions you may be asked
Create a free profile and we email you new IT jobs in Bangalore, at most once a week.