A website for The University of Sydney Sciences & Technology Students



Case study

Kenneth was a Systems Integrator with Telstra-Protocom and is now a PhD student

Job pathway

Franklins cashier > Woolworths shelf filler > DoubleClick Australia Web Ad Traffic Coordinator > Sydney University IT Tutor > Systems Integrator Telstra-Protocom > PhD student

Qualifications

B.Comm, B.Sc (Honours I in Information Systems)

How did you end up working in your current job?

I graduated in 2002. After finishing honours, I was busy contemplating whether to undertake postgraduate studies or to work in the industry. The latter sounded very interesting, new and exciting for me. I really wanted to work in the IT industry; I wanted to get experience first-hand working in an Australian IT company; and on some challenging IT projects. While I was applying for jobs, a good friend of mine introduced me to Protocom Technology – a young and promising firm that develops innovative telecommunication applications such as SMS (Short Message Service) and MMS (Multimedia Messaging Service). After understanding the huge potential for growth in the company (both for me and the company itself), I decided to take up the job. I was placed in Telstra (Australia's largest telco and Protocom's major customer) as the Systems Integrator, where I liaised with business managers, project managers, developers and the technical analysts on a full time basis.

What skills do you use in your job?

The nature of my job demanded both technical and soft skills. I felt that the training I received from the Commerce, Computer Science and Information Systems schools at Sydney University made me highly adept for the job. Initially, I spent a great deal of time learning the various SMS systems and subsystems used by Telstra. They were very complex. Technically, I had to rely on my Unix skills – (eg. server set up, configuration and scripting), understanding of the C programming language, java script, assembly language, and SQL.

On the other hand, I had to liaise many a time with the developers, project managers, business managers as well as other technical analysts in the projects. That demanded a lot about how you talk with people, knowing when to listen instead of speaking, and knowing when to ask for help when needed. It was challenging and I learnt a lot about corporate politics as well.

What are some alternative jobs that you would be qualified for?

Unix Systems Administrator, Business Analyst, Technical Analyst, Systems Architect, Systems Analyst, Team Leader (Testing), and Project Manager.

"I believe people primarily get the job that they want through connecting with other people. Otherwise, you get a job that you do not want..."

What do you think it was that got you the job over other applicants?

I am quite confident it was attributed to the combination of both technical skills and people skills.

What advice would you give to students who have commenced a IT degree and want to get a great job when they graduate?

First, ensure that you know yourself and that you are honest about what you can do and what you cannot do. If you cannot program in C, it is better to admit that rather than to say something like, "That's not a problem!" and then tell yourself that you will learn it as you go along.

Next, find those seniors who are willing to believe in you and willing to give you a chance. Those are the people that will advocate your ideas and actions, and really help you when you need help.

Network, network, network. Know who knows what and who doesn't know what! When you work in IT projects, you will find a challenging task facing you. Knowing who to ask for help means tapping into your people network. I learned that I needed to open up and talk with people in order to establish connections with them.

What were your biggest mistakes during your life when applying for jobs? How would you have done it better?

1. Blindly applying for jobs without learning much about the company. I should have planned for more time to understand the company's needs and then reflect on whether my needs matched with theirs or not. I was hungry for industry experience in IT – I thought I could get into any IT firm and then hop to another if it didn't suit me.
2. Not getting out of my comfort zone to go out and network with people at a social level. I believe people primarily get the job that they want through connecting with other people. Otherwise, you get a job that you do not want.

What type of activities were you involved in at university and high school, and did they give you any skills that you use in your job now?

I was a tutor, class representative, and treasurer for i.Soc (Information Systems Society) during my undergraduate years. Those experiences definitely helped me in knowing how to talk with people, understanding different work environments and the culture that we work in.

What was the most surprising thing about working full time in IT that you did not expect?

On the first day of my job, I was asked to remove my tie and get rid of my suit. That was surprising. A senior colleague of mine wore socks with different colours – one yellow and the other red. That was shocking. Overall, I enjoyed my job thoroughly although the start was a bit difficult. I was most surprised that I found the projects and tasks no longer challenging once I had learnt the works of the systems and sub-systems. I wanted something that was intellectually more stimulating.

If you could go back to the start of your degree and change anything you did since then, what would it be?

I would build on my English (how to write) and Math (how to think).

Where do you see yourself in five year's time?

Researching, teaching, and contributing to the world of knowledge.

Back to Case studies

Home Glossary Site map

Credits
Please read The University of Sydney website privacy statement and disclaimer.
This website is maintained by UniServe Science for the Faculties of the Sciences, The University of Sydney
Please email feedback and comments to: BioSciCH@mail.usyd.edu.au