Skip to main content

Airtable

Software Engineer, Product Backend (4-8 YOE)

San Francisco, CA; New York, NYFrom $277.6kfull-timemidAdded today

About this role

Airtable seeks a backend-focused full-stack engineer with 4-8 years of experience to build enterprise-grade features for their no-code platform. You'll work across AWS, Node.js, SQL, and React to ship product features while collaborating with cross-functional teams on initiatives like admin governance, security, or AI capabilities.

What you'll do

  • Design and implement end-to-end product features across the full stack with emphasis on backend development
  • Collaborate with product managers, designers, and data scientists to translate customer needs into technical solutions
  • Build and maintain systems using AWS, Node.js, SQL, React, and related technologies
  • Own the execution of new features from specification through deployment
  • Work on enterprise-focused initiatives such as security, compliance, governance, or AI integration
  • Participate in code review and knowledge sharing with engineering team members

What they're looking for

  • Backend development (Node.js or equivalent)
  • Full-stack web development
  • SQL and database design
  • AWS or cloud infrastructure
  • React and frontend technologies
  • Web application architecture at scale
  • JavaScript
  • System design and API development
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Airtable

Airtable builds a no-code platform used by hundreds of thousands of organizations and Fortune 100 companies to create and manage custom applications. The company is hiring full-stack engineers, backend engineers, infrastructure engineers, and data engineers to develop AI-powered features, scale foundational systems, and build data pipelines that power the platform.

View all jobs at Airtable

Likely interview questions

  • Can you describe your experience building backend features in a full-stack capacity and how you've balanced backend vs. frontend work?
  • Tell us about a time you shipped a complex end-to-end feature—what was your role and what challenges did you overcome?