• Responsible for the reliability and operational readiness of the AEM CS Platform • Improving monitoring systems, driving incident analysis, and automating operational tasks • Work in an Agile team to build scalable services • Help engineer our platform strategy • Translate business requirements into architectural and implementation choices • Capture loosely defined requirements/concepts and expand them into complete solutions together with your team • Review and provide feedback on features, technology, architecture, designs • Define and implement DevOps components to operate the platform • Own the reliability, performance, and operational readiness of the storage components. • Leverage AI tools to automate repetitive operational work.

• Work in an Agile software development environment to design, code, test, debug, document, and deploy software applications • Build production‑ready cloud and desktop applications that deliver advanced geospatial, analytical, and modeling capabilities • Translate business and system requirements into scalable, maintainable software designs. • Learn and apply concepts in water-resources engineering, including flood modeling and mapping workflows • Develop automated unit, integration, and functional tests to ensure long‑term code quality and maintainability • Collaborate with cross‑functional teams - including civil engineers, GIS specialists, and project managers - to define technical approaches and deliver high‑value solutions • Participate in design reviews, code reviews, and continuous improvement of software development practices

• Work responsibly with stakeholders using team tools (Slack, Jira, Github) • Drive decision-making processes that match the importance and urgency of decisions • Foster productive discussions with strong opinions weakly held • Collaborate with Product, Design, and Data teams to plan viable, desirable, and feasible solutions • Build technical solutions using Node.js, TypeScript, PostgreSQL, Terraform, and AI • Deploy and manage services in AWS staging and production environments • Improve reliability through testing, observability, monitoring, and deployment automation • Participate in support rotations and incident management • Evaluate and improve team processes through regular reflection and experimentation

• Scope, design, build, and maintain APIs, services, and workflows that reliably process high-scale money movement and settlement. • Own the architectural direction for the settlement domain in partnership with the CTO; produce and maintain architecture documentation (current state, target state, and migration plan) and drive alignment across teams. • Review and approve architecture decision records (ADRs) and technical designs for settlement-related changes; ensure decisions meet standards for correctness, operability, security, and long-term maintainability. • Drive end-to-end execution for large, ambiguous initiatives: reduce risk early, align stakeholders, and deliver in phases. • Improve correctness and operational safety across settlement flows: deeply understand how money moves end-to-end (timing, state transitions, adjustments, exceptions), design for edge cases, and implement idempotency, reconciliation guarantees, safe backfills, incident readiness, and disciplined releases. • Partner with Engineering Manager, Product, Performance, CTO, and other Staff peers to shape roadmaps and strategy for settlement—develop deep expertise in both the technical system and the business needs (what clients require from settlement, reporting, timing, and exception handling) and translate that into durable platform capabilities. • Raise engineering standards across the team and broader org by partnering with other Staff engineers to define and drive consistent patterns for building and operating money- movement systems (design reviews, abstractions, testing strategy, observability, and operational practices) across monolith + microservices. • Drive adoption of AI-assisted engineering practices (tooling, workflows, guardrails) to improve throughput and quality—especially for testing, incident response, code review, and documentation.