Skip to main content

Maybern

Forward Deployed Engineer

New York Office$185k–$310kfulltimemidAdded 1 month ago

About this role

Maybern is seeking a Forward Deployed Engineer to lead complex technical initiatives that enhance their innovative platform for private fund management. The role requires expertise in AI, system design, and a strong aptitude for collaborating with clients to solve intricate problems in fund management.

What you'll do

  • Lead forward-deployed engagements from discovery to production
  • Architect custom systems integrating AI and decision-making workflows
  • Design application patterns linking platform to customer-specific processes
  • Build frameworks for evaluation and validation of outputs
  • Act as a technical advisor to senior stakeholders
  • Mentor team members and define technical standards

What they're looking for

  • 3+ years in software engineering or applied research
  • Strong in Python and SQL
  • Experience in AI or ML with a focus on reliability
  • Deep understanding of quantitative modeling
  • Excellent communication skills
  • Ability to handle ambiguous technical challenges
  • Proficiency in system design and application architecture
  • Strong mentorship capabilities

Benefits

  • [unknown]
  • [unknown]
  • [unknown]
  • [unknown]
  • [unknown]
  • [unknown]
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.

Maybern

Maybern builds a sophisticated platform and operating system for private fund management, including scenario modeling tools designed to enhance investment performance. The company is hiring Software Engineers, Forward Deployed Engineers, and Corporate IT Engineers to develop innovative applications, lead client engagements, and establish IT operations.

View all jobs at Maybern

Likely interview questions

  • Walk us through a production AI or quantitative system you built that others depended on—what made it reliable, and what broke that you had to fix?
  • Describe a time you had to translate technical complexity to non-technical senior stakeholders while maintaining precision. How did you know you got it right?