AI Software Engineering, Agentic Development (Gemini CLI)

About the Role

We are seeking a hands-on Tech Lead to design, build, and integrate AI-driven systems that automate and enhance real-world business workflows. This is a high-impact role for someone who enjoys full-stack ownership — from backend AI architecture to frontend user experiences — and can align engineering decisions with measurable product outcomes.

You will begin as a strong individual contributor, independently architecting and deploying AI-powered solutions. As the product portfolio scales, you will lead a distributed team across India and Australia, acting as a System Integrator to align engineering, data, and AI contributions into cohesive production systems.

Example Project

Design and deploy a multi-agent AI system to automate critical stages of a company’s sales cycle, including:

• Generating client proposals using historical SharePoint data and CRM insights
• Summarizing meeting transcripts
• Drafting follow-up communications
• Feeding structured insights into dashboards and workflow tools

The solution will combine RAG pipelines, LLM reasoning, and React-based interfaces to deliver measurable productivity gains.

Key Responsibilities

• Architect and implement AI workflows using LLMs, vector databases, and automation frameworks
• Act as a System Integrator, coordinating deliverables across distributed engineering and AI teams
• Develop frontend interfaces using React/JavaScript to enable seamless human-AI collaboration
• Design APIs and microservices integrating AI systems with enterprise platforms (SharePoint, Teams, Databricks, Azure)
• Drive architecture decisions balancing scalability, performance, and security
• Collaborate with product managers, clients, and data teams to translate business use cases into production-ready systems
• Mentor junior engineers and evolve into a broader leadership role as the team grows

Ideal Candidate Profile

Experience Requirements

• 5+ years in full-stack development (Python backend + React/JavaScript frontend)
• Strong experience in API and microservice integration
• 2+ years leading technical teams and coordinating distributed engineering efforts
• 1+ year of hands-on AI project experience (LLMs, Transformers, LangChain, OpenAI/Azure AI frameworks)
• Prior experience in B2B SaaS environments, particularly in AI, automation, or enterprise productivity solutions

Technical Expertise

• Designing and implementing AI workflows including RAG pipelines, vector databases, and prompt orchestration
• Ensuring backend and AI systems are scalable, reliable, observable, and secure
• Familiarity with enterprise integrations (SharePoint, Teams, Databricks, Azure)
• Experience building production-grade AI systems within enterprise SaaS ecosystems

Location: Hyderabad, India. Based at the KnackLabs headquarters, with occasional travel to client locations for workshops and reviews. This role does not involve extended onsite deployments.

About the Role

You will work as an AI Architect who designs the systems behind our client engagements: AI agents, RAG systems, automation platforms, and the conventional backend systems around them.

This is a hands-on design role, not a slideware role. You will scope architectures with clients, make the hard technical decisions, defend them in review, and stay accountable for how the systems perform in production.

You will work directly with clients. Everyone at KnackLabs does. You will sit in design discussions with client engineering teams, present architecture decisions to technical and business stakeholders, and answer for the choices you make.

A full KnackLabs engineering team in Hyderabad builds with you. You own the technical design and the quality of what ships.

What you'll own

1. Architecture - Design AI agents, RAG systems, integrations, and the scalable backend systems around them, for multiple client engagements.
2. Technical scoping - Work directly with clients to turn a business problem into a system design, with clear trade-offs and clear reasons.
3. Scale and reliability - Make sure what we build handles real load: data stores, queues, caching, horizontal scaling, and fault tolerance.
4. Design reviews - Review designs and builds across engagements. Set the technical bar and hold it.
5. Evaluation strategy - Define how we measure accuracy, safety, latency, and cost for the AI systems we ship.
6. Guiding engineers - Raise the level of the engineers building with you, through reviews and direct pairing.
7. Feedback to the platform - Feed what you learn across engagements back into our platform and internal tools.

What we are looking for

