Junior Software Engineer

at  Dye Durham

WHAT DO YOU NEED TO BE CONSIDERED?

We’re not expecting you to have years and years of experience in software engineering, nor would we expect that you know how to build applications straight away!

What we are looking for is;

• Someone with passion for their industry, with a desire to learn and grow.
• Someone who loves to work collaboratively as part of a team, able to communicate well.
• Basic programming knowledge (preferably .NET) and an understanding of best practices e.g. SOLID principles. We aren’t going to expect you to know them off by heart, but an idea of what following the SOLID principles means would help you in this role.
• Open to new ideas and ways of working, able to take a concept and implement into your everyday.
• Experience with microservices and cloud platforms would be beneficial but as long as you’re open to learning new things, not essential!

You will join an experienced and supportive Software Engineering team of between 6 engineers, working on one of our main systems that we have for our large enterprise customers in Australia. This is an on-site position and so you must be able to commute to either our Brisbane, Sydney or Melbourne office, whichever works for you.
You will have many opportunities to pair with Senior Engineers to work through problems and build up your skills and knowledge.

You’ll have a wide and varied role, but we think the most important are;

• Work directly on designing, developing and maintaining API’s for one of our main products in Australia.
• Understanding testing and incorporating it into your code.
• Create accurate and up-to-date documentation
• Pairing with other members of the team and department.
• Learn, understand and incorporate programming best practices into your day-to-day, ensuring the work you are doing is the best it can be.
• Become confident in your work and in yourself as an engineer, always looking for new learning and development opportunities.
• Understand that mistakes are learning opportunities, and that to become an excellent engineer, it’s not always about what goes right, but also what goes wrong and how to avoid that in the future.