hirly

Plantingspace

Quantitative Modelling Engineer

Remote

hirly Pro

Get in front of the people hiring at Plantingspace

  • Reach the hiring manager at Plantingspace on LinkedIn, from your own account
  • hirly applies to this job for you, with unlimited applications
  • A resume and cover letter written for this job, unlimited
  • The hiring manager and recruiter at Plantingspace, with contact details
Get Pro for this job →

$49 a month · ₹1,999 for 30 days in India · cancel any time

See how you match this job — and similar ones. Free.

Upload your resume and hirly scores it against this role at Plantingspace first, then against similar open jobs, and shows where you fit and why.

PDF or DOCX, up to 12MB. No sign-up to see your matches.

Get past the screening software and onto a recruiter's desk

hirly rewrites your resume for this job — matching the keywords and skills in the posting, moving your most relevant experience to the top, and writing a cover letter to fit. About 30 seconds.

  • Keywords matched to this posting
  • Fit score before you apply
  • Cover letter included

Matched against 2.8M live jobs from 220,000+ employers in 200+ countries.

Tailor my resume for this job →

Apply from your AI assistant

Connect hirly to Claude or ChatGPT and ask it to apply to this job. hirly tailors your resume, fills the employer’s form and asks before sending.

Some employer sites stop an application at a CAPTCHA or sign-in and hand it back with a link. Applying needs a paid plan. Works with any assistant that supports MCP.

hirly's read of this role

Seniority
Mid level
Work mode
Remote-friendly
First seen by hirly
7 Nov 2026

Derived automatically from the posting. Upload your resume above to see how the role scores against it.

the posting

We are building a system that represents domain knowledge as modular probabilistic models. Users compose them into larger structures, the system enforces consistency across them, and uncertainty is propagated across model boundaries autonomously by the composition itself.

You will implement models that our users need, inside of our framework. Our current applications range from equity valuation and financial distress monitoring to particle physics.

The interesting part is not any single model. It is that the same compositional machinery has to carry models from very different domains (finance, physics, others) without special-casing any of them. That generality is the hard part of the design, and it is what we are building toward.

What you will do

Work with the product team to define what a model needs to do, then own it through to something a user can run

Define and document the implementation approach for harder modelling problems

Write code that is clean enough to be maintained by others and fast enough to run at the scale users need

Establish that a model is correct, not just that it executes

Find where the framework constrains the model you are trying to build, and feed that back concretely enough to act on

Contribute to the surrounding production system

Useful experience

Taking models into production for external users and remaining accountable for their correctness in use

Applied mathematical modelling in finance and/or scientific applications

Strong foundation in computer science algorithms and data structures

Experience in a collaborative, commercial software engineering environment, working on large codebases and using practices like CI/CD, testing, and code reviews

Julia, or usage of some more functional or typed languages, e.g. Rust, OCaml, Clojure, C++, or Haskell

Profiling and performance optimisation

Advanced degree in Mathematics, Physics, Engineering, Computer Science, or Statistics

Where you might be coming from

Scientific or engineering software, where you implemented solvers or physical models into a product with external users

A risk or analytics vendor, where you built the model library itself rather than configuring it for clients

A research background in a computational field, followed by several years shipping in a commercial product team

How we work

Hierarchical goals, not personal hierarchies : We organise around a transparent tree of goals and tasks. Every quarter we plan milestone goals, which branch down into smaller and smaller tasks. This tree is the foundation of how we organise, not a side tool.

Transparency : Everyone should have access to every opportunity in the team that they can realistically handle. All goals, tasks, and the reasoning behind them are visible to everyone.

Decisions become tasks : When something is discussed and decided, it gets captured as a task in the right place in the tree, so that nothing dissipates as hot air.

Written and asynchronous by default : We are fully remote and document our learnings in writing. Communication happens transparently in shared channels, not in private threads and one-on-ones.

Growing from leaf to tree : New joiners start from smaller leaves of the tree and work themselves up to ownership of larger branches as trust and understanding build. Teams form around topics and dissolve when the work is done; people move to where they are most useful.

Want to know more?

On our website you can find more about our team and work culture, as well as example tasks that share some insight into the type of things team members are working on.

What we do: https://planting.space/

Ways of work: https://planting.space/org/

Team culture and example tasks: https://planting.space/joinus/

Our team works fully remotely, and mostly within the CET timezone.

Original posting on Plantingspace's site ↗

Listed on hirly, a job board. hirly is not the employer: Plantingspace is hiring for this role.

Want this one?

Upload your resume and hirly rewrites it for this job and writes the cover letter — in about thirty seconds, before you sign up.

Tailor my resume for this job