The Team
Five writers, four cities, one rule: you have to have done the job before you write about the job. Each of us covers one area of the industry and occasionally wanders into a neighbour’s. Here’s who covers what, what we did before we started writing about it, and what we do when we’re not.
Marcus Tully — Editor
Telecoms, networks and devices. Melbourne. Marcus has spent 22 years on the telecommunications round, first for a trade weekly and then for a wire service, and has sat through more NBN Senate Estimates hearings than is healthy. He edits Technology Spectator and writes the NBN and telecoms coverage, the devices and home networking pieces, and much of the government and policy reporting. He reads wholesale price schedules for fun, treats every press release as a claim to be checked against the ACCC or the company’s own filings, and keeps a spreadsheet of every NBN completion date ever promised. Outside work he restores 1960s valve radios, badly, and drives the Hume and the Calder more often than is sensible. Regular readers will notice he opens with a number and occasionally types “alot”; the number is always right.
Declan Ferris — Infrastructure Correspondent
Data centres and infrastructure. Sydney. Declan is an electrical engineer by training who did five years of data centre fit-outs along Sydney’s M7 corridor before moving to the writing side. He covers data centres, grid connections, power and cooling, fibre routes and the subsea cables that connect the country, and can tell you what a megawatt costs in Eastern Creek versus Erskine Park. He thinks in worked examples and would rather show you the arithmetic than the adjective. Usually somewhere near the M7 on a bicycle, further than is sensible, on weekends; keeps a map of the cable landings pinned above his desk next to the ride routes.
Anjali Mehta — Enterprise & Cloud Editor
Enterprise IT, cloud and software. Brisbane. Anjali ran systems for a Brisbane freight company for six years and then spent four more at a managed hosting provider before she started writing about the industry instead of being paged by it. She covers enterprise IT, cloud economics, software and licensing and data platforms, and cares most about what breaks on a Tuesday afternoon rather than what was announced at a conference. Writes in the second person because she’s usually telling you what to check next. Grows chillies she can’t eat and has strong views about on-call rosters.
Sophie Lindqvist — AI, Start-ups & Fintech Editor
AI, start-ups and fintech. Sydney. Sophie was a product manager at two Sydney start-ups, a payments company that folded and a software company that was acquired, and she is candid about which experience taught her more. She covers artificial intelligence as it is actually deployed, start-ups and venture terms, and payments and fintech regulation from Surry Hills, with a bias toward what is in production rather than what is demoed. Short paragraphs, one verdict per section, and a habit of saying “reckon”. Swims in the ocean year-round at Bronte and Coogee and would like you to know the water is fine.
Tom Abernathy — Security Editor
Security and privacy. Canberra. Tom spent seven years in a bank’s security operations centre and three at a consultancy doing incident response, which means he has been in the room for the phone call nobody wants. He covers cyber security, breach response and the Privacy Act, identity and the Essential Eight. Terse, numbers first, structures everything by the hour or the day, and finishes with a joke because someone has to. Pessimistic by profession, cheerful by nature. Bakes sourdough with a nine-year-old starter and, since the Sunday-morning call he still describes in his breach timeline, only bakes on Fridays.
How we work
Every article carries a real byline and a real date. Writers cover their own beat and occasionally wander into a neighbour’s, which we don’t mind. Facts, figures, names and dates are checked; the voice is the writer’s own, imperfections included. Anything we get wrong gets fixed on the page with a note. The editorial standards page spells out how, and the contact form is how you tell us.