This is not a managerial CTO role. This is a builder CTO role.

You will:

- Architect the system
- Write and review critical code
- Lead AI implementation
- Design ERP strategy
- Hire and mentor engineers
- Make hard technical decisions early

You are expected to stay close to the codebase while building the engineering organization.

Core Mandate

You will own and evolve:

- Consumer & internal mobile platforms
- AI companion systems
- Kitchen AI systems
- ERPNext-based operations backbone
- Shared backend, data, and AI infrastructure
- Engineering culture and hiring

What You Will Build

1. AI Systems

Current AI ecosystem includes:

- Custom Agent Pipelines
- OpenAI / Cohere (via OpenRouter)
- Langfuse (evaluation & observability)
- mem0 (memory layer)
- Redis / BullMQ for async orchestration

You will:

- Architect agent systems (memory, tools, orchestration)
- Define evaluation frameworks
- Build reliability and observability
- Ship AI features that create measurable outcomes
- Decide where deterministic systems outperform AI

We are not building demos. We are building production AI.

2. ERP & Operations Backbone

ERP Stack:

- Frappe Framework (Python)
- MariaDB
- Redis
- Vue 3, React
- WhatsApp integrations

You will:

- Architect ERPNext customization without breaking upgrades
- Align ERP workflows with real kitchen operations
- Integrate ERP cleanly with AI and product systems
- Build for multi-country expansion

3. Backend & Platform Architecture

Product Stack:

- Node.js, TypeScript, Express
- PostgreSQL, Prisma
- Redis, BullMQ
- React, TypeScript, shadcn/ui
- React Native (mobile)

You will:

- Define service boundaries
- Establish API contracts
- Maintain system clarity across products




- Prevent technical debt from accumulating early

4. Kitchen & Real-World Systems

You will oversee:

- Kitchen apps
- Ops dashboards
- Big Boss AI monitoring

Systems must work in real production kitchens — not just in staging environments.

You must be comfortable building technology that interacts with messy physical environments.

What Makes This CTO Different

You are:

- Writing and reviewing code regularly
- Designing architecture personally
- Interviewing every senior engineer
- Deciding build vs buy
- Owning the AI roadmap

You are not:

- Just managing managers
- Detached from the codebase
- Focused only on slide decks

What Success Looks Like (12 Months)

- AI companion delivers measurable insights, not generic chat
- Big Boss operates reliably in live kitchens
- ERP scales without becoming brittle
- Engineering velocity increases without chaos
- Architecture supports multi-region expansion

Ideal Profile

Must Have:

- 10-15+ years building complex systems
- Led multi-product engineering teams
- Strong backend engineering background (Node.js and/or Python)
- Built AI systems beyond easy API integrations
- Experience with ERP or operations-heavy systems
- Strong product judgment

Strong Plus:

- Agentic AI architecture experience
- Healthtech, foodtech, logistics, or supply-chain domain
- Video AI or real-time systems exposure
- Prior startup scaling experience

Why This Role Is Critical

At this stage, technology defines whether:

- Dieture becomes a scalable Food care platform or
- It becomes a collection of disconnected systems

The CTO will define the company’s technical DNA for the next 5-7 years.

Benefits :

- Work from home

Work Location: Remote

Work Location: In person

📌 Chief Technology Officer (CTO) (Bengaluru)
🏢 Dieture
📍 Bengaluru