Company Culture

Here's where you'll find information on what it's like to be part of Code for Australia day-to-day.

Where To Find Things

We pride ourselves on having great documentation, but sometimes it's tricky knowing where to look.

Here's a rough guide:

  • Google Drive is where we keep all of our documents safe. Team members have access to everything at Code for Australia once we get them sorted with an email address. With this freedom we encourage you to peruse and read freely, but ask you not move or delete things.

  • We use Trello to map our work and processes, including boards especially for onboarding and for navigating what it means to be an ambassador of Code for Australia as a Fellow.

  • Fluid information on plans and meetings are managed through Slack and Google Calendar - so those are the best ones to keep an eye on.

Our Office

A tiny history: Alvaro started working out of the Henley Club in 2014, then we moved to Teamsquare in June 2014 when Michael and Katherine were setting up Teamsquare (now YBF Ventures). We were one of the first members in the space when Teamsquare occupied only Level 1. We stayed on as Teamsquare grew around us to fill 3 of the 4 levels. Then we missed having windows and direct sunlight, so we moved to Digital Garden on level 1, 237 Exhibition Street.

When we heard that our friends at Today were vacating their old digs, we jumped at the opportunity to move into their old space at 4 Brunswick Place, which was converted into a coworking space for digital types. This is now called Neighbourhood Work and is a place we love calling home.

Oh, and you can drop by at any time. We love seeing you.

Our Culture

We have many artefacts that try and sum up our culture.

One is the aforementioned Ambassador Guidebook. Another is a Trello Board called We Are Code for Australia. You can find both below or chat to any of our amazing community to hear what it's like from a human.

Our Code of Conduct

Code for Australia is dedicating to creating a safe and respectful place for people to bring their full selves. Read over our Code of Conduct which has practical guidelines of how we do this, and what we expect from every member of our community.

We're always up for hearing how our Code of Conduct can be improved. Feel free to reach out via our contact page here.

Our Current Focus

We're an open book. Have a look at our regular Open Nouse posts on our blog to see what's happening in our world. We also share updates during our Open Houses. Find out when they're next running here.

You can also reach out to any of the Code for Australia team via meetings or on Slack or email, anytime.

For Fellows working with Code for Australia, you also can check out the Base Team's Weekly Sprint Board at any time too.

Our Rituals

Here are some of our weekly / fortnightly / monthly practices, which are defined by the team working together (this includes Base Team along with our Fellowship Teams).

  • Sprint Planning to work out what you’ll work on

  • Regular Retrospectives to reflect and make incremental improvements

  • Show & Tell as you go (via showcases) - not waiting till something’s perfect to share it

  • Open Houses once every six weeks-ish (organised by Base Team)

  • Ongoing mentorship from great minds (supported and connected by Base Team, initiated by you)

  • Team lunches every Friday

  • Sharing our music taste on Slack (whenever the rhythm calls)

We love face to face time - there really is no substitute for it for teaming well. Here's a rough guide on what that looks like in practice.

Within Fellowship Teams

We encourage Fellows to hold the following meetings and rituals with their government partners.

  • Showcase (every two to four weeks, on top of Open Houses)

  • Sprint Planning (every one to two weeks)

  • Retrospective (every one to two weeks)

We, the Base Team, also run retrospectives with government partners as a cohort depending on how many Fellowships are running. We hold these about once a month.

Within The Base Team

  • Every week for sprint planning and finances

  • Every two weeks for a retrospective


  • Once a month for a team-wide retro, including the Base Team and all Fellows

  • Every Friday is team day, where Fellows head to a co-working space (with Base Team if in Melbourne) to share, learn and work together. Each cohort of Fellows design their own Fridays, here are some sessions we've run in the past:

    • Snacks & Scandal - an open Q&A session where the Base Team share what else is happening within Code for Australia and Code for All, what we’re cooking up outside of the Fellowship programs and where everyone else can share what other projects they are working on outside of CfA.

    • Guest Speakers of their choosing. Can be a peer-led learning session.

    • Trouble-Shooting Sessions - we get hands-on as a team and solve common problems collectively, or bring in a someone else to run clinics where Fellows can get coaching, help, guidance with specific issues they're facing on their project.

All Fellows, Individually

  • One-on-one with someone from Base Team to check in and see how things are going

  • At their favourite place in the city (if Melbourne), or their favourite platform (if online)

  • At a frequency of their choosing - definitely in week one and week six of the Fellowship, then however often they would like

Our Work-Life Balance

Code for Australia encourages everybody to follow their passions - seriously, ask some of the team what they're working on.

No one needs to work the nine to five like a robot. As long as they're supporting their team, and getting things done, we are happy for folks to work when and where they like, subject to what their team agrees on and what works for our government partners.