Mental Fulfillment
DEExplore collaboration
DE
← All collaboration areas

Architecture, Full-Stack Engineering and AI Systems

Exploratory Collaboration: Lead AI Systems Architecture & Full-Stack Engineering

Potential future scope: Large Language Models and Agentic Systems

Explore whether a later, written and appropriately compensated collaboration on lean architecture, full-stack foundations and responsible AI systems could make sense—including, across our two technical explorations, one possible additional founding profile for an intended and unconfirmed EXIST application.

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
Express interest

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 senior or lead engineers with whom a later collaboration on lean, dependable architecture and critical implementation foundations might make sense.

Following a separate written and appropriately compensated agreement, a future scope could establish technical foundations for internal orchestration systems and the separately governed AWALA product runtime. It would require strong architectural judgment and production-level implementation capability, not only advisory or management experience.

This exploration does not appoint anyone as Lead, Chief Technology Officer, co-founder, core-team member, company officer or authorised company representative. Any later responsibilities and decision rights would be defined in writing.

What a later paid scope could include

  • Define the lean target architecture, system boundaries, data flows and trust boundaries
  • Make and document pragmatic build-versus-buy and technology-stack decisions
  • Produce Architecture Decision Records: concise, traceable documentation of significant technical decisions
  • Design deterministic workflows and carefully bounded large language model and agent components
  • Establish explicit state models, human approval, auditability, versioning, backup, recovery and readback verification
  • Define interfaces between internal company systems and the technically and legally separated AWALA runtime
  • Prevent uncontrolled mixing of company documents, product specifications, user data and sensitive wellbeing information
  • Design provider abstraction and avoid unnecessary dependency on a single artificial intelligence or cloud vendor
  • Establish automated testing, evaluations, observability, security controls and cost measurement
  • Create technical contracts that allow other engineers to implement independently and safely
  • Build reference components and critical vertical slices where architectural validation requires hands-on implementation

Role boundaries and collaboration

Under a later written mandate, a Business Systems & Automation scope could own internal document and workflow automation, while an architecture scope could define and validate architectural patterns, security boundaries and shared technical contracts.

A later AI Product Engineering scope could primarily implement AWALA’s vertical product slices. Exact responsibilities and review rights would be agreed before operational work starts.

Possible first 90-day outcomes after a paid agreement

  1. A documented lean target architecture covering system boundaries, data flows, provider choices, security assumptions, cost limits and delivery stages
  2. A concise set of Architecture Decision Records and enforceable technical contracts for state, approval, audit, testing and data separation
  3. Technical validation of the first controlled document-orchestration slice together with the Business Systems & Automation Engineer
  4. A working foundation for the separately governed AWALA text and voice runtime
  5. A realistic build plan with release gates, risks, operating costs and clear handover documentation

What we are looking for

Experience with voice artificial intelligence, realtime systems, European data protection or safety-critical systems is valuable but not required for every initial work package.

  • At least five years of substantial production experience in software engineering, system architecture or closely related roles
  • Demonstrated ownership of system architecture combined with hands-on full-stack implementation
  • Strong experience with Python and TypeScript or comparable production technologies
  • Experience with application programming interfaces, relational databases such as PostgreSQL, cloud infrastructure and deployment
  • Practical experience building large language model applications, tool-calling workflows or agentic systems
  • Experience with structured model outputs, explicit state management, automated tests and evaluations
  • Strong understanding of security- and privacy-by-design
  • Experience with continuous integration and continuous delivery, monitoring, logging and incident recovery
  • Ability to design for cost control, provider portability and technical handover
  • Clear written communication, disciplined documentation and pragmatic minimum-viable-product judgment

Possible founding-team pathway through an intended EXIST application

Across our two technical explorations, we are currently considering one additional senior technical founding profile for a possible joint EXIST-Gründungsstipendium application. The profile could focus on architecture or hands-on artificial-intelligence product engineering. This means one possible profile across both descriptions—not one place per description.

This is an early and unconfirmed pathway—not an awarded funding place, employment offer, stipend promise or guarantee of admission to a founding team. The programme can support a maximum of three stipend holders. Participation depends on each person’s eligibility, an eligible German university or research institution, a formal application and a positive funding decision. The eligibility of the project and the company-formation timing must also be confirmed before an application.

No company shares, founder title, core-team status, salary or later employment are promised. Any founder role, governance, responsibilities, intellectual-property arrangements and possible equity would require separate discussion and a written agreement.

Until a written paid agreement or an approved and properly documented funding framework exists, we request no productive work. Under the current EXIST rules, active employment during the funding period is excluded and paid side work exceeding 20 hours per month is not permitted.

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.

What a later collaboration could offer

  • Potentially 100% remote, with future collaboration considered worldwide
  • Regular agreed overlap with Central European working hours
  • Potential direct collaboration with the Founder/Product Lead
  • Potential technical ownership within clearly documented decision boundaries
  • A possible long-term perspective if financing, professional fit and a separate agreement allow it

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: Lead AI Systems Architecture & Full-Stack 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.

Software and system architecture *System boundaries, data flows, trust boundaries and technical contracts.
Hands-on full-stack engineering *Production delivery with Python, TypeScript, APIs and relational databases.
Large language model and agent systems *Tool calling, structured outputs, explicit state and bounded autonomy.
Security and privacy by design *Data separation, access control, auditability and recovery.
Testing, evaluations and operations *Continuous integration and delivery, observability, cost control and incident recovery.

4. Role-specific questions

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

1. How many years of professional production experience do you have owning system architecture while also implementing full-stack systems hands-on? *We generally expect five or more years, but review evidence and responsibility rather than years alone.
2. Have you personally shipped a production large language model or agent system involving tool calling, explicit state management, automated testing and evaluations? *
3. Do you understand that the possible EXIST pathway is unconfirmed, supports at most three stipend holders, requires individual eligibility and formal approval, and carries no promise of a stipend, founder or core-team status, equity, salary or employment? *
4. 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? *

5. Privacy and submission

Your expression of interest is sent by transactional email to an access-controlled recruiting mailbox. It is not stored in a website applicant database. Please read our privacy notice (opens in a new tab) before submitting.