Founding AI Engineer

Product Engineer — Role Summary

We are looking for a Product Engineer to build user-facing products that combine AI capabilities with practical applications. You will work at the intersection of software engineering and AI, developing autonomous, agent-driven systems that solve complex educational and research problems.

Key Responsibilities:

• Product Development: Design, build, and deploy production-ready applications powered by LLMs and AI agents.
• Data Engineering: Build scalable ETL/ELT pipelines to process structured and unstructured data, including text and audio, for RAG and model fine-tuning.
• Agentic Workflows: Develop multi-step AI agents with tool calling, APIs, databases, search, reasoning, and memory.
• Rapid Prototyping: Turn ideas and research concepts into interactive, production-ready applications.
• AI Integration: Use frameworks such as LangChain, LlamaIndex, AutoGen, or custom orchestrators to integrate AI into scalable systems.
• User Experience: Transform raw AI outputs into reliable, intuitive, and responsive user experiences.
• Collaboration: Work closely with ML researchers and data engineers to integrate custom and fine-tuned models.
• Observability: Monitor agent behavior, manage edge cases, reduce hallucinations, and improve reliability in production.

The ideal candidate combines strong software engineering, AI/LLM expertise, data engineering, and product thinking, with the ability to take an AI concept from prototype to production.

AI Engineer

LLMs, Agents & AI Services

📍 Mumbai (On-site) | Full-time | 2-4 years

About the Role:

Unico Connect is an AI-first technology partner that builds custom mobile, web, and AI products for clients across multiple geographies.

AI is core to how we design, deliver, and scale software for our customers.

We are hiring an AI Engineer for a dedicated client engagement building a complex production AI platform, working on the AI capabilities and agentic features at the core of the product.

The mandatory requirement for this role is at least one AI feature personally shipped to production for real users, with operational ownership.

The role suits someone who thinks quickly on solutioning, can take an ambiguous problem to a working prototype in days, and has the discipline to carry it through to production with predictable economics.

You will work alongside the Senior AI Engineer and the wider pod, with ownership of parts of the AI surface area of the product.

Responsibilities:

Solutioning and POCs

Translate ambiguous customer problems into working POCs at speed.

Pick the right model, framework, and architecture, and demonstrate value early before scaling investment.

LLM Application Development

Build AI features and services using LLM APIs from OpenAI, Anthropic, Google, and self-hosted open-weight models (Llama, Qwen, Mistral).

Choose the right model per use case based on cost, latency, capability, and context-window trade-offs.

Agentic System Design

Design and implement agentic workflows using LangGraph, CrewAI, AutoGen, LlamaIndex Agents, or custom orchestration.

Cover tool use, planning, memory, and multi-step reasoning appropriate to the problem.

API and Service Development

Build production AI services and APIs using Python and FastAPI.

Handle streaming responses, async processing, structured outputs, retries, and graceful degradation when models or tools fail.

Retrieval and Tool Integration

Implement RAG pipelines with vector databases (Pinecone, Weaviate, Qdrant, pgvector, Chroma), embeddings, chunking strategies, hybrid search, and reranking.

Integrate external tools, internal APIs, and document sources through tool-calling and MCP-style patterns.

Cost Analysis and Unit Economics

Model the per-request and per-user cost of every AI feature before it ships.

Track token usage, prompt caching, batching, and model-routing strategies.

Drive measurable improvements in unit economics.

Production Hardening

Add observability and tracing (LangSmith, Langfuse, OpenTelemetry), guardrails, content safety checks, prompt injection defences, and fallback behaviour.

Prompt Engineering and Evaluation

Design, test, and iterate prompts with measured outcomes.

Build evaluation harnesses for accuracy, hallucination, latency, and cost.

Run benchmarks across models and prompt variants before locking in a design.

Requirements:

AI Feature Shipped to Production (Mandatory)

Must have personally built and shipped at least one AI feature that runs in production for real users, with operational ownership.

POCs, internal demos, and one-off scripts do not qualify.

2 to 4 Years of Professional Software or AI Engineering Experience

With at least one production AI feature owned end to end.

Strong Python Proficiency and API Development with FastAPI

Comfort with type hints, async, packaging, testing, streaming responses, and authentication.

Production-grade Python, not notebook-only code.

Hands-on Depth Across the LLM and Agent Stack

