Mission, not management theatre
Audecius is not run through long approval chains. Small, accountable groups work directly on the problem, understand the product boundary and own their decision through operations and support.
Careers at Audecius
Help build it before the category is settled.
Clarity is designed to give people back time, orientation and room to act. This category is taking shape now. Those who build early do more than take on tasks — they shape what may later feel inevitable.
Open roles
No open role. Not the end of the question.
You can still submit a complete speculative application. It is stored, acknowledged by email and read by the company leadership — without promising an interview or a future role.
Submit a speculative application
What we work on
We are not building for the existing standard. We are building the next one.
A helpful next step takes more than a beautiful screen: dependable identity, clear language, safe approvals, durable data paths, good support and an explicit boundary for AI.
That is why product work at Audecius ends neither at the interface nor at release. We want to build decisions that remain understandable under real pressure from school, family and international exchange.
Technology at ClarityValues made visible in the product
Not on the wall. In every decision.
Our values should be testable in claims, permissions, interviews and the way work is assessed.
01
Truth before speed
We distinguish clearly between released, preview and planned. A precise no is better than an impressive promise.
02
Responsibility is architecture
Minors, school, health, family and exchange change permissions, data paths and approvals — not only legal copy.
03
Expertise may disagree
Good decisions emerge when specialists defend the details, test arguments openly and build a better solution together.
04
Access begins in the design
Language, contrast, motion, keyboard use and assistive technologies belong in specification, design, engineering and QA.
How we want to work
Depth beats hierarchy. Responsibility beats status.
The best solution wins through relevant knowledge, honest discussion and exceptionally careful execution — not through the most senior title in the room.
- People retain the decision
- Clarity can organise, explain and prepare. For consequential steps, preview, approval and a way back remain visible.
- Details are leadership work
- A data path, a focus state and a comprehensible sentence are part of the same product quality. Responsibility is not delegated to the final review.
- Writing creates shared context
- Decisions, boundaries and open questions are recorded clearly. That makes collaboration across functions and time zones resilient.
- Evidence beats volume
- We assess work by problem understanding, depth of craft, impact and learning ability — not by the loudest self-presentation.
01
02
03
04
Founder-led operating model
Small teams. Serious responsibility.
The strongest Silicon Valley teams were never strong because they abolished hierarchy. They were strong because responsibility, expertise and decisions moved closer to the work. We translate that ambition for Audecius — without chaos or founder folklore.
This is an early stage. People who join now do more than inherit a finished job description: they can shape how Clarity is built, which boundaries apply and what standard this product category sets.
Something important is not created by claiming to be important. It is created through exceptionally good, accountable work — often long before that becomes obvious from the outside.Craft at Audecius
Thinking becomes visible before it becomes code.
We work with sketches, prototypes, data contracts, tests and written decisions. The goal is not more process. The goal is to see mistakes early and make the details precise together.
- Product
- Problem, boundary and intended outcome
- Design
- States, language, interaction and access
- Engineering
- Contract, failure mode, test and operation
Fields for future collaboration
The disciplines from which a category is built.
These fields describe possible directions for speculative applications. They are not current job advertisements and make no claim about team size.
Engineering
Apple platforms, web, backend, identity, data flows, reliability and security engineering.
AI & Research
Context, evaluation, sources, action safeguards and clear boundaries between on-device and cloud AI.
Product & Design
Product strategy, interaction design, information architecture, language, motion and design systems.
Operations & Support
Reliable answers, routing, incident work, quality review and processes that genuinely help people.
Education & Context
School, learning, teachers, families and international exchange as real product domains.
Trust & Business
Privacy, legal, partnerships, finance, communications and responsible scaling.
Profiles for possible future roles
Depth in the discipline. Responsibility for the system.
These profiles show work that may become relevant when a future need arises. They are not open roles, a guarantee of contact or complete job descriptions.
01
Engineering
Software Engineer · Apple Platforms
Build Clarity as a native, accessible and dependable Apple platform — from its local data model to approvals, widgets and system integrations.
What you would work on
- Swift and SwiftUI architecture for iPhone and iPad
- SwiftData, StoreKit, EventKit and permissions paths
- Performance, offline behaviour, accessibility and release QA
What matters
- A bachelor's degree in computer science or a related field — or exceptionally strong, demonstrably equivalent practical experience
- Usually at least four years of responsibility for production native software; exceptional open-source, research or founder work may provide equivalent evidence
- Deep Swift expertise, sound Apple-platform patterns and demonstrated work on performance, concurrency, persistence and accessibility
- Ability to defend product boundaries, data flows, failure modes and architecture decisions precisely in writing
Good evidence
Several released products, a technically strong repository, in-depth case studies or specific contributions to architecture, performance, accessibility and operational quality.
02
Engineering
Software Engineer · Web & Platform
Develop fast, accessible web experiences and durable platform contracts for account, support, storage, Developer Center and public product surfaces.
What you would work on
- TypeScript, React and Next.js product experiences
- API, authentication, database and background-job contracts
- Observability, security reviews, tests and reproducible deployments
What matters
- A bachelor's degree in computer science or a comparable field — or exceptionally strong equivalent engineering experience
- Usually at least four years of responsibility for production web or platform software with real user, authentication and data paths
- Excellent TypeScript expertise and deep practical experience with at least one production backend, database and observability stack
- Sound judgement in authentication, authorisation, privacy, distributed failure modes and backwards-compatible contracts
Good evidence
Production systems, open-source contributions, traceable architecture decisions or technical incident and reliability work.
03
Intelligence
Machine Learning Engineer
Make AI features measurably useful through evaluated context paths, controlled actions, clear budgets and safe fallbacks.
What you would work on
- Evaluation pipelines, retrieval and model or prompt experiments
- Inference boundaries and measurement of latency, quality and cost
- Product integration across on-device and cloud models
What matters
- A bachelor's degree in computer science, machine learning, mathematics or a related field; a master's is preferred — or exceptionally strong equivalent ML work
- Usually at least three years working on production ML systems, evaluation infrastructure or high-quality research engineering
- Very strong foundations in statistics, data quality, model evaluation, experimental design and reproducible analysis
- Demonstrated understanding of privacy, safety, bias, cost and latency, and the limits of automated metrics
Good evidence
Evaluation reports, production ML systems, research code, methodologically sound benchmarks or model improvements you owned.
04
Intelligence
AI Research · Applied Scientist
Investigate new methods for context, planning, reliability and human–AI collaboration, then translate them into verifiable product prototypes.
What you would work on
- Define research questions, baselines and robust evaluations
- Run experiments in reasoning, tool use, memory and human oversight
- Document results clearly and productise them with engineering
What matters
- A master's or doctorate in machine learning, computer science, mathematics, cognitive science or a relevant field is preferred — alternatively, exceptionally strong demonstrable research
- Publication, preprint or research-engineering evidence at an internationally competitive standard
- Excellent foundations in statistics, experimental design, baselines, ablations and scientific writing
- Ability to publish negative results, uncertainty, reproducibility and limitations as clearly as successes
Good evidence
Peer-reviewed work, preprints, reproducible experiments, research engineering, open source or rigorous independent research.
05
Product
Product Designer · Systems & Interaction
Design complex school, family, exchange and AI journeys so that people immediately understand state, consequence and the next step.
What you would work on
- End-to-end journeys, information architecture and prototypes
- Design system, motion, accessibility and clear product language
- Research synthesis and close development with engineering
What matters
- A degree in design, HCI or a comparable subject — or exceptionally strong equivalent product-design experience
- Usually at least four years working on complex digital products, or an outstanding and comprehensively evidenced earlier career
- A portfolio showing problem understanding, research, iteration, rejected options, system decisions and impact rather than only final screens
- Exceptional judgement in interaction, typography, motion, system states, product language and inclusive design
Good evidence
Two to four detailed case studies, functional prototypes, design-system work or shipped products with your contribution clearly identified.
06
Product
Product Manager · Clarity Systems
Turn user problems, technical truth and safety boundaries into a clear sequence of decisions and verifiable releases.
What you would work on
- Problem definition, discovery, specification and prioritisation
- Precisely defined metrics and release and risk decisions
- Coordination across design, engineering, support, legal and domain expertise
What matters
- A bachelor's degree or comparable qualification — or exceptionally strong equivalent product ownership
- Usually at least five years of responsibility for complex, technical or regulated products
- Evidence of translating ambiguous problems into clear product contracts, prioritised roadmaps and measurable releases
- Technical depth, precise writing, strong analytical judgement and a willingness to stop unsupportable claims or releases
Good evidence
Product memos, launch or experiment reports, decision records or case studies with trade-offs and outcomes.
07
Trust
Security, Privacy & Trust Engineer
Secure identity, data access and consequential actions so that protection does not depend on one interface or a favourable outcome.
What you would work on
- Threat modelling and reviews of authorisation, secrets and data flows
- Security tests, incident readiness and auditable controls
- Privacy by design for minors, families, schools and AI
What matters
- A bachelor's degree in computer science, IT security or a related field — or exceptionally strong equivalent security experience
- Usually at least four years of in-depth work in web, cloud, mobile or identity security
- Practical experience with threat modelling, authentication and authorisation, cryptographic foundations, least privilege, secure SDLC and robust incident work
- Clear communication of exploitability, risk, residual uncertainty and prioritised mitigations to engineering and leadership
Good evidence
Security reviews, responsibly published research or disclosure work, hardened systems, tools or substantial incident experience.
08
Experience
Support & Product Operations
Turn real user questions into better answers, safe escalations and specific product improvements.
What you would work on
- Case routing, quality review, escalation and knowledge management
- Feed patterns of failure and friction back to product and engineering in a structured way
- Operational workflows, response standards and traceable service metrics
What matters
- A degree or vocational qualification in a relevant field — or exceptionally strong equivalent operational experience
- Usually at least three years of demanding product, support or service-operations responsibility
- Exceptionally clear and calm written communication in German and English; further languages provide valuable evidence
- Very good judgement on sensitive topics, safety boundaries, incident escalations and human hand-offs
Good evidence
Support or operations processes, redacted writing samples, quality programmes, incident coordination or documented service improvements.
Qualifications are assessed in relation to the role. A degree can demonstrate strong foundations; equivalent practical work, research, open source, vocational training or demonstrable impact can provide the same evidence.
When interest becomes a role
Clear before it begins.
There is no active selection process today. If a specific need matches later, every step should be clear, role-specific and mutual.
- 01
Application received
The system stores your speculative application and sends an acknowledgement. It does not refer to a currently open role.
- 02
Review the evidence
We consider relevant experience, work samples and public profiles together, without treating CV keywords as a shortcut.
- 03
Meet when there is a match
If a specific need fits your profile, we clarify the role, working model, expectations and mutual questions in an initial conversation.
- 04
Structured conversations
Later interviews cover the same topics explained in advance. Participants assess specific, role-related evidence.
- 05
Work sample only with a reason
If a work sample is genuinely needed later, it remains appropriately bounded and is paid when the work can be used productively. No disguised unpaid work.
- 06
Decision and joining
The decision, terms and next steps are communicated clearly. Only then does a documented, role-specific onboarding path begin.
Before submitting
Clarity also applies to application
You should know what this path is, what it is not and which documents do not belong here.
- Current status
- No role is currently advertised publicly. Your speculative application is nevertheless genuinely received; a selection process starts only when a specific need matches.
- No promise of a reply
- An entry creates no entitlement to an interview or later consideration. If a concrete need fits, Audecius will contact you at the address provided.
- Accessible process
- If you need an adjustment for a later conversation, you can tell us in advance. It is handled separately from the professional assessment.
- Less data
- Please do not send identity documents, health data, proof of salary, certificates or confidential material from previous employers.
- Fair work samples
- No productively useful assignment is disguised as an unpaid test. Scope, purpose, use and any compensation are agreed in advance.
Careers · Speculative application
Show us what has helped you grow.
There is no advertised position at present. You can still submit a speculative application to Audecius. Experience, motivation and optional work evidence are captured securely; if a future need matches your profile, we will contact you.
- Open roles
- None published
- Account required
- No
- CV
- Not currently available as an upload
- Profiles
- GitHub, LinkedIn and portfolio optional
Checking the secure application path
The connection is being checked live.
Questions about speculative applications
Good to know.
Can I apply for a specific position?
Not yet. As soon as a genuine role is approved, it will appear on this page with its working model, responsibilities, requirements and own process.
Do I need an Audecius account?
No. The speculative application works without a product account. Careers and product identities remain separate.
Is a GitHub profile required?
No. GitHub, LinkedIn and a portfolio are optional evidence. What matters is what explains your work best without disclosing confidential information.
What belongs in the CV?
A clear overview of relevant positions, responsibilities and impact is enough. A PDF is optional; the structured details in the form remain the primary starting point.
Can I discuss accessibility requirements?
Yes. If a conversation takes place, you can tell us about a necessary adjustment in advance. It is not an assessment criterion.
Should I send confidential work samples?
No. Share only material you are legally permitted to show publicly. Remove internal data, customer names and protected content.
Audecius
Your role may not exist yet. The problem already does.
We publish when the task, decision space and selection process are clear. Until then, people doing exceptional work need not remain invisible.