A podcast episode about Salesforce admin interview skills.

What Are the Key Skills for a Successful Salesforce Admin Interview?

By

Today on the Salesforce Admins Podcast, we talk to Jason Atwood, CEO and Co-Founder of Arkus. Join us as we chat about how to land your first Salesforce Admin role, from where to find good opportunities to how to prep for the job interview and more.

You should subscribe for the full episode, but here are a few takeaways from our conversation with Jason Atwood.

How Salesforce Admins should split their learning time

We’re talking with Jason because he spends a lot of time interviewing and hiring people for Salesforce roles. So if you want to be a Salesforce Admin, how should you split up your learning time?

Jason recommends following the 20/30/50 rule. Spend 20% of your time on Trailhead, 30% on acquiring certifications, and 50% on finding some way to gain experience. This split corresponds to how important they are on your resume.

  • Trailhead: Becoming a Ranger is priority one, followed by getting some Superbadges. Take the time to set up your profile with a photo, a description of yourself, and a custom URL so that you look like you’re an active member of the community.
  • Certifications: When is the best time to take a Salesforce certification test? As soon as possible! If you don’t get it this time, you can use your results to help you prep for the next exam. And if you do pass, you can get the next cert sooner.
  • Gain Experience: Volunteering isn’t the only way to get experience. You can enroll in a program where you build mock projects in Salesforce, or just build something on your own. The important thing is to have projects you’ve built in Salesforce that you can demo in your job interview.

Interview preparation and skill assessments

When you’re going for your first Salesforce job interview be ready for some sort of skill assessment. Time pressure is usually a factor in these tests, so Jason recommends doing a practice run.

Talk to a friend, find out what kind of data they collect, and then give yourself a day to build them an app. It could track the books they’ve read or the distance they’ve run, the important thing is that you don’t know what it’s going to be before you talk to them. 

All admins are consultants

It’s also important to realize that an interview isn’t just about showing your skills—it’s about showing who you are. It’s a chance to listen and empathize with the person on the other side of the table. It’s a chance to share something that stood out to you in your research about the company. And most importantly, to show who you are by asking questions.

Why does Jason place such an emphasis on soft skills in a Salesforce Admin job interview? Because, at the end of the day, every admin is a Salesforce consultant for their organization. You talk to people about their problems to get requirements, come up with a solution, and then iterate on that solution.

We touch on a lot more in this conversation about how to look for Salesforce jobs, developing listening skills, and what it’s like to be a Salesforce consultant, so be sure to listen to the full episode and subscribe so you don’t miss out.

Podcast swag

Learn more

Admin Trailblazers Group

Social

Full show transcript

Mike Gerholdt:

I got an idea. How about we tackle the hardest question on the Salesforce Trailblazer community? That’s right. This week on the Salesforce Admins Podcast, we’re going to look for advice on finding your first admin job and doing the interview, getting experience, and more. And we’re going to do all that with CEO and co-founder of Arkus, Jason Atwood. Jason and I chatted at TrailblazerDX and really wanted to dive into this topic. Now, before we bring Jason on, I just want to make sure that you’re following the Salesforce Admins Podcast on iTunes or Spotify. That way, when new episodes like this one come out, they’re automatically downloaded to your phone. But enough about that. Let’s talk about finding that first job or even finding your next job as a Salesforce administrator. Oh, I almost forgot to mention we tackle the myth of “but it’s just an admin job.” So with that, let’s get Jason on the podcast. So, Jason, welcome to the podcast.

Jason Atwood:

Thank you for having me. It’s been a long time since we’ve podcast together.

Mike Gerholdt:

I know. I was thinking back; well, we were just reminiscing of the days at the Marriott Marquis and the Arkus podcast.

Jason Atwood:

Yep. You were on an episode of CloudFocus Weekly. We had it as part of our trivia once there was only four or five guests ever on the podcast, and you were one of them.

Mike Gerholdt:

Snuck in, only proximity. I’m going to say. So catch people up. What have you been up to?

Jason Atwood:

Well, since then, whatever that was, 10 years ago. Yeah. So I am now the current CEO and co-founder of Arkus. We’re a Salesforce consulting firm. We deal mostly in the nonprofit space, and we’ve grown from that little company back then. We’re almost up to 75 people. And now I run around between putting out fires, talking on podcasts, and trying to educate myself on the whole changing landscape of technology.

Mike Gerholdt:

Yeah, it does feel like in the last decade, it’s gone from everything we know to a brand new world.

Jason Atwood:

It certainly is. And I just spent three hours at a Heroku dev meetup and could hang there mentally for a bit, but they lost me at a little point. So it’s both fun, interesting, and challenging to stay up with all this stuff.

Mike Gerholdt:

So one of the things that everyone’s trying to stay up with is the ever-changing job market and hiring. We see a lot of the questions in the Trailblazer community from new admins, people getting into the ecosystem that want to become Salesforce admins, people in the ecosystem that are looking for jobs, or maybe have kind of hit a career plateau. And you and I were chatting, and boy, I think it’d be fun to kind of delve into that topic with you.

