Promoted into a newly created senior role to drive transformation across the business: a data driven operating model and oversight of QA delivery.
Lew Brown
Quality engineering and business intelligence. Twelve years where data, software and operations meet, the last three spent owning quality across the bulk of our client work. I map the critical paths, test them by hand, then build the automated regression suites, and hold final say on go/no-go for what I cover. On the data side, I pull a business's scattered systems into one source of truth and build the platforms and automations that turn it into decisions, not just another dashboard.
Experience
Owned quality across the agency's client web projects, and built software hands on, including the flagship product I developed solo from scratch.
Promoted from Customer Care Executive into a Business Analyst role created through a transformation that cut the contact centre's executive headcount. The department later moved under the Customer Journey business unit.
Predominantly contact centre work, resolving customer issues by phone, email and mail, with the back office responsibilities that led to the analyst role.
How I work
Quality Engineering
I'm the last yes or no before something ships, and I put my name on it. I work out the paths that have to keep working, check them by hand every release, then automate the ones worth it. Knowing what to test, and catching what a passing build hides, is what takes experience.
Business Intelligence
Deciding what is worth measuring, spotting when a number is lying, and turning a contradictory pile of operational data into something a person can act on. The chart is the easy last step.
Transformation & Automation
Understanding how a business actually works, then cutting the waste and manual grind that slow it down, so the team gets further, faster.
Product & Platform
Building customer facing apps and internal tools by hand, so they are fast, own their data, and stay usable by the people who aren't engineers and have to live in them.
Recent highlights
Quality Engineering at Atomix
Over three years I worked on quality across Atomix's client web projects, first as an engineer on the release gate, then as the Lead who evolved the approach. I built and maintained the bulk of the Key Functionality Checklists that map the critical paths to re-verify whenever anything changes (plugin updates, new features, template changes), run by hand against every release.
The step change came in my senior tenure: I took the team off manual testing and into automated end to end regression suites in Ghost Inspector, then, through regular catchups with the broader QA team across our Adelaide and Sri Lanka groups, explored and initiated the move to Playwright for tighter control and lower cost, overseeing the build with the analyst I had recruited and mentored, who stepped into my former role. Throughout I held final say on go/no-go on the bulk of the code that shipped.
Spanning my time at Atomix as QA Engineer and then as Lead, where ownership of the team's quality delivery became part of a newly created senior remit.
Working with AI
AI runs through most of my recent work. I build with Claude and Claude Code every day, design agentic workflows, and have written Claude skills the rest of the team uses for test suite and checklist generation. At Atomix I built AI into how we actually worked, including tracking real usage and cost so the spend stayed accountable rather than hand waved.
The harder skill is knowing where it belongs. AI is enormous leverage on the mechanical parts of a job, and a real liability the moment it is trusted to make a decision. I use it to move faster and reach further, then bring experience to bear on what is actually right. It amplifies the person doing the work. It does not replace the part that has to be accountable for the outcome.
“A computer can never be held accountable, therefore a computer must never make a management decision.”
IBM internal training presentation, 1979
In practice
- Claude and Claude Code, daily, for building and analysis
- Agentic workflows on OpenClaw, with custom skills shared across the team
- Operate a multi agent AI development pipeline as the product owner, scoping the work, reviewing every change, and holding the final say on what ships
- AI built into the operating model, not just the tooling
- Tracked AI spend by owner and API key, so nobody had to guess what it cost
- The judgment, and accountability for it, kept with a person
About
I work where data, development and operations overlap, drawn to the problems that sit between systems, where the insight is hiding and nobody has looked yet. Over twelve years across contact centres, e commerce, healthcare and digital agencies, I've built the reporting platforms, dashboards and automations that turn operational noise into decisions a business can act on.
Most recently I led business intelligence and transformation at Atomix, where I built an automated reporting platform from scratch and owned the products clients rely on. I work autonomously across a broad technical remit and care about work that is both rigorous and well made.
I build primarily in vanilla JavaScript, and I do it deliberately: fast, maintainable, and free of unnecessary abstraction. I want to leave behind systems that still make sense once I have gone.
Let's talk.
Open to the right opportunity. The quickest way to reach me is email, and I reply promptly.