Skip to main content

Maybern

Software Engineer, Scenario Modeling

New York Office$140k–$180kfulltimemidAdded 1 month ago

About this role

Maybern is seeking a skilled Software Engineer to focus on developing their Scenario Modeling product, which aims to modernize private fund management. The ideal candidate will have a blend of technical expertise and business insight to create innovative solutions for clients in a collaborative environment.

What you'll do

  • Build, test, and deploy software continuously
  • Architect and develop core system components
  • Collaborate with experts to design flexible solutions

What they're looking for

  • 2+ years in server-side languages (Python, Ruby, Java)
  • Experience with web frameworks (Django, Rails)
  • Familiarity with JavaScript frameworks (React preferred)
  • Solid understanding of relational databases
  • Knowledge of cloud technologies (AWS is a plus)
  • Detail-oriented mindset
  • Strong communication skills
  • Ability to work in fast-paced, adaptive environments

Benefits

  • Competitive salary and equity package
  • Comprehensive healthcare coverage
  • Family-friendly policies including paid parental leave
  • Flexible work schedule and PTO
  • 401k plan
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 scenario modeling or financial calculation system you've built. How did you handle complexity and ensure accuracy?
  • Tell us about your experience architecting server-side systems from scratch. What were the key technical decisions you made?