Jason Atwood:

Let’s do it. I have some experience in hiring people over the last 15 years, so I can certainly talk about it.

Mike Gerholdt:

A little bit more than me. More than me.

Well, let’s get started. So let’s start fresh. There’s a lot of new people. As we were talking about in the intro, there’s a lot of new people coming into the ecosystem that maybe don’t have tech advice. They are doing Trailhead modules, completing challenges, getting a lot of badges, trying to round out their resumes, and they don’t know A, what to look for, or B, what to put on their resumes. So somebody that’s hired a bunch of people and been around for a long time, let’s start there with some of your advice and where they should go.

Jason Atwood:

Sure. This is a very common thing, and the first thing I would tell everybody is relax. It’s going to be okay. I know it feels daunting, and you see these triple all-star rangers and you see all these, the hoodies, and you see the people with the 15 certifications and 10 years of experience, and you feel like, “How am I ever going to get there?” You will; you’ll get there. So the first thing is just to take it easy and not to get too worked up on it. It does feel like a lot. It’s a very big community and filled with lots of hungry people for jobs, a lot of recruiters, a lot of activity. When I talk to people about getting started in the ecosystem, and certainly on the admin track, and we can talk about other tracks if you want, but on the admin track, I kind of say all those things matter.

So when it comes to certifications, when it comes to Trailhead, when it comes to experience, they all matter. And usually the question I get is, “But what should I focus on?” And so I came up with something, I maybe made it up years and years ago. I call it the 30, 20, 50 rule, or 20, 30, 50. It doesn’t matter; you can break it up anyway. And if you’re going to take your time, right, you’re in the hunt for a job, and you need to do the education, you need to get enabled, you need to build your experience level. I break it down into those percentages. So 20% of the time, I’d focus on Trailhead. And the trick for Trailhead is A, you just have to be a ranger. We don’t even look at people who aren’t rangers. I had an intern apply the other day, and I said, “No, you’re not even on Trailhead. Go get a ranger before I even talk to you.”

So that, to me, is just a minimum bar. Just go be a ranger, and then if you can go up from there, that’s great. And then, if you’re still in your Trailhead worlds, the thing that we then look for besides looking at their profile, is it filled out? Have they thought about it? Have they created it like LinkedIn? So second advice on the Trailhead side is treat your profile like LinkedIn: fill it out, put your picture, put your description, do all the things. It’ll probably take you no more than a half an hour. Make your URL; you can make your customized URL so people can find you; do all the things so it looks like you’re part of the community, right? Make sure that your profile is rich and full. And then the third thing on the Trailhead side of things is to go for super badges.

So I can look at double ranger, triple ranger all day long, but if I don’t see some super badges and I speak from someone who doesn’t have any super badges.

Mike Gerholdt:

Oh, no.

Jason Atwood:

I know, I know, it’s on my hit list for this year. I know, I know, I mean, I have 15 certs, and so I have some experience, but I’d say, get some super badges. We see that when we look at that as a higher level of dedication and of expertise, because, as you know and as I’ve been doing them, they’re difficult. They show that you have really dug in, and they’re more than just answering some questions or watching videos, or getting fun ones. I love badges, but the super badges really show that kind of a deeper level of education and sort of just being in the Trailhead world. So that’s the 20%. Then the 30% is certifications.

You need to have both. You can’t have one without the other. I don’t know what that commercial was, peanut butter and chocolate or something, but-

Mike Gerholdt:

Yeah, I think so, yeah.

Jason Atwood:

You might be [inaudible 00:07:08]. Certifications are important; you should focus on them. What I tell people is you need to get them, but you can’t stall. Most people, I think, when we talk to them and we’ll find in the ecosystem, say, “Oh, I’m thinking about getting that, or I’m planning to get that one next year.” And our advice is, “Nope, go get it. Go get it now. Go take it. Go take the test a couple of times.” Do whatever it is you can do to start your certification journey; don’t put it off; don’t procrastinate on it. You don’t have to be perfect; just go get some. And obviously there’s a path of which ones you should get, blah, blah, blah.

It depends on where you’re going in your world, but having at least one or two certs is kind of a bare minimum. So if you’re starting off and you’re trying to get into the ecosystem, that’s your 20 and your 30, and then the 50 is the hardest part. And it’s just hard to tell people because it’s the experience. The third thing we look for is experience. I want to see that you’ve done something obviously new to the ecosystem, harder to have the experience, but that’s where I say spend 50% of your time trying to gain that experience. There’s the old adage: try to go work with a non-profit. Although there’s some pushback on that nowadays because of the complexity of the platform, you don’t want to hurt a non-profit.

