Skip to main content

Outtake

Software Engineer (Product)

New York City$160k–$300kfulltimemidAdded 1 month ago

About this role

Outtake is seeking a Software Engineer to drive product development through close collaboration with customers and agile decision-making. The role emphasizes hands-on engineering across the stack, allowing for ownership and innovation in tackling real-world problems in a fast-paced environment.

What you'll do

  • Engage directly with customers for feedback and insights
  • Identify and prioritize problems worth solving
  • Design and build initial product features
  • Work across both frontend and backend systems
  • Participate in team retrospectives and alignment meetings
  • Adapt quickly to changing requirements and market signals

What they're looking for

  • Experience in product development
  • Ability to thrive in ambiguous situations
  • Strong problem-solving skills
  • Familiarity with customer-embedded engineering
  • Proficiency in working with large-scale data systems
  • Excellent collaboration and communication
  • Bias towards action and execution
  • Understanding of product success metrics

Benefits

  • Opportunity for meaningful mentorship
  • Working with a high-caliber team
  • Chance to shape product direction
  • Strong financial stability of the company
  • Focus on personal and professional growth
  • Collaborative and dynamic work environment
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.

Outtake

Outtake builds an AI-driven platform focused on combating digital impersonation, fraud, and security threats through innovative cloud infrastructure solutions. The company is hiring Software Engineers across full-stack, platform, and security specializations, along with Sales Engineers who bridge technical expertise and customer relationships.

View all jobs at Outtake

Likely interview questions

  • Tell us about a product you shipped that users actually used. What made it successful, and what would you do differently if you built it again?
  • Describe a time you worked directly with customers or were embedded in a customer-facing role. How did that influence your engineering decisions?