This post has been de-listed
It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.
Hello everyone, first I'd like to mention I'm not here because I believe Salesforce is an easy 100k a year in my pocket type of deal or a free pass not at all. I'm here just for information, I currently work in a production environment and obviously its soul crushing and unfortunately I'm quite good at production manufacturing so most of my value at my job is there and I'm trying to change that.
My company uses Salesforce and more specifically Rootstock and I have some experience with Rootstock already. I've tried to do some research and it seems Salesforce can be such a broad deal so many roles its ever evolving I'm having trouble pin pointing certain things. So as for my question I'm just wondering what is your role/job title and what do you do everyday? Look at reports? Look at code? I'm trying to see if it's a realistic path to set myself on I enjoy technology and I've enjoyed using Rootstock thus far and I know I need a change. I don't mind doing all the certifications and training and I know I can get on the job experience at my current company. But I just want to know what people actually use it for on a day to day basis in their roles. Obviously I'm reaching out to the people I work with and use Salesforce as well but I wanted a more open view with more opinions from people. And please feel free to be specific I'm here because I want the broad scope not just the good parts. Thank you all very much it's much appreciated.
Salesforce Solution Architect (50m / yr company)
I start with a standup with the team to go over progress and solve any issues they are facing. I help prioritize their day if needed.
I check email for any fires that need to be addressed then put email away for the day.
I lead/listen to Salesforce planning, project status, stakeholder needs. Gather requirements, put together tickets, design solutions.
Then the hardest part - I think. I try to think about how we accomplish business needs in a way that we can plug and play an unknown acquired business into (our growth model is mergers and acquisitions).
I then will spend time building things that are above the current skill of my team, write documentation, review tools to acquire, manage budget, and a million other things.
As part of a smaller company I wear pretty much all the hats and then some. Comp is ~200k. 8 years experience. College drop out / high school drop out. In my 30s.
Subreddit
Post Details
- Posted
- 1 year ago
- Reddit URL
- View post on reddit.com
- External URL
- reddit.com/r/salesforce/...
Tickets from “need a new user created” to “help, I broke this”. My system is that everything comes in as a ticket, is evaluated by my Jr. If it needs more work than say 48hrs it is then moved to Jira for my review, I can then deny it, roadmap it, or whatever else needs to happen to resolve it.
Projects - like we just made a large change to the way we handle currencies and are testing our new method this year. We gathered requirements, collaborated with finance, provided a PoC, implemented, and now are working on reporting out the changes and how they impact our book of business.
These are small examples that run in parallel with other project/tickets.