Working experience with at least two of OpenAI, Anthropic Claude, Google Gemini, or self-hosted open-weight models (vLLM, Ollama, Together, Replicate).

Working familiarity with at least one agent framework (LangGraph, CrewAI, AutoGen, LlamaIndex Agents) or hand-rolled equivalent.

Working knowledge of RAG, embeddings, and vector databases (Pinecone, Weaviate, Qdrant, pgvector, Chroma).

Solutioning Speed and POC Velocity

Demonstrated ability to move from a fuzzy problem to a working prototype in days.

Strong instinct for what to build first, what to defer, and what to throw away.

Cost Discipline for Production AI

Ability to calculate, monitor, and optimise the cost of LLM APIs, tokens, embeddings, vector store usage, and infrastructure.

Treats unit economics as a first-class concern.

AWS Familiarity

Working knowledge of EC2, S3, IAM, and at least one of Bedrock, SageMaker, or equivalent.

Comfortable in a Fast-Moving Environment

Self-directed, comfortable with ambiguity, takes ownership without being asked, and ships under shifting priorities.

Strong Written and Spoken English Communication

Able to explain trade-offs to non-AI engineers, designers, product managers, and clients in plain language.

Nice to Have

• fine-tuning or LoRA, QLoRA, PEFT exposure
• MCP server authoring
• eval framework experience (LangSmith, Promptfoo, Ragas, DeepEval)
• open-source AI contributions
• multi-modal models (vision, audio)

The role

A working product and a working deployment are two different things. You are the person who closes that gap.

You sit inside the client's head office. You get the deployment live, you get their teams using the dashboards, and you own whether the AI is returning something worth acting on. Every client is different: different languages on the floor, different store noise, different vocabulary for the same product, different CRM, different idea of what a good conversation looks like. The core platform does not change for each of them. You are the layer that makes it fit, and you are the one the client meets.

You are encouraged to spend time in stores. The engineers who do the best work here are the ones who have stood on a shop floor and watched where the pitch and the pipeline actually break. Nobody will make you go. You will also spend real time in the codebase, because you fix what you find rather than filing it.

What you build has a commercial edge to it. A pilot converts when the client sees the result they were promised, and an account grows when a second team inside it sees what is already sitting in their data. Both of those outcomes are yours to deliver, not somebody else's to chase.

How you will work

You design the deployment, you build it, and you own whether it holds up on a Saturday evening in a crowded store. Nobody hands you the plan, and nobody hands you the spec. You write both.

The decisions are yours. Which integration is worth the week, which vertical taxonomy needs building, what ships in the pilot and what waits, and when to tell a client that the thing they are asking for is the wrong thing to build. You go and find out what a client needs before anyone writes a line of code.

You will not be doing it alone. There are founders, AI engineers and product people around you, and they will build alongside you. What nobody will do is tell you what the client needs. That call is yours.

The work compounds if you do it well. What you learn on one deployment becomes a specification, then code, then a pattern the next one starts from. A year in, the deployments you designed should be running without you, and a new client should take a fraction of the time the first one did.

What you will do

Own the deployment end to end. Device provisioning, store connectivity, data flowing, first insight in front of the client. Get from kickoff to something real inside

the pilot window, and know by the halfway mark whether it is in trouble.

Get their HQ using it. A dashboard nobody opens is a failed deployment. Sit with the sales, marketing and L&D teams, show them what is in their own data, and

make sure the people who asked for this are actually looking at it every week.

Make the AI work on their floor. Their languages, their store noise, their product vocabulary. Benchmark transcription and speaker separation on their actual

audio, and fix what fails instead of explaining it away.

Build the vertical. Intent taxonomies, objection maps and prompt libraries for the category you are deployed into. A jewellery floor and an electronics floor do not

share a conversation model.

Wire it into their systems. CRM and POS integrations, so conversation data connects to what actually got sold and the insight can be checked against reality.

Build what the client asks for. Custom reports, dashboards and agents. Ground everything in source conversations and verify it before it ships, because a confident

wrong number costs an account.

Close the pilot. A pilot converts on results, not on effort. Know what the client agreed to judge this on, work backwards from it, and make sure the output in front of

their leadership at the end is the thing they asked for.

