Pros
High trust & ownership: You’re given real responsibility early. If you show initiative, leadership will trust you to design and own systems end-to-end rather than micromanage. Strong learning environment: Great place to grow quickly, especially if you’re motivated. I was able to significantly deepen my skills across IT operations, security, automation, cloud-first tooling, and compliance. Modern tech stack: Cloud-first SaaS company using Google Workspace, Kandji, Intune, Automox, CrowdStrike, Jira, Confluence, and modern security/compliance platforms. You’re not fighting legacy infrastructure. Career acceleration: Exposure to projects that would normally take years to access elsewhere — SOC-2 preparation, security incident response, endpoint vulnerability reduction at scale, MDM migrations, automation initiatives, and vendor negotiations. Supportive teammates: Smart, collaborative people who genuinely want to help each other succeed. Flexibility: Hybrid/remote work is well supported, with reasonable flexibility when expectations are clearly communicated. Meaningful impact: Your work directly affects customers and global venue operations. Gym/Showers inside the Melbourne office is super nice! Amazing Snacks and Monthly pub lunches. The work culture is extremely good.
Cons
Very low pay: Compensation is significantly below market, particularly for IT and Security roles. Pay does not reflect the scope, complexity, or risk of the work being performed. Job title mismatch: Official IT job titles do not align with the actual responsibilities. The role often covers IT Operations, Security Engineering, Compliance, Automation, and Support — without title or pay reflecting that reality. Fast growth = pressure: Rapid scaling leads to shifting priorities, heavy workloads, and frequent context switching. Under-resourced IT & Security: These functions are often reactive and stretched thin, playing catch-up to business growth. Role scope creep: High performers tend to absorb more and more responsibility without formal recognition. Process maturity still evolving: Documentation and long-term planning lag behind growth and rely heavily on institutional knowledge.
