Software Engineer
Job description
About the role
Maybern develops an operating system that gives private fund managers deterministic guard rails and agentic capabilities. The engineering team delivers core product workflows for managers of large capital pools. This role solves complex product problems for early clients and future use cases.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Platform code is built, tested, and deployed through continuous pipelines to ensure reliability. Core system components are architected, scoped, and implemented to address current product needs and future growth. Product and domain experts define flexible, elegant solutions that solve existing client problems and anticipate future requirements.
Requirements
You bring two or more years of experience with server-side languages such as Python, Ruby, or Java, and web frameworks like Django or Rails. Relational database concepts and transaction knowledge are necessary for data integrity. Platform and distributed systems knowledge is required, with AWS experience as a valued bonus. Detail orientation supports thorough implementation and clear communication in fast-paced settings. Excellent written and verbal skills enable effective collaboration across the team. Adaptability helps you thrive in a high-growth, fast-moving environment.
Practical notes
The role is based in the New York office with an in-office culture that emphasizes collaboration. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Software engineering roles often rely on strong server-side logic and database design. Cloud platforms and distributed systems knowledge are increasingly valuable in modern products. Clear communication supports alignment across product and engineering teams. Detail orientation reduces defects in complex financial systems. Fast-paced environments demand adaptability from engineers.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.
About the company
Maybern is transforming the way private fund managers effectively manage their funds through cutting edge technology. Maybern is founded by top engineering experts with deep knowledge of the fund management space.