Build the software that serves the local church, and set the standard the rest of the team builds to, as we grow from a scale-up into a world-class engineering group. This is a senior, hands-on individual-contributor role with real ownership, foundational problems to solve, and room to grow.
Amazing Life exists to serve the local church, and the world's greatest mission deserves the world's greatest tools. We are moving from fast, informal systems to durable, scalable platforms without losing speed or ownership. The software you write here supports churches running services, caring for people, and reaching their communities. What you ship affects real people, every week.
You will build and run features end to end on our platform, a Node and Next.js application on AWS. You set the standard by shipping. A lot of what a mature engineering organization takes for granted has not been written here yet, and the patterns you establish doing real product work become the ones the rest of the team follows. You will have real ownership, in partnership with engineering leadership, of:
You will not be handed a fully specified ticket. Breaking a large, vague problem into increments that ship is a core part of the job.
Engineering runs a shared on-call rotation, so you support what you ship. We are early in building formal incident practice and you will help shape it, including blameless reviews, sustainable rotations, and recovery time after after-hours work.
This role grows in technical scope, architectural ownership, and influence. Near term you are deeply hands-on, shipping on the current platform and laying down the patterns the team builds on. Over time you take on larger and higher-stakes work, shape architecture beyond your immediate team, and grow other engineers. In your first 90 days, success looks like shipping meaningful changes to production, earning trust in code review, and landing at least one thing the rest of the team then builds on.
We are not a finished system today, and that is why this role exists. You will meet an older codebase nobody remembers writing, gaps in automation, and competing priorities. This role fits you if you:
It is likely not for you if you want narrowly scoped, ticket-driven work, or a codebase that is already clean.
Above all, we're looking for someone who learns fast and builds real capability in new, uncertain areas. That matters more than any single tool on your CV. The essentials:
Everything below is a bonus rather than a requirement. You will not have experience with all of them, and any combination of skills in these areas is welcome:
If you have a strong foundation in building software and a track record of picking up new areas quickly, we would like to hear from you, even if you do not match every line above.
Senior Software Engineer
Crimson Academies
Senior Software Engineer - Full Stack
Lawvu
Software Engineer
Kiwibankpeople
Software Engineer - Typescript/React Fullstack
Objective Corporation
Java Software Engineer
Dotmatics
EverWell - Senior Software Engineer (Remote, NZ)
Evercommerce