← All collaboration areas

Internal Systems, Automation and Knowledge Operations

Exploratory Collaboration: Business Systems & Automation Engineering

Explore whether a later, written and appropriately compensated collaboration on Mental Fulfillment’s internal systems, knowledge workflows and carefully bounded automation could make sense.

Non-binding collaboration exploration

This is not a current employment vacancy, paid project or unpaid operational role. No development or other usable work product is requested at this stage.

Exploratory conversations onlyFuture collaboration considered worldwideNo operational work at this stagePotential future remote scope

About Mental Fulfillment and AWALA

Mental Fulfillment is an early-stage, purpose-driven artificial intelligence software company being built in Germany. Our first product, AWALA, is a voice-first AI wellbeing assistant designed to support adults through short, structured sessions that help them pause, reconnect with themselves, gain clarity and identify a constructive next step.

AWALA is not intended to provide therapy, diagnoses or emergency support. We are committed to responsible artificial intelligence, psychological safety, privacy, human dignity and clear product boundaries.

Our broader vision is to contribute to a more conscious and compassionate world—one in which people are better able to care for themselves, other people, animals and nature.

The potential future scope

We are not currently hiring for or commissioning this role. We would like to meet hands-on engineers with whom a later collaboration on the internal systems that help Mental Fulfillment operate reliably and efficiently might make sense.

Following a separate written and appropriately compensated agreement, a future scope could cover document orchestration, knowledge workflows, process automation, internal tools and secure integrations. It would be a software-engineering and systems-ownership scope—not prompt-engineering-only or no-code-only work.

Role boundaries and collaboration

Under a later written mandate, this scope could own an agreed operational backlog for internal company-document orchestration, knowledge workflows and business-process automation.

It would not own AWALA’s text or voice runtime, wellbeing methodology or company-wide architecture governance. Responsibilities among future contributors, interfaces and decision rights would be agreed before work starts.

What a later paid scope could include

  • A modular architecture for internal business systems and automation
  • A first usable document workflow for intake, classification, routing, review, human approval, versioning and publication
  • Clear sources of truth that prevent conflicting document versions
  • Two or three high-value automations across recruitment, founder operations, knowledge management, handovers or reporting
  • Secure integrations between Google Workspace, project tools, databases and artificial intelligence services
  • Deterministic workflows combined with carefully bounded AI components
  • Permissions, audit trails, monitoring, testing, error handling and recovery
  • Maintainable documentation and measurable outcomes such as time saved, fewer errors and reliable operation

What we are looking for

  • Strong experience building internal applications, workflow systems or integration platforms
  • Solid software-engineering skills in Python, TypeScript or a comparable modern language
  • Practical experience with application programming interfaces, webhooks, OAuth, databases and tools such as n8n, Make, Zapier or Power Automate
  • Ability to build custom software when low-code is insufficient
  • Understanding of AI-supported workflows, structured model outputs, tool use and document retrieval
  • Sound judgment about what should be deterministic, AI-assisted or deliberately human-led
  • Experience with testing, observability, data security, access control and European privacy requirements
  • Clear communication, disciplined documentation, high personal responsibility and genuine mission alignment

What a later collaboration could offer

  • Significant ownership of internal business systems and operating standards under a written mandate
  • Close collaboration with the Founder/Product Lead and relevant technical contributors
  • Potentially 100% remote work from anywhere in the world, with agreed overlap during Central European working hours
  • A culture built on honesty, empathy, responsibility, sustainability and constructive disagreement
  • A possible long-term perspective if financing, professional fit and a separate agreement allow it

The current exploration and funding reality

Mental Fulfillment and AWALA are in an early company-building and product phase. Institutional financing is not secured, and there is currently no approved budget for employment or productive services under this exploration.

This page is a non-binding collaboration exploration—not a current employment vacancy, paid project or unpaid operational role. At this stage, we may hold introductory conversations, review an existing portfolio or discuss existing materials in general. We do not request or accept unpaid development, consulting, design, strategy or any other operational work product.

Any productive contribution would begin only after a separate written and appropriately compensated agreement covering scope, compensation, contract type, confidentiality, intellectual property, data protection and acceptance.

Mental Fulfillment cannot currently provide an ongoing source of income. Interested people should not base their present professional or financial planning on compensation from us. We do not ask for private income, savings or family-finance information.

Funding, employment, salary, equity, a title, core-team status or a particular start date is not promised. Mission fit, vision fit and team/collaboration fit are important, but they do not replace professional evidence or a clear agreement.

How to express interest

Use the form below in English or German to express interest in a non-binding introductory conversation. Please provide a current profile or CV link, relevant evidence, your availability for an initial conversation and your expectations for any possible later paid engagement.

Different backgrounds and perspectives are welcome. We consider demonstrated ability alongside mission fit, vision fit and team/collaboration fit. An expression of interest does not create a role, engagement or commitment on either side.

Non-binding expression of interest

Explore Exploratory Collaboration: Business Systems & Automation Engineering

You may answer in English or German. We do not ask for a file upload: a profile or CV link is sufficient, and documents can be shared later if needed.

This is not an application for a current paid position or a request for unpaid operational work.

Fields marked with * are required.

1. Contact details

2. Motivation and evidence

3. Five skill self-ratings

Rate your current practical ability from 1 star (basic familiarity) to 5 stars (expert, able to lead and teach). These ratings are context for human review—not an automated score.

Python or TypeScript *Production-quality software engineering and maintainable code.
APIs, webhooks and OAuth *Secure integrations between business systems and external services.
Workflow automation *Deterministic workflows, recovery paths and appropriate human approval.
Document and knowledge systems *Sources of truth, routing, versioning and retrieval.
Security, testing and observability *Access control, testing, monitoring, audit trails and error handling.

4. Role-specific questions

Please answer honestly. A “No” does not trigger an automatic rejection on this website.

1. Have you designed and implemented at least one internal workflow, automation or document/knowledge system used by real users? *
2. Do you have hands-on experience with Python or TypeScript and integrations using application programming interfaces, OAuth and databases? *
3. If a later paid agreement is reached, could you reliably overlap at least four working hours with Central European Time on agreed days? *
4. Please describe one existing document, knowledge or workflow system you personally delivered, including your contribution, the safeguards used and the practical result. *Describe past work only. We are not requesting a design, specification or work product for Mental Fulfillment.
5. Do you understand that this is only a non-binding exploration, that no operational work is requested now, and that any future productive work would require a separate written and appropriately compensated agreement without any promise of funding, employment, salary, equity, title or core-team status? *