Salesforce QA

Engineering Square LLC; Hyderabad; On-site; INR 900,000 - 1,500,000; Full time

Job summary

Engineering Square LLC in Hyderabad, India is seeking a hands-on Salesforce QA tester for a full-time role. You will manually test Apex, Lightning Web Components and Flows, and own regression across portals, lending flows, and the Salesforce–NetSuite integration, coordinating with the Tech Lead and developers.

You will join daily standups, report status to stakeholders, and ensure test evidence is attached to every story. A background in 1–3 years of Salesforce QA and portal testing is preferred.

Qualifications

• Hands-on manual functional and regression testing of Salesforce Sales Cloud / Service Cloud.

Responsibilities

• Test changes before release: manual functional testing of Apex, Lightning Web Component and Flow changes on both Salesforce orgs against acceptance criteria; exploratory testing around the change.

Skills

Salesforce testing

Experience Cloud testing

Financial‑process testing

Integration testing

Regression discipline

Delivery tooling

Communication

Overlap with US time

Software QA experience

Tools

Jira

Confluence

Git basics

Postman

SFDX

GitHub Actions

Job description

This is a full-time Engineering Square role placed with the client. You manually test every change before it is released and run regression before every release — across Experience Cloud partner portals, a consumer-lending platform and the Salesforce NetSuite integration — working inside the client's Jira boards and CI/CD pipeline with the pod's Tech Lead and developer as your daily partners. You own the test evidence on every story.

RESPONSIBILITIES

• Test every change before release: manual functional testing of Apex, Lightning Web Component and Flow changes on both Salesforce orgs against the acceptance criteria in the Jira ticket; exploratory testing around the change
• Run regression before every release: own the regression checklist across portals, lending flows and integrations; execute it in full before each release; keep it current as features ship; record the result as release evidence
• Test Experience Cloud portals: partner and customer sites — self-registration and onboarding, login including federated single sign-on, sharing and guest-user visibility, page and LWC behaviour across partner roles, personas and devices
• Test lending flows: application intake, status visibility, document and e-signature steps, and post-origination hand-offs (funding, disbursement, servicing) built on custom objects alongside the managed loan-origination package
• Test integrations end to end: the Salesforce NetSuite quote-to-cash sync (customer/account, product and pricing, opportunity → sales order, invoice and payment status back-sync), partner APIs and Platform Events — field mappings, error handling and retries, duplicate and idempotency checks, and record‑level reconciliation across Salesforce, NetSuite and Snowflake
• Attach documented test evidence to every story before release — test cases, results, screenshots and defect logs; log, triage and retest defects in Jira; keep test plans and the regression checklist current in Confluence
• Join the client's daily standup inside the overlap window; report test status, risks and blockers directly to client stakeholders; provide the testing line for the Tech Lead's Friday written summary

CONTEXT YOU WILL WORK IN

Two Salesforce orgs. The manufacturer runs a Sales, Service and Experience Cloud org with an installer partner portal (self-registration, knowledge, support). Its consumer-financing affiliate runs a separate org on a Salesforce-native loan and lease origination managed package, with its own installer partner portal (login federated to an external identity provider). Around both sit NetSuite (ERP — the Salesforce NetSuite quote‑to‑cash integration is the lead backlog item), Snowflake (financing and credit‑risk analytics), an AWS integration layer (Lambda, API Gateway, SQS) and an integration platform. Testing spans both orgs, the portals and the data hand‑offs between them.

MUST-HAVE SKILLS

• Salesforce testing: hands‑on manual functional and regression testing of Sales Cloud / Service Cloud — objects, fields, validation rules, Flows, profiles, permission sets and record‑level security; writes clear, reproducible test cases and defect reports
• Experience Cloud testing: has tested at least one partner or customer portal — user registration and onboarding, login and access across partner roles, sharing and guest‑user visibility, multi‑persona and cross‑device checks. Candidates who have tested a partner portal go to the top of the list
• Financial‑process testing: has tested a lending, financial‑services or order‑to‑cash process on Salesforce — understands status lifecycles, document steps, calculations and the sensitivity of the data; works on masked or synthetic data only
• Integration testing: verifies data flows across REST/SOAP APIs with Postman or equivalent; compares records across systems; working SOQL for data checks; reads integration and API logs to isolate a defect to the right system
• Regression discipline: builds and maintains a regression checklist, executes it completely before every release, and produces evidence a client can audit
• Delivery tooling: Jira for test management and defects, Confluence for documentation, Git basics; familiarity with SFDX and GitHub Actions pipelines; works to a release checklist
• Communication: camera‑on meetings, direct stakeholder communication in clear English; reports status without being asked; raises risks early, never late; works the US business calendar and US federal holidays
• Overlap: a daily overlap of at least 4 hours with US Pacific time (mandatory); confirmed in the first screen
• Experience: 1–3 years in software QA, including at least 1 year testing Salesforce and at least one portal or financial‑process implementation

NICE TO HAVE

• Test automation for the regression suite — Provar, Selenium or Playwright — run in the client's CI/CD pipeline
• Exposure to Q2 Cloud Lending / Symphonix or another Salesforce-native loan‑origination package; NetSuite or another ERP (order‑to‑cash flows); middleware such as Workato, MuleSoft or Boomi
• SQL against Snowflake or another warehouse for reconciliation checks; Data Loader and Workbench for test‑data setup
• API automation (Postman collections, Rest Assured) and bulk‑data or performance testing
• AI‑assisted test‑case generation and AI‑enabled testing workflows, on masked or synthetic data only
• Solar‑financing, renewable‑energy or fintech domain; prior experience working with US enterprise clients from offshore