ServiceNow's product is powerful and will be useful to many clients for a long time. The company is on solid ground financially. Corporate culture is pretty good in general.
Pay is low for the area, even for today's climate.
The architecture is bizarre. Don't expect to build sites using relevant technologies like React, Webpack, etc.
Building apps for ServiceNow means writing pre-ES5 JavaScript into CSDATA blocks in XML, then hand-copying files to the right repos.
There's never truly been a paradigm like this, but if I had to place it, I would say SN's engineering practices are somewhere in the early 2000s to early 2010s on average—light years behind the average.
The impact of this is up to you, personally. I found it jarring.
Also, this may be specific to my team, but despite having 2 days/week in office, I am completely isolated.
I'm vaguely aware of neighboring teams but not who to contact to reach them.
I've never had a skip-level meeting and didn't meet my boss's boss until over a year into my job.
I've barely met anyone outside my team, despite the clear architectural opportunities to modernize and improve broad Engineering practices and technologies.
Skip-levels should happen 2-4 times per year.
Second-level team meetings should occur.
I know you can't use Slack, but Teams is garbage for collaboration. A 90s PHP-based web forum would work better than what we have.
Fully embrace Workspaces or dump it. It's just a tool for SNL at this point.
The interview process was straightforward: * Phone screen * Meeting with the hiring manager * Three more interviews with team members and the department head, involving technical and behavioral questions. However, at the end of it all, even t
I had 2 technical interviews. Each one included 2 coding questions and 1 system design question. One of the coding questions was NP-hard. The recruiter was about to move me to the final interview, then rejected me saying "new requirements are showin
Two 90-minute technical interviews were conducted. The first interview was disorganized and not very time-efficient. The second interview was well-organized, but the questions were very easy and basic. Only one of the three people on the interview
The interview process was straightforward: * Phone screen * Meeting with the hiring manager * Three more interviews with team members and the department head, involving technical and behavioral questions. However, at the end of it all, even t
I had 2 technical interviews. Each one included 2 coding questions and 1 system design question. One of the coding questions was NP-hard. The recruiter was about to move me to the final interview, then rejected me saying "new requirements are showin
Two 90-minute technical interviews were conducted. The first interview was disorganized and not very time-efficient. The second interview was well-organized, but the questions were very easy and basic. Only one of the three people on the interview