There’s definitely… Get in in a way, there’s programs, there’s tons of programs out there that will help you do mock projects and things where you can just get your hands dirty. And even if you have to build your own thing that you’re going to demo, you got to get experience because I’ve not hired people with 22 certifications, and because it didn’t add up to any experience, and I’ve seen people with tons and tons of experience with zero certs, and I would hire anyway, just from the experience. But for me, that’s how I tell spend your time: 20% trailhead, 30% certifications, and 50% getting that experience.

Mike Gerholdt:

I think that 50%, that part that you’re talking about is always the part that feels like the hardest to get into. Because if you’re not in tech and you don’t have any experience and you’re trying to land that first job, that can feel like, “If I could get this job, then I could get the experience.” And so, part of that lends to my next question is, so you’re new, we’ve checked all the boxes on filling out our profiles and done that part. What should I get ready for when I interview?

Jason Atwood:

So every interview’s going to be different, obviously, but a lot of places are using assessments now. So I would say be prepared for an assessment. That means functionally, they’re going to ask you to do something; they’re going to ask you to build something or take something they’ve done and turn it into something on the platform, using Salesforce as the platform. So I would just be ready for that, be prepared, be okay with it. Even do mock versions of it, go have a friend, and I have to given this advice to some people, but go have a friend, sit down with them, talk to them about what they do, and you’ll uncover something that they’re collecting data.

And as soon as you can figure out what the data they’re collecting, whether it’s books or they collect comic books, or they’re a skier or they’re a runner, anything you do, you can just come up with, “Ooh, what if I built you an app to track that?” So be prepared to have an assessment of your skills and be able to show that in a short period of time. Meaning it might be a take-home. Sometimes it’s a take-home. Like, “Hey, go do this over the weekend.” Other times it’s, “You have an hour; come back and show us what you did.”

Mike Gerholdt:

Ooh!

Jason Atwood:

So I’d say… Ooh! Yeah, I know. I’ve been doing that for 15 years to people. Trust me. I’ve seen a lot of, oohs.

Mike Gerholdt:

I would imagine.

Jason Atwood:

Even had one person pass out in the…

Mike Gerholdt:

Oh, my. Oh, goodness.

Jason Atwood:

It happens.

Mike Gerholdt:

You get an extra hour now.

Jason Atwood:

Yeah. So I think that it’s coming more and more in the ecosystem, because again, when you look at a resume, when you look at LinkedIn, a lot of it’s just you can’t tell whether they know what they’re doing. If you actually do an assessment, you can then assess, “Okay, you know, you functionally know how to do things.” So I’d be prepared for that. The other thing is, I think when you’re really, especially in the new, just be honest about what you do and do not know. That’s really, really key. Don’t fluff up your resume; don’t put things that you don’t know; don’t put clouds, don’t throw in data cloud if you don’t know what data cloud is and haven’t used it or can’t really explain it. Just because you took a Trailhead on something doesn’t mean that platform or know that cloud. So I’d really say be honest with what you know and the clouds, and the products, because that’s going to be super important in the interview process.

Mike Gerholdt:

Wow. How much… In prep work for resumes, there’s a lot of AI tools out there, so I’d love to know your perspective on both sides of this one: how much do you, as somebody hiring, kind of look for, “Oh, they used AI to generate most of this resume?” And on the flip side, how much should somebody building their resume that could really benefit from an AI tool? How much should they lean into it?

Jason Atwood:

So I’m going to be the strange answer on this one, or…

Mike Gerholdt:

Oh, good.

Jason Atwood:

Yeah, because I’m going to say, resumes don’t matter.

Mike Gerholdt:

Okay.

Jason Atwood:

They’re just checking a box. When people get to me in the interview process, they’re beyond the resume. So yes, you need to have a resume; you need it because that’s the part. It’s like you have to have the internet; you have to have a way to fill out the form. So you need to have a resume, and it should have your accomplishments and stuff on it. But I don’t look at resumes because they’re just lies. They’re just you telling me all these things, and sometimes I don’t know if any of that’s really true or not true. So to me, it’s like it’s just a checking the box. “Yes, you have to have a resume. Yes, it should be okay.” Honestly, your LinkedIn profile should be your resume, right? Because that’s real; it’s on the web. And if you’re lying, someone might actually call you out for it.

“Hey, you didn’t work at that company for 10 years.” So I would say focus more on the LinkedIn. Because I’ll look at that. If you gave me 10 minutes, I’d look at your LinkedIn first. I would not look at your resume, what you’ve put on, rather than what your actual history has been. That being said, you want to throw all this stuff on there for this ecosystem. So I do think showing work that you’ve done and really pointing to problems you’ve solved, if you really think about any job, especially as an administrator, you’re a Salesforce admin, you’re basically solving problems all day all.

