Deep-tech programmes fail quietly
They fail by carrying an unexamined assumption for years, until it is too expensive to revisit. Everything about how we work is arranged to make that harder, and it is applied to our own results before anyone outside sees them.
Every number regenerates
No figure enters a document unless a committed model reproduces it. Results that stop regenerating are retired.
The opposing case gets its best shot
Any optimisation available to a competing system is credited to that system before a comparison is drawn.
Limits ship with results
Every study carries a written account of what it does not establish.
Assumptions are named and dated
Where a constant is a placeholder awaiting real data, it is labelled as one wherever it appears.
Where things actually stand
Architecture
Defined. Plan of record under revision control with a written history of corrections.
Microarchitecture
Block-level specification complete across major blocks, budgets checked mechanically.
Validation
Campaign complete for every question public inputs allow us to answer.
Open
Vendor timing under confidentiality, durable-tier data, and the co-design engagement.
Come and build the memory system
We are a small, early-stage programme designing silicon that does not exist yet. That is the honest description, and it is also the reason the work is unusually good: nothing here is maintenance, and every decision is still open.
You will be checked, and so will we
Every number regenerates from committed code. Claims are argued against the strongest version of the opposing case, and results ship with their limits attached. If you like being right more than being persuasive, you will recognise the place.
The problems are unusually concrete
How many sessions fit in a bank group. What survives refresh and row activation. Whether an idle timer beats a learned predictor. These are questions with answers.
Early means early
There is no product, no revenue and no customer. There is an architecture, a microarchitecture, a validation campaign and a patent programme. We would rather you knew that here than found it out in the second interview.
Where we expect to hire
Areas we are building toward rather than open requisitions. We are collecting expressions of interest now; formal postings, with compensation ranges and locations, will follow as roles are funded.
Memory architect
DRAM and processing-in-memory internals: bank organisation, timing, refresh and thermal behaviour, and what actually survives between a nominal figure and a delivered one. You would own the co-design requirement the economics rest on.
RTL and verification
The session state machine, the migration datapath and the allocation engine: sequential logic with hard determinism requirements, verified against an independent behavioural model. Formal methods count for more here than they usually do.
Serving systems engineer
You have run inference at scale and felt this constraint from the software side: KV tiering, prefix caching, scheduler behaviour under bursty agent load. You would define what the hardware should expose so a runtime can actually use it.
Performance modelling
Discrete-event simulation, trace analysis, and the discipline of making a model earn trust. Much of what we know comes from this work, and so does much of what we have had to retract.
Hardware security and cryptography
Per-session key management, an in-path encryption stage, a hash-chained attestation journal and a root of trust with post-quantum agility. The threat model is a shared machine holding other people's conversations.
Something we have not thought of
If you have looked at this architecture and can see a problem we have missed, or a discipline we will need and have not named, write to us about that instead.
How to apply
Use the contact form and choose Engineering roles, or write to careers@remaneta.com
Tell us what you have built and what you would want to work on here. We read everything. There is no automated screening and no keyword filter between you and a person.
Equal opportunity
LABSPOTS LLC is an equal opportunity employer. We consider all applicants without regard to race, colour, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status, genetic information, or any other characteristic protected by applicable law. If you need an adjustment to take part in our process, tell us and we will arrange it.
We are hiring the people who want this problem
Memory-system architects, verification engineers, and serving-systems people who have felt this constraint from the software side.