• Our Software Developer position reports to our Senior Director of Technology Strategy and is part of a team of developers designing and developing both web-based and mobile software products for Common App. • Our Developers work in a team environment to assist in software architecture design and to implement high quality software products that meet the needs of the Common App community. • This position plans, develops, modifies and tests software components using .NET technologies within an Amazon Web Service and Agile development environment to create new products and enhance existing software systems. • The developer also utilizes various tools (such as GitHub Copilot and Claude Code) to deliver .NET and Angular solutions at an accelerated velocity.

• Evaluate and implement emerging AI tools to drive measurable GTM efficiency and effectiveness • Automate pre- and post-event workflows for marketing campaigns, lead capture, and content distribution • Enable intuitive knowledge discovery with intelligent, searchable internal systems for Sales and Customer Success teams • Orchestrate ABM campaigns across channels with dynamic personalization and closed-loop measurement • Enhance revenue forecasting with AI-assisted frameworks, automated performance tracking, and predictive analytics • Develop educational lead magnets, calculators, interactive tools, and other content to engage targeted micro-segments • Automate QBR decks, competitive briefs, and reporting from product usage, revenue, and account health signals • Generate AI-driven sales decks tailored to buyer role, industry, and deal stage, eliminating one-size-fits-all materials • Launch AI-driven re-engagement campaigns to revive closed-lost opportunities

• Drive the delivery of the Shop Builder developer surface: MCP server, CLI and local dev environment, public SDK, documentation pipeline, sandbox and preview environments, deploy and versioning path. • Lead and mentor a team of three engineers — setting technical direction within the squad, running code reviews, and ensuring consistent engineering quality. • Own cross-team coordination: identify and pull inbound API capabilities from payments, auth, live ops, and catalog teams; unblock dependencies; manage integration timelines. • Actively contribute to implementation — you ship production code alongside the team, particularly on the most critical and complex components. • Partner with the Principal Engineer to translate architecture decisions into sprint-level execution plans and realistic timelines. • Collaborate with the PO on roadmap sequencing, scope decisions, and trade-offs between speed and correctness. • Own the team's delivery rhythm: sprint planning, technical grooming, retrospectives, and status visibility to engineering and business leadership. • Define and maintain the team's engineering standards: testing strategy, observability, deployment practices, and documentation quality. • Act as the primary technical contact for integrations with headless partners and the MIT professional services team during early partner onboarding. • Contribute to hiring by conducting technical interviews and defining what great looks like for the engineers joining this team.

• Own the technical architecture of the agent-readable Shop Builder platform: which APIs to expose, in what shape, through which surfaces (REST, SDK, MCP, CLI). • Define the interface contracts that LLMs and developers interact with — React component APIs, custom block schemas, theme tokens, data binding formats — and maintain them with the rigor of a public API. • Design and lead delivery of the MCP server that allows AI agents (Claude Code, Cursor, etc.) to build, deploy, and operate Shop Builder storefronts end-to-end without the editor in the loop. • Architect the CLI and local development environment: how developers scaffold projects, iterate locally, preview changes, and push to production. • Define the deploy, versioning, and rollback model for developer-published content — custom blocks, themes, and layouts. • Design the sandbox and preview environment system so agents and developers can iterate without touching live partner sites. • Set the documentation standard: written for LLMs and humans as first-class users, maintained from single canonical sources and published to every surface (CLI help, dev docs, MCP tool descriptions, AI context). • Lead the eval harness architecture: how the team measures whether an LLM-generated block, theme, or layout is correct before it ships. • Collaborate with Principal/Staff Engineers across payments, auth, live ops, and catalog to pull inbound capabilities into coherent developer-facing surfaces. • Serve as the technical bar-raiser for the team: define code standards, review critical implementation decisions, and mentor the Tech Lead and engineers. • Contribute to hiring and define the technical culture of the team from day one.