And you’re communicating. So two things that I tell people about the resume and the process is how do you show that you’ve solved problems in the past in your resume, and then how do you show that you are a great communicator? Because great communication, it doesn’t matter what, I mean, well, not what job, but certainly in this world, you are basically talking to people, helping them out, doing stuff, re-communicating with them, getting what they need to do, building it, whatever. You might work with different groups or whatever. But that communication skill is something we deeply look at. So again, if you’re going to focus on stuff, don’t so much focus on your resume as focus on how to be a great communicator.

Mike Gerholdt:

That’s really good advice because I have been at that level where people show up and the resume looked good, but they couldn’t facilitate the conversation or articulate any kind of answer in the interview.

Jason Atwood:

It is a skill that not a lot of people have, but it’s a skill, you can learn it. So a couple of things to put into that communication bucket. We’ll go down a little rathole here.

Mike Gerholdt:

Yeah, let’s do.

Jason Atwood:

One is empathy.

Mike Gerholdt:

Okay.

Jason Atwood:

Have the ability to show empathy, and that means sort of having a conversation with somebody and throwing in stuff that’s like listening to them, talking to them, obviously pulling out information about them, but having the empathy when they say something’s not going to happen or whatever, they could say, “It’s a rainy day.” I look for it in every interview that I do. Now this is going to be on the podcast; everybody’s going to know this, but I will actually throw things into my talk track or as just the warm-up when you’re sort of, “How are you and what’s going on?” I will always throw in something to test empathy.

I’ll say, “Oh, I’m okay, but I didn’t sleep well last night. Or I had a bad egg sandwich this morning, or I’ve tripped over the dog when I came into the room.” And I just listened to hear what they react. If they go, “Oh, that’s terrible. Oh, yeah, I know dogs can be really difficult. Or you know what? I get my egg sandwiches from downstairs, whatever.” But hearing that back of that empathy, super important. Second is actually listening, so I will listen to people, how they listen to me. Are they interrupting me? Are they talking over me? Are they going? Yeah, yeah, yeah, yeah, as I speak, I listen for their real intent and true conversational skills. And so the ability to actually listen, pause, and then answer is a really big; it’s a great skill to have. And so the people who can do that, I know that they can do almost any job better because they’ve intently done that listening skill and they’ve got it working. So those are two that I throw out to most people when they’re trying to build their conversational habits.

Mike Gerholdt:

Yeah, I’m listening to you answer that, and I’m playing devil’s advocate in my head and saying, “Maybe people are hearing Jason say this because he’s hiring consultants.” So why do you think this also translates over to people that are embedded in different work groups, or teams, or have stakeholders within an organization and aren’t consultants, like for your organization?

Jason Atwood:

Because basically, being an admin is being a consultant in one organization. You are a consultant. What are you doing? You’re talking to people; they’re coming to you with their problems; you are getting their requirements; you’re satisfying their needs; you’re working with them; you’re iterating; you’re changing it; you’re updating things, and then you’re presenting it back to them. The thing that changes when you become a consultant is you’re paying for someone’s time, which then becomes a whole other thing. But also, you might be working with other organizations, and the level of expectation of how you do that and your expertise goes way up. And this is something I tell, I warn people about moving into consulting is that when you’re an admin, you have the ability to take some time. Someone says, “Hey, can you build me these three dashboards that I want to track my sales forecasting?”

You go, “Sure,” and you can go Google it, and you spend a week, and you come back, and you’re like, “Here’s your three dashboards.” They’re ecstatic; they’re like, “Great, thank you.” They don’t care that it took you three weeks or whatever, and then you had to ask your friend and Google it or ask ChatGPT to do it for you. In the consulting space, it’s different. They don’t ask, “Could you build this for me?” They say, A, “What are the options to build it? How long is it going to take you, and can you get it to me by next Tuesday?” So the expectation level of what you’re doing goes way up, and they expect you to be expert. They don’t expect you to ever say, “I don’t know, but I’ll figure it out.” As an admin, I said, “I don’t know. I’ll figure it out.”

“Oh, you want to build some tracker for your feedback form? Sure, let go figure it out.” Go away for a week, and I’ll come back and show you something. So I think that’s part of it, but as an admin, you’re still doing all this stuff. It’s the same stuff inside the organization. You’re just not working with external companies or people; you work with internal people. So you still have Mary from accounting coming over and wants to synchronize with the QuickBooks, and you still have the CEO come over and they want an update to some dashboard because they can’t figure it out, and you’re doing the same stuff; it’s more internal, more ad hoc, generally.

Mike Gerholdt:

I mean, I couldn’t agree more. Also, Mary from accounting, they always want to, for some reason, can’t seem to get opportunities flowing through your sales org, but let’s integrate finance.

Jason Atwood:

So true, so true.

Mike Gerholdt:

But you kind of led into that. So what are the different jobs, or different tasks, types of jobs that admins would tackle within an organization?

Jason Atwood:

Yeah, I mean, we kind of started in there. You do become an internal consultant, but I think you first off just think of what, especially when you’re applying for it, and this goes back to sort of the applying and getting the jobs’ thing. When you’re looking at the organization, you obviously want to know what their Salesforce landscape is. So if I were in the interview process, what I would do is come loaded with a bunch of really good questions, and I would pepper that person with tons of questions about their Salesforce instance, or, as we call it in the biz, we call it their org.

But I would come in with, “What kind of licenses? How old is it? What kind of integrations? What kind of applications do you have? When’s the last time you did a health tech? Do you use permission sets or permission set groups? Or did you flip the lightning yet?” I mean, I would be peppering them showing my expertise to get that admin job. So that’s just on the interview side; I just want to throw that in. But coming back to what you do, again, it really depends on the organization, and this is actually a myth that is out there in the ecosystem, is that admins get bored and admins don’t get to play with lots of different clouds, and admins don’t do a lot of diverse things. That’s completely not true because it depends on what organization you’re with. I was with a company who had 375,000 people.

I had a team; I had five people, or five, including me; we were all admins; that’s what we did. And we had 12 different production orgs, 12 orgs with production, and I think nine different applications running in them with thousands and thousands and thousands of users. We were not bored; we had plenty to do; we were playing with great, big, unlimited licensing and integrations and projects, but we were admins. At the end of the day, we were admins. Same thing: you go work for a small company that’s four… I don’t think anyone would hire a full-time admin with four people. But the smaller the organization who’s just using Salesforce for one thing and has no chance of expanding it or doing it, or going anywhere.

Yeah. You’re going to get bored, right? You come in, you’re going to help out Mary in accounting, you get that one project done, and then they’re going to be like, “Can you reset passwords all day?” So I think as part of the interview process to pulling it back in to that, and when your job seeking, you should be really interested in what their, especially if you want to be a Salesforce admin and you really want to do it full time, what’s their Salesforce roadmap? Are they just solid? They have it, and they have had it up and running for five years, and that’s it? Or do they have things that they want to do? New stuff you can build? Do you want to do the integration with that? We want to bring in marketing cloud next year. We’re looking at how to do predictive AI, whatever.

So if I were bringing more questions as the trying to get the job, I would bring in that to the organization. I’d say, “What do you guys, where’s your roadmap? Or do you not have one?” And I think that would show as a hiring person; I’d be like, “Oh, they’re forward-looking.” And it’ll also give you the idea of: “Are you going to get bored in six months?” Because you don’t want to get bored in six months.

Mike Gerholdt:

Right. Although maybe a smaller footprint would be really good if you’re looking to get that first admin job.

Jason Atwood:

Exactly. Exactly right. But then you have the counter, right? You have a smaller footprint, but they have 40 users, and they only use it for service. So you get in, you do some work, you do all the stuff, and then you’re like, “Now what?”

Mike Gerholdt:

Right. So you brought up myths of admins, and one is, well, “I don’t get exposed to enough clouds,” and I’ve heard that at various events. “Well, we only use data cloud, or I just don’t get to see it.” And I feel like, and this still exists, all of these articles on admin to something else, as though admin is just the front door; all you got to do is get in and do that for a few months. But the real money and the real challenge is elsewhere. What would you say to that myth of just an admin?

Jason Atwood:

I think it is a bit of a myth, and it makes admins and being an administrator, Salesforce administrators feel like this… It’s like you’re the fry person in the back at McDonald’s. It’s like, “Well, I don’t ever go back and cook the hamburgers.” I don’t know. And it’s not true.

Mike Gerholdt:

Although the fries are kind of the best part.

Jason Atwood:

That’s true. I actually worked at McDonald’s, and I was the fry person, so that’s why I brought it up.

Mike Gerholdt:

Yeah.

Jason Atwood:

But yes, at some organizations, you could be the one admin, and that could be your role for a long period of time. And you could get bored, and it could just be a starter. At other organizations, you could run an entire group of admins. You could have six or seven admins, you could be part of a team of people supporting a lot of different Salesforce instances, and it could go anywhere from just administrative down to sort of more the solution architect type of stuff, or more towards the BA towards so stuff or more towards the development.

One of the things you and I have been in this ecosystem for a long time, what we were able to do 10 years ago on the platform with our clicks and what we’re able to do with clicks now, we’re programming. Let’s be clear: when we’re building flows, we’re programming; we’re just programming with a user interface. But that’s programming, and the stuff you can do is stunning, that you just couldn’t do with any of the tools unless you’re writing Apex. So I think even the idea that admins who are getting that technical acumen and are going into the more programmatic type of world of admin that could go long, there’s lots of paths you can go down for that. So that’s where I think some of the myths should go away because you’re not just the admin who’s building a report, adding a field to a page way out, and assigning a permission set. There’s many, many different pieces of that platform. And that’s before you even talk about the clouds; before you’d say there’s now, I don’t know how many clouds. There’s a lot of clouds.

Mike Gerholdt:

There is a lot.

Jason Atwood:

Yeah.

