Lead Software Engineer/Architect

About the role

Atlanta, GA Newell Brands is a leading consumer products company with a portfolio of iconic brands like Graco®, Coleman®, Oster®, Rubbermaid®, Sharpie® and Yankee Candle® - and 24,000 talented teammates around the world. Our culture is built on values in action: Integrity, Teamwork, Passion for Winning, Ownership, and Leadership. We work together to win, grow, and make a real impact—supported by a high-performing, inclusive, and collaborative environment where you can be your best, every day. The Lead Software Engineer/Architect provides hands-on technical architecture and engineering leadership for DYMO's software ecosystem, including the web application, desktop application, cloud services, APIs/SDKs, local print device services, data models, software security, device integration, and external-system interoperability. The role owns detailed software requirements, software ecosystem architecture, critical software technical decisions, design code review, final software technical acceptance for internally and externally developed software. This role reports to the Sr. Manager, Software and Software Quality Assurance Engineering and operates within the software technology roadmap, priorities, delivery commitments, processes, staffing model, and budget established by the manager. The role partners with the Sr. Lead Systems Engineer Product Architect, who owns overall product-system architecture, system requirements, cross-discipline interfaces, system integration, verification strategy, and system-level technical acceptance. The Software Engineer Lead Architect remains hands-on in the codebase while strengthening internal technical capability and reducing long-term dependence on external development partners.

Responsibilities

• Define and own detailed software ecosystem architecture across the DYMO Hub Web App, DYMO Desktop Application, Azure cloud services, local print and device services, APIs/SDKs, data models, software security, device integration, and external-system interoperability.
• Translate allocated system requirements and approved customer workflows into detailed, measurable, traceable, and testable software requirements and software acceptance criteria.
• Make and communicate software-level technical trade-offs within the approved roadmap, product-system architecture, system interfaces, delivery commitments, and engineering standards; contribute software expertise to broader system-level decisions.
• Serve as DYMO's internal technical authority for externally developed software, including architecture direction, design and code review, acceptance criteria, technical debt assessment, and final software technical acceptance.
• Write, review, debug, and ship production code across the software ecosystem; maintain a hands-on presence in the codebase as a working engineer, not solely as a reviewer.
• Define and maintain technical standards for code quality, security, scalability, reliability, performance, observability, maintainability, and production readiness.
• Define the technical allocation interfaces across web, cloud, desktop and local services, APIs/SDKs, printer firmware in partnership with the Sr. Lead Systems Engineer Product Architect and relevant domain technical owners.
• Own software security architecture and detailed software security requirements; partner with Systems Engineering, IT/Security, SQA, and external specialists on threat modeling, security testing, vulnerability management, and technical remediation.
• Evaluate emerging software technologies and recommend architecture and technology choices that support the manager-owned software technology roadmap and improve platform capability, maintainability, security, and engineering efficiency.
• Evolve the software ecosystem through common APIs, shared modules, reusable