Time since we first saw it
Day 85
Up longer than most. Similar jobs usually come down between day 2 and day 14.
From 954 similar postings that came down. Coming down is not always a hire.
You MUST be eligible to work in NZ to be considered for this role
8+ Years in Software Engineering with significant time spent as a technical lead in Platform, Infrastructure, or DevEx.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 85
Up longer than most. Similar jobs usually come down between day 2 and day 14.
From 954 similar postings that came down. Coming down is not always a hire.
1 open job
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Production Agentic Experience: You have actually operated non-deterministic LLM/agentic workloads in production—managing cost governance, tracing, and eval pipelines, not just building prototype wrapper apps. - Backend & Cloud Mastery: Deep proficiency in C# or Python paired with strong AWS cloud-native expertise (Lambda, API Gateway, Bedrock, IAM/KMS). - Developer Empathy & Leadership: A track record of driving tool adoption and technical standards across multiple teams through pairing, mentorship, and clear communication rather than authority.
Tech Stack You'll Touch Claude Agent SDK • AWS Bedrock • LangGraph / LangChain • OTEL • Langfuse • New Relic • C# / .NET • Python • AWS Lambda • .NET Aspire • LocalStack Ready to build the platform that powers the future of our engineering organization?
What You'll Do - Architect & Build Agentic Systems: Design internal supervisor loops, router patterns, and state machines using the Claude Agent SDK, AWS Bedrock, and frameworks like LangGraph. - Run Workloads at Scale: Establish SLOs for agent success rates, latency, and token efficiency. Take point on observability, prompt versioning, and incident response when agents misbehave or hallucinate.
- Run Workloads at Scale: Establish SLOs for agent success rates, latency, and token efficiency. Take point on observability, prompt versioning, and incident response when agents misbehave or hallucinate. - Elevate Developer Experience: Identify SDLC bottlenecks, optimize build/CI performance, refine local dev setups (LocalStack, .NET Aspire), and tune AWS serverless architectures (Lambda cold-starts, SnapStart). - Set the Bar for AI Safety & Quality: Define reusable component models, context retrieval (RAG) architecture, and guardrails to ensure autonomous systems degrade safely.
Complete your application on job-boards.greenhouse.io. The employer’s form will show what is required.
Already applied? Track this application
Most companies are still experimenting with AI wrappers in local environments. At Pushpay, we are building production-grade agentic systems that directly amplify how our entire engineering organization builds, ships, and operates software.
As a Staff AI Platform Engineer, you will operate with significant autonomy to architect, run, and scale our internal agentic platforms and developer tooling (like PR review agents, SDLC copilots, and context engines). You won't just build these systems—you will own their operational discipline, cost governance, evaluation suites, and reliability in production, acting as a force multiplier for every engineer across Pushpay.
True Engineering Leverage: You aren't building internal gimmicks. You are designing systems that fundamentally transform our SDLC and reduce friction for every product team.
Production-Grade Non-Determinism: You treat agents as distributed, operational workloads—implementing token budgets, trace-level observability (OTEL, Langfuse), SLOs/SLIs, and eval-driven regression testing before code hits main.
Influence Without Dictatorship: You won't enforce top-down mandates. You will drive org-wide adoption of tools like Claude Code and custom MCP implementations through technical credibility, pairing with teams, and building platforms engineers want to use.
Architect & Build Agentic Systems: Design internal supervisor loops, router patterns, and state machines using the Claude Agent SDK, AWS Bedrock, and frameworks like LangGraph.
Run Workloads at Scale: Establish SLOs for agent success rates, latency, and token efficiency. Take point on observability, prompt versioning, and incident response when agents misbehave or hallucinate.
Elevate Developer Experience: Identify SDLC bottlenecks, optimize build/CI performance, refine local dev setups (LocalStack, .NET Aspire), and tune AWS serverless architectures (Lambda cold-starts, SnapStart).
Set the Bar for AI Safety & Quality: Define reusable component models, context retrieval (RAG) architecture, and guardrails to ensure autonomous systems degrade safely.
8+ Years in Software Engineering with significant time spent as a technical lead in Platform, Infrastructure, or DevEx.
Production Agentic Experience: You have actually operated non-deterministic LLM/agentic workloads in production—managing cost governance, tracing, and eval pipelines, not just building prototype wrapper apps.
Backend & Cloud Mastery: Deep proficiency in C# or Python paired with strong AWS cloud-native expertise (Lambda, API Gateway, Bedrock, IAM/KMS).
Developer Empathy & Leadership: A track record of driving tool adoption and technical standards across multiple teams through pairing, mentorship, and clear communication rather than authority.
Claude Agent SDK • AWS Bedrock • LangGraph / LangChain • OTEL • Langfuse • New Relic • C# / .NET • Python • AWS Lambda • .NET Aspire • LocalStack
Ready to build the platform that powers the future of our engineering organization?
Apply now to join Pushpay's Enablement team as our Staff AI Platform Engineer!
You MUST be eligible to work in NZ to be considered for this role.
We file this job under AI Engineer, by the work the posting describes.
AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.
Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.
An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Auckland
Working pattern and location restrictions need checking in the full posting.
Ready to build the platform that powers the future of our engineering organization? Apply now to join Pushpay's Enablement team as our Staff AI Platform Engineer! You MUST be eligible to work in NZ to be considered for this role.