Mike Gerholdt:

Yeah. I mean, you brought up flow. I think back to the days of, “Boy, if I could just stand up like a window pane that a screen that people could input the data into as opposed to just editing raw right on the record.” And now we can do that, and you can do that just using the interface. You don’t have to try a single line of code, which is…

Jason Atwood:

It is stunning what you can do with that tool. And it’s one of the things that has left me a little bit behind because I’m old school admin. I’m a work-for-rule person. And for that, I would’ve gone wrote in a user story and had someone written up a Visualforce, and with Apex in the background, and now it’s… The stuff that we can produce with flows, screen flows, and even the call-outs. I was watching the call-out today, a flow that made a call-out to a Heroku Dyno that did a hookup to a Postgres database that pulled in AI predictions. I was like, “What?” So yeah, the world of an admin is becoming very, very broad in some ways.

Mike Gerholdt:

Yeah, no, I agree. And you can also now trigger flows through prompts and have it call AI. And I mean, in a year from now, this is all going to sound like super, “Wow, they were impressed they could do that. Now look at where we are.” kind of stuff. One thing we didn’t touch on is there’s a lot of job places to look at and career stuff. Often, when looking for a developer architect, I think those are a little more defined also, especially with developer, they’ve got experience in writing developer job titles for other platforms. So it’s very easy to translate that over to Salesforce. What are things that an admin should look for in job descriptions? That maybe if the title or description doesn’t say Salesforce admin, that will be the role?

Jason Atwood:

Yeah, it’s a tough one because, I mean, the easiest thing to say is look for the keyword Salesforce. Obviously, there’s going to be some sort of piece of that. I think you’d have to go a little old-school and think of the platform and what it’s doing. So I would start to look for things that were based on what Salesforce, the platform’s doing? Is it sales, right? Is it marketing? Is it service? Is it nonprofit? Especially in the nonprofit space, which is for me. So we would look at grant writing, fundraising, and all that stuff, which could be keywords for, we’re using Salesforce in the background, but we’re using it to do all these things. So I guess the meta hint without giving you the keywords is: What is this organization doing? What is the output of their world? And then looking at what the tool set they’re using.

They might not be Salesforce, right? There are other ways of saying the word. They might say something like health cloud and a health cloud administrator, and you’re like, “Well, that’s Salesforce.” Or they might say, “net-zero cloud.” Or they might say, “nonprofit cloud.” Again, not saying Salesforce, but that’s what it’s based on. So sometimes, as an administrator and as part of this ecosystem, you have to know that there are products that are sitting on top of the platform that don’t necessarily say the word in it. Remember when they named everything Force? Everything was Force something Force, this Force, that Force.

Mike Gerholdt:

We had everything named Lightning for a while, too.

Jason Atwood:

That too. That was fun.

Mike Gerholdt:

We like to do that a lot. I think everything’s named Einstein now.

Jason Atwood:

Pretty much.

Mike Gerholdt:

I’ll probably get in trouble for saying that.

Jason Atwood:

Yes, you will.

Mike Gerholdt:

But you could do the bingo card of name everything, Einstein, Lightning, Force, and then you’re covered.

Jason Atwood:

I’m going to win that Bingo.

Mike Gerholdt:

Einstein, Lightning, Force, and then the actual product. Then you’re covered.

Jason Atwood:

Totally.

Mike Gerholdt:

I was looking through all my notes, roles and descriptions and interviewing and challenges, and certifications, and I feel we touched on a lot. What is something that you feel we missed, that you talk about, that you bring up that maybe people aren’t thinking about when they’re looking to interview or get an admin position?

Jason Atwood:

Sure. I think there’s a couple of things. A couple more things I would, if I were giving advice, which I happen to do all the time.

Mike Gerholdt:

You’re full of advice.

Jason Atwood:

I’m full of advice, maybe too much. So one thing, and this is just generic to not Salesforce, but as anybody looking for a job, cultural fit, I think, is becoming more and more of a need. And I think, as people applying for jobs, you should be looking at it both ways. Do I fit that culture, and does that culture fit me? And that’s do my values and the company’s values or the organization’s values align together. And asking a lot of questions around culture is going to become more and more important, especially because we go do remote work and all that. So I think what we used to think of, like, “Oh, we had coffee breaks and pizza parties for every quarter,” is now a much bigger discussion. So I would say bring culture into the conversation. Another tip that I hadn’t given yet is just preparedness.

It seems silly to say you have to be prepared for an interview, but I can tell you the amount of people who show up who are not prepared, they’re just not prepared; they don’t know their resume; they don’t have good questions; they don’t know how to talk to their experiences. And I’m stunned when it happens, but it happens a lot. And one of my little pet peeves, I’m giving away all my hints, boy, anybody interviewing is going to be able to nail the interview the next time they get to me.

Mike Gerholdt:

Yeah, you say that, but I bet not.

Jason Atwood:

