Chief Technology Officer

Meraki Labs; Bengaluru; On-site; INR 4,000,000 - 7,000,000; Full time

Job summary

Meraki Labs is seeking a high-velocity, production-grade engineer to build 0-to-1 AI-first products alongside founders in Bengaluru. You will own the architecture, quality, and production-readiness, treating AI as a force multiplier while delivering reliable, scalable systems.

Ideal candidates bring 10+ years of production software experience, a strong background in LLM-based native apps, and proficiency in Python, Shell, and TypeScript/Node.

Qualifications

• 10+ years of software engineering with production ownership.
• Experience building LLM-based native applications and agent frameworks.
• Expertise in Python and shell in production environments.
• Strong emphasis on test-driven development and reliability.

Responsibilities

• Own architecture, quality, and production-readiness for 0-to-1 projects alongside founders.
• Collaborate with founders to move ideas from concept to production.
• Design scalable, observable systems with robust monitoring and reliabilty.

Skills

Distributed systems

LLM-based apps

Python

Shell

TypeScript/Node

Testing & reliability

Tools

Node.js

Shell scripting

Job description

Meraki Labs (founded by Mukesh Bansal & Peeyush Ranjan) builds and rapidly scales AI-first, \"moonshot\" startups. We're looking for a high-velocity, production-grade engineer to build 0-to-1 products alongside founders.

You treat AI IDEs as a force multiplier—but you own the architecture, quality, and production-readiness that AI can't.

What We're Looking For

• 10+ years of software engineering with real production ownership of distributed or stateful systems - you've been paged for something you built and made it not happen again
• Strong understanding of LLM-based native app building, combining classic and model-driven applications to get the best of both
• Built on LLMs beyond demos: agent frameworks, tool use, context management, eval fixtures; you know why \"it worked in the transcript\" isn't evidence
• Python and shell in production settings; comfortable in TypeScript/Node
• Write boring, testable code and prefer the standard library to a new dependency
• Systems taste: append-only logs, idempotent reconciliation, fold-the-events state machines, and read-only debugging surfaces feel like home
• Evidence discipline: tests before features, claims backed by quoted observations, decisions written down

Nice to Have

• Experience running multi-tenant and single-tenant / on-prem-style fleets with per-customer isolation, upgrade paths, and migration compatibility
• Security instincts for products touching sensitive data (executives' email, calendars, messages): least privilege, loopback-only services, secrets that never hit a log
• Already orchestrate AI coding agents in your workflow and have opinions about where they break

How We Work

Small team, high trust, written decisions. Designs get adversarial review before code; PRs get automated review driven to zero open findings; features aren't done until verified on a live system. AI agents do a large share of the implementation-your leverage is judgment: framing the problem, freezing the right design, and knowing when the machine is wrong.

You Should Apply If

• You enjoy turning messy problems into concrete solutions
• You thrive in fast-moving, low-process environments
• You're excited about production engineering (monitoring, reliability, cost, latency)

You Should Not Apply If

• You want remote/hybrid (this is onsite Bangalore only)
• You prefer narrow tickets and minimal ambiguity
• You prefer highly structured, slow-moving product organizations