1. Around 7 or more years of software engineering experience, including direct work with customers on design or delivery.
2. Full-stack development experience with strength in backend technologies.
3. Experience designing and building scalable applications. You understand how large-scale distributed systems work: data partitioning, queues, caching, horizontal scaling, and fault tolerance.
4. At least 2 years of strong, hands-on AI experience with large language models in production.
5. You build with AI coding tools like Claude Code or Codex as your default way of working. You understand Claude Skills, have written skills yourself, use them actively, and have contributed to them.
6. Hands-on experience building retrieval-augmented generation (RAG) systems: chunking, embeddings, vector databases, retrieval, and reranking.
7. Hands-on experience building AI agents.
8. Strong programming skills in Python. Working knowledge of TypeScript or JavaScript.
9. Experience with at least one cloud platform (AWS, Azure, or GCP).
10. Clear communication. You can explain an architecture decision to an engineer and to a business leader, and defend it under questioning.
11. High ownership and comfort with ambiguity. You can take an unclear problem and turn it into a design.

Nice to have

1. Experience building evaluations to measure accuracy, safety, latency, and cost.
2. Experience with observability and tracing tools such as LangSmith or Braintrust.
3. Experience with on-premises or private cloud (VPC) deployments.
4. Experience deploying AI systems in regulated industries such as insurance, banking, or the public sector.
5. Experience with data engineering and pipelines.
6. A history of side projects, open source contributions, or products you shipped end-to-end.
7. Experience working at a consulting or professional services firm in a client-facing delivery role.

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, skills, 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.

Role Overview 

We are looking for an AI Engineer to design, build, and ship production AI systems, including agentic AI applications, for enterprise clients. This is a hands-on engineering role: you will write production code, build and evaluate models and agents, and work closely with architects and product teams to take solutions from prototype to scale. 

Key Responsibilities 

Design and build agentic AI systems: agent workflows, tool/function-calling, memory, and human-in-the-loop patterns. Build and productionise RAG pipelines, prompt-based applications, and LLM integrations across providers. Develop and maintain data and ML pipelines: feature engineering, model training, evaluation, and monitoring. Integrate AI systems with enterprise applications (CRMs, ERPs, ITSM tools) via APIs, events, and MCP-based tool servers. Implement guardrails, prompt-injection defences, and evaluation frameworks to keep AI systems safe and reliable in production. 

Write clean, tested, production-grade code and participate actively in code and design reviews. 

Collaborate with architects, product managers, and delivery teams to translate requirements into working AI solutions. Troubleshoot and optimise AI systems for accuracy, latency, and cost in production. 

Required Qualifications 

8–12 years of hands-on software engineering experience, with a strong, unbroken technical track record. Hands-on experience building and shipping AI/ML systems in production, not just POCs. 

Practical experience with agentic AI systems and at least one major agent framework (LangGraph, CrewAI, AutoGen, OpenAI Agents SDK, Bedrock Agents/Strands, or Semantic Kernel). 

Experience with LLM/GenAI systems: RAG pipelines, prompt engineering, structured outputs, and tool calling across providers. 

Strong Python skills (TypeScript/Node.js a plus), with production-grade testing, CI/CD, and API design practices. Working knowledge of ML fundamentals: model evaluation, feature engineering, and experimentation. Cloud-native experience on AWS and/or Azure: containers, serverless, event backbones, and vector databases. Understanding of LLM safety and reliability practices: guardrails, prompt-injection defences, and observability. 

We're Hiring: Agentic Tools Architect

Contract | Remote-first | Global

We're currently recruiting for one of our clients, A company that specializes in acquiring enterprise software businesses and transforming them into AI-native, profitable, scalable operations. They run remote-first, globally distributed teams, and their internal operations platform (Odoo, Redmine, GitHub) currently runs on human-shaped workflows. They're looking for someone to rebuild it for agents.

The Role

Redesign the client's operational tooling so AI agents can create, route, and resolve work alongside people — with minimal oversight. You'll own the roadmap, build the plugins (Rails-first), and set the guardrails.

You'll:

• Own feature roadmap across Odoo, Redmine, GitHub & adjacent systems
• Design agent-operable APIs, MCP servers, and automation
• Build Rails-based Redmine plugins, Odoo modules, GitHub Apps that survive version upgrades
• Review AI-generated PRs and agent-authored config; set standards for access, integrity, observability

You bring:

• 10+ years in software/platform engineering with deep SME knowledge of Odoo, Redmine, GitHub, or similar
• Expert Ruby on Rails, production Redmine plugin experience
• Real-world agentic dev experience (MCP, LLM tooling, agent workflows)
• Strong grip on delivery/support/ops business processes

Nice to have: Python + Odoo modules, PostgreSQL, legacy modernization experience, PE-backed/SaaS scale-up background

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.

Read This Before Anything Else

We have 6 developers who can ship. What we don't have is someone who turns that into a real engineering function: real architecture, real leverage, real AI-driven advantage. If that gap sounds like an opportunity rather than a headache, you're in the right place. If it sounds like a lot of undefined work with no playbook handed to you, this one probably isn't for you. That's completely okay. There are plenty of great roles that fit differently.

About CraftMyPlate

CraftMyPlate is Hyderabad's go-to platform for food experiences for micro-events: house parties, birthdays, office celebrations, festive gatherings, and more. We're building the operating system for how India discovers, customises, and orders food for smaller events. We're backed by established founders and investors, and we're funded and growing fast. The next phase of that growth runs through engineering.

Where We Stand

Some numbers, because they matter more than adjectives. Order volume has grown 50x in two years, and we're compounding at roughly 3x year over year, without giving up equity to fund it. That means the business runs on its own economics. The growth is real demand, not runway bought with dilution, and every efficient architectural decision this role makes directly protects that.

Most people size up an opportunity by asking what's going to change in ten years. The more useful question, and the one this company is built around, is what won't change. People will keep gathering. They'll keep celebrating, hosting, and marking festivals, in 10 years and in 20. That permanence is the bet. You're not building infrastructure for a trend cycle. You're building for a category that outlasts the current AI wave, the next funding round, and probably us too.

The Technical Reality

Here's an honest read of the engineering problem, not a sanitized version of it.

Event-driven commerce doesn't scale like typical e-commerce. Demand isn't smooth, it's spiky: weekends, festival calendars, and event dates create real load concentration, and each order is tied to a hard deadline that can't slip the way a shipped package can. That has direct architectural consequences: systems need to handle bursty, unpredictable traffic without paying for idle capacity the rest of the time, which is exactly why we're serverless-first on AWS rather than running a fixed fleet sized for peak.

Underneath that, every order touches multiple systems that have to stay consistent: kitchen and vendor fulfillment status, inventory across partners, payment gateway settlement, and refunds, often in real time and often across more than one vendor for a single event. Getting that consistency right across SQL and NoSQL stores, without it becoming a source of support tickets and manual reconciliation, is a real architecture problem, not a CRUD problem.

The AI-agent layer is the next lever, and it's a business lever as much as a technical one. Every workflow we can hand to a well-orchestrated agent instead of a new hire is a workflow that scales without adding headcount, which is exactly how a company grows 3x a year without diluting equity to fund the team behind it. That's why agent orchestration across multiple LLMs, using LangGraph, sits in the "go deep" tier of this role rather than being a nice-to-have.

You'll likely find some of this framing right and some of it worth challenging once you're actually in the codebase. That's expected, and honestly preferred over someone who just nods along.

Why This Role Exists

You'll be the most senior technical person in the company, reporting directly to the founder. Not a manager brought in to run standups. An owner. You set the architecture, you write code yourself, and you make the team materially better. You also own where AI and automation take this company next, starting with our first in-house AI agent product (details shared in the interview), and expanding from there into how the company runs, department by department: HR, finance, marketing, design, development, all sitting on an engineering layer that you design.

If you've outgrown a role where you plan but don't build, or where good ideas die in a committee, this is built to be the opposite of that.

What You'll Own

• Architecture, end to end. Scalable, cost-efficient systems from day one, not "fix it later" engineering. You own the decisions and their long-term consequences.
• Hands-on building. You are still writing code and shipping. This isn't a seat where you review other people's work all day. You lead by building.
• The engineering team. Directly manage, mentor, and level up our 6 developers. Build the technical bar, the review culture, and the calibration that lets the team ship independently.
• The AI-agent roadmap. Own the architecture behind our first AI agent product, then the broader strategy for AI agents and automation across every function in the company, with engineering as the layer underneath all of it.
• Team scaling. Build the next layer of leads under you so execution quality scales without you being the bottleneck.
• Technical accountability. When something breaks, you fix it. You don't escalate and wait.