Probably not, right? No one’s even going to pay attention. But having really good questions is something that I look for. Again, we work in an industry where being able to ask your users what they want and question them, and being insightful is a great skill. So if I get to the end of one of my diatribe speeches and I say, “Do you have any questions?” And they’re like, “No, I’m good.” I immediately go, “Okay.” And then I’m not good because I… So have questions ready at the go; have them sitting in front of you on a piece of paper, on a sticky note in a NeverNote, wherever. It’s super important, and don’t be generic. Don’t say, “Where do you see yourself?” Don’t interview the interviewee.

Ask really stuff that’s based on homework you did. And that’s sort of the prepared thing too. When people come in and they say, “Oh, I read your blog post last week about blah, blah, blah. I was really interested about this key point.” Immediately, I’m like, “They did their homework; they know what they’re talking about, and they’re asking me something interesting.” Don’t say, “How do you guys do raises?” That’s not going to be; you need to have the questions about the culture or the stuff. I mean, I’ve had some really good in the past, but I’ve had some really terrible questions. And then two more, I’ll give you two more tips. This is like the hundred tips for interviewing the Salesforce Ecosystem Podcast.

Mike Gerholdt:

We’ll call it 98.

Jason Atwood:

There you go.

Mike Gerholdt:

So there’s two.

Jason Atwood:

Two more is you can never, if you want to get two skills. If I told someone to go get two skills before they get any job to be super useful on day one, two things they should be focusing on: data and documentation. Your ability to understand data is like you need to have it, you have to have it as a skill; you need to know data; you need to know how data interconnects with other data, you need to know how to report on it. It’s getting more and more and more important. So I look for data skills, even data nerds, people who say, “I love data.” So if you’re not that type of person, I would say these jobs are going to be tough. Because I don’t know anywhere in the ecosystem that we are not just really crazed about and or dealing with lots of data.

It is sort of what Salesforce is, in the back of all of it. So understanding data, taking courses on it, go learn SQL, go learn regular databases, go learn third normal form, learn it, and understand it because any of your skill sets that you have that are based in data will make you better at any job in this ecosystem. So data. Second is documentation, because one of the things you can do very quickly in any role is document things. You need to be able to document; you need to be able to take what people say, summarize it, put it into something, and spit it back out for people to take in. If you’re an admin, you’ve got to come up with a training plan or a training agenda. You are an admin; you have to come up with a user story; you hand it off to a developer or someone to build something.

Documenting is, and it’s, I know there’s Trailheads on it, and you can go to those, but really learning how to document even so much prove that skill when you talk to somebody and you follow up with an email. Follow up with an email that proved that you listened and that you’re following up with documentation skills, coming back with key points or things that you wanted or questions, all great ways to show. But I would say two things you could just learn to show up on day one to start working and doing things is know data very well and know how to document things.

Mike Gerholdt:

Well, that was a really good point. I would hammer on that cultural fit and question part a lot because I always feel like you and I are of a certain generation that we kind of almost interviewed in the hopes that they chose us, right? The best of the survivor, we get picked. But the part that really dawned on me as I moved through my career was I also need to interview that person to see, is this the type of person that I’m comfortable… Would I be excited to get on a call with them every day? Does this feel like the type of company that I’m going to be excited to go to work at? Or do I just want to get in to get in? And I’ve made the mistakes of going to work for companies and then realizing I didn’t ask enough cultural questions. The way things operate here and my expectations for this job are very different than what I had in my head, and it’s my fault because I didn’t talk about it.

Jason Atwood:

Yeah. And again, I think it’s different. Even again, culture was, I hate to say it, but it wasn’t really that much. It wasn’t that important. 20 years ago, I wasn’t worried about culture; now I think it’s above compensation.

Mike Gerholdt:

Yeah.

Jason Atwood:

I think it really is. And I’ve seen people go to places for less compensation because of a better culture. I’ve seen people leave terrible cultures that were highly paid. So really bringing that in, and that means how do they work? How do people collaborate? And you can ask these questions in the interview. You can say, “What are the three things you’re doing this year to help your culture be better or to improve your culture at your company?” If someone asked me that, I’d be like, “Ooh, wow. Okay.”

Mike Gerholdt:

That’s a good question.

Jason Atwood:

That’s a great question, right? You’re then learning A; are they doing anything to make it better.

Mike Gerholdt:

Right.

Jason Atwood:

Or ask about… One of the things that we take at Arkus as very important is when I was doing my key goals for the next five years, and I was doing some presentations and talking to the staff about it. I had culture as a fifth thing, and then after doing it, I thought, “Wait, no, that’s wrong. It’s got to be number one.” So for me, you ask a company, you say, “What are the main things you’re thinking about doing for the next five years? What are the five key things that you’re doing? What are your pillars?” Or whatever. And if they don’t say culture, then you’d be like, “Oh, why isn’t culture there?” And then you’ll probably catch someone off guard; maybe they won’t hire you there, but they should be thinking that keeping the company culture and embracing it, and making sure that it is… Culture isn’t something that you set up and then walk away from.

