Working life in a software company

It’s the industry with some of the most extravagant success stories and extraordinary characters, but what’s life really like working for a software company? UK based tech company Scott Logic has published a series of employee stories detailing life behind the code, and it gives great insight for graduates who want to work in software development.
The stories come from Lead Developers, Graduate Developers, Test Engineers, Senior Developers and even the Head of Development – offering students a real insight into each rung on the ladder of a software company.

If you’ve ever been interested in a career in software development these are invaluable stories to read through and get an idea of working life in a leading business. Below are some key takeaways from the stories told by the employees.

Graduate Developer
Jack, who works in Scott Logic’s Edinburgh office, aims to arrive at work early to look over his previous day and plan his activities in. After a brief meeting to discuss any problems and to plan the day, Jack gets to work. At lunch he plays Fifa and explores Edinburgh’s best places to eat, before spending the afternoon working hard. He works in a team of 2 and is encouraged to pass ideas around to solve problems.

Jack’s advice to graduates:
• Don’t leave a task undone if you can tidy it up with a bit of extra time. It’s better to leave a bit late happy than to leave dead on time and worried about an incomplete task.
• Don’t be afraid to learn new skills. As a graduate developer, you’ll be expanding all of your skills and pushing the boundaries of what you know. Embrace it!
• Don’t be afraid to ask questions – Scott Logic in particular encourages it, as do most leading tech companies.

Senior Developer
Further up the chain, a senior developer is a step above a developer and two above a graduate. Steven, a developer in Edinburgh, loves the social side of working in a software company. He also works hard, with a morning comprising of lots of client interaction, working through workloads assigned to him and liasing with other developers.

Steven’s advice:
• Don’t forget Google. Even a senior developer admits he often uses Google to find solutions for common problems. Don’t go too in depth when you can find the answer in a simpler fashion.
• Do ask questions – this is the same as Jack’s advice above. Notice a trend? Both guys encourage open discussion as part of a supportive work environment.

Technical Architect
A fairly fancy sounding job title, a tech architect is responsible for setting up and maintaining networks and systems. Matt at Scott Logic deals with issues as part of a team and solves problems with systems and code.

Matt’s advice:
• Don’t feel penned in by your degree. Matt studied outside of computing but retrained as part of a graduate scheme.
• Don’t ignore the anomaly; it’s a challenge to find the explanation.
• Don’t be intimidated by the amount of intelligent colleagues you’ll have. You’re part of a team now and can draw on them for help.

The following two tabs change content below.

Sinead Morrissey

"Professional napper with a love of all things fashion and beauty. Easily bribed with a bag of Doritos."

You Might Also Like

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>