Document processing automation and data processing projects for the Australian Department of Defence, working under a Baseline Security Clearance.
Overview
I worked as a Junior Java Developer at Jakeman Business Solutions (later Citadel), contracted to the Australian Department of Defence. My role involved developing enterprise software solutions for document processing automation, productivity tools, and data processing projects. This was my first professional development role after university, and it provided a strong foundation in enterprise software development practices.
Technical Work
I developed enterprise code across multiple languages and frameworks, primarily using Java for backend services, SQL for data management, and Angular for frontend interfaces. The work involved building automation pipelines for processing large volumes of documents, creating productivity tools for defence personnel, and developing data processing systems that handled sensitive information.
Professional Development
Working in the defence sector taught me the importance of rigorous software engineering practices, security-conscious development, and professional communication. I gained experience working directly with clients to understand requirements and deliver solutions, and I developed skills with enterprise project management tools like Jira. I held a Baseline Security Clearance throughout my tenure.
What I Learned
Enterprise Software Discipline
The defence sector demands a level of rigour that most software environments don't. I learned to write code that prioritises correctness and auditability over cleverness. Every change needed to be justified, documented, and reviewed. This discipline โ writing code as if someone's career depends on it working correctly โ became a habit that serves me in every role since.
Security-First Thinking
Working under a Baseline Security Clearance and handling sensitive data taught me to think about security as a first-class concern, not an afterthought. I learned about data classification, access controls, secure coding practices, and why 'it works on my machine' is never an acceptable standard when the stakes are high.
Client Communication
This was my first role working directly with non-technical clients. I learned to translate technical concepts into plain language, to ask the right questions during requirements gathering, and to manage expectations when timelines shifted. The ability to bridge the gap between technical implementation and business needs is a skill I use daily.
From University to Industry
As my first professional role, Defence was where I learned how real software teams operate โ version control workflows, code review culture, deployment processes, and the importance of writing maintainable code that others will inherit. The gap between university assignments and production software was significant, and this role bridged it.
Key Challenges
- Developing software under strict security and compliance requirements
- Building reliable document processing automation for high-volume workflows
- Communicating technical solutions to non-technical stakeholders