Skip to main content

Opto Investments

Software Engineer, Product

New York, New York, United States; Remote; San Francisco, California, United States (Remote)$160k–$240kmidAdded today

About this role

Opto seeks a Software Engineer to build innovative solutions for private markets investing. You'll develop intuitive user experiences across investment workflows using TypeScript, React, Next.js, Python, and AWS, while owning full-stack projects in a fast-paced fintech startup.

What you'll do

  • Own end-to-end delivery of software projects, coordinating with teammates and stakeholders on timelines
  • Contribute across all product development phases: specification, implementation, code review, QA, deployment, and operations
  • Build and maintain design systems and reusable component libraries at scale
  • Seek context and rapidly iterate on solutions to eliminate ambiguity and drive progress
  • Participate in engineering recruiting, interviewing, and technical problem definition
  • Collaborate with product and stakeholders to unblock progress and raise concerns proactively

What they're looking for

  • TypeScript and React
  • Next.js frontend development
  • Python and FastAPI
  • REST API design and integration
  • AWS services and containerization
  • Testing frameworks (Jest, Vitest, Playwright)
  • Component architecture and state management
  • Design system 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.

Opto Investments

Opto Investments builds technology solutions that transform private markets and investment processes. The company is hiring Software Engineers and Backend Engineers to develop innovative systems that enhance investment workflows and solve complex business challenges.

View all jobs at Opto Investments

Likely interview questions

  • Walk us through a complex component architecture challenge you've solved and how you optimized rendering performance.
  • Describe your approach to building and maintaining a design system at scale—what patterns did you use and what would you do differently?