Staff Software Engineer

Feathr is a nonprofit marketing SaaS platform that helps more than 1,300 nonprofits build purposeful community connections and grow their impact. The Staff Software Engineer owns product areas, shapes technical direction and solutions, builds the most challenging software, and advises on architecture, feasibility, hiring, and engineering standards across the full stack.

Responsibilities:

• The technical solutions for the bets in your product areas, including the technical scope and the tradeoffs behind it
• The hardest technical work on the board, which you build yourself
• The quality standards for your areas, including code review and testing strategy
• Work you ship, until the bet closes at outcome confirmed. The team monitors the outcome metric for about 30 days after launch, and you handle monitoring, debugging, and fixes during that period
• Bets: feasibility, cost, and risk during discovery, and how the team breaks them into work items that match the technical scope
• Architecture: long-term technology choices, major changes to shared systems, and standards shared across pods
• Engineering hiring
• Technical scopes for the bets in your areas, with the options, the chosen approach, and the tradeoffs. These documents extend the Scope artifact from discovery
• Prototypes that retire feasibility risk before the team writes production code
• Working software, including the most challenging pieces in your product areas
• Standards, templates, and examples that other engineers reuse
• Upgrade and migration plans for the systems you own

Requirements:

• 8+ years building software that runs in production
• Expert skill in backend or frontend development. You can work productively in both
• Experience with our stack or a similar stack: Python and Flask-style APIs, MongoDB, Elasticsearch, and Redis on the backend; React and TypeScript on the frontend
• You have scoped and shipped distributed systems that use queues, caches, and search
• You have run software on AWS and Kubernetes at production scale
• You have scoped solutions that other engineers built successfully
• You have mentored engineers and helped them advance to larger roles
• You write clearly: your technical scopes and decisions are easy to follow
• You have built and improved CI/CD pipelines, and you consider security in the solutions you scope