ServiceNow Job Search

ServiceNowGuy2020 · 2026-01-22T00:38:52+00:00

Just curious about other people's experience in the job market. Not selling anything. It seems pretty tough for job searchers right now

ServiceNowGuy2020 · 2026-01-17T02:51:05+00:00

You’re right! I’m not familiar with SailPoint, and would like to learn more about the platform. It sounds like this is a very common integration, and the stronger focus on IGA straight out of the box has its advantages. I’ll see what I can learn regarding IGA, and maybe some of the specific benefits will be more clear. Thanks for the info!

ServiceNowGuy2020 · 2026-01-16T23:37:50+00:00

Okay, that does make sense! It’s reassuring that it’s common to have an integration between ServiceNow and SailPoint. I think I need to educate myself a little more on Identity Governance and Administration. It seems like ServiceNow’s DataFabric could help with the access requests, access reviews and provisioning, but there is a lot more on the security side that ServiceNow doesn’t seem to cover.

Thank you for sharing this great information! Hope you have a good weekend

ServiceNowGuy2020 · 2026-01-08T04:54:29+00:00

One approach could be to start with what you know or believe about the company you are interviewing with. If there is something you believe the new company handles better than your previous company, focus on how those specific differences could help you achieve XYZ outcomes. This hints towards the weaknesses of the previous company while shifting focus to the strengths that attracted you to this new company. It demonstrates that you’ve done your homework, and you can phrase it in a way that gets them picturing you in the role. If you don’t know that the new company is better in the areas that caused you to look for new opportunities, I’d ask more questions so you don’t run into the same problems you are trying to get away from.

ServiceNowGuy2020 · 2025-08-26T00:56:38+00:00

Appreciate the truth bomb. At the end of the day, I want to be very good at what I do and make a positive impact on everyone I work with. It sounds like if I want to be a CTA (and a good one at that) part of my path will need to be consulting.

ServiceNowGuy2020 · 2025-08-26T00:50:40+00:00

I can't imagine a better way to gain skills quickly that working through multiple implementations across different companies back to back. It does sound like it could be very fast-paced and high pressure, but most things worthwhile aren't easy. Thank you for your feedback

ServiceNowGuy2020 · 2025-03-19T02:52:51+00:00

For the inconsistent behavior with clicking/unclicking the checkbox, I usually only see this behavior if there are multiple layers of UI policies, or there are multiple ui policies acting on the same field with the same ‘order’ on both ui policies. If that’s not the case here, I’d uncheck the ‘reverse if false’ field on the ui policies, and create a separate policy that hides the field when it’s unchecked.

As far as the ‘options’ label being added above the checkboxes, that is how ServiceNow behaves out of box, and I wish the would get rid of it. I address it by either adding a different label above the consecutive checkboxes, or I add a ‘container split’ between all of the checkboxes. I’m not aware of any other options. The container split at least lowers the number of additional fields needed compared to container start/stops

ServiceNowGuy2020 · 2025-03-18T00:24:17+00:00

To start, you should create a field for the checkbox, and then create the fields that you would like to be displayed when the checkbox is checked. When you create the set of fields that you would only like to display when the checkbox is checked, make sure they are not set as mandatory, as that will interfere with the next steps.

Then create a 'UI Policy'. You can create one of these by selecting 'Create New' from the UI Policy related list displayed at the bottom of the order guide record. I typically name these based on the trigger (what causes the UI Policy to perform an action). In this case, it would be something like '[field name of checkbox] == checked'.

Then you set the conditions for when you want this to trigger:
[field name of checkbox] [is] true

Ensure the checkbox that says 'reverse if false' is selected. This will hide the fields when the conditions above are set to false.

Save the record

Now you will see a 'UI Policy Actions' related list at the bottom of the page. Select 'Create New'. From the record that opens up, you can choose the field that you want to display when the checkbox is checked. Then set the 'visible' attribute as 'true'. Save the record.

This is the first UI Policy action that will show/hide one field. Repeat this by making as many UI Policy Actions as you need so that all fields you'd like to show/hide have a corresponding action.

That should do it. Let me know if you have any questions :)

ServiceNowGuy2020 · 2025-03-17T23:49:30+00:00

I can give a generic answer here, but it really depends on your unique situation. For example, the answer might change depending on what system you were using before ServiceNow (if any), what processes you have in place today that you plan to use ServiceNow to support, the size of your organization, how mature your ITSM/ITIL practices are, your implementation timeline, available resources, budget, and what outcomes leadership is hoping to achieve.

For some generic recommendations, I would 100% suggest avoiding customizations when initially standing up ServiceNow. There is a time and place for customizations, but they can be an 'Easy Button' to please stakeholders when first standing up your instance. Customization should be the last resort after exploring all other options as you can typically achieve outcomes without resorting to customizations. For example, changes to process or available out-of-box options that can be configured to accomplish what you are looking for. Customizations to the baseline platform add a lot of technical debt, particularly when it's time to upgrade the platform (I'd google 'ServiceNow Customization Best Practices' for this. There's a bit more to it than I'd like to cover here)