Grow the account. The same intelligence is worth something to marketing, L&D and category teams inside the same client. Spot which of them would benefit, show them what is already in their data, and hand a real opening to the account team.

Push it back into the product. Turn one-off client work into something the platform does by default, so the next deployment starts further ahead than this one did.

What we are looking for

Must have

• 0 to 5 years of experience. A consulting internship or an analyst role is the closest match to what this job actually asks for, but we care more about what you can do than where you did it
• Coding ability, ideally Python. Degree, internship, first job or your own projects. What we want to see is something you built that other people actually used
• Excel or Sheets at a real working level. A lot of the first conversation with a client happens in a spreadsheet before it ever happens in a dashboard
• The ability to explain a complicated idea simply. You will be taking AI output to people who do not think about models, and the explanation matters as much as the result
• Comfort at the boundaries. APIs, data pipelines, some frontend, some hardware when a device misbehaves
• An eye for where a deployment turns into more business, and the willingness to raise it yourself
• Heavy hands-on LLM usage. Prompts, evaluations, retrieval, and a clear view on where these tools break
• Fluent English and Hindi. A third Indian language counts for a lot, since the useful conversations happen on store floors and not only in HQ meeting rooms
• The instinct to go and find out what a client needs rather than waiting to be told

Good to have

Speech or audio work. Transcription, diarization, voice activity detection, or

anything that survives noisy real-world recording

Embedded or IoT experience, on ESP32 or similar

SQL and experience building things customers actually look at

Side projects, hackathons or internships where you shipped without a spec

and it worked

The Role

You own AI systems end to end. From the speech-to-text models that turn audio into text, to the diarization that separates and identifies speakers, to the agentic layer that turns conversation into memory and action, to the observability and evaluation that keep all of it honest in production. This is a wide role by design. You will own model selection, serving, and production reliability. If you want to tune one model and ignore the system around it, this is not the role.

What You Will Own

•     Speech-to-text. Evaluate, integrate, and optimize STT models across cloud and self-hosted. Drive accuracy and cost trade-offs with ground-truth metrics.

•     Speaker diarization and identification. Push accuracy on hard, real-world, multi-speaker audio.

•     Agentic AI. Build the memory and retrieval pipeline, LLM orchestration, and the agent workflows that sit on top of captured conversation.

•     Model serving and infrastructure. Stand up and optimize self-hosted serving (vLLM, Triton class). Own latency, throughput, and cost per user.

Observability

An always-on wearable means models run in production every second, on messy real-world audio. You own the visibility into that.

•     Instrument the full audio-to-memory pipeline: STT, diarization, retrieval, and LLM calls.

•     Define and track model-quality SLOs in production: transcription drift, diarization error over time, retrieval relevance, latency, throughput, and cost per user.

•     Build dashboards and alerting so model degradation is caught before users feel it.

•     Trace failures across a distributed, always-on system using metrics, logs, and traces.

•     Close the loop. Production signals feed back into evaluation and model selection.

Evaluation

We do not ship what we cannot measure. You own the systems that prove a model is actually better, not just newer.

•     Build and own ground-truth evaluation harnesses for every model in the stack.

•     Measure with real metrics: WER for transcription, DER for diarization, Recall and F1 for retrieval and speaker identification.

•     Build and maintain labeled benchmark datasets that reflect real, messy, multi-speaker audio.

•     Run regression and A/B evaluations on every model swap, prompt change, or pipeline update. Nothing ships on a vibe.

•     Reject anecdotal proxies, single confidence scores, and cherry-picked examples as evidence of quality.

What We Are Looking For

•     3 to 5 years as an AI/ML engineer with production systems behind you. Engineering and production experience is non-negotiable.

•     Depth across the modern AI stack: LLMs, speech models, vector retrieval, model serving.

•     Strong software engineering. You write code that ships and survives contact with real users.

•     Fluency in Python and the production ML ecosystem.

•     Comfort with cloud infrastructure (GCP a plus) and containerized deployment on Kubernetes.

•     A working command of observability and evaluation. You measure first and trust metrics over intuition.

•     First-principles reasoning and metric discipline.

Nice to Have

•     Research background or publications. A strong signal, not a substitute for production work.

•     Audio and speech ML experience (STT, diarization, voice).

•     Experience self-hosting and optimizing open models.

•     Experience with LLM gateway and agent orchestration patterns.

