Search
Twitter
« Tips for a Successful Salesforce | Main | Hit Again: Salesforce.com's Performance Issues »
Tuesday
Aug072012

Hire Vs. Train 

 

Choosing the Right Salesforce Talent

When it comes to Salesforce (SFDC) and its tight market for talented admins & developers, many organizations are faced with the challenge of whether they should hire an experienced professional or train a current member of staff. There are many factors that dictate whether it makes sense to train an employee from within or hire a seasoned professional, the following are a few of which:

A critical factor to consider is the size of your SFDC instance. The fact is, the bigger the SFDC instance the more complex its customizations and processes are. Ask yourself, do you have the bandwidth and the flexibility to train for an admin or go for an immediate hire that can handle such a big-user base and may consequently result in an overhaul of the entire structure.

Another factor to consider is your existing staff and whether you already have an experienced SFDC admin who’s capable and willing to mentor and train internal employees. If so, then promoting an existing employee is the feasible option here as it can be a great morale booster.

Third, what is the status and nature of your SFDC instance? What are the future plans for your organization? Will fundamental business processes be changing? If you have an established and prominent SFDC instance that’s optimal in performance, you might be in a position to promote from within your organization.

Lastly, how adoptive are executives in your organization? Is it within their capacity to wait for the employee to ramp or are they leveraging SFDC analytics and are in for need new reports/dashboards on a regular basis?

In order to shed some more light on the relevance and significance of hiring a SFDC expert VS training one, I talked to several SFDC developers and asked them what the hardest thing they had to adjust to when moving from another language over to Salesforce development. Here is some of what they had to say: one particular factor that echoed with most of the developers is the fact that they had to adapt and understand SF Apex governor limits, which are positioned to refrain from sloppy code that would otherwise unintentionally bottleneck their cloud: “ Saleforce governance and limits is by far the most maddening hindrance to productivity and overall application robustness.”   

About the cloud: The transition from traditional desktop-development to cloud-based development was a little tough at first. Although SalesForce offers a plug-in for the very popular desktop IDE (Integrated Development Environment), Eclipse, many operations are happening “over-the-wire” and on the SalesForce platform itself, not the developers local machine. Cloud-based development is not really using your local resources which has both pros and cons. I think that is really the ice-breaker in bu. You are making changes in a local tool, but saving code, compiling, syntax checking, unit tests, etc. are actually happening in the cloud….”

About ramping up and training for developing in Salesforce:  I personally found the APEX tutorial to be a huge fire-starter. Let me say first that I loathe the hand-holding and pace of a tutorial and normally skip them. I am a dive in and get your hands dirty sort of guy. However, I humbly admit that the tutorials covered a great deal of ground quickly. I spent almost a day walking through the tutorials, making notes, and researching some of the questions that remained. In the end, I came out with a surprisingly comfortable sense of the available features, tools, and language. This allowed me to gain so much traction that I was able to write some fairly sophisticated code the very next day.”

 

 

 

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
All HTML will be escaped. Hyperlinks will be created for URLs automatically.