Back to all roles

Extreme-Scale, Nano & Fundamental Engineering

/

Senior leadership

Mathematical Systems Lead

What this division proves and builds, who does it, and the rule that a method ships with its regime of validity.

Lead Full-Time On-site — Kolkata, West Bengal, India Permanent

Compensation

Engagement

Full-Time

Permanent role. Full-time commitment. This is an on-site role at Kolkata. It is not remote and not hybrid.

Scope of role

Set direction within your domain. Build and mentor a team. Own outcomes at the function level.

Research classification

Mathematical Theoretical research Level 6 · Lead Mathematics & Computational Foundations →

Proving results and building the mathematical structures other work is expressed in. Theorems and proofs, well-posedness and convergence results, formal statements of method.

Theoretical research. Mathematical and theoretical work. Derivation and internal consistency are the standard here; experimental confirmation is not currently available at this scale.

Scale range 10^-100 m to 10^100 m

01
02
03
04
05
06
07
08
09
10
11
10-100 m 100 m 10100 m
Experiments reach here 3 bands no experiment reaches This role

A numerical result without a convergence statement is an opinion with decimal places. This division reports the order of a scheme, the conditions under which it is stable, and the regime where its error estimate no longer holds. Where a method is used outside the range it was analysed for, that is stated rather than hoped over. Scientific integrity is a condition of every role in this department. Assumptions are stated separately from conclusions. Uncertainty is reported. Negative and inconclusive results are written up, not discarded. Speculative work is labelled speculative, including when that makes it less impressive. Fabrication, falsification, and presenting a simulation as a measurement end an engagement here.

Scale bands are a research classification, not a claim of experimental reach. Most of this span cannot be probed by any apparatus that exists: nothing below about 10^-19 m has been measured directly, and anything at 10^26 m or beyond is inferred from observation rather than engineered. Every opportunity states the kind of work it actually is.

01 — The role

Why this role exists at EduRankAI

Department of Extreme-Scale, Nano & Fundamental Engineering, Division D09: Mathematics & Computational Foundations. This division develops the mathematics other divisions use. It builds numerical methods and proves what they converge to, designs optimisation algorithms, and supports modelling across every scale band the department declares. It is a service division and a research division at once, and it is mandatory to the department because a method nobody has analysed is a method nobody should trust. This position: What this division proves and builds, who does it, and the rule that a method ships with its regime of validity. Scale range for this work: 10^-100 m to 10^100 m. Research classification: Mathematical. Proving results and building the mathematical structures other work is expressed in. Evidential standing: Theoretical research. Mathematical and theoretical work. Derivation and internal consistency are the standard here; experimental confirmation is not currently available at this scale. A numerical result without a convergence statement is an opinion with decimal places. This division reports the order of a scheme, the conditions under which it is stable, and the regime where its error estimate no longer holds. Where a method is used outside the range it was analysed for, that is stated rather than hoped over. Scale bands are a research classification, not a claim of experimental reach. Most of this span cannot be probed by any apparatus that exists: nothing below about 10^-19 m has been measured directly, and anything at 10^26 m or beyond is inferred from observation rather than engineered. Every opportunity states the kind of work it actually is. Level 6 (Lead). A research programme or an engineering area: what gets worked on, by whom, and to what standard.

02 — The work

What you will own

  • 01 Develop the mathematical foundations other divisions build their models on.
  • 02 Create numerical methods and establish what they converge to and under what conditions.
  • 03 Analyse convergence, stability and conditioning, and report the regime where the analysis holds.
  • 04 Develop optimisation algorithms and characterise where they fail as well as where they succeed.
  • 05 Support modelling across every division, including saying when a proposed model is ill-posed.
  • 06 Review other divisions' numerical work and say plainly when a result is not supported by its method.
  • 07 Decide what this area works on, who works on it, and the standard the work is held to.
  • 08 Be accountable for the honesty of what leaves the division, including under time pressure.
  • 09 Recruit, develop and retain the people the programme needs.

03 — The expertise

What we look for

Can state and use the definition of convergence for a numerical scheme, not just cite the order.Linear algebra to the level of conditioning, decompositions and why an ill-conditioned problem is not a bug in the solver.Real analysis: limits, continuity, and what makes a problem well-posed.Has implemented a numerical method from a paper and verified its convergence order empirically.Probability and statistics sufficient to state what a confidence interval does and does not claim.PythonJuliaC++Symbolic mathematics

04 — The bar