•     Experience building eval harnesses or production model-monitoring systems.

Requirements

Agentic work is must. Audio is good to have

. Self hosting models is a must

 Experience with LLM gateway and agent orchestration is a must have

Senior AI Engineer

Code Generation, Agent Architecture & LLM Systems

📍 Mumbai (On-site) | Full-time | 5+ years

About the Role:

Unico Connect is an AI-first technology partner that builds custom mobile, web, and AI products for clients across multiple geographies.

We are hiring a Senior AI Engineer for a dedicated client engagement focused on building an AI-powered application builder platform - a product where users describe software in plain English and the system generates, previews, and iteratively refines working code.

The mandatory requirement for this role is hands-on production experience shipping LLM-powered systems with agent architectures, with experience in code generation or developer tooling contexts a strong advantage.

The role is product-focused and deeply hands-on. You will own everything between the user's prompt and correct code landing in the project: the agentic loop, code generation pipeline, context management, evaluation suite, and model cost strategy.

You will work alongside the Senior MLOps Engineer who operationalises the infrastructure around your system, and collaborate closely with backend, frontend, and DevOps engineers.

Responsibilities:

Agent Architecture

Design and own the agentic loop for the platform - request interpretation, planning, tool-calling sequence (read file, edit file, run build, search code, install package), and stop conditions.

Make and revisit architectural decisions on single-agent vs. multi-agent designs, including planner/executor splits and dedicated build-repair sub-agents.

Code Generation Pipeline

Own the end-to-end generation flow: task classification, context gathering, planning, targeted edits, verification, and commit.

Implement diff/search-replace-based file editing with fuzzy matching and fallback strategies.

Enforce scope discipline so the agent makes minimal diffs and does not modify code it was not asked to touch.

Self-Repair Loop

Build and tune the automated repair loop that pipes compiler, lint, build, and runtime errors back to the model with retry budgets and model escalation.

This loop is the primary quality lever - the difference between 60-70% and 90%+ build success rates.

Context Management

Build file-relevance retrieval so the agent sees the right files, not the whole codebase: dependency graphs, AST/tree-sitter-based chunking, embeddings, recency signals, and hybrid retrieval.

Implement conversation summarisation and memory for long sessions, and address long-project degradation through codebase summaries and periodic consistency passes.

Own token budgeting and prompt caching strategy.

Prompt Engineering as a Discipline

Own the system prompt and per-task prompt variants (new feature, bug fix, styling change).

Maintain few-shot examples and enforce coding conventions, stack rules, and prohibited behaviours such as no hardcoded secrets and no whole-file rewrites.

Version prompts like code with changelogs and rollback capability.

Evaluation and Quality Measurement

Design and own the evaluation suite: representative test prompts run on every prompt and model change, scored on build success rate, instruction adherence, and output quality including LLM-as-judge and visual/screenshot checks where relevant.

Define regression gates that block quality-degrading changes from shipping.

Treat evals the way engineers treat automated testing: versioned, automated, and tracked over time.

This responsibility is non-negotiable at this level.

Model Strategy and Cost

Design model routing - cheap and fast models for classification and small edits, frontier models for complex generation.

Drive cost optimisation through prompt caching, diff-based edits over full-file rewrites, and tighter context selection.

Track cost per agent run and tokens per task; evaluate new model releases against the eval suite and lead migrations when results justify it.

Safety and Reliability of Agent Behaviour

Defend against prompt injection from user content and fetched web content.

Ensure secrets never appear in generated client code.

Define what the agent's tools may and may not do in collaboration with the platform team.

Contribute to output moderation and abuse-pattern awareness.

Mentorship and Engineering Standards

Run code reviews, define engineering conventions for AI work, and raise the engineering bar across the AI team.

Work closely with the Senior MLOps Engineer on handoff of eval design, prompt configurations, and model routing logic.

Requirements:

Hands-on Production Ownership of LLM-Powered Systems with Agent Architectures (Mandatory)

Must have personally shipped and operated at least one complex production AI system - agentic, multi-step, or code generation - with end-to-end ownership of architecture, evaluation, and cost.

POCs, internal demos, and tutorial-grade work do not qualify.

5+ Years of Professional Software or AI Engineering Experience

With at least 3 years focused on LLM applications, AI engineering, or production AI systems.

