What used to take a team weeks now ships in days. The repo replaces the wiki.
Code is cheap. Judgment, taste, and verification are the new constraints.
Engineer types; the tool suggests the next line. Faster typing, same job, same SDLC.
Engineer chats with the model inside the IDE. Pair-programmed features, debugging, code exploration. Cycle weeks → days.
Engineer briefs an agent; the agent plans, codes, tests, and ships. Engineer steers, reviews, and owns the outcome.
Three stages, four years. Each shift redefined what the engineer actually does — and compressed the cycle from weeks to days.
Engineer types every line. Tool suggests function templates and the next-line completion.
Treated as table-stakes. No engineering team turns it off; no team builds a feature around it.
Engineer chats with the model in the IDE. Pair-programs features, debugs, explores unfamiliar code.
Standard daily workflow on Cursor, Claude Code, and Codex across Fynd. Cycle for routine features compresses from weeks to days.
Engineer briefs an agent with a problem statement. Agent plans, writes the code, runs the tests, opens the PR. Engineer steers, reviews, and owns the outcome.
A single engineer + an AI coding agent built HireFirst end-to-end in under 3 days.
A single engineer + an agent can now ship what previously took a feature team weeks. The constraint is no longer headcount — it is the clarity of the brief and the strength of the verification step.
Issued to all of Product Engineering — Dev, PM, Program, QA. Repos, knowledge hubs, agent design, team shape, role boundaries, QA automation, architecture restraint, curiosity.
All microservices for a product live in one Git repo. Long-term target: ~25 repos for the entire company. Microservices architecture preserved — the change is purely at the code-repo level.
PMs contribute at SDE-1 level with AI assist; designers ship UI/UX changes directly.
All docs, skills, rules, hooks, runtime versions live inside the repo under /docs. Markdown by default. No more scattered Quip docs, Jira tickets, or PDFs.
The repo becomes the indexed knowledge base for Cursor and Claude Code. QA, Program, and Product query the codebase directly instead of routing through engineers.
CRUD is now the "hello world" prompt — anyone with clear English can generate a CRUD app in under an hour. Engineering attention shifts to autonomous systems that reason, decide, and act.
Build on LangGraph, OpenAI Agents, CrewAI. Don't reinvent agent infrastructure.
No more frontend / backend / OMS silos. One team owns a feature end-to-end: problem definition, design, development, integration, testing, release, post-launch impact.
End-to-end ownership. Clear accountability. Real outcomes.
Boundaries between Dev, QA, PM, and Program are dissolving. AI lowered the barrier to execution across frontend, backend, testing, automation, documentation.
PMs and Program Managers prototype with AI. Engineers engage directly with customers and shape solutions, not just implement tickets.
Generating code is no longer a scarce skill. Scarce: clarity of thought, strong judgment, deep problem understanding, the ability to move fast with conviction.
Either expand the role beyond defined boundaries, or specialise in problems AI cannot easily solve — deep performance engineering, advanced security analysis, large-scale architecture, complex domain challenges built on non-public knowledge.
Quality engineer becomes Quality + automation engineer. Automation that used to take weeks now takes 15 minutes with AI.
Building has become easy; verification is still the unsolved phase of SDLC. Manual-only work is counterproductive.
No Kafka or Redis on new projects without real scale. Speed and clarity beat architectural sophistication in early stages.
Optimise fundamentals first — if database indexes aren't tuned, adding Redis just masks inefficiency. Complexity is earned, not assumed.
Same argument once said washing machines would make us forget how to wash clothes by hand. The outcome and the value matter, not the manual effort behind it.
Most systems aren't written in Assembly or C any more, despite their efficiency. AI is the next step in the same evolution. At core, the work is problem-solving; code is a tool.
AI is endlessly patient and available 24/7. The fastest way to close a knowledge gap is to ask, not to pretend or to spend hours searching.
Learning runs both ways: as people ask AI questions, they teach it their codebase, product, and constraints. The people who grow fastest are the ones who keep asking until they truly understand.
One repo per product. Frontend, backend, QA, SRE, UI/UX, DevOps, security, docs — what used to be eight teams with eight stacks now live as skills inside the repo. Any engineer or agent invokes any skill.
Two internal surveys, 1,168 responses four months apart. The numbers below are the baseline pulse. The HireFirst proof point is the existence proof.
Prompted by an MM Sir WhatsApp message describing the platform. Live on SIT today; production sign-off targeted 15-Jun-2026 (RIL HR Tech). Five capabilities wired end-to-end across JD creation, sourcing, screening, interview design, and final decision support.
HireFirst is one platform built this way. The target for Fynd Engineering itself: L5 on the autonomy framework — a fully autonomous SDLC. Engineer sets intent. Agents plan, code, test, ship. Humans intervene only at the boundary.