Graduate Software Engineer | Reserve Bank of Australia

Collaborated closely with the development team by performing software development and testing to successfully integrate APIs, enhancing the functionality and capabilities of the product. Worked on completing small scale projects in Python and C# to introduce new features to the platform. Brainstormed, designed, and tested enhancements and new features to the system. Regularly provided input in development meetings with engineering team and developers.

Junior Software Engineer | Neurocom Pty Ltd

Collaborated closely with the development team by performing software development and testing to successfully integrate APIs, enhancing the functionality and capabilities of the product. Worked on completing small scale projects in Python and C# to introduce new features to the platform. Brainstormed, designed, and tested enhancements and new features to the system. Regularly provided input in development meetings with engineering team and developers.

Technical Sales Specialist | Neurocom Pty Ltd

Worked with MemberCheck and NameScan (AML/CTF) solutions providing technical demos and information to clients. Processed customer emails by finding a relevant service and providing information on our data acquisition, APIs, and UI. Performed inbound and outbound sales duties by drafting, negotiating, and reviewing agreements and closing client deals in a timely manner. Collaborated closely with the development team by performing software development and testing to successfully integrate APIs, enhancing the functionality and capabilities of the product.

University of Technology, Sydney

The comprehensive curriculum provided me with a strong foundation in various aspects of software development. Key subjects, such as Data Structures and Algorithms (DSA) and Programming Concepts, honed my problem-solving skills and coding proficiency. My education at UTS equipped me with a deep understanding of software design, development methodologies, and the ability to approach complex challenges systematically. The practical experience gained through various projects and coursework has instilled in me a passion for creating efficient and innovative software solutions.

Glenwood High School

I undertook a diverse range of subjects, further nurturing my passion for technology and business. Graduated with an ATAR of 95.35 completing subjects Software Design and Development, Business, Economics, Mathematics, Information Technology and English. Formed a solid foundation for my endeavors in the field of software engineering, empowering me to contribute meaningfully to innovative projects and teams

During my internship, I worked on developing and enhancing sanctions screening software, with a key focus on integrating AI to improve functionality and provide more accurate insights for customers. Our team followed an agile approach, working in small groups with frequent stand-ups to ensure rapid iterations and feedback loops. The objective was to deploy an AI-enhanced solution efficiently while maintaining high performance and regulatory compliance.

Initially, I felt both excited and challenged by the complexity of the project. The prospect of leveraging AI to enhance financial security was intriguing, yet the fast-paced environment and high expectations created moments of uncertainty. Additionally, as this was one of the first times I would be writing commercial level code, a sense of doubt was kicking in. There were also times when unexpected technical roadblocks arose, causing frustration, but overcoming these challenges provided a deep sense of accomplishment. Working collaboratively in an agile setting was rewarding, as it fostered a dynamic exchange of ideas and continuous learning. Nevertheless, it felt rewarding to work in a collaborative environment with the dynamic exchange of ideas providing a great opportunity for learning.

I did not know how valuable integrating AI into our systems would be. I believed that the pace of the project before proper research was not the best way to proceed and could lead to an unsustainable system with errors. The rapid integration of AI without comprehensive testing initially seemed risky, as it could introduce unintended biases or inefficiencies. This experience made me reconsider the importance of a more measured and research-backed approach to AI implementation, ensuring long-term sustainability and ethical compliance.

One difficulty was the decision to use an existing model or to create our own. This was a challenge as it could cut into the schedule if we were to create our own. On the other hand, using an existing model could be unsustainable due to potential biases, lack of transparency in decision-making, and the difficulty of adapting it to our specific needs. Additionally, existing models often come with privacy and security concerns, as they may not comply fully with regulatory requirements or could expose sensitive data to third party vulnerabilities. Balancing these trade-offs required careful evaluation to ensure that the final system was both effective and sustainable.

This experience deepened my understanding of how sustainability principles apply beyond environmental concerns, extending to technological and ethical sustainability. I learned that developing viable systems requires a balance between efficiency, accuracy, and long-term responsibility. Moving forward, I aim to continue exploring ethical AI implementation and advocate for sustainable software development practices.

Further reflecting on my experience above, whilst working on developing our systems I was to collaborate with a globally distributed team. The goal was to work together to using an agile approach ensuring alignment across different time zones and cultural perspectives. This experience exposed me to diverse working styles, communication preferences, and regulatory considerations in international markets.

Initially, I felt both excited and challenged by working in an intercultural team. While I appreciated the diverse perspectives, I also experienced moments of uncertainty when navigating different communication styles and expectations. Being from different parts of the world, especially Asia, most of the team was very fast-paced and did not appreciate falling behind schedule. I was also concerned as to how the team would communicate and work effectively due to the varying time zones,, which could cause delays in decision-making. At times, these circumstances became frustrating for the team as having to accommodate team members on a different schedule was difficult. However, I also found it rewarding to collaborate with professionals from different backgrounds, as it broadened my understanding of global software development practices.

Before this experience, I underestimated the impact of cultural and global differences in software development. I initially believed that technical expertise alone would drive the project’s success, but I quickly realized that effective collaboration across cultures requires strong communication, adaptability, and an awareness of different work ethics and expectations. I always believed that a locally situated team would be more productive and effective at achieving desired outcomes. However, this experience has reshaped my perspective and made me realise the benefits of working with globally distributed teams due to the thinking and ideas they bring to the table.

One major challenge was coordinating work across different time zones. With team members spread across multiple regions, scheduling meetings that accommodated everyone was difficult, often leading to delays in decision-making and feedback loops. There were instances where tasks were blocked overnight, waiting for responses from colleagues in other time zones, which sometimes slowed down our agile workflow. Additionally, aligning work schedules required careful planning, especially when considering cultural holidays and varying work cultures. For example, team members in some regions observed religious holidays such as Eid, during which availability was limited, while others worked through national holidays that were not recognised globally. These differences required us to proactively plan ahead, ensuring that key deliverables were not delayed due to unexpected absences. Work cultures also varied significantly. Some team members were accustomed to strict work-life balance policies, avoiding overtime and weekend work, while others operated in environments where extended hours were the norm. This contrast sometimes created misaligned expectations regarding availability and responsiveness.

I have gained a valuable lesson in the importance of understanding cultural and global contexts when working in software team. Whilst our technical objectives were aligned, we had different cultural nuances, work cultures and other personal differences. This deepened my appreciation for intercultural communication and the complexities of working in a global context. Moving forward, I aim to further develop my intercultural competence by engaging in more global projects and learning from diverse perspectives.