Skip to main content

SRD

I am glad to be able to clinch a job in Shell through SRD. I did not give much hope in SRD beforehand because I took it as a challenge and more of a free test on my skills (can claim traveling and accommodation expensive*)

In my attempt to get jobs during my university time, no matter what the company is, I had been assisted by many people, my friends who offered me transportation convenience, interview and job advices, moral support and also those LYN forumers who shared their experience and attended to my inquiries on the net.

Therefore, I felt the responsibility to contribute some information that I have previously obtained both from exposure and enquiries. I hope the below information will help you to have a clearer picture of the SRD.

SRD is a one day event, which is design to assess the employability criteria set by Shell.
It begins with individual case study, followed by group discussion and a technical interview or a business case study if you are not from technical background.

There is a SRD pre-briefing a day before the SRD event so make full use of the day. Learn and try to identify your strength and weaknesses when practicing during the pre-briefing as it may be helpful in boosting confidence and also understand better what is expected during the SRD.

In here, I will not reveal or describe the task that I have done but I will share my experience vaguely. I believe that every person has his/ her unique way of dealing with problems.

Individual case study- You will be given many articles and pieces of information relating to several issues. You need to identify the issues from these articles and propose solution/ action to solve the issues.

Group discussion- You will be working in group of two to discuss on a certain plan or options that serve a certain stakeholder (maybe a few of them). In the end, you and your partner will gather with other groups to come out with the finalized options.

Technical interview- This appeared to be a much easier task to me. I had my interview done based on my Final Year Project. Try to understand your project well and try to be broader in the sense of technology involved, other direct and indirect issues, implication of work and constraints and also the people and stakeholders involved.

In overall you may need to consider/ give a thought on the following:
The stakeholders involved, not just who, but how, when and why
Timeline of your propose solutions/ actions
Linkages of identified issues and solutions/ actions
Relation of the case/project with reality
Thinking out of the box, think of how a certain action may solve not only the certain issue, but also developing other aspects as well.
Motivation, involvement between you and your group members

You may want to look at the criteria set based on CART:
Capability
Achievement
Relationship
Technical

You may need to look for further descriptions on these criteria on Shell website. Believe me, giving a deep thought on the CART criteria really helps.

Good luck to you and all the best in SRD.
* subjected to terms

Comments

Popular posts from this blog

Leisure Driving

I've just returned from driving around Miri. From Miri Airport bypass to Miri-Pujut road. I stopped by a bakery to ease my stomach after paying so much attention on the road. (maybe it's the brunch, not the drive..lol) When I returned home. I felt so wasted. The road is not twisty and I wasn't even in a fun hot hatch. I was doing a spirited driving in a TOWN CAR! Boring. If I were to be relocated back to KL someday, bet that I would get a car that I could appreciate the thrill of driving up to Genting once in a while for a short getaway from the city. Well, Miri aint city... there's no my claimed 'getaway' for me here. Nevertheless, my current car is a decent one, a nippy zippy town car. Just that sometimes it serves the wrong purpose. Tried hard to cope with my demand. lol. I'm not abusive of my car. I'm more of touge style that drag. I guess 2 more tyres are ready to go. In short, the car is here to stay although it did not really meet my expectation. ...

easier said than done..

A recent conversation with a friend made me realise there are so much things, when said is ideal, when done might turn out to be less pleasant. Well of course one cannot run away from continuously managing an activity or action so that it does not turn ugly at all. Continuous management is what human tend to call, commitment. And who the hell made that word up, I've missed an M the first time I wrote it! As far as I lived to write this post today, I am 'proud' to still not tied down by the human-termed 'commitment'. I can have all the 365 days for myself, all my earnings for myself (of course I voluntarily treat my family which made me happy, and that's what I do for myself too) and all the time for myself. I can safely assume that I have almost zero commitment. Probably as the level of maturity heightens with age, responsibility and commitment come into play naturally. Not sure if from zero to hero sounds great when it is about commitment to everyone but I gues...

we asked for it..

I was surfing the internet for privileged banking criteria as I really hate queuing in the bank just to handle some small matter. Not that I am earning loads, but I am looking forward for the day. ... until I came across a forum where a person mentioned, with ebanking, transactions are done without even leaving your home. Ah, that's right. Most of the time now, I just manage transactions via online banking. Probably larger sum requires me to visit the branch but common people can just manage their account in front of their laptop. So, I thought, probably 10 years ahead, there will be only 2-3 frontline bankers in each branch rather than the sum we have now. Same to many industries, with expansive of specialization and automation, probably the world might need more maintenance technician rather than the person who once did the job before machines took over. Hahaha... sounds terminated? I'd rather say retrenched (similar terminated term in workforce hahah) Similar to LEAN. LEAN i...