Noah Sterling
- Software Engineer
- fast, durable web applications
Studio profile
Noah Sterling — Software Engineer
Noah Sterling is a Software Engineer at Genome, building the web applications and storefronts that clients and their customers rely on every day. Noah's focus is fast, durable web applications: software that responds quickly when people use it and keeps working as features, traffic and teams change around it.
Strategy and design only reach people once they are built, and a studio that takes on Shopify Plus commerce and young products from its incubation program needs engineers comfortable with both. Noah's role exists to turn agreed plans into dependable code, and to raise practical concerns early enough that they shape the plan rather than delay it.
Noah doesn't spend most of the week in client meetings, but when there, the conversation stays concrete. What should happen if a payment fails? How should the site behave on a train with patchy signal? Clients often find these questions sharpen their own priorities, because speed and durability depend on choices only the business can make.
Noah treats accessibility as part of writing correct code. Native elements are preferred over custom widgets, focus is handled carefully in dynamic views, and features are tried with a keyboard before anyone calls them done. Efficient code is also a sustainability habit for Noah, since lighter pages ask less of devices, networks and data centers.
Noah collaborates easily with client developers, app vendors and agency partners, and is generous with explanations when someone inherits a codebase. Clients should expect working software delivered steadily, honest answers about what is and isn't finished, and a system that still feels reliable long after the launch excitement fades.
Learn about the wider team, explore the studio services, or visit the contact page to start a conversation about your own product challenge and see how software engineering could help.
Shipping small, testing early and leaving code someone else can read
Much of a software engineer’s week on a studio project is unglamorous, and that’s how it should be. Noah picks up a ticket with clear acceptance criteria, builds the smallest version that meets them, writes tests around the parts most likely to break, and gets it reviewed and onto staging within the same week wherever possible.
Speed for users is mostly decided early. At the start of a build Noah agrees a performance budget covering page weight, script size and how quickly the main content appears, then checks every significant change against it. On commerce sites that means watching app scripts, image handling and third-party tags, which pile up quietly until a store feels sluggish. Durability comes from similar habits: type safety, deliberate error handling and logs that explain what went wrong instead of simply recording that something did.
Clever code that nobody else can maintain is a cost the client pays later. Noah writes for the client’s next developer as much as for this release, with a README explaining how to run the project, how to deploy it and where the tricky parts are. Bigger architectural questions go to the principal engineer, while interface details get settled directly with the product designer and creative engineering lead.
Included in every handover
- A test plan for critical journeys such as checkout, search and forms
- Setup and deployment steps that work on a fresh machine
- Environment variables, services and who owns each account
- Known limitations and suggested next improvements
