Skip to main content

Anything

Product Engineer

San Francisco$125k–$200kfulltimemidAdded 1 month ago

About this role

Join Anything, a rapidly growing AI agent that converts natural language into full-stack applications, as a Product Engineer. You'll own complex product features end-to-end, working across frontend and backend systems while partnering with product and design to shape the platform's direction.

What you'll do

  • Design and implement user-facing features across frontend and backend using TypeScript, React, Tailwind, and Postgres
  • Translate ambiguous product goals into clear technical plans and shipped outcomes
  • Partner with product and design to shape roadmap decisions and execution strategy
  • Drive fast iteration loops by collecting user feedback and leveraging product data
  • Mentor junior engineers through pairing, code review, and modeling strong technical practices
  • Identify and resolve structural issues that impact team velocity or product quality

What they're looking for

  • TypeScript and modern frontend development
  • Backend fundamentals including data modeling, APIs, and system design
  • Complex problem-solving and debugging across systems
  • Full-stack product ownership from conception to production
  • Technical and product tradeoff decision-making
  • Clear written and verbal communication
  • Rapid learning in new domains
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.

Anything

Anything is an AI platform that converts English prompts into full-featured applications. The company is hiring Backend Engineers, Mobile Engineers, Infrastructure/DevOps Engineers, and Product Engineers to build and scale its AI-driven app generation platform.

View all jobs at Anything

Likely interview questions

  • Tell us about a time you owned a complex product feature end-to-end, from problem definition through shipping and iteration. What made it challenging and how did you measure success?
  • Walk us through how you'd approach translating an ambiguous product goal into a clear technical plan. Can you share a concrete example?