Skip to main content

AirOps

Product Engineer

New York City or San Francisco (Onsite)$200k–$300kfulltimemidAdded 1 month ago

About this role

AirOps is seeking a Product Engineer to design and launch AI-powered features for their content engineering platform used by leading marketing teams. You'll move quickly from concept to production, collaborate closely with product and design, and iterate based on direct customer feedback in a fast-growing startup environment.

What you'll do

  • Design, prototype, and ship AI-powered products from concept through scaled feature
  • Engage directly with customers to understand needs, validate ideas, and drive iteration
  • Collaborate across product, design, and data teams to deliver features at startup velocity
  • Define product direction and scope when requirements are ambiguous
  • Maintain system performance and reliability in production

What they're looking for

  • Product development and zero-to-one thinking
  • Rapid prototyping and shipping
  • Customer empathy and user research
  • Cross-functional collaboration
  • Python (nice to have)
  • ML/LLM knowledge (nice to have)
  • Product evaluation frameworks (nice to have)
  • Communication across technical and non-technical teams

Benefits

  • Equity in a fast-growing startup
  • Competitive benefits package tailored to location
  • Flexible time off policy
  • Parental leave
  • Collaborative, fast-moving team culture
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.

AirOps

AirOps builds an AI-powered content engineering platform used by leading marketing teams. The company is hiring Platform Engineers to establish core infrastructure and deployment systems, and Product Engineers to design and launch AI-powered features directly with customers.

Website
airops.com
View all jobs at AirOps

Likely interview questions

  • Tell us about a product feature you took from zero to one. How did you decide what to build, and how quickly did you iterate based on customer feedback?
  • Describe a time when you had to navigate ambiguity in requirements. How did you determine the right path forward, and how did you communicate that to your team?