The work is patient.

Where we are

Palanor is a pre-seed company. The product is live. The first paid pilots are in motion. Palanor is a small team, supported by a few contracted developers and advisors.

We are not posting roles today. We will post the first roles after the pre-seed closes and the first pilot revenue lands. That timeline is months, not weeks.

If you are reading this and the work resonates — stay close. The right candidates for the first roles are almost always the ones who were paying attention before the listing went up.

How we think about the people we will hire

A few principles, stated plainly.

Stewards hire stewards.

The company is built around a vocabulary of long horizons, careful seeing, and responsibility. We will hire people who recognize themselves in that vocabulary — not people who have to be convinced of it.

Range over speciality, at least early.

The first ten people will each carry several jobs. We will index toward range, taste, and judgment over specialist credentials. The credentials will matter more later. Right now, the bias is toward people who can hold many domains and do not need the room to be quiet to think.

Writing is the work.

Almost every artifact we produce — product copy, scenario libraries, Numen output, investor materials, customer briefings — is writing. Strong writing is a hard requirement, regardless of role.

The principles are the culture.

Palanor runs on six published principles. We will hire people of any background who share the ethic underneath them: care for what is entrusted to them.

Remote, with intention.

Work is remote-first. We will gather deliberately a few times a year. The work is asynchronous and writing-heavy by design.

What we will hire for first

Roughly, in order of likely sequence:

• Founding engineer — full-stack, Next.js + Postgres + LLM-fluent — to build alongside the team, the contracted developers, and the Council
• Founding designer — product + brand, single craftsperson — to extend the visual system into the next twenty surfaces
• Founding council partner — advisory, ex-strategy consultant or former operator — to lead the Council practice as it formalizes
• Editorial lead — writing, methodology, scenario library curation — to build the masthead and deepen the methodology

These are guesses, in the right register. The actual roles will be specified when the moment arrives.

How to reach us

If you are reading this carefully and thinking that is me — write to us.

Send a short note on what you are working on, what you have built, and why Palanor's particular framing of the problem caught your attention. No résumés required at this stage. Substance over format.

hello@palanor.com — subject line: Careers — [your name]