Engineering Team

We're currently hiring for remote team members in the following states:  DC, DE, GA, MA, MD, NC, NH, NJ, OH, PA, SC, UT, and VA.

We're AWeber, a remote‑first company that helps small businesses around the world form meaningful connections with their customers and grow their businesses using our marketing communication software. We are fanatical about small businesses and we hope you are too!

At AWeber, agentic development is core to how we build. Our engineers spend most of their time designing agents and agentic engineering systems, reviewing agent‑generated work for quality and correctness, and coordinating that work across the codebase. As an Engineering Team Lead, you build a small team of engineers who do exactly that into a high‑performing, healthy, well‑functioning group, and you lead them from inside the work.

This is a player‑coach role. You run 1:1s, grow careers, own hiring and reviews for your team, and own its delivery and quality bar. You also stay hands‑on: designing solutions, reviewing agent output on the risky paths, and shipping the hard parts yourself. We are not looking for someone who leaves the code behind. We are looking for the senior engineer other people already rely on, who leads and grows a team without losing their own hands on the keyboard. Your mission is to help a capable, curious group ship work the org can trust, move quickly without cutting corners, and consistently finish what they start.

On any given day, you could be found reviewing an agent‑generated pull request on a risky path and coaching the engineer on how they verified it, running a 1:1 that turns someone's recurring frustration into an owned initiative, interviewing a candidate and sharpening how your team evaluates new hires, pairing for an hour to unblock a stalled migration, deciding what comes off the plate so your team is not underwater, or carrying your team's priorities into a cross‑team engineering forum.

You'll thrive as an Engineering Team Lead if you

• Lead from inside the work, stay hands‑on in the code, and measure success by your team's output and growth rather than your own.
• Have a bias to action, turning recurring problems into owned, dated, shipped solutions instead of letting good ideas recirculate.
• Treat verification and trust as the real throughput limit in an AI‑first org, and hold the line on quality without stalling momentum.
• Make people decisions and difficult trade‑offs with care, and own the outcomes.
• Establish standards and inspire others, not just through your own expertise but through mentorship and advocacy.
• Default to open, transparent communication, and adapt your message to engineers, peers, product partners, and leadership.
• Stay calm and steady when priorities compete, and keep your team oriented on what matters most.