Posts Tagged ‘internship’

here for you

and so the search for summer 2012′s revenue-generating activity has ended, with bagpipes and kilts if you don’t recognise the logo. this year’s process started off with confidence, followed by shock, disappointment, uncertainty, insecurity, despair, and ended with relief (mostly in that order). looking back, it was a black swan event, meaning i could have cut back a few heart attacks that were disruptive to my academic life. in hindsight, the causes were a mix of complacence, bad timing, market conditions awareness, and a discrepancy between my goals and the market demand for it. by the time i realised that my ultimate priorities were to [a] facilitate my (possible) exchange programme in fall and [b] secure a full-time offer before that (as opposed to gaining experience in my very specifically desired field), it was mostly too late. not that i am unhappy with my present offer, in fact i was thoroughly elated when i received the news, just that things could have been done much, much better. i am certainly looking forward to how these ten weeks will differ from last year’s and will have to start planning for my actual career soon, lest the same painful process repeats itself.

summer/fall 2011 mega update

, , , , ,

i realise termites are almost chewing this place away, hence the facelift to something simpler. the last time i had a moment to breathe was midway through my internship; everything else from then on was a blur. here are the last six months in summary:

one; the credit suisse internship
more or less the best thing that happened to me in 2011. the application through to the interviews seemed so smooth, some people commented that they were rather lenient this year. the entire summer analyst cohort numbered ninety plus, where more than half were from technology. the key takeaways from those ten weeks were opportunities: to meet people, to experience culture, to learn things, and to make a difference.

the mandatory nature of meeting people became apparent on day one and two which ended with compulsory networking. from then on, it was understood that every other event would have a networking element (there was some correlation to whether food and alcohol were served). teams were also randomly assigned for the meet the md program where teams had to schedule and meet five managing directors or directors by the end of the term to uh.. chat. sometimes the interaction was one-sided, like CEO brady dougan’s address to the global summer analyst cohort, which was cool since i’ve never sat in a video conference with hundreds of people in it (i think my manager was envious). the whole idea of building networks suddenly has tremendous value once you realise you have a problem you can’t solve and help is but a phone call/IM/email away. to quote induction training, “would you rather google for five hours or call someone for five minutes?”. the question then becomes: have you made enough effort in getting to know more people so that you know the right someone to call in times of need?

culture was another inevitable aspect. you can lie in a ten-minute interview, but you can’t get 55,000 global employees to lie to you over ten weeks. everything i saw on each of those 50 days was real-world work to run the bank and continually increase efficiency. the fact that CS is less keen on lateral hires and focused on grooming internal talent from graduate levels to fill senior positions eventually shows their long-term vision that attempts to rid diluted cultures.

out-of-office learning was my favourite, even if it was just an off-site training lecture at raffles link. of course field trips to the trading floor and datacenter plus the IT expo where the entire of technology got together to share were highlights. besides the basic finance elearning that everyone had to complete, i was very much into how people manage complexity. since studying technical processes was kinda part of my job, it was interesting to see how much i could comprehend (the answer was barely enough, but i grew to understand that was normal). taking charge of my own projects meant that i was at liberty to propose solutions (unfortunately to build them as well) which ended up making life easier for certain people. to hear managers with vastly more expertise than me showing appreciation for my work exudes quite a bit of satisfaction, especially when i felt more could be done given time. that said, the potential to drive change in an open organisation with overflowing complexity is limitless.

shortly after completing my stint at CS, i was given an offer for a repeat internship. i also learnt from a colleague that my projects were inherited by a new graduate analyst to be further developed (hopefully my documentation makes sense). though it was a great experience, i turned down the offer in favour of exploring other avenues. trust me, that email was one difficult mail to write but i felt it was necessary in my capacity of continual learning at this point in life.

two; attempting to squeeze government money
as part of ida’s elite initiative, i had 6 grand to spend on training courses. being the opportunists we are, most of those in my batch unwillingly parted with 6 grand of our own in an effort to increase our perceived value through certifications. unfortunately, time became quite an issue and i only managed to complete and pass (and reimburse) the easiest of three certs: the ITIL v3 Foundation. CAPM and CEH funds are frozen till i complete and pass them :(

three; the semester begins. and ends.
junior year: a weird term for a penultimate student if you ask me. my first semester doing four IS mods that don’t feel like IS mods. taking both retail banking and financial markets made the contrast between retail banks and investment banks rather obvious, down to the guest speakers. the “don’t throw away until it completely breaks down” mindset against the “do whatever it takes to achieve competitive advantage” focus made it pretty clear where i am not headed in my career. architectural analysis and networking felt like computer science mods, where the former drained out the cpu cycles of all my peers doing performance load tests and the latter was an opportunity to buy expensive toys and perform weird tests on them.

i also spent the greater part of post-internship and term time to work on PRISM, the faculty magazine i revived after a two-year hiatus. this will be my legacy after stepping down as publications director from the 7th smu school of information systems society.

four; fyp begins
right after the exams, it was full speed ahead to clear fyp acceptance. we already shipped in a pair of nexus s phones because of their special powers and built a simple prototype for the presentation. thankfully we passed acceptance, but there is still a tonne of fuzzy work left to sort out before actual development can begin. no risk, no return right?

five; plans for summer/fall 2012
summer 2012 planning has commenced on a rocky start with an early rejection note, but i can’t possibly expect everyday to be sunday. applications will continue and hopefully i will end up in a nice place. i am also planning for an exchange semester in fall 2012, so stay tuned.

credit suisse allocation

,

looks like i’ll be staying in the east..

credit suisse IT internship application

,

just thought i’d share the entire process since i got in and i would have wanted to know before i applied.

step 1: application (30th nov / day 0)
fill in the (relatively long) online forms. standard process.
applications close end of the year like most investment banks.

step 2: online test (30th nov / day 0)
after submitting the application, you have 1 week to complete the online tests. credit suisse uses verbal and numerical tests, as opposed to other banks which replace verbal with logical. the verbal test is like english comprehension, except in a much tighter time frame. the numerical test is more of a mental ‘numeracy’ test, so a calculator didn’t save me since i’m not inclined in that area. i didn’t complete the numerical one, well the last few questions anyway.

step 3: wait for reply (18th jan / day 48)
i thought i had been rejected at this point, since cs claims to process applications on a rolling basis.

step 4: round 1 “individual screening” (24th jan / day 54)
held at smu, all applicants were invited to sit in a presentation about cs. roughly the same content i’ve heard at the 2 info sessions i attended previously. after the presentation, short networking session while i waited for my interview slot. the 10-minute interview was individual and focused on getting to know you as well as your objectives.

step 5: round 2 “group assessment” (25th jan / day 55)
held at cs, the very next day. i was expecting a large room where we would “play” group activities, but it was more of an assessed hour-long group discussion and presentation in a crammed meeting room.

step 6: round 3 “individual assessment + interview” (31st jan / day 61)
also held at cs, started with half an hour to digest a case study and prepare a presentation. then off to meet my assessor to do my 15-minute pitch, followed straight after by a detailed version of round 1. my resume was heavily scrutinised, before the competency questions came in.

step 7: cross fingers and wait (1st feb / day 62)
i got the call during class just now. dashed out to find the caller had hung up. i dialled back to no avail, and it was cat-and-mouse until break time when the familiar voice of Dan from recruitment got connected. “congratulations” was all i needed to hear, and that, is the best chinese new year gift ever.

still waiting to process some admin stuff and sign on the dotted line, but i’m very much looking forward to those 10 weeks commencing in may. awesome would be an understatement.

first positive reply

wish me luck