Candidates with strong backend backgrounds and a clear, substantive pivot into LLM systems qualify.

Strong Python Proficiency and Service Development

Production-grade Python with FastAPI or equivalent: type hints, async patterns, streaming responses, testing, and packaging.

Not notebook-only.

Depth Across LLM APIs and Agent Systems

Production experience with at least two of OpenAI, Anthropic Claude, Google Gemini, or open-weight models (vLLM, Ollama, Together).

Production experience with at least one agent framework (LangGraph, CrewAI, AutoGen, LlamaIndex Agents) or hand-rolled equivalent.

Hands-on with tool calling, structured outputs, and multi-step reasoning.

Demonstrated, Systematic Evaluation Practice - Non-Negotiable

Must have built evaluation harnesses that gate production releases, not ad-hoc testing.

Hands-on with at least one of LangSmith, Langfuse, Promptfoo, Ragas, or DeepEval.

Candidates with no systematic answer to evaluation should not be considered at senior level regardless of other strengths.

Cost Discipline for Production AI

Track record of measurable cost optimisation on production AI features.

Able to speak in specifics: cost per request, savings achieved through caching or model routing, context reduction decisions.

AWS Working Knowledge

Hands-on with EC2, S3, IAM, and Docker.

Comfort with CI/CD workflows and deploying AI services.

Awareness of LLM Security Failure Modes

Familiar with prompt injection patterns, understands that system prompt rules alone are insufficient, and has experience with output validation and content safety in production.

Nice to Have

• Experience with AST/tree-sitter tooling, diff-based editing systems, or compiler-adjacent work
• MCP server authoring
• Open-source AI contributions
• Published technical writing on LLM systems
• Multi-modal model experience
• Fine-tuning exposure (LoRA, QLoRA, PEFT)

Job Description – AI Engineer (End-to-End Development & Deployment)

Role Summary

We are looking for an AI Engineer with hands-on experience in designing, developing, deploying, and maintaining Generative/Agentic AI solutions in production. The ideal candidate should have end-to-end ownership of AI applications, from development to deployment, monitoring, and optimization.

Key Responsibilities

●        Design, build, and deploy Generative/Agentic AI solutions.

●        Develop applications using LLMs, RAG, AI agents, and vector databases.

●        Build scalable APIs and integrate AI solutions with enterprise applications.

●        Implement CI/CD pipelines, containerization, and MLOps best practices.

●        Monitor, optimize, and maintain production AI systems.

●        Collaborate with cross-functional teams to deliver business-driven AI solutions.

Required Skills

●       Strong programming skills in Python.

●       Experience with vector databases (e.g., Pinecone, FAISS, ChromaDB) and graph memory systems

●       Knowledge of atleast one agent development framework: Google ADK (preferred), LangChain/LangGraph/LlamaIndex, CrewAI

●       Experience with LLMs, RAG, GenAI, AgenticAI Agents

●       Hands-on experience with FastAPI, and REST APIs.

●       Knowledge of Docker, Kubernetes, Git, CI/CD.

●       Experience with AWS, Azure, or GCP. 

●       Experience with security compliance, monitoring and observability tools such as AWS CloudWatch, Azure Monitor, Google Cloud Monitoring.

About Venxr

VenXR is an AI-driven AdTech startup building AdsGPT, redefining how brands plan, execute, and optimize ad campaigns through AI. We're a fast-growing, lean team looking for a Product Engineer who can own features end-to-end, from idea to shipped product.

About the Role

We're looking for a Product Engineer who thinks like a builder, not just a coder. Someone who cares as much about why we're building something as how it's built, and takes real ownership of the product outcomes, not just the code they ship.

Tech Stack

Frontend: React.js | Backend: Python (Django) | AI: Claude / LLM-driven development

Roles & Responsibilities

