Partners

Work with us

Work with inAi as a builder, operator, researcher, designer, writer, contributor, contractor, future team member, or serious collaborator.

Help build an AI-native product company for the intelligence era

inAi is building an AI-native product company for the intelligence era.

That means we are not looking only for people who want a standard role in a standard software company. We are interested in people who want to help build products, systems, tools, research, open technology, and public explanations for a world where AI becomes part of real software and real work.

This page is for people who want to work with inAi directly: future team members, collaborators, contractors, operators, engineers, researchers, designers, writers, product thinkers, technical builders, and people who can help turn ambitious AI-native ideas into useful public products.

If you want a narrower path, you may also want Internships, Contributions, Academia / Research, Testers, or Contact.

For the company mission, read AI in the Real World. For how we think about trust and maturity, read How We Build. For the company overview, read About.

Who this page is for

This page is for people who look at inAi and think: I can help build this.

You do not need to fit a traditional role perfectly. You do need to be able to explain what you can actually do.

  1. An engineer who wants to build AI-native products, interfaces, tools, agents-facing systems, or backend infrastructure.
  2. A product builder who can turn a broad thesis into usable product decisions.
  3. A researcher interested in AGI as a system, agentic decision systems, limits of intelligence, AI for knowledge creation, or AI in business operations.
  4. A designer who can make complex AI-native ideas understandable and usable.
  5. A writer or educator who can explain AI clearly for broad audiences.
  6. An operator who can help a young product company become sharper, faster, and more reliable.
  7. A business or partnership builder who understands pilots, grants, institutional relationships, product positioning, or early markets.
  8. An Open Source contributor who wants to help with tools, documentation, examples, repositories, or developer experience.
  9. A contractor or independent collaborator with a specific useful skill.
  10. A future team member who does not fit a neat job title but can show concrete work.

What inAi is building

inAi builds across several connected areas. If your work can strengthen any of these areas, this page is the right path.

What kind of people fit inAi

inAi needs people who can work with ambition and precision at the same time.

Ways to work with us

There is not only one way to work with inAi.

Work areas that may matter

The following areas are examples of where serious work interest can fit. They are not guaranteed openings.

What inAi can offer

The exact answer depends on the relationship. A contractor relationship is not the same as an internship. A future team conversation is not the same as a research contribution. An Open Source contribution is not the same as a product role.

Strong work with inAi may offer a chance to work near the foundation of an AI-native product company; exposure to product categories that connect business, consumers, agents, Open Source, research, and public education; work on real product pages, systems, repositories, workflows, and public architecture; a company thesis that is broader than one app or one workflow; room for serious initiative if you can produce useful work; an environment where writing, reasoning, building, and product thinking all matter; opportunities to contribute to public-facing work where appropriate; and direct connection to early product and company decisions.

inAi cannot promise a role, contract, internship, compensation, title, response, or collaboration from every message.

The right expectation is simple: send a serious, concrete proposal. If there is a fit, the conversation can continue.

What to send

Do not send a generic message that could be sent to any company.

A useful first message includes your name; where you are based or how you prefer to work; the type of work you are proposing; whether you are looking for employment, contract work, collaboration, internship, contribution, or another relationship; why inAi specifically interests you; which part of inAi you want to help with; what you have already built, written, researched, shipped, designed, organized, or contributed to; links to a portfolio, GitHub, writing, CV, LinkedIn, website, research, or examples of work; what you think you could do first; your availability, constraints, and preferred working model; and whether anything in your message is confidential.

Keep the first message concise. A clear one-page message is better than a long unfocused pitch.

Do not include sensitive personal data, private employer data, customer data, credentials, private datasets, or confidential information unless inAi has explicitly asked for it and the right process is in place.

What not to send

  1. Generic mass applications.
  2. Messages that only ask whether there are “any openings” without explaining fit.
  3. Requests to become an “AI employee” or to join internal agent architecture.
  4. Claims that you can deliver AGI or solve all AI problems.
  5. Confidential material from another company.
  6. Private datasets, credentials, or sensitive personal data.
  7. Long pitch decks without a clear work proposal.
  8. Partnership requests disguised as job applications.
  9. Agency pitches with no relation to inAi's actual product architecture.
  10. Spam, automated outreach, or irrelevant services.

Contact route

For work, collaboration, contractor, future team, or career-related messages, use careers@inai.world.

If your message is more general, use Contact.

If your message is about a partnership rather than work, use Partners or partnerships@inai.world.

If your message is about research collaboration, use Academia / Research or research@inai.world.

If your message is about privacy, legal, or formal company information, use Legal and Privacy.