YouTube2Text

ServiceNow Mock Interview No. 1 | ServiceNow 2.5 years Experienced Candidate — Transcript

by ServiceNow Interview Guide · 3,151 words · 460 segments · language en · Watch on YouTube

Full transcript

  1. 0:01hello Priya how are you yeah I'm good
  2. 0:04how are you I'm fine thank you so much
  3. 0:06for
  4. 0:07joining uh so how much experience you
  5. 0:10have yeah so I overall have two plus of
  6. 0:13years experience in service no developer
  7. 0:16and also in
  8. 0:17it okay great so can you please provide
  9. 0:19your brief
  10. 0:21introduction yeah sure so um myself
  11. 0:24briya I completed my graduation in
  12. 0:26electronics and communication
  13. 0:27Engineering in 2021 and later I have
  14. 0:30started my it career and it's been like
  15. 0:32overall 2.5 years of experience I have
  16. 0:35as a service node developer I'm working
  17. 0:37and uh relevant experience is also 2.5
  18. 0:41years and then I have uh started working
  19. 0:44in one of the uh mnc's and I have no
  20. 0:47good knowledge on majorly all itm
  21. 0:50related modules and have experienced in
  22. 0:53creating configuring
  23. 0:54workflows uh service cataloges business
  24. 0:57tool client scripts and all itm majorly
  25. 0:59it assim related
  26. 1:01yeah okay thank you so as you said you
  27. 1:05have experience in itm so can you tell
  28. 1:07me what is
  29. 1:09itm uh yeah itm is like uh it uh it
  30. 1:13service management it deals is merly uh
  31. 1:18endend delivery of IT services to the
  32. 1:20customers or
  33. 1:22clients okay so from like from the
  34. 1:25starting to end process like designing
  35. 1:27and then creating and then supporting it
  36. 1:29and in it it deals with all
  37. 1:33those okay so can you give any
  38. 1:37example uh example suppose if you uh say
  39. 1:42if you if any company having their
  40. 1:44specific products that they were selling
  41. 1:46uh into the market then with this uh itm
  42. 1:50help we can create some uh Pages like
  43. 1:52service cataloges where they can submit
  44. 1:55their orders same we have like Amazon
  45. 1:57where we can give the orders and then in
  46. 1:59the the background that people can work
  47. 2:01on that and provide that delivery to the
  48. 2:03client or to the
  49. 2:05customer okay so this delivery is known
  50. 2:08as delivery of IT services okay so do
  51. 2:12you know about change
  52. 2:14management uh yeah I'm not majorly
  53. 2:18worked on it but I know a little bit
  54. 2:20about it okay can you tell me what is
  55. 2:22change management and what are the types
  56. 2:24you have heard
  57. 2:26of type of changes okay
  58. 2:31okay uh so whenever any problem is
  59. 2:34created and uh that resolution comes uh
  60. 2:37when we when we have a problem there
  61. 2:38will be some uh root cause analysis that
  62. 2:41we did we do for the problem and then we
  63. 2:43come across any updates or anything that
  64. 2:45need to be changed then we will raise
  65. 2:47that change request that what need to be
  66. 2:49changed for that particular uh
  67. 2:54problem
  68. 2:57okay yeah yeah any example
  69. 3:00uh like uh do you know the types of
  70. 3:03changes uh types of changes I'm not able
  71. 3:08to recall at the moment okay no problem
  72. 3:11uh have you created any change till now
  73. 3:14oh no okay okay fair enough no problem
  74. 3:18uh so I see you have worked on SLS right
  75. 3:21yeah can you tell me what are
  76. 3:23retroactive
  77. 3:25slas what is the meaning of retroactive
  78. 3:28SLA
  79. 3:30re act
  80. 3:36uh so uh what I understood I I will
  81. 3:40explain suppose once we create that SLA
  82. 3:42we have some specific time like when
  83. 3:45that uh should when that in task SL SLA
  84. 3:49should be
  85. 3:50completed
  86. 3:52so this retroactive uh maybe like a
  87. 3:56timing where we will calculate that uh
  88. 3:59how much timeing left like date in the
  89. 4:01past and how much time it's still now
  90. 4:03I'm not sure I'm just assuming that okay
  91. 4:07so you know this is not retroactive SLA
  92. 4:09it means retroactive
  93. 4:12means doing calculations from the past
  94. 4:15date as well okay so suppose you have
  95. 4:17created SLA today but the process is on
  96. 4:19from last five months so or or let's say
  97. 4:23incident is on from the last five months
  98. 4:25so it will do the calculations from past
  99. 4:28date not today okay okay so this is
  100. 4:30known as
  101. 4:31retroactive okay so have you written any
  102. 4:34server side code yeah I did okay so how
  103. 4:38many ways you write means what are what
  104. 4:41all are the utilities in service now
  105. 4:43where you can write server side
  106. 4:45codes yeah so we will write this server
  107. 4:48as grop in business rules UI actions and
  108. 4:51in scripting CL we will uh write this
  109. 4:54okay any
  110. 4:57other uh
  111. 5:00[Music]
  112. 5:03uh I I remember only these for now okay
  113. 5:07okay no problem so this UI action is it
  114. 5:11server side or client side we can use
  115. 5:14that both in u u action both in server
  116. 5:17side and client side but if we want to
  117. 5:19use that uh in client side there will be
  118. 5:22we have uh client we will have this
  119. 5:24client check box we have to uh tick that
  120. 5:26to make that client
  121. 5:28callable okay okay great okay let's move
  122. 5:32to the next question uh have you used G
  123. 5:35scratch Pad
  124. 5:37variable yeah we use that in uh display
  125. 5:40business to to call
  126. 5:43uh uh to call to client side server side
  127. 5:46data to client side okay so to retrieve
  128. 5:49data yeah okay so what are display
  129. 5:53business
  130. 5:55rules uh dis business rule are like when
  131. 5:58we want to uh it will execute like uh
  132. 6:02when before the form is presented to the
  133. 6:04user and data is saved into the database
  134. 6:07so if you want to uh give or you want to
  135. 6:09display any information to the client
  136. 6:12even before uh us submit any information
  137. 6:15we will use this display business R okay
  138. 6:18any scenario you have in mind where we
  139. 6:20can use this type of
  140. 6:24thing uh just a minute I think take a
  141. 6:28Time
  142. 6:39okay so uh suppose when any user or uh
  143. 6:46if any user belongs to one suppose he
  144. 6:48belongs to some Australia company and in
  145. 6:50the form uh he only the form need to
  146. 6:53only display based upon his comp uh his
  147. 6:57country specific data then we will use
  148. 6:59display business
  149. 7:01tool okay okay let's move to the next
  150. 7:05question so have you used flow
  151. 7:08designer yeah uh I didn't work but uh
  152. 7:11yeah I know I got good knowledge on FL
  153. 7:13designer okay so uh can you tell me the
  154. 7:16difference between the workflow which we
  155. 7:18have traditionally right from bong and
  156. 7:21this flow designer what difference you
  157. 7:25feel uh actually the latest I mean the
  158. 7:28advanced verion of workflow uh is the
  159. 7:31flow designer suppose in flow designer
  160. 7:34we can have this uh we have this
  161. 7:36platform op where we have parall create
  162. 7:38multiple
  163. 7:40subflows okay and uh instead of uh
  164. 7:45writing any scripts we can easily uh use
  165. 7:48this flow
  166. 7:50designer
  167. 7:53okay um and we uh suppose we will have
  168. 7:57this data pills all those which we which
  169. 8:00makes the process simply simpler and
  170. 8:03easy to understand and take less time to
  171. 8:06code in FL designer than workflow and
  172. 8:09there is some reusable action suppose in
  173. 8:11one FL designer if you used any action
  174. 8:14the same thing we can use in uh another
  175. 8:16flow designer also okay okay great good
  176. 8:21example okay so uh you worked on Agile
  177. 8:25development so right yeah
  178. 8:29so what is this agile thing how we why
  179. 8:33we are using it and what is the basic of
  180. 8:37agile okay so aile development is like a
  181. 8:40uh flexible approach suppose we have
  182. 8:42some uh we got got some requirement we
  183. 8:45need to complete in so on so date before
  184. 8:47the headline then we make a proper
  185. 8:49planning like uh it's like a management
  186. 8:53like how many uh in the way how we have
  187. 8:55to deliver
  188. 8:58that okay so basically it is a kind of
  189. 9:02software development
  190. 9:06cycle yeah I think
  191. 9:08so okay so I see you have hands-on
  192. 9:12experience in driving upgrades
  193. 9:15right yeah so in
  194. 9:19upgrade what was your
  195. 9:23role uh first of all tell me uh which
  196. 9:26which release of upgrade you were in
  197. 9:32involved uh I don't play majorly but uh
  198. 9:35while uh people are upgrading I just uh
  199. 9:40I will also be uh I'm invited to that uh
  200. 9:43calls and I will also just have I still
  201. 9:46have to know that I'm not sure exactly
  202. 9:49okay so so what you did basically just
  203. 9:52wanted to check in all the upgrade
  204. 9:57process uh okay you did testing or
  205. 10:01what uh no once we upgrade from uh
  206. 10:05suppose if you upgrade to another uh
  207. 10:07release then we will make in the back
  208. 10:09end we will see that if we have same
  209. 10:12number of updates that there previously
  210. 10:15before and the updates we have done
  211. 10:17we'll just compare before and after and
  212. 10:21yeah okay and if it's anything missing
  213. 10:24we will load that uh update set to the
  214. 10:27new release okay
  215. 10:29so I say you have also experience on
  216. 10:32fixed scripts right yeah you know what
  217. 10:35is the fixed script can you tell me what
  218. 10:37is the use of fix script and where we
  219. 10:39are using
  220. 10:41it okay so uh if we have a large data
  221. 10:45that we need to uh we need to update
  222. 10:48then we will use this uh fix
  223. 10:50script
  224. 10:52okay so uh when we trigger this fix fix
  225. 10:58script
  226. 11:06okay no problem let's move to the next
  227. 11:08one uh um do you know what are import
  228. 11:13sets huh I know yeah please tell
  229. 11:17me yeah import set like uh suppose in in
  230. 11:22service not to uh navigate from one
  231. 11:23instant we will use uh update set and
  232. 11:26data sources so import set is like a uh
  233. 11:29we will import the data firstly to the
  234. 11:31import set and then we from import set
  235. 11:33we will transfer the data to Transformer
  236. 11:35to the Target
  237. 11:37table okay but this is used for moving
  238. 11:40of data from outside systems yeah it is
  239. 11:43like a staging
  240. 11:44table okay okay fair enough so I have
  241. 11:48one you
  242. 11:49know some one question where you have to
  243. 11:53build some logic okay just just listen
  244. 11:56carefully okay so I have a spread sheet
  245. 12:00which is present on a server location
  246. 12:02okay so there is a server and someone is
  247. 12:06adding a spreadsheet with the same name
  248. 12:08on every week there what I want I want
  249. 12:12to move that spreadsheet or you can say
  250. 12:15data from that spreadsheet of that Excel
  251. 12:18into one of my custom table every day
  252. 12:21not every day every
  253. 12:23week okay so there is a server we have a
  254. 12:25file on that and that file I want to be
  255. 12:28loaded service now tables or one of the
  256. 12:31table every week okay so how should I
  257. 12:34approach
  258. 12:36it um we can create a schedule job with
  259. 12:39by mentioning like uh time as one we and
  260. 12:42what need to be
  261. 12:44done okay that schedule job is okay but
  262. 12:47what we will do in that schedule
  263. 12:57job
  264. 13:01I'm not able to recall it I didn't work
  265. 13:05much on schedule job I just lent on my
  266. 13:08own
  267. 13:09okay no issues uh have you worked on
  268. 13:14ATF uh yeah uh manual testing yeah we
  269. 13:17are currently uh did for one of the
  270. 13:20project and atfs yeah I have created a
  271. 13:22few ATS for cataloges and testing the
  272. 13:26workflows Okay so can you tell me how to
  273. 13:30configure an ATF what are the
  274. 13:33steps okay so we will have the separate
  275. 13:36module in our PDI only to create ATF and
  276. 13:40uh there we will have this or few
  277. 13:43already existed templates if we want we
  278. 13:46can use get once we uh template we can
  279. 13:48use them suppose if you are creating any
  280. 13:50incident then there are already
  281. 13:52pre-build templates for the incident we
  282. 13:54can make use of them or you can create
  283. 13:56then some custom steps
  284. 13:59uh Customs test steps for each uh test
  285. 14:02suit and then according to the condition
  286. 14:05you can build
  287. 14:07those okay can we schedule
  288. 14:11atfs uh yes I uh yes I think yeah we can
  289. 14:16schedule an ATF okay okay uh fair so
  290. 14:22have you created any
  291. 14:25ACL uh
  292. 14:27yeah so tell me what you did in that ACL
  293. 14:33creation what was your
  294. 14:36task okay so uh ACL suppose if you want
  295. 14:41to make any um ACL is generally not to
  296. 14:44restrict any user like uh which data he
  297. 14:47has to modify and which data he has
  298. 14:50to uh so by using this ASL we have uh
  299. 14:55suppose we can give condition suppose if
  300. 14:58you in instant table we have one record
  301. 15:01where there will be one field if you
  302. 15:02want that field to be visible only to
  303. 15:05that particular role person then we can
  304. 15:08create ACL like by giving condition like
  305. 15:11this can be accessible we have this two
  306. 15:14uh types in like lower level and field
  307. 15:16level ACL in field level ACL we can use
  308. 15:18this field level AC and create give
  309. 15:21conditions like this specific field
  310. 15:22should be uh used by this person only
  311. 15:25and we can do that accordingly okay okay
  312. 15:28so which level of ACL execute
  313. 15:32first field level or row level or you
  314. 15:35can say table level table level AC okay
  315. 15:39and then it will go to field
  316. 15:42level okay okay great so have you worked
  317. 15:45on any Integrations till
  318. 15:47now uh Integrations I didn't work but uh
  319. 15:51I learned
  320. 15:52Integrations I sorry sorry but I know I
  321. 15:56I have good knowledge on them okay give
  322. 15:58me one example whatever you feel
  323. 16:01good okay suppose if you are integrating
  324. 16:04with uh with service now with Postman
  325. 16:08then we need first the endpoint like the
  326. 16:10URL of that Postman and uh we'll get
  327. 16:14that endpoint URL of that Postman and in
  328. 16:17the service now we will open this rest
  329. 16:19uh API Explorer and we will provide that
  330. 16:22Postman end URL into this uh service now
  331. 16:25and uh if you need any authorization we
  332. 16:28will give those credentials and then we
  333. 16:30will integrate
  334. 16:32according okay so what basically we are
  335. 16:34doing you you do in this integration I
  336. 16:37you told me the steps but but what is
  337. 16:39happening why integrate with something
  338. 16:43else to exchange information suppose if
  339. 16:46we want any information from third party
  340. 16:48we'll use this integration uh to build
  341. 16:50like a connection between two
  342. 16:52applications okay
  343. 16:55great
  344. 16:57Okay so uh what is the background
  345. 17:01script uh back background script in
  346. 17:04service now used to uh suppose if we
  347. 17:08want to do any uh client size scripting
  348. 17:10or server size scripting instead of just
  349. 17:12opening the module we can use this
  350. 17:13background scripting service know where
  351. 17:15we can uh it's like a we can use that
  352. 17:18for a testing purpose
  353. 17:20also okay so it's you said the client
  354. 17:24side and server side so is it applicable
  355. 17:26for both or oh no only for Server site
  356. 17:30yeah server site okay so have you
  357. 17:33created one have you tested anything
  358. 17:35there yeah suppose while writing any
  359. 17:38code and we want that to be tested
  360. 17:40before or uh before submitting that
  361. 17:43exactly in then then we will write the
  362. 17:46code in the uh background script and
  363. 17:48verify then and then we will use that
  364. 17:50all if we facing while debugging also we
  365. 17:53can use this background script okay uh
  366. 17:57so suppose you have a code Cod of around
  367. 17:59you know 500 lines okay there is a
  368. 18:03schedule job which was written and it
  369. 18:05has around 500 lines so I want to debug
  370. 18:09that code that 500 lines how you debug
  371. 18:12means what are the ways you debug that
  372. 18:14particular
  373. 18:16script we can keep this break sorry we
  374. 18:19can keep this break and we will uh
  375. 18:22validate accordingly uh that may be
  376. 18:24little easy than going uh to the code
  377. 18:28and
  378. 18:29L okay
  379. 18:31okay great so you have used it break and
  380. 18:34all right yeah okay great and what about
  381. 18:40reporting uh reporting uh I didn't
  382. 18:43worked on much but I I know little much
  383. 18:46about it yeah okay so uh you know what
  384. 18:49are database
  385. 18:53views you mean that uh for any form the
  386. 18:57views that one no no database views
  387. 19:01database
  388. 19:03view we create in service now database
  389. 19:05view
  390. 19:08right you have not worked on database
  391. 19:10view that's okay no
  392. 19:12problem uh okay
  393. 19:16so okay tell me one more thing uh the
  394. 19:20difference between record producer and a
  395. 19:22catalog
  396. 19:24item okay so uh in catalog item we use
  397. 19:27this part and then once we submit this
  398. 19:30uh catalog item we will uh the request
  399. 19:33will be created and for that request RM
  400. 19:36will be created but for record producers
  401. 19:38it will directly create a
  402. 19:41task in the table level yeah in the
  403. 19:44table okay it will not use any card
  404. 19:48something okay okay great and uh in cogs
  405. 19:54we can uh attach the workflows but in
  406. 19:57recall producer we cannot attach but we
  407. 19:59can trigger that in script we can
  408. 20:01trigger the workflows in script great
  409. 20:03great uh good answer okay so uh one last
  410. 20:08thing yeah what is a scoped application
  411. 20:12and what is This Global and all this
  412. 20:15scoped can you tell me difference
  413. 20:17between This Global application and a
  414. 20:19scoped
  415. 20:20application yeah scoped application is
  416. 20:22like a unique application that was
  417. 20:24created only for that uh to deal only
  418. 20:27with the specific application uh suppose
  419. 20:30uh people are who are not a part of any
  420. 20:33uh project or who are not part of that
  421. 20:35application couldn't able to uh make
  422. 20:38changes or can view this application it
  423. 20:40is only for security purpose we should
  424. 20:43use the scoped application whereas
  425. 20:45Global is for everyone they can able to
  426. 20:48see this view this and can able to edit
  427. 20:50this so majorly we will use the scoped
  428. 20:54application okay okay great uh so I hope
  429. 20:58I'm done uh with the discussion uh can
  430. 21:02you provide me a feedback like which
  431. 21:04where I I can improve and where I have
  432. 21:06to improve so that can be helpful for me
  433. 21:08for the my future learning also sure
  434. 21:12sure see the points which I have noted
  435. 21:14till now is that you know whatever you
  436. 21:17mentioned in your
  437. 21:19resume like whatever you have written so
  438. 21:22you must have some idea about that first
  439. 21:24of all right and prepare best examples
  440. 21:29okay for each and everything let's say
  441. 21:32integration sorry when someone ask for
  442. 21:34integration you must have though you
  443. 21:36have not worked on it that's okay but uh
  444. 21:39you must have a fair idea what are the
  445. 21:41components of integration why we are
  446. 21:43doing integration okay so if you have
  447. 21:46written in your resume then you have to
  448. 21:48be at least one or two examples so you
  449. 21:51can prepare these things well in advance
  450. 21:54and what you mentioned just focus on
  451. 21:57that okay rest all things are fine you
  452. 22:00are confident and you are you know
  453. 22:03talking patiently I'm okay with that but
  454. 22:06just one feedback related to this which
  455. 22:09I just shared okay sure thank you okay
  456. 22:13so with this uh let's wind up this and
  457. 22:16uh all the best for your
  458. 22:19interviews yeah thank you so much for
  459. 22:21taking time to interview me no problem
  460. 22:24my pleasure thank you thank you

About this transcript

This page contains the full transcript of ServiceNow Mock Interview No. 1 | ServiceNow 2.5 years Experienced Candidate by ServiceNow Interview Guide, generated from the public captions YouTube serves with the video. The transcript has 3,151 words across 460 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.