Senior Software Engineer positions focus on delivering results in their domain. This page aggregates open Senior Software Engineer roles and what employers typically expect.
At Bloomerang, we believe change happens on purpose. We champion the power and potential of nonprofits, igniting next-level impact with the team and technology built for purpose. Our powerful giving platform and stellar support enable tens of thousands of nonprofits to raise more, recruit more, and retain more, fueling maximum impact and raising the bar on what’s possible for the nonprofit sector. That's why, even as the nonprofit sector sees declines in giving, Bloomerang customers raise more year over year. We're also in the business of creating thriving employees. Join a mission-driven culture built on our core values of Simplify, Care and Act. We know our people are the key to our success, and we're proud to be home to some of the most innovative and skilled individuals in the workforce today. Come feel invigorated and unstoppable with us! The Role As a Senior Software Engineer (Technical Lead) at Bloomerang, you are the senior-most technical engineer on a delivery team and a key driver of the team’s technical success. You are a hands-on engineer who writes code, solves difficult problems, shapes technical direction, and helps the team consistently deliver high-quality software for the nonprofits we serve. This is an opportunity to help define what great engineering looks like in an AI-first world. AI is changing what individual engineers and entire teams can accomplish, and we're actively exploring how to use that leverage to build better software, automate the work around software development, and give our engineers more time to focus on the problems that matter. You'll be one of the technical leaders helping turn that opportunity into everyday engineering practice. You will own the technical outcomes for your team, partnering with Product, QA, and Engineering to turn ambiguous problems into practical solutions. You'll lead through technical excellence by mentoring engineers, raising the team's engineering standards, and using AI and automation to increase team leverage, improve engineering workflows, and ultimately help us build better products for the nonprofits that depend on us. What You Will Do Own the team's technical outcomes. Set a high bar for code quality, reliability, maintainability, security, and technical execution, and make sure the team follows through on what it ships. Lead technical direction and design within your team’s domain. Translate product and business problems into pragmatic technical solutions, independently shaping the approach for small-to-moderately scoped features and driving them through implementation. Partner with Staff Engineers and architects when decisions have broader cross-team or cross-product implications. Make the team better. Mentor engineers across experience levels, provide actionable technical feedback, identify opportunities for growth, and help engineers develop the judgment and skills to solve increasingly complex problems independently. Champion AI-driven engineering and automation. Use AI tools such as Claude Code and other emerging tools as part of your daily development workflow, while identifying opportunities to automate repetitive or high-friction engineering work. Experiment with new approaches, measure their effectiveness, and turn successful practices into repeatable workflows that increase team leverage, improve quality, and accelerate delivery. Balance delivery with long-term technical health. Proactively identify technical debt, architectural risks, performance concerns, and reliability issues, and work with the team to address them while staying focused on product outcomes. Diagnose and resolve complex technical problems. Use deep debugging, observability, and system-level knowledge to find root causes and improve the systems and practices that prevent issues from recurring. Own quality end to end. Build quality into the development process through appropriate automated testing, code review, observability, and continuous feedback. What You Need to Succeed T…