Skip to content
NEXTMOVEFDE careers · United States

Software Engineer, Enterprise Expansion

Job description

The full responsibilities and requirements are on the employer’s site.

Read the job description
Source and classification

Internal deployment & tooling · Evidence for this classification:

range of use cases across the entire organization. The challenge that enterprises are facing today is not “how do we build it?” but “how can we build this together at scale?” On the Enterprise Expansion team, you’ll build and own systems and solutions that enable customers to organize, manage, and secure Retool at scale. Our team owns the full customer journey, from administrator setup and onboarding, to how teams discover and manage their work, to scaling spaces and instances for thousands of employees across the organization. Your work will span the entire technical stack, from full-stack web development to data pipelines and product infrastructure. You'll focus on the problems that matter most to customers: What slows them down? What keeps their security teams up at night? How do we make the right thing easy and the wrong thing hard? This team is responsible for making Retool
More from the job description

ABOUT RETOOL Nearly every company in the world runs on custom software for critical operations like tracking performance metrics, handling support workflows, building admin dashboards, and countless processes you might never have thought of. But most companies don't have the resources to properly invest in these tools, leading to a lot of old, clunky internal software, or worse, teams still stuck in manual and spreadsheet workflows. AI has changed who gets to build software. The definition of "developer" now includes analysts, operators, and domain experts creating solutions directly—and the tools they reach for are multiplying by the week. That's both an opportunity and a challenge: as more people build with more AI tools, the risk of shipping ungoverned software into production grows just as fast. At Retool, we're building the platform that makes all of it safe to ship. Build with any AI tool you want, then deploy into one place that connects to your real business data, enforces enterprise policies automatically, and lets teams create once and reuse everywhere with shared, trusted components. The cost of building software has collapsed. The cost of governing it hasn't—and that's the problem we solve. Developers and domain experts have already automated over 100 million hours of work on our platform, freeing them to focus on creative problem-solving and strategic work that [... source excerpt omitted ...] facing today is not “how do we build it?” but “how can we build this together at scale?” On the Enterprise Expansion team, you’ll build and own systems and solutions that enable customers to organize, manage, and secure Retool at scale. Our team owns the full customer journey, from administrator setup and onboarding, to how teams discover and manage their work, to scaling spaces and instances for thousands of employees across the organization. Your work will span the entire technical stack, from full-stack web development to data pipelines and product infrastructure. You'll focus on the problems that matter most to customers: What slows them down? What keeps their security tea [... source excerpt omitted ...] tup: Redesign how administrators onboard and manage Retool. Build the landing page experience, global search, and the guided setup flow that gets enterprises from sign-up to first production app faster. Surface security insights, flag under-authenticated resources, and create the admin dashboard that makes platform health visible at a glance. Build the features that change Retool from something that admins manage to a system that is self managing and self healing, with proper admin oversight and controls. Projects: Build the new organizational primitive for Retool. Projects group apps, agents, and workflows into a shared space with their own membership and role-based permissions.

How jobs are selected

Employer postings · Data from · Sources