Who thrives here

  • Education: Doctorate or an equivalent research record.
  • Experience: 8 to 12 years, with a record of directing work carried out by other people.
  • Scope of the role: A research programme or an engineering area: what gets worked on, by whom, and to what standard.
  • Must have: Can state and use the definition of convergence for a numerical scheme, not just cite the order. Also: Linear algebra to the level of conditioning, decompositions and why an ill-conditioned problem is not a bug in the solver.
  • Portfolio: at least one piece of work — code, a written result, a thesis chapter, a preprint — that somebody outside your institution can read and assess. It does not need to be published.

Terms of Engagement

How working time works at this level

No counted hours. A five-day week with a four-hour overlap window, plus responsibility for the coverage of your area — including who is on call and when.

Type

Lead

Working days

5 per week

Rest days

2 per week

Hours counted

No

Daily overlap

4h

Measured by

The outcomes of the area you lead, the reliability of its coverage, and the growth of the people in it.

Where this stands legally

Hours are not counted at this level. The statutory ceiling of 9 hours a day and 48 a week remains the limit the role is designed to fit inside: if the work cannot be done within a normal week, the scope is wrong, not the person.

The full per-level model is published at Working Hours by Level.

05 — Hiring process

What to expect after you apply

  1. 01

    Application review

    Every application is read personally within five business days. We respond either way.

  2. 02

    Take-home or live exercise

    Role-specific. Time-boxed. Real problems we are actually working on, not invented puzzles.

  3. 03

    Conversations

    Deep technical and values conversations with the team you would join. No trick questions. No panel ambushes.

  4. 04

    Offer or honest no

    If yes: digital offer letter, signed in-portal, transparent terms. If no: written feedback if you want it.

The standard

What you deliver, and how it is judged

Deliverables

  • Methods with a written convergence and stability result, and an empirical verification of it.
  • Reference implementations other divisions can adopt without reimplementing.
  • Reviews of numerical work carried out elsewhere in the department.
  • Statements of the regime of validity, attached to the method rather than to a memory.

Evaluation criteria

  • Whether the convergence claim is proved or measured, and stated as which.
  • Whether the method's failure modes are characterised.
  • Adoption: does another division actually use it.
  • Willingness to say a colleague's result is not supported by its method.

Preferred, not required

Nothing in this list is a bar to applying.

Partial differential equations: classification, boundary conditions, and standard discretisations.Optimisation: convexity, gradient methods, and the failure modes of each.A second language beyond Python for performance-critical numerics.Experience writing a proof somebody else has checked.Differential geometry or topology beyond a first course.Stochastic differential equations or Monte Carlo theory.Formal verification or interval arithmetic.A published or preprinted mathematical result.

Tools you would work in

NumPy and SciPySymPy or MathematicaSparse and iterative solver librariesOptimisation frameworksLaTeXGit

Reports to: Department Director

Works with: D01, D02, D08, D10, D11, D15

Before you start

What we will collect. What it costs. What we will not do with it.

We will collect

  • Name, email, phone — Account + application updates. No marketing.
  • Resume / portfolio link — Human review of your work.
  • Date + place of birth — Identity verification only.
  • Your written responses — Selection rubric. Read by humans.
  • Government ID (later) — Anti-fraud at offer / interview stage. Not at signup.

We will never

  • Sell your data
  • Share with third-party recruiters
  • Use for advertising
  • Train models on it
  • Send marketing email

Our situation

EduRankAI is a small, independent organization building long-term capabilities in educational intelligence, advanced AI systems, and research infrastructure. We take no advertiser money, no donations with strings attached, and no investor pressure on hiring decisions. Applying is free, and every application is read by a human — recruitment, technical, academic and leadership teams. It buys us the right to be honest.

Full transparency policy Questions? Email us

Ready to apply?

We read every application personally. If you are the right person for this role — regardless of pedigree, background, or where you are based — you will hear back from us within five business days.

Apply through this page. You will be asked for your education, your experience, and links to work we can actually read — a repository, a write-up, a thesis chapter, a preprint. Send the piece of work you would defend, not the one with the best title. If a result in it turned out to be wrong, say so; we would rather read that than not know. Every application is read by a person. We assess applications on evidence of the work. We do not filter on institution, on age, on gender, on caste, on religion, on disability, or on where you are from. If any part of this process is inaccessible to you, tell us and we will change it for you.

Lead Full-Time

Mathematical Systems Lead

Apply →