It’s not a database system. You don’t just go, “Oh, it’s set up, and it’s running in the corner.” It’s something that needs to be cultivated; it’s something that needs to be put into; it’s something that needs to be fed and loved, and thought of, and changed as the ecosystem and the world changes. Our culture changed when COVID happened, right? We had to adapt; we adapted to that; it wasn’t the same culture as before. When we were three people, now 75, but the culture’s different, but we’re adapting to that. So again, it is a really, really big point. It is something you can catch people on, you can ask, and everybody likes to talk about their culture. Everybody will tell you that they have a great culture, but that’s how, as an interviewer or interviewee, you should be questioning it and really ask the deep questions. So when they say they have a great culture, “Say, can you give me three examples from last week where you prove that or that you know that it is a great culture?”

Mike Gerholdt:

That’s a good question. Thanks for coming by, Jason, and sharing your wisdom with us. You said you present some of this. Are you going to be presenting any of this at upcoming Dreamin’ events after?

Jason Atwood:

I am. Well, you’re catching me on my road tour. I don’t know if this podcast…

Mike Gerholdt:

Oh, there’s a road tour.

Jason Atwood:

There’s a road tour.

Mike Gerholdt:

Are you going to have shirts made up?

Jason Atwood:

I might. So yeah, I actually-

Mike Gerholdt:

Have dates on the back.

Jason Atwood:

-I go to a lot… A lot of things, I will be at World Tour this year. World Tour New York in two days, but I don’t think this podcast will be out by then. But you can catch me at Texas Dreamin’, I’m doing this year. You can catch me at WITness Success, you can catch me at Mile High Dreamin’, you can catch me at Dreamforce, you can catch me at Northeast Dreamin’. And is that it? I think that’s it.

Mike Gerholdt:

I mean, Northeast Dreamin’ is kind of the tail end of the year for us.

Jason Atwood:

Yeah, it is. It’s the last one. So I’ll be at all those. I don’t know if I’ll always be presenting this, but you can at least find me if you wanted to.

Mike Gerholdt:

Right. I appreciate you coming by.

Jason Atwood:

Thank you. It’s been great talking to you. Let’s do it in another 10 years.

Mike Gerholdt:

Or sooner.

Jason Atwood:

Or a little sooner.

Mike Gerholdt:

Well, I thought that episode turned out phenomenal. I’m so glad I got to have Jason back, and he is going to be on a road tour presenting and helping admins at different Dreamin’ events. So hopefully, you can get to some of those that he mentioned. I think that’d be really neat, and some really solid tips on interviewing, and even I couldn’t agree more on building experience when you’ve never had a job in the tech industry. So thanks, Jason, for coming on and sharing everything. And speaking of sharing, if you love this episode and you’ve got friends, or maybe you’re going to a user group and you’d love to say, “Hey, I’ve got a podcast for you to listen to on finding that first job or getting your next Salesforce admin’s job,” here’s how you do it. You click the three dots in the corner; most of these apps, podcast apps, have this now.

And you can click share episode and you can post it to social; you could send it as an email to somebody, and then they get a link and they can listen to the podcast right on their phone, maybe as they’re walking their dog, and even more. Now, if you wanted to look for any links or any resources, everything, everything I’m telling you, start your day admin.salesforce.com; everything is there for you. And of course, we also include a link to the Admin Trailblazer community, which is the admin group in the Trailblazer community, which is a great place and also the place I went to get all of these questions. Now, we’ll also include a transcript if there’s something you need to go back and read through; that is all going to be in the show notes. So, of course, until next week, we’ll see you in the cloud.

Love our podcasts?

Subscribe today on iTunes, Google Play, Sound Cloud and Spotify!

What Should Salesforce Admins Know About User Learning Styles?

Today on the Salesforce Admins Podcast, we talk to Lisa Tulchin, Senior Curriculum Developer at Salesforce. Join us as we chat about user learning styles and how to use them to create better training sessions. You should subscribe for the full episode, but here are a few takeaways from our conversation with Lisa Tulchin. Choose […]

READ MORE

Essential Tips for Creating Effective Presentations

Today on the Salesforce Admins Podcast, we talk to Ella Marks, Senior Marketing Manager at Salesforce. Join us as we chat about the keys to creating an effective presentation, how to prep, and how to create a strong ending. You should subscribe for the full episode, but here are a few takeaways from our conversation […]

READ MORE

Why Mentorship Is Crucial in the Salesforce Ecosystem

Today on the Salesforce Admins Podcast, we talk to Warren Walters, Salesforce MVP and host of the Salesforce Mentor YouTube channel and website. Join us as we chat about what admins and devs can learn from each other and why everyone can learn to code. You should subscribe for the full episode, but here are […]

READ MORE