Someone suggested I try salesforce. I looked around a bit - it has tons of certifications (red flag?), doesn't seem hard to learn. Looks like there are enough jobs, as of now.
So my question is - can this be a long term career? at least 8-10 years? Are there interesting projects to work on, or is it similar to doing CRUD web development again?
Notably, our certifications are freely available at https://www.trailhead.com/. You can get started, learn, and get credentials for free. It is a great place to start, and we purposely made our learning and credentialing free so we could make it as easy as possible for folks pivoting mid-career into Salesforce.
I would be happy to point you in the right direction. My email is bret.taylor@salesforce.com.
Personally, I think that working with salesforce is the worst of CRUD development combined with the worst of SaaS platforms. If you want fun work, I would not recommend Salesforce.
Can you make solid money doing it? Well sure. That's not really the question, from what I read of your question. The question is if I spend n years doing this, when n is greater than 10 will I have learned anything that lets me step into the next thing.
However, myself and every developer I know hates it. Having to work with it full time seems like it would be one of the more soul-crushing jobs in tech. Plus you'll constantly be doing requirement discovery with non-technical stakeholders. So you're combining the worst parts of consulting with the worst parts of development. You specifically seem to want to avoid unfun jobs, so I recommend very strongly to run in the other direction.
Also, Salesforce development is a specialized field. What you're basically saying is that in the entire, vast field of web development you can learn anything new or find anything interesting to do, so you want to move into something much more specialized/narrow in focus?
Can you provide some more details on what you're currently doing?
- Salesforce could announce a massive change in priorities.
- Salesforce could be bought by a competitor.
- Salesforce could be [more slowly] replaced by a competitor.
The odds of any of these things happening in the next year are probably quite low. The odds of something like this happening in the next ten years is pretty high.
I can't speak to whether the work is interesting or not -- I would assume that's it's not much different from any other general business programming jobs -- but IMHO, having general skills and being able to learn new techniques is key to having a long-term career in IT.
I see it as a long term career. Salesforce has the tallest building in SF. They own Heroku.
Salesforce is not fun to work with. What is fun for me is being in demand making a ton of money.
The start may be getting good at the tool, but which of the more valuable?
1 - I can help you properly set up Salesforce to track your Sales team.
2 - I can help you increase Sales by 20% by optimizing your Sales funnel and putting your best people on the largest deals. We will use Salesforce to do this.
#1 charges hourly in comp with low cost locations. #2 gets equity.
Consulting is a blanket term I'm using for what is in many ways a jack-of-all-trades. These are seen by techies as a negative in many careers, but is a life-saver if you go the path of Salesforce. These include: analyzing proposals, communication with non-technical people, analyzing existing systems, change management, and influence without authority.
You need to start at the bottom and ideally get to work on some larger Salesforce deployments where you have limited responsibility. That'll give you space to learn with lower risk. You'll get to see some of these consulting skills in action over a few engagements if working with reasonable companies (do a lot of research on how companies treat IT folks.) This will help you adjust because the life of a great Saleforce dev involves engagement outside of IT.
If you don't have interest in developing these consulting skills then Salesforce will start to feel like CRUD web dev again. The skills open up opportunities to do more interesting things, or be involved in design of the systems, use newer Salesforce products, etc.
It's interesting that you complain about CRUD because 99% of web dev is CRUD when you look at all web dev. There are small group of devs who are working on startups, open source libraries, or unusual areas of web dev. Most people are just building business apps or sites that read and write data. Moving to modern frontend dev and the like is justified for various reasons among regular devs, but most often everyone really just wants the novelty after years of server-side CRUD. Nothing wrong with that, but we could be more honest and less defensive about it.
The problem with a lot of technical folks is they disregard Salesforce, but they aren't the target market. Salesforce is for all the large and mid-sized companies out there who need to move from an old process to a new one, which is why Salesforce focuses so much on "digital transformation" messaging. You can make millions in this space if you can align yourself with Salesforce + the skills needed there, and actually solve problems for executives.
On your certifications concern: I'd bet that each product can go quite deep and also a lot of large companies need people to do very specific things, which is why they look for niche certifications. I find most technically specialized folks can skip certifications and actually focus on solving problems for users.
But if you are sick of doing web dev because of "not doing anything interesting/fun" I would say there's a great chance you'll be sick really quick - most of the SaaS platform's developer experience are just horrifying.
Yes. I've been working in Salesforce Commerce Cloud for about 8 years (it was Demandware back then[0]), been a certified Commerce Cloud Developer the whole time, and got an Architect certification in December. I'm working for a support/integration partner agency, as opposed to a merchant. So instead of working on one thing everyday, I'm assigned to a handful of clients, whose storefronts are vaguely similar.
There's a stock storefront that new ones are built from, so most storefronts work the same, the only differences being external integrations like payment and order processing. It ends up being a narrow problem space that I've enjoyed working in, instead of a customized sky's-the-limit line of business app.
[0] https://www.salesforce.com/news/press-releases/2016/07/11/sa...
Second, if you want to love doing work with Salesforce or any other CRM, you have to really like business processes, otherwise, it will feel like boring CRUD work... So much of day-to-day for sales and customer success is spent working with really awful software (and lots of great software, badly configured), with lots of double data entry and copy-pasta going on. If you can help integrate, automate and build decent UIs, you are going to do very well.
Finally, when you become an expert on enterprise software three things will create opportunity: new features to implement/customize, new customers to migrate and price sensitivity. With Salesforce, even though they are a leader both situations are great for a consultant. Salesforce customers are also willing to spend money, and aren't as price sensitive (this is a good thing) as users of many other CRMs are.
Pros: Salesforce abstracts a lot of the DevOps/database work that I don't have a lot of experience with and lets me focus on building the applications we need. Much of my current work is building out Lightning Web components, which is your basic JavaScript web development work built on top of some pre-existing components provided by Salesforce. There is a ton of documentation and it's easy to pick up on things you need to learn.
Cons: Salesforce has a lot of quirks to it that you'll become familiar with as you get into it. Build/test/deploy cycles are slower than normal, but they are working on tools to make that experience better. In some ways, their focus on no-code is nice and it's really easy to get simple things done. In some cases though, it feels easier just to write code to get things done, especially if you suspect the feature you're working on will get more complicated over time.
All in all I'm not sorry for getting into this space. I've had enough variety in my jobs that I've done some work outside of Salesforce and I don't feel pigeon-holed. The Salesforce ecosystem seems to be growing and their is a lot of work available. I'm in my mid-40s so if I can get steady work over the next 10-15 years with decent pay, I'll be more than happy continuing work in this space.
FYI: I haven't bothered with any paid certifications though I do complete Trailheads when I need to learn something new as a way to both learn things and provide a signal to potential future employers that I know what I'm doing.
Currently I'm back home in the Netherlands making €95/hour or about €13.680 per month or about €164.160 per year which is about $200k US dollars at the moment of writing.
Salesforce is a product that will be replaced by others or better ones over time. It'll come with endless required certifications and, let's be honest, is being in a vendor-locked world going to be fun or GOOD for your career?
At least as a web developer you focus on open-source standards that are free for all to use and free to learn about. You will naturally evolve with future developments.
That depends. The question you want to ask yourself is, do you want to spend the rest of your career learning to use one limited toolbox or do you want to make your own tools?
If you're bored (and someone please correct me if I'm wrong here), you're just replacing one set of Legos you piece together with another, except this new set is much more specialized and limited.
Personally (although I have to give the COO cred for replying to this post personally) I wouldn't want to tie my horse to this one pole. You're basically a puppet to Salesforce whims. If they decide to become super evil, your career is now Madvillianry.
Are you one of those people?
Salesforce has an app store (https://appexchange.salesforce.com/). You could try making an app, and see how you like it.
You are good probably for your whole career