• End-to-End Feature Ownership
• Own features from concept to deployment — writing clean, scalable code while staying closely tied to the product goal and user impact behind it.
• Full-Stack Development
• Build and maintain front-end interfaces in React.js and back-end systems in Python/Django, ensuring performance, reliability, and scalability across the product.
• Product Thinking
• Work closely with Product, Design, and Founders to shape specs, question assumptions, and suggest simpler or smarter ways to solve user problems.
• Rapid Iteration
• Ship fast, test in production, gather feedback, and iterate, balancing speed with code quality.
• Cross-Functional Collaboration
• Partner with Design and Data teams to bring dashboards, AI-driven features, and data visualizations to life.
• System Design & Architecture
• Contribute to technical architecture decisions, ensuring the codebase stays scalable as the product and team grow.
• Debugging & Problem Solving
• Diagnose and resolve complex technical issues quickly, treating downtime or bugs as urgent, customer-impacting problems.
• AI-Native Development
• Actively build with AI — using Claude and other LLM tools not just to assist coding, but to develop AI-powered features, prompt workflows, and intelligent product capabilities within AdsGPT itself.

Requirements

• 3–5 years of experience as a Product Engineer, ideally in a startup or B2B SaaS environment
• Strong proficiency in React.js for front-end development
• Strong proficiency in Python, with hands-on experience in Django for back-end development
• Solid understanding of REST APIs, databases (SQL/NoSQL), and system design fundamentals
• Hands-on experience building with AI tools (like Claude), not just using them for coding assistance, but developing core AI products.
• Experience working directly with Product/Design teams, not just executing tickets
• Comfortable working in ambiguous, fast-changing environments with minimal hand-holding
• Strong debugging and problem-solving skills

Good to Have

• Familiarity with the Model Context Protocol (MCP) for securely connecting LLMs to external tools and APIs.
• Experience building conversational AI interfaces or managing complex multi-turn chatbot state across various platforms and channels.
• Experience in AdTech, MarTech, or data-heavy SaaS platforms.
• Exposure to cloud infra (AWS/GCP/Azure), Docker, and CI/CD pipelines.
• Experience with LLM evaluation/monitoring tools (Ragas, LangSmith, Langfuse, or similar).
• Experience with data visualization libraries (Recharts, D3.js, Chart.js).
• Familiarity with compliance-aware or explainable AI design in regulated domains.

What We Look For In Candidates

• Customer Obsession – A genuine curiosity about how your code impacts the customer's experience, not just whether it compiles.
• Ownership – You drive features to completion, chasing down blockers instead of waiting on them.
• Stakeholder Understanding & Management – You know when to loop in Product, Design, or Business to unblock yourself fast.
• High Standards – You hold your own code to a higher bar, even when no one's checking.
• Disagree and Commit – You debate technical decisions hard, then commit fully once the call is made.
• Simplify Relentlessly – You reach for the simplest working solution, not the most "clever" one.
• Solidarity with the Team – You show up for your teammates, no invitation needed.
• Vitality – You bring real energy and resilience that keeps you (and others) going.

• Why Join Venxr?
• Be part of a fast-growing startup that puts data at the heart of every decision.
• Opportunity to work on high-impact, real-world business challenges.
• Collaborative, transparent, and learning-oriented work environment.
• Flexible work culture with a strong focus on career development.
• Comprehensive health benefits to support your well-being.
• Team offsites and engagement activities to build stronger connections beyond work.
• Performance-based incentives and rewards recognizing your contribution and impact.

AI Product Builder | Consumer Experiences

TL;DR: ₹1 lakh/month. HSR Layout, Bengaluru. Full-time, in-person preferred, with flexibility for an exceptional fit. Use AI to build and refine consumer experiences. No CV or prior experience required. Apply by email, then an unpaid 48-hour workout assignment.

I'm Vishnu, building Aira. AI is the biggest equaliser we have, but nobody has figured out the consumer use case yet. I think Aira will be the reason everyday people start using AI daily.

I don't believe chatting is the final interface for AI. So Aira is built around a hand-drawn character that feels alive, shapes what's on your screen, and brings voice, animation and music together. The goal is the best answer, delivered in the best way for your situation, with help acting on it.

Say you're deciding what to cook. Aira helps you pick a meal, shows the ingredients, arranges the purchase with your confirmation. While you cook, it keeps the recipe and your current step on screen, speaks short instructions, and waits while your hands are busy. The same screen won't work at the gym, in meditation or while fixing a tyre. The conversation, the actions and what you see and hear should feel like one experience that adapts to what you're doing.

I'm hiring people who would have wanted to work on the first iPhone. People who obsessed over the small details that made something unfamiliar feel natural, and cared about what a person felt the first time they used it.

