<p>Code for America believes government can work for the people, by the people, in the new digital age, and that government at all levels can and should work well for all people. For more than a decade, we’ve worked to show that with the mindful use of <span style="color: rgb(0, 0, 0);">technology, we can break down barriers, meet community needs, and find real solutions.</span></p> <p><span style="color: rgb(0, 0, 0);">Our employees build and transform government and community tools and services, making them so good they inspire change. We merge the best parts of technology, nonprofit, and government to help support the people who need it most.</span></p> <p><span style="color: rgb(0, 0, 0);">With a focus on transparency and fairness, and deep empathy for partners in government and community organizations and the people that our partners serve, we’re building a movement of motivated change agents driven by meaningful results and lasting impact.</span></p> <p><span style="color: rgb(0, 0, 0);">At Code for America, you contribute to exciting work while learning and developing in a supportive and flexible environment. Our compensation and benefits are holistic and thoughtfully curated to represent our employees and our mission. Help us drive real generational change that lasts.</span></p> <p> </p> <p><span style="color: rgb(0, 0, 0);">Code for America is looking for a talented<strong> Principal Software Engineer </strong>who will help define the technical standards and practices that our engineering discipline builds on — driving reliable, high-quality software delivery across multiple teams and projects that make public services more accessible and effective for the people who need them most.</span></p> <p><span style="color: rgb(0, 0, 0);">The pace of change in the policy and government landscape is accelerating at the same time that technology possibilities are shifting rapidly. Together, these shifts create new windows of opportunity to develop technical solutions that make critical public services more effective for the people who need them. Principal Software Engineers frame and solve the undefined technical problems that sit across or ahead of any single team's roadmap, so that the engineering discipline as a whole stays ready for those moments.</span></p> <p> </p> <h1><span style="color: rgb(0, 0, 0);"><strong>About the role: </strong></span></h1> <p><span style="color: rgb(0, 0, 0);">All Code for America software engineers are involved in every stage of our products' lifecycle, from prototyping and design to developing features in response to user feedback, to operating technical systems at scale. <strong>Principal Software Engineers </strong>pair deep technical expertise with cross-team influence — setting technical direction and best practices across Engineering, resolving our most ambiguous and highest-leverage technical problems, and raising the bar for how the discipline builds software.</span></p> <p><span style="color: rgb(0, 0, 0);">This role will report to the <strong>Director or Senior Director of Product Engineering</strong> and is expected to travel no more than <strong>10%</strong> of the time. </span></p> <p><span style="color: rgb(0, 0, 0);">Code for America is based in California and can employ those who reside full-time within the United States. This is a remote position.</span><br><br></p> <h1><span style="color: rgb(0, 0, 0);"><strong>In this position you will:</strong></span></h1> <ul> <li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);"><strong>Technical Delivery </strong></span> <ul> <li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);">Craft new features that help users more easily navigate government services and receive a dignified experience, taking on the hardest and highest-leverage problems across your domain and modeling the standard other engineers build toward.</span></li> <li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);">Drive solutions to technical problems that are ambiguous or undefined, weighing tradeoffs across competing priorities at a discipline-wide scale.</span></li> <li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);">Own architecture and data-modeling decisions for systems that span multiple services or teams, weighing tradeoffs across competing priorities: speed vs. maintainability, the familiar tool vs. the right one, ideal vs. feasible.</span></li> <li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);">Work iteratively to prove out approaches, then engineer what works into durable, reusable capabilities (shared services, libraries, and AI-enabled components) that other teams build on. </span></li> <li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);">Support Engineering's culture of writing by producing documentation, technical decision records, and learning materials that engineers across multiple teams rely on.</span></li> </ul> </li> <li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);"><strong>Technical Leadership & Mentorship</strong></span><br> <ul> <li style="color: rgb(0, 0, 0);"><span style="color: rgb(0, 0, 0);">Set and document technical direction for your domain, anticipating cross-team challenges before they become blockers and explaining the reasoning behind hard calls.</span></li> <