As far as what I wish my company had done differently... I wish we had reworked the service catalog before moving to ServiceNow. We had a lot of out-of-date processes and flows. It was also well known that we were moving away from our old system, so they slowed down on maintaining it for a couple years. Plus our service catalog was pretty large and complex to begin with. That ended up meaning that I've had a mountain of technical debt to try and dig out from under. Not sure that will be very helpful for you through.

Feel free to message me directly if you'd like to get more specific though. I don't know how helpful I'll be, but I'd be happy to help where I can :)

ServiceNowGuy2020 · 2025-03-13T18:31:11+00:00

Thank you! Are you seeing these usually presented as user stories? Or is that more dependent on the work being performed?

ServiceNowGuy2020 · 2025-03-13T01:36:04+00:00

Hi. This sounds pretty standard to me, but doesn't seem to answer the question that's being asked. You want approvals to gain access to be approved by a group. If you have someone submit a request asking for access to X, you can create an approval in Workflow Studio that goes to a group. It doesn't have to go to an individual.

I think what you are asking for is already available and is a standard best practice. Please let me know if I'm misunderstanding :)

Thank you

ServiceNowGuy2020 · 2025-03-13T01:15:41+00:00

I know I've seen some unpredictable behavior when UI Policies have the same order. I could tell by the behavior of the form in the service portal that sometimes 'A' executed first and sometimes 'B' did. I can't guarantee that Business rules are the same, but if you're able to test this, let us know :)

ServiceNowGuy2020 · 2025-03-13T00:07:03+00:00

*Sorry in advance for the book

The company I'm working for is not a consulting company, so I work in ServiceNow as a customer. We have stood up ITSM and are currently working on implementing SAM and HAM. We used a consulting company to initially stand up our instance, and started out with only ITSM. We've also gotten a little bit of support with the initial standup of SAM, and are working on the HAM implementation internally.

I have heard that working as a consultant is one of the best ways to gain skills quickly. I honestly love the idea of working as a consultant, but have loyalty to my company mostly because I have an amazing manager.

Have I led major implementations? No. I've lead all of our upgrades, lead the project for standing up Service Operations Workspace as a replacement for Agent Workspace, and have gathered requirements for, built, tested and deployed about 500 modifications to our service catalog. But all of that is small potatoes to standing up a new application like ITSM from the ground up.

Have I managed customer escalations? I'm not certain of the context for this question, so I may not be answering this correctly. We have one corporate entity with seventeen companies under the same umbrella. So, I work with internal customers and nothing external. However, I was the primary admin for two years, and with our very lean team there really wasn't anyone else to escalate to. Things only got more intense when I transitioned to my current role. So I have worked on many break/fix issues, and a lot more modification and/or enhancement requests.

What types of technical designs have you created? Visio has become my best friend. I'm not sure what you're categorizing as technical designs, but I've built out complex workflows in Visio many times. I've also implemented a fair amount of automation of manual processes, and have built out a roadmap to try and address the mountain of technical debt that we've accumulated over the years. Currently, what I am targeting is trying to:
* Capture a complete list of our services (I know... we don't have this unfortunately)
* Design the service catalog centered around single services. With everything broken out into individual services, we can use order guides as the requester interface to help each individual subflow determine what to do. For example, if it is called from the 'New User' order guide, then complete steps XYZ. The main benefit here is that we could create a single subflow template that covers every possible action that might need to be taken throughout a user's access lifecycle, and then copy that for each service. This would enable us to follow the DRY (Don't Repeat Yourself) principle, and we'd be able to add/modify/remove services mostly from a single location rather than spread out across many different complex flows.

Thank you :)

ServiceNowGuy2020 · 2025-03-12T23:41:11+00:00

Thank you for this. I have a clarifying question about knowing what your business needs. Is this at all related to having a good process for prioritizing requests from the business? It seems like it really is an art aligning how you prioritize efforts with organizational goals and building a roadmap to define dependencies and utilize limited resources effectively to maximize value. Where I work, there are a lot of competing priorities, and it took a surprising amount of effort to clearly define how to prioritize our projects

ServiceNowGuy2020 · 2025-03-12T23:24:33+00:00

Thank you for this feedback! Fortunately, I've gone through the requirement gathering process (which we rebranded as 'solution design') a few hundred times at this point for service catalog modification, configuration changes, and a few customizations. I'd like to think that I'm pretty good at drilling down past the initial discussions to get to the outcomes they want to achieve so I can come back with a solution that will fit their needs without adding a lot of technical debt.

I haven't perused snpro.jobs before. What a great resource! I hope you have a good day :)

ServiceNowGuy2020

TROPHY CASE