We've built the foundation. Your job is to take an experience, decide how it should work, build it with AI, and keep agonising until it feels right. In practice: tuning prompts and behaviour files, building or changing screen components with AI, and testing what you've made.

You may not yet be able to explain why an interaction feels incomplete. I want you to follow that feeling and build a better version. That's why we don't ask for a CV, prior experience or a coding background. We need product thinking, creativity and ownership — you question what AI gives you, make it work, and keep improving it.

We're launching in San Francisco this month. You'll work directly with me and help shape what people experience the first time they meet Aira.

The process

You'll build a workout experience from a minimal starter. We give you a stepper, a timer and the component plumbing; you decide how it behaves and build the rest. Anyone can attempt it, before any screening. You have 48 hours after receiving it. It's unpaid, for evaluation only, and your work stays yours.

AI helps me review, but I pick the shortlist myself. Shortlisted candidates get a 30-minute conversation. I aim to reply within 24 hours of submission and finish within a week.

About Venxr

VenXR is an AI-driven AdTech startup building AdsGPT, redefining how brands plan, execute, and optimize ad campaigns through AI. We're a fast-growing, lean team looking for a Product Engineer who can own features end-to-end, from idea to shipped product.

About the Role

We're looking for a Product Engineer who thinks like a builder, not just a coder. Someone who cares as much about why we're building something as how it's built, and takes real ownership of the product outcomes, not just the code they ship.

Tech Stack

Frontend: React.js | Backend: Python (Django) | AI: Claude / LLM-driven development

Roles & Responsibilities

• End-to-End Feature Ownership
• Own features from concept to deployment — writing clean, scalable code while staying closely tied to the product goal and user impact behind it.
• Full-Stack Development
• Build and maintain front-end interfaces in React.js and back-end systems in Python/Django, ensuring performance, reliability, and scalability across the product.
• Product Thinking
• Work closely with Product, Design, and Founders to shape specs, question assumptions, and suggest simpler or smarter ways to solve user problems.
• Rapid Iteration
• Ship fast, test in production, gather feedback, and iterate, balancing speed with code quality.
• Cross-Functional Collaboration
• Partner with Design and Data teams to bring dashboards, AI-driven features, and data visualizations to life.
• System Design & Architecture
• Contribute to technical architecture decisions, ensuring the codebase stays scalable as the product and team grow.
• Debugging & Problem Solving
• Diagnose and resolve complex technical issues quickly, treating downtime or bugs as urgent, customer-impacting problems.
• AI-Native Development
• Actively build with AI — using Claude and other LLM tools not just to assist coding, but to develop AI-powered features, prompt workflows, and intelligent product capabilities within AdsGPT itself.

Requirements

• 1-2 years of experience as a Product Engineer, ideally in a startup or B2B SaaS environment
• Candidates with B.Tech in CSE, AI/ML or any other equivalent educational background from Tier-1 and Tier-2 colleges will be preferred
• Strong proficiency in React.js for front-end development
• Strong proficiency in Python, with hands-on experience in Django for back-end development
• Solid understanding of REST APIs, databases (SQL/NoSQL), and system design fundamentals
• Hands-on experience building with AI tools (like Claude), not just using them for coding assistance, but developing core AI products.
• Experience working directly with Product/Design teams, not just executing tickets
• Comfortable working in ambiguous, fast-changing environments with minimal hand-holding
• Strong debugging and problem-solving skills

Good to Have

• Familiarity with the Model Context Protocol (MCP) for securely connecting LLMs to external tools and APIs.
• Experience building conversational AI interfaces or managing complex multi-turn chatbot state across various platforms and channels.
• Experience in AdTech, MarTech, or data-heavy SaaS platforms.
• Exposure to cloud infra (AWS/GCP/Azure), Docker, and CI/CD pipelines.
• Experience with LLM evaluation/monitoring tools (Ragas, LangSmith, Langfuse, or similar).
• Experience with data visualization libraries (Recharts, D3.js, Chart.js).
• Familiarity with compliance-aware or explainable AI design in regulated domains.

What We Look For In Candidates

