I Waited Five Years to Join Salesforce and It Was Worth It
by Valerie Nadi
Starting the Journey
After graduating in 2011 from the J B Institute of Engineering and Technology (JBIET) in Hyderabad, Kranthi relocated to Pune where he joined India’s Center for Development of Advanced Computing (CDAC). Over the next three years, he applied his skills in Python, PostgreSQL, and other software languages to security and defence related projects.
Although Kranthi embraced his role, he was looking for something that combined new challenges with a family culture. Later that year, he learned Salesforce had been named a top workplace for exactly those reasons — opportunity and culture.
“Until I found Salesforce, it seemed most companies’ primary concern was growth and revenue, not employee happiness. But it was obvious that Salesforce really cared about employee happiness in and out of the workplace.”
In 2011, Kranthi applied for a role in software engineering. The timing wasn’t quite right, but his interest in Salesforce continued. Salesforce maintains a database of applications and searches them as new roles arise to find candidates whose skills align with our opportunities. So Kranthi was excited — and a little surprised — when a recruiter reached out years later to see if he might be open to discussing a new role.
The interview process included a coding assessment, three telephone and two video interviews while Kranthi was still in Pune, and one face-to-face interview in Hyderabad.
“All the interviews were friendly discussions. Not intimidating encounters where I was expected to have the right answer to tough questions. Interviewers were interested in how I might resolve a customer issue or how my approach to optimized coding could also maintain security.”
For the coding assessment, Kranthi was encouraged to use “smart skills” to optimize his approach to solving the coding problem. He was not expected to identify a pre-determined solution. Smart skills allow someone in a technical role to approach a problem from dual perspectives — that of the developer and customer.
“I recommend prioritizing quality code over completing the entire assignment. Salesforce wants to know that your code can maintain its standards for performance and security.”
Making an Immediate Impact with Space Reclamation
For any cloud-based company that hosts data for its customers, maintaining enough space for that data is vital. Salesforce continually invests in its storage infrastructure to meet this need. Nevertheless, as customers delete data from their Salesforce databases, the servers that hold the data become fragmented, so empty space cannot be reallocated to new data. Multiplied across hundreds of databases, this fragmentation wastes a lot of usable space.
In his first project after joining Salesforce, Kranthi developed an automated space reclamation framework using Python and Java. Database administrators (DBAs) can trigger space reclamation through a visual interface to the framework and the process is designed to run during off-peak hours, so it’s transparent to customers.
“Before the project, space reclamation was very manual. DBAs logged into each database and executed shell code to get the fragmented space back. But when I joined Salesforce in 2016, we decided to fully automate the process. Automation boosts efficiency by saving time, and in two years the project has reclaimed more than two Petabytes of data.”
The Pause that “Refreshes”
We communicate with customers four months in advance so they can prepare for the downtime refresh requires, which is about two hours. During downtime, customers can still use their Salesforce instance, but they cannot add or delete anything. Once the refresh is complete, customers will notice significantly improved performance.
“The process used to take much more time and it was very manual, but the time has been cut substantially with the automation tools we’ve built.”
Finding the Perfect Fit
Take the next step: apply for an open position today!