Our Stack, and the Depth We Expect

Not everything on this list needs the same level of mastery. Some of it you need to own at an architectural level. The rest you need to be strong enough to build yourself, direct the team on, or delegate to AI agents with confidence.

Go deep here. This is where the real architecture decisions live, and where the business impact is highest:

• AWS, serverless first. You should be genuinely well versed in AWS application development, not just "have used AWS." You should be able to design and guide serverless architecture (Lambda, API Gateway, DynamoDB, Step Functions, and similar) as our default way of building, because our demand curve is spiky by nature and fixed infrastructure is money left on the table.
• TypeScript, our primary language across backend and frontend.
• Agent orchestration across multiple LLMs, using LangGraph. This is core to our AI roadmap and our path to scaling operations without scaling headcount. You own how it's architected, not just how it's used.

Working proficiency. Build it yourself, direct the team, or hand it to an AI agent and know if the output is right.

This Is You If

• You've built and shipped real production systems yourself, not just reviewed other people's architecture from a distance.
• You go deep wherever the problem is, and you're comfortable owning the exact stack described above, not just "full-stack" in the abstract.
• You've made engineers around you measurably better, whether or not you've held the title for it yet.
• You're already using AI coding tools and agents seriously, like Claude, Cursor, or similar tools, as part of how you build, not as something you tried once. We'll likely explore this together in the interview.
• You have a bias toward leverage over hours. You'd rather automate or systematize a problem than grind through it. But when something's live and needs to be done right, you see it through completely, with no half-finished work.
• You want to build something for years, not land somewhere comfortable. We'll know the difference from how you talk about your last three years.

This Might Not Be the Right Fit If

• You'd prefer a stable, well-defined role with clear boundaries and someone else making the calls. That's a fair thing to want, just not what this is.
• You'd rather receive direction than bring us architecture and AI strategy yourself.
• You haven't yet gotten hands-on with AI coding tools in your daily work.
• You're drawn more to the title than the work behind it.

If none of that sounds like you, we'd love to hear from you.

Requirements

• 5 to 7 years of experience in software engineering, with real ownership of architecture-level decisions, not just feature delivery.
• Prior experience leading or mentoring engineers, formally or informally.
• Tier-1 or Tier-1+ engineering college strongly preferred (IIT, BITS, top NIT tier, or equivalent). We'll consider other institutions only with clearly commendable, verifiable work: real systems you can walk us through in depth, strong open-source contributions, or a track record that speaks for itself. Pedigree is a proxy for speed, not a checkbox. We test for the underlying ability regardless.
• Comfortable in an early-stage environment: undefined problems, few processes, and the expectation that you help define both.

Compensation

Competitive, with equity. We're formalizing a structured ESOP program alongside this hire. Specific numbers are discussed directly in later interview rounds.

If reading this got you a little excited about what you'd build here, we'd genuinely love to talk. If it didn't quite land, no hard feelings. We just want the right fit for both sides.

Supercharge Your Career as a Principal Lead Developer at Technoidentity!

At Technoidentity, we're a Data & AI product engineering company with over 15 years of expertise in building durable digital products, intelligent enterprise solutions, and scalable Data & AI platforms. As we continue expanding globally, it's the perfect time to join our team of tech innovators and make a lasting impact.

What’s in it for You?

Technoidentity is building a high-impact Temporal Capability Center to design, deliver, and scale resilient workflow-orchestration solutions for enterprise customers. We are seeking a hands-on, technically strong Principal Lead Developer who combines deep software-engineering expertise with solution-architecture leadership, distributed-systems knowledge, and an ownership mindset.

This role is suited to a resourceful engineer who can independently take multi-faceted business and technical requirements from discovery through design, implementation, rollout, and operational improvement. You will work directly with overseas clients, shape architecture decisions, lead multiple technical workstreams, and mentor junior developers while remaining actively involved in code, design reviews, and delivery.

The ideal candidate has strong practical experience in Python, Java, and/or TypeScript, has experience with Cloud Platforms, understands modern AI-assisted engineering practices. Experience with distributed workflow solutions using orchestration platforms such as Temporal, Cadence, Camunda, or similar technologies will be preferred, but is not a requirement.

Requirements

What Will You Be Doing?

• Lead the end-to-end technical delivery of workflow-orchestration and distributed-systems solutions for enterprise clients.
• Design robust, scalable, secure, and observable architectures using durable execution, asynchronous messaging, APIs, event-driven patterns, and cloud-native components.
• Build production-grade services and workflow implementations using Python, Java, and/or TypeScript.
• Design and implement long-running business processes using orchestration frameworks such as Temporal, Cadence, Camunda, or equivalent platforms.
• Apply distributed-systems principles to address reliability, idempotency, retries, timeouts, compensating transactions, eventual consistency, failure recovery, and data consistency.
• Design and implement Saga patterns, including orchestration-based and choreography-based approaches, for multi-service business transactions.
• Lead architecture discovery sessions, technical workshops, solution presentations, and design reviews with overseas clients and internal stakeholders.
• Translate business requirements into clear solution architectures, implementation plans, technical specifications, estimates, and delivery milestones.
• Drive multiple concurrent technical streams, identify dependencies and risks early, and maintain delivery quality under changing priorities.
• Establish engineering standards for workflow design, API contracts, error handling, versioning, testing, deployment, observability, and operational readiness.
• Use AI-assisted SDLC practices responsibly to improve developer productivity, code quality, test coverage, documentation, and delivery velocity.
• Design and contribute to agentic orchestration solutions, including coordination of AI agents, tool/API integrations, workflow state management, guardrails, human-in-the-loop controls, and evaluation approaches where relevant.
• Perform hands-on development of critical components, prototypes, integrations, and reference implementations.
• Conduct code reviews and architectural reviews, ensuring solutions are maintainable, performant, secure, and aligned with engineering best practices.
• Mentor and guide junior developers; support technical growth through pairing, reviews, reusable patterns, technical sessions, and constructive feedback.
• Collaborate with delivery, product, platform, QA, DevOps, security, and client teams to ensure successful implementation and production adoption.
• Contribute reusable assets, accelerators, templates, documentation, and best practices to the Temporal Capability Center.

Benefits

What Makes You the Perfect Fit?

• Bachelor’s or Master’s degree in Computer Science, Engineering, or a related technical discipline, with 6+ years of relevant work experience.
• Significant professional software-development experience, including experience leading technical delivery and mentoring engineering teams.
• Strong hands-on proficiency in at least one of the following languages:

o  Python

o  Java

o  TypeScript

• Demonstrated experience designing and building distributed, scalable, highly available, or event-driven systems.
• Strong understanding of microservices architecture, REST and/or asynchronous APIs, message-driven systems, and integration patterns.
• Practical expertise with distributed-systems concerns, including:

o  Idempotency and duplicate-message handling

o  Retries, backoff, timeouts, and circuit-breaking strategies

o  Failure handling and recovery

o  Eventual consistency and data synchronization

o  State management for long-running processes

o  Observability, logging, metrics, tracing, and operational debugging

• Strong understanding and practical application of the Saga pattern and compensating-transaction design.
• Experience designing solution architectures and communicating technical trade-offs to both engineering and business stakeholders.
• Ability to lead junior developers through technical direction, task decomposition, code review, and mentorship.
• Strong written and verbal communication skills in English.
• High ownership, self-motivation, adaptability, and the ability to make sound decisions in ambiguous and fast-moving environments.

Preferred Qualifications

• Production experience with Temporal, Cadence, Camunda, AWS Step Functions, Azure Durable Functions, Netflix Conductor, Apache Airflow, or comparable orchestration technologies..
• Experience migrating from legacy schedulers, BPM platforms, or synchronous microservice flows to durable workflow orchestration.
• Experience building agentic or AI-enabled applications using LLMs, tool calling, agent frameworks, retrieval-augmented generation, MCP, guardrails, or evaluation frameworks.
• Practical use of AI coding assistants and AI-aided SDLC workflows for planning, implementation, testing, code review, documentation, and troubleshooting.
• Cloud-native development experience on AWS, Azure, Google Cloud Platform, or a hybrid-cloud environment.
• Experience with Kubernetes, Docker, CI/CD pipelines, Infrastructure as Code, and container-based deployments.
• Experience with event-streaming and messaging platforms such as Kafka, RabbitMQ, cloud queues, or pub/sub systems.
• Experience with relational and NoSQL databases, data-modeling strategies, and transactional/outbox patterns.
• Experience with API gateways, security controls, OAuth/OIDC, secrets management, and secure service-to-service communication.
• Familiarity with domain-driven design, event sourcing, CQRS, and enterprise integration patterns.
• Experience in technical consulting, pre-sales support, solution accelerators, or client-facing technical leadership.

Leadership Expectations

As a Principal Lead Developer, you will be expected to:

• Act as a trusted technical advisor to clients and internal delivery teams.
• Balance architecture leadership with hands-on engineering execution.
• Proactively identify problems, propose practical solutions, and drive them to completion without waiting for detailed direction.
• Manage and prioritize several workstreams while communicating progress, risks, decisions, and dependencies clearly.
• Raise engineering quality through reusable standards, design patterns, code reviews, and mentoring.
• Build confidence with clients through technical depth, clarity, responsiveness, and reliable delivery.
• Foster a collaborative, accountable, learning-oriented engineering culture within the Temporal Capability Center.

Success Measures

Success in this role will be measured by:

• Delivery of reliable, scalable, and maintainable orchestration solutions that solve real client problems.
• Quality of solution architecture, code, technical documentation, and operational readiness.
• Effective application of workflow-orchestration and Saga patterns to complex distributed business processes.
• Ability to independently lead client-facing technical discussions and turn them into executable delivery plans.
• Delivery predictability across multiple concurrent technical initiatives.
• Measurable improvement in engineering productivity and quality through AI-assisted SDLC practices.
• Growth, engagement, and technical effectiveness of junior developers under your guidance.
• Contribution of reusable Temporal Capability Center assets, reference architectures, and best practices.

Why Join Technoidentity’s Temporal Capability Center?

• Work on complex, high-value enterprise workflow and distributed-systems challenges.
• Help shape a specialized capability center focused on durable execution, orchestration, AI-enabled delivery, and modern architecture.
• Collaborate with overseas clients and multidisciplinary global teams.
• Influence technical standards, reusable accelerators, and the future direction of orchestration solutions at Technoidentity.
• Take on a role with meaningful architecture ownership, technical leadership, and hands-on engineering impact.

Key Skills:

• Agentic AI / AI Agents

• Python or Java

• LLMs & Generative AI

• RAG & Vector Databases

• LangChain / LangGraph / AutoGen / CrewAI

• REST APIs & Microservices

• Prompt Engineering

• AI Workflow Automation

Roles & Responsibilities:

• Design and develop AI agents and agentic workflows

• Build scalable backend services using Python or Java

• Integrate LLMs, APIs, tools, and external systems into AI workflows

• Develop RAG-based solutions and intelligent automation

• Design multi-step AI workflows with tool/function calling

• Evaluate, monitor, and optimize AI agent performance

• Collaborate with engineering and product teams to deliver production-ready AI solutions

Forward-deployed engineers (FDEs) are Mactores' services layer. You embed with the customer's team, own outcomes from discovery through the production cutover, and personally carry the delivery commitment.

The agent platform we deploy absorbs 60–70% of engagement work, discovery, assessment, design, and testing. You absorb the judgment: target architecture, refactoring trade-offs, model selection, cutover strategy, and the decisions an agent platform cannot make. The agent absorbs scale. You absorb judgment. 

This is not a staff-augmentation seat and not an advisory role. You ship.

What you will do?

• Deliver production agentic AI systems and AWS modernization engagements on committed dates across three pillars: Data Platform Modernization, Application & Database Modernization, and AI Agents for Apps.
• Build and productionize AI agents, orchestration, retrieval pipelines, evaluation harnesses, observability running against real customer data, not demo data.
• Convert existing products into agents: expose product functionality as callable tools for agent-to-agent composition, or replace form-and-click UX with agent-native, intent-driven interfaces.
• Convert existing Business processes into agents: expose process functionality as callable tools for agent-to-agent composition, or replace form-and-click UX with agent-native, intent-driven interfaces.
• Embed directly with customer engineering teams. Run architecture sessions, defend design decisions, and align stakeholders from VP Engineering to CTO.
• Make agent decisions traceable and defensible, validation runs in parallel with live workloads, and outputs hold up to internal audit and regulators (HIPAA, PCI-DSS, FSI-grade governance where the vertical demands it).
• Feed field experience back into the platform and practice: your deployment patterns, integration playbooks, and edge cases shape how we deliver.

What are we looking for?

• Excellent communication skills (English) — verbal and written. Non-negotiable. You will present architecture to customer CTOs, write documents that hold up in audit, and defend judgment calls in the room. If you can build but not explain, this role is not a fit.
• You have shipped production agentic AI systems on AWS. Not POCs, not notebooks — systems running in production for real users. This is the primary qualification. Be prepared to walk through what you shipped, the decisions you made, and what broke.
• Deep understanding of agentic architecture — you can design an agent system from first principles and explain why each component exists:
• Agent design patterns: single-agent vs. multi-agent systems, supervisor/orchestrator patterns, hierarchical agent topologies, planner–executor separation, and when each applies.
• Orchestration: building and operating orchestrator agents that decompose tasks, route work to specialist agents or tools, and manage state across multi-step workflows (LangGraph, Strands Agents, CrewAI, or equivalent).
• Memory: short-term/working memory (context management, conversation state) and long-term memory (episodic and semantic stores, vector- and graph-backed retrieval), and the production trade-offs of each.
• Reflection and self-correction: critique loops, self-evaluation, retry-with-feedback patterns, and evaluation harnesses that catch agent failures before customers do.
• Tool use and function calling: schema design, tool-selection reliability, error handling, and agent-to-agent composition.
• RAG and retrieval pipelines: chunking, embedding, hybrid retrieval, reranking, and grounding agent decisions in customer data.
• Strong AWS production experience: Amazon Bedrock and AWS AI services, plus core platform services (Lambda, API Gateway, DynamoDB, RDS/Aurora, Glue, EMR, Redshift, Kinesis, or similar depending on specialization).
• Solid software engineering fundamentals Python, TypeScript, CI/CD, infrastructure-as-code, testing-driven development discipline.
• Experience with data or application modernization (database migration, legacy refactoring, data platform builds) is a strong plus, since agents run against these workloads.
• Indicative experience: roughly 3–10 years in engineering roles, with agentic AI / GenAI as your current day job. We have demonstrated agent-native expertise over tenure — an engineer with 3–4 years of hands-on agentic AI work typically outperforms a 12-year generalist on this work.

You'll be preferred if you've:

• US English verbal and written fluency 
• Delivery experience in one or more of our verticals: Financial Services, Healthcare & Life Sciences, Internet & Software, Manufacturing, or Telco/Media/Entertainment/Gaming/Sports.
• Model tuning and fine-tuning: systematic prompt engineering and optimization; parameter-efficient fine-tuning (LoRA/QLoRA or similar); instruction tuning; working knowledge of RLHF/DPO; sound judgment on when to fine-tune vs. prompt vs. RAG; and evaluation of tuned models against baselines. Fine-tuning experience on Amazon Bedrock or SageMaker is a plus.
• Experience with compliance-sensitive AI systems (HIPAA, PCI-DSS, SOC 2, data residency).
• Knowledge graph, code-analysis (AST), or CDC/streaming experience (Debezium, Kafka/MSK).
• Solid software engineering fundamentals — Java, C++, Go Lang, .Net, Rust
• Prior customer-facing consulting or forward-deployed experience.
• AWS certifications (Solutions Architect Professional, Machine Learning Specialty, or Data Analytics).

Why This Role?

• You own outcomes, not tickets. FDEs carry the delivery commitment personally — architecture, judgment, and cutover are yours.
• You work agent-native from day one. Our delivery model would not function without agents. You build with the platform, not around it.
• You ship. Engagements measured in weeks to production, legacy retired, outcomes named. No archived pilots.
• You compound. Field delivery informs the Aedeon platform roadmap; the platform's growth expands what you can deliver. Few engineering roles sit in that loop.