• Customer Obsession – A genuine curiosity about how your code impacts the customer's experience, not just whether it compiles.
• Ownership – You drive features to completion, chasing down blockers instead of waiting on them.
• Stakeholder Understanding & Management – You know when to loop in Product, Design, or Business to unblock yourself fast.
• High Standards – You hold your own code to a higher bar, even when no one's checking.
• Disagree and Commit – You debate technical decisions hard, then commit fully once the call is made.
• Simplify Relentlessly – You reach for the simplest working solution, not the most "clever" one.
• Solidarity with the Team – You show up for your teammates, no invitation needed.
• Vitality – You bring real energy and resilience that keeps you (and others) going.

• Why Join Venxr?
• Be part of a fast-growing startup that puts data at the heart of every decision.
• Opportunity to work on high-impact, real-world business challenges.
• Collaborative, transparent, and learning-oriented work environment.
• Flexible work culture with a strong focus on career development.
• Comprehensive health benefits to support your well-being.
• Team offsites and engagement activities to build stronger connections beyond work.
• Performance-based incentives and rewards recognizing your contribution and impact.

Location: Hyderabad, India (home base), deployed at client sites in India. Occasional Middle East exposure possible.

About the Role

You will work as a senior AI consultant who embeds inside a customer's business. Your job is to learn how the business makes money, find the highest value problem, and build a working system that solves it.

You will not hand over a document and walk away. You will show working software early, own the roadmap, own the client relationship, and stay after go-live to run and improve the system.

Four behaviors define this role:

1. Go where the work happens. You work onsite with the customer, in the room where decisions are made.
2. Show working software early. You build a prototype in days, not a document in weeks.
3. One person owns the outcome. You are the single point of accountability for the result.
4. Stay after go-live. You keep running and improving the system after launch.

You are the single point of accountability. You are not a solo builder. A full KnackLabs engineering team in Hyderabad builds and runs the production systems behind you.

This role involves extended onsite deployments at client locations in other cities, sometimes up to six months at a stretch. Please apply only if you are ready for this way of working.

What you'll own

1. Discovery - Learn how the customer makes money. Find the highest value problem to solve first.
2. The prototype - Build a working prototype fast, using real or sample data, to prove the idea.
3. The roadmap - Decide what to build, in what order, and set clear success measures tied to business outcomes.
4. The build - Design and ship the production system with the Hyderabad engineering team. This includes data integration, agents, retrieval, and evaluations.
5. The client relationship - Be the trusted technical contact for the customer, from engineers to senior leaders.
6. Go live and after - Deploy the system, watch how it performs, fix problems, and improve it over time.
7. Feedback to the product - Share what you learn in the field so our platform and internal tools get better.

What we are looking for

1. Around 7 or more years of software engineering experience, including customer-facing or client delivery work.
2. Experience working at a consulting or professional services firm in a client-facing delivery role.
3. A full-stack development experience with strength in backend technologies.
4. Strong programming skills in Python. Working knowledge of TypeScript or JavaScript.
5. Production experience with large language models, including prompt engineering and agent development.
6. You build with AI coding tools like Claude Code as your default way of working. You have built real apps and agents this way, not just used it for document generation or review.
7. Experience building retrieval-augmented generation (RAG) systems: chunking, embeddings, vector databases, retrieval, and reranking.
8. Experience building and deploying AI systems.
9. Experience integrating with APIs and enterprise systems.
10. Experience with at least one cloud platform (AWS, Azure, or GCP).
11. Experience building evaluations to measure accuracy, safety, latency, and cost.
12. Clear communication. You can explain a technical choice to an engineer and to a business leader.
13. High ownership and comfort with ambiguity. You can take an unclear problem and turn it into a plan.
14. Willingness to work onsite at client locations in India for extended periods, and to travel as the work needs.

Nice to have

1. Experience deploying AI systems in regulated industries such as insurance, banking, or the public sector.
2. Experience with on-premises or private cloud (VPC) deployments.
3. Experience with observability and tracing tools such as LangSmith or Braintrust.
4. Experience with data engineering and pipelines.
5. A history of side projects, open source contributions, or products you shipped end-to-end.
6. Experience in embedded or forward-deployed roles before.

Stack and tools

1. Languages: Python and TypeScript.
2. Models: Claude and other frontier or open source models, chosen to fit the customer.
3. AI patterns: RAG, agents, prompt engineering, and evaluations.
4. Vector and retrieval: vector databases and retrieval pipelines.
5. Cloud: AWS, Azure, or GCP, on public or private cloud.
6. Integration: REST APIs and enterprise system connectors.