Skip to main content

Pear VC

Founding Applied AI Product Engineer

New York City$150k–$250kfulltimemidAdded 1 month ago

About this role

As a Founding Applied AI Product Engineer at Spur in NYC, you'll be integral in developing cutting-edge QA technology that enhances digital experiences. You'll have the opportunity to ship features from design to deployment while directly engaging with customers to quickly implement feedback.

What you'll do

  • Design, code, test, deploy, and own product features
  • Collaborate with users for rapid feedback implementation
  • Develop both frontend and backend performance code
  • Iterate quickly with product, engineering, and design teams
  • Launch new features and gather customer insights

What they're looking for

  • Strong experience with Typescript
  • Proficiency in Next.js and React
  • Ability to learn new technologies quickly
  • High autonomy in project management
  • Customer-focused mindset
  • Attention to detail and quality

Benefits

  • Daily lunch and snacks provided
  • High quality medical, dental, and vision coverage
  • Meaningful equity in a fast-growing company
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.

Pear VC

Pear VC invests in and supports AI-driven enterprise software companies building automation platforms, compliance systems, and specialized tools across industries like financial services, insurance, and software development. The portfolio companies are hiring founding and senior engineers to design core infrastructure, build AI systems, and develop scalable backend platforms alongside their leadership teams.

View all jobs at Pear VC

Likely interview questions

  • Walk us through a feature you shipped end-to-end—from design through production. How did you handle the full ownership cycle, and what feedback loops did you create with users?
  • Tell us about your experience with TypeScript, React, and Next.js. What's a complex frontend problem you solved, and how did you approach performance?