Lead UX Designer

Who We Are

Neighborly Software was built to help communities make a difference in the lives of low-income families and vulnerable populations. Our mission is simple, “Helping Communities, Help People.”

Headquartered in Atlanta, GA we offer a cloud-based technology platform for the administration and disbursement of governments funds for programs such as Housing, Economic, Community Development, Disaster Recovery/MIT, Home Energy Rebate Programs, and Housing Choice Voucher programs.

The UX Lead is the first dedicated user experience role at Neighborly Software. Our users — government agency staff, nonprofit administrators, contractors, and the residents and applicants they serve — rely on the platform to run complex, high-stakes programs where clarity matters. The UX Lead owns how that platform looks, feels, and flows.

This is a founding, individual-contributor role with no direct reports. You will build the design practice from the ground up — a design system and reusable component library, documented personas and user journeys, a standard style guide, and accessibility and responsive design as standing norms — while remaining hands‑on with the design work itself. Because the role carries no team, it leads through influence: setting a direction that product managers, engineers, and QA choose to follow because the thinking is sound and the work makes theirs better.

Beyond producing design artifacts, you will set standards and hold the organization to them, guiding product, engineering, and QA toward a simpler, lower-friction experience. Success is measured in friction removed: fewer clicks, clearer workflows, visible status and feedback, and interfaces that embrace a “don’t make me think” philosophy. This is an opportunity to take the platform into its next phase and align the experience with where the company is headed.

• Owner — treats the platform experience as their responsibility end to end, and holds the standard when it would be easier to let it slide.
• Systems thinker — sees the reusable pattern behind the one‑off request and builds for reuse.
• Simplifier — instinctively removes steps, clicks, and cognitive load.
• Voice of the customer — advocates for the user in rooms where the user is not present, grounded in research rather than opinion.
• Leads without a team — earns influence through credibility, clarity, and collaboration rather than reporting lines.
• Pragmatic builder — ships improvements incrementally rather than waiting on a perfect, all‑at‑once redesign.

• Build and own a design system — a reusable component library, interaction patterns, and usage guidance that product, engineering, and QA work from.
• Establish and maintain a style guide for consistent branding across the platform, aligned with company positioning and messaging.
• Establish accessibility as an organizational norm — set WCAG‑based standards, build accessible patterns into the design system, and define how compliance is validated before release.
• Establish responsive design as an organizational norm so the platform behaves predictably across desktop, tablet, and mobile.
• Hold the organization accountable to these standards, reviewing work in progress and partnering with product and engineering leadership when the bar isn’t met.

• Redesign core workflows to reduce friction — fewer clicks, clearer paths, and meaningful status and feedback.
• Modernize and simplify the interface, both visually and in how users interact with it.
• Guide user experience solutioning for known pain points, turning recurring customer complaints into designed, validated solutions.
• Assess core functionality for reuse across personas and program types —…