ThalenorThalenor
Careers · Thalenor

Do work that stays close to the problem.

Thalenor is a small, founder-led software and AI engineering studio. We hire deliberately for roles where clear ownership, sound judgement and direct communication can change the quality of the work.

See open rolesHow we hire
STUDIO WORKBENCH · LIVE
Decision in progress

Make the failure path visible.

IN REVIEW
01ContextWhat is actually happening?
02Working proofCan another person inspect it?
03Owned outcomeDid the real task improve?
CURRENT QUESTIONWhat should happen when the upload fails?
REVIEW NOTE

The edge case is now part of the product—not hidden in a ticket.

States checked4 / 4
Next actionDECIDE
CONTEXT → EVIDENCE → OUTCOME
A clear answer

What does working with Thalenor actually mean?

It means working close to the person accountable for the business and the engineering. There is little room for anonymous handoffs or performative busyness. The useful contribution is the one that improves a real client conversation, product decision or working system—and leaves the reasoning clear enough for another person to trust.

Open opportunities

A real role should explain the work—not just describe the person.

These are different engagement models with one shared expectation: make your contribution specific, inspectable and dependable.

OPENROLE 01

Business Development Partner

Build credible business relationships in markets where Thalenor can solve a real software, product or automation problem.

ENGAGEMENTIndependent partner
LOCATIONUnited Kingdom, Canada & Australia · Remote
Business developmentB2BRelationship buildingRemote
Apply for this role
Why this role exists

You open the right conversations and carry the commercial context clearly. Thalenor owns technical discovery, solution planning and delivery. The role is consultative: qualify fit, protect trust and avoid selling work that should not be built.

01

What you would own

  • Identify businesses whose product or operational constraint is a genuine fit for Thalenor.
  • Start and develop thoughtful B2B conversations without mass outreach or inflated claims.
  • Capture the business context, stakeholders, urgency and commercial reality before a technical discussion.
  • Stay accountable through introductions, follow-ups and the transition into a qualified opportunity.
02

Strong signals

  • You already understand one or more of the listed markets and how business relationships develop there.
  • You can explain a technical service in business language without pretending to be the engineer.
  • You are patient enough to build trust and disciplined enough to disqualify poor-fit opportunities.
  • Your written communication is specific, concise and dependable.
03

What to include

  • The market or sector relationships you know best.
  • Two examples of B2B relationships or opportunities you helped develop—and your exact contribution.
  • How you would introduce a founder-led software studio without relying on generic agency language.
  • Your location, working availability and preferred engagement rhythm.
OPENROLE 02

React Native Developer Intern

A hands-on mobile engineering internship for someone who wants to understand how a production-ready application is shaped, built and verified.

ENGAGEMENTInternship · 3 months
LOCATIONRemote
React NativeTypeScriptAndroidiOSRemote
Apply for this role
Why this role exists

You will contribute to real client and internal product work at an internship-appropriate scope. The point is not to collect framework keywords. It is to learn how interface decisions, application state, device behaviour, testing and communication come together in a dependable mobile product.

01

What you would own

  • Build and refine React Native screens and flows from clear product requirements.
  • Work with TypeScript, application state, APIs and native Android or iOS behaviour where the feature requires it.
  • Test the complete user path, including loading, empty, error and offline-adjacent states.
  • Explain progress, assumptions and blockers in writing so review can focus on the actual decision.
02

Strong signals

  • You have built at least one mobile or substantial frontend project that you can demonstrate and discuss honestly.
  • You understand JavaScript and TypeScript fundamentals instead of depending entirely on generated code.
  • You notice interaction details and can reason about why an interface behaves a certain way.
  • You ask focused questions, act on feedback and finish the unglamorous parts of a feature.
03

What to include

  • A link to the strongest relevant project you have built. A repository, working build or short walkthrough is useful.
  • What you personally implemented and one technical decision you would reconsider now.
  • Your current experience with React Native, TypeScript, Android and iOS.
  • Your location, availability during the three-month period and what you want to learn.
How the studio works

Autonomy is useful only when paired with clarity.

A small team gives people room to act. It also makes vague ownership, weak communication and unfinished follow-through impossible to hide.

01

Own the result

Responsibility includes understanding the context, communicating uncertainty and following the work through—not merely completing an assigned fragment.

02

Stay close to reality

Products and commercial conversations should be grounded in how a business actually operates, not in a rehearsed pitch or an isolated ticket.

03

Make the work inspectable

Working software, specific examples and written decisions create more trust than status language, performance theatre or a long list of tools.

04

Use judgement

Small teams cannot replace thinking with process. Know when to ask, when to decide, when to simplify and when a promising direction is still wrong.

05

Communicate directly

Say what changed, what remains uncertain and what you need from another person. Remote work becomes fragile when important context stays implicit.

06

Protect the standard

Care about the details that affect the user, the client and the next person who must understand the work. Quality includes maintainability and handover.

An honest fit check

A small studio is not a smaller version of a large company.

LIKELY A GOOD FIT
  • You want responsibility close to the work.
  • You can show and explain what you have done.
  • You value useful simplicity over visible complexity.
  • You communicate before ambiguity becomes delay.
PROBABLY NOT THE RIGHT FIT
  • You need a large-company ladder or a tightly defined silo.
  • You prefer activity metrics to responsibility for an outcome.
  • You wait for perfect instructions before moving the work.
  • You use confidence or jargon to conceal uncertainty.
How hiring works

Enough process to make a careful decision. No theatre.

The exact evidence changes with the role. The principles do not: tell candidates what is being assessed, keep the number of stages proportionate and resolve important terms before work begins.

01

Relevant application

Use the prompts for the role. Show enough evidence for the first conversation to be useful.

02

Practical conversation

Discuss your actual work, decisions and expectations—not rehearsed answers to generic interview questions.

03

Role-specific evidence

A commercial scenario, project walkthrough or focused technical discussion may be used to examine how you work.

04

Mutual decision

Clarify scope, working rhythm, terms and open questions before either side makes a commitment.

Before you apply

Specific beats impressive.

Choose the relevant role, answer its application prompts and link to evidence where useful. Do not inflate a team result into an individual claim. Explain what you did, why you did it and what happened next.

contact@thalenor.com
Questions

Questions candidates should not have to guess about.

Yes. The roles shown on this page are the opportunities Thalenor is currently presenting publicly. If a role closes, its status will be changed or removed rather than left as an evergreen application funnel.

A useful first message

Tell us what you can own—and show us the evidence.

Apply to a current role with a concise, role-specific note. If the fit is unclear, ask a direct question instead of guessing what we want to hear.

Write to Thalenor