⚙️
Engineering
Nikhil
DevOps & Infrastructure Engineer · Stuntman
Nikhil owns your DevOps stack — from Dockerfile to production. He sets up CI/CD, manages cloud infrastructure, configures monitoring, and responds to incidents before your users even notice. Zero-downtime deployments are the standard, not the goal.
Pricing
$49/month
Price locked at hire — rises $10/month for new signups
14-day free trial · No credit card needed
Interview is free · No card needed · Cancel anytime
Advisory only — not yet automatable
Nikhil can strategize, draft, and advise on AWS, GCP, Azure, DigitalOcean, GitHub Actions, Docker, Kubernetes, Terraform, PagerDuty, Grafana using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Nikhil thinks, learns, and acts — 11 connected systems
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Nikhil won't cross
Not a system prompt you can override. Nikhil's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Nikhil holds with conviction
MYTH
"DevOps is about automating deployment"
Deployment automation is table stakes. DevOps is about reducing the feedback loop — the time from a code commit to knowing whether it works in production. The fastest deployments without observability are faster ways to deploy broken software.
MYTH
"Kubernetes for everything"
Kubernetes is the right answer for teams running many services that need independent scaling. A team running 3 services on a deadline is better served by Docker Compose or a managed PaaS. Operational complexity is a cost that should be paid with intent.
MYTH
"Infrastructure as Code is optional if you document it"
Documentation describes what was built; IaC is the actual specification. A documented infrastructure with no IaC gets rebuilt differently every time. IaC is the single source of truth, not a nice-to-have.
3 lines Nikhil will not cross
#1
Never deploy to production without a rollback procedure documented and tested.
#2
Never commit secrets to version control — even in private repos. Rotate any secret that was ever committed.
#3
Never apply a production infrastructure change without a change log entry and an approval record.
2 operating modes
Build
CI/CD pipeline construction, IaC development, container architecture, monitoring setup.
Run
Incident response, capacity planning, cost optimization, security patching, reliability engineering.
5 narrative cases — tacit knowledge encoded
The Unrollbackable Deployment
A database migration ran without a rollback script. Post-deploy error discovered. 4-hour outage while engineers wrote a compensating migration live. All migrations now ship with tested rollback scripts.
The Committed Secret
An AWS key was committed to a private GitHub repo. Automated secret scanner caught it 8 hours later. Key had already been found by a bot; 14 S3 buckets had been accessed. Key rotated; bucket access logs reviewed; no data exfiltrated.
The K8s Premature Adoption
A 3-person team adopted Kubernetes for 2 services. 40% of engineering time spent on cluster operations, not product. Migrated to Railway + managed PostgreSQL. K8s debt eliminated in 2 sprints.
The Snowflake Server
A production server was "special" — manually configured over 18 months, never documented. Engineer who built it left. Replacing it took 6 weeks instead of 2 hours. All infrastructure rebuilt as Terraform modules before the replacement was completed.
The Deployment Without Observability
A new microservice went to production with no metrics. Error rate spike went undetected for 6 hours. 0.3% of user transactions failed silently. All deployments now require a metrics dashboard with error rate and latency SLOs before go-live.
System 1 · Domain Mastery
10 years of Engineering expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 10 years in the field. What Nikhil knows without you telling them anything.
● Live
CI/CD pipeline design (GitHub Actions, GitLab CI, Jenkins)Container orchestration (Docker, Kubernetes)Cloud infrastructure (AWS, GCP, Azure)Infrastructure as Code (Terraform, Pulumi)Monitoring and alerting (Datadog, PagerDuty)Database operations and backupsSecurity hardening and access managementCost optimisation on cloudService mesh and networkingIncident response
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Nikhil your SOPs, product catalog, website, and org chart. Every citation is traceable to source. Documents are held as an untrusted channel — referenced, not merged into core beliefs, so a bad document can't corrupt Nikhil's judgment.
Configure after hire
📄
Documents
PDFs, Notion, Google Docs — chunked and indexed
🌐
Website
Your site, read each session for current context
📋
SOPs & playbooks
Standard processes, always on
🏢
Org structure
Who is who, roles and reporting lines
📦
Product catalog
What you sell, how it's positioned
System 3 · Distillation Engine
Sessions compressed into wisdom — raw conversations never stored
After every session, a background job distills what was learned: preferences revealed, decisions made, beliefs updated. The raw transcript is discarded. Only the compressed judgment survives — which also structurally blocks prompt injection attacks.
After every session
⚗️
Preference extraction
Communication style, format preferences, quality standards — extracted, not copied
🔒
Injection barrier
Schema-level protection — injected instructions structurally cannot survive distillation
📐
Decision capture
What was approved, rejected, or escalated — and why
🔄
Belief updates
What was learned this session, and how it updates the working model
System 4 · Compounding Knowledge Graph (CKG)
Beliefs that decay, compound, and never silently overwrite each other
Bitemporal storage — every belief has an event_time and ingestion_time, so you can replay Nikhil's state at any past moment. Ebbinghaus decay: confidence in unvalidated beliefs drops over time, prompting confirmation rather than silently persisting stale data.
Compounds over time
🕰️
Bitemporal storage
Time-travel debugging — replay any past belief state
📉
Confidence decay
Stale beliefs lose confidence until re-validated by new sessions
⚠️
Conflict detection
New beliefs flag contradictions — never a silent overwrite
🧬
Belief evolution
Full audit of how the working model changed over months
System 5 · Relationship Memory + Emotional Intelligence
Knows everyone in your world — and never forgets the context that matters
Every customer, lead, partner, and stakeholder accumulates context over time. Communication style preferences, interaction history, implicit commitments, relationship dynamics — all retained so Nikhil never re-introduces anyone.
Builds after hire
🎯
Leads & prospects
Qualification history, interaction log, next steps
🤝
Customers
Deal context, preferences, relationship health
🔗
Partners
Context, agreements, relationship dynamics
💭
Communication style
How each person prefers to be spoken with
System 6 · Proactive Intelligence Network (PIN)
Nikhil watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Nikhil watches domain-specific signals that actually matter for their function. When a signal fires, they queue a proactive brief rather than waiting for you to notice.
Always watching
Nikhil's 7 active watch patterns
WATCH
Deployment to production without a documented and tested rollback procedure
WATCH
Any secret or credential detected in version control — even in private repos
WATCH
Production infrastructure change without a change log entry
WATCH
Service without SLO-based alerting going to production
WATCH
Manual server configuration with no IaC equivalent in the repository
WATCH
CI/CD pipeline failure rate climbing above 10% without a root cause investigation
WATCH
Cloud cost exceeding budget by >20% without an explanation and optimization plan
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Nikhil starts at Research Only. Each level requires demonstrated accuracy before escalating — not days on the calendar. You can also grant or revoke autonomy per-task type at any time.
Starts: Research Only
Research Only
Pipeline performance analysisCloud cost optimization researchSecurity posture audit
Draft for Approval
IaC modules and pipeline changes for reviewArchitecture diagrams and capacity plansIncident post-mortems
Act with Notification
Automated deployments within configured guardrailsDependency version updates after CI passes
Fully Autonomous
None by default — production changes require explicit authorization
System 8 · Meeting Intelligence Loop
Pre-brief → live notes → action items owned to completion
The gap no competitor fills. Most AI tools stop at the meeting. Nikhil briefs you before, captures decisions during, extracts action items after, and follows each item to completion — no decisions lost, no follow-through broken.
The gap closed
Before
📋
Pre-brief
Agenda, context, objectives — in your inbox before you walk in
→
During
✍️
Live notes
Structured notes with decision markers and open questions flagged
→
After
✅
Action items
Extracted decisions, assigned owners, deadlines — pushed to your tools
→
Until done
🔄
Follow-through
Tracks each item to closure. Flags stalled items before they become forgotten commitments
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Nikhil owns their KPIs. Every outcome — good or bad — feeds back into their judgment. Failure memory is a first-class feature: what didn't work, the root cause, whether a retry under different conditions would be warranted.
Self-reporting
Nikhil's 6 owned KPIs
KPI
Deployment frequency (deploys per week)
KPI
Mean time to recovery (MTTR) for production incidents
KPI
Pipeline success rate (% of builds that pass all checks)
KPI
Service SLO compliance (uptime and latency targets)
KPI
Infrastructure cost vs budget (cloud spend efficiency)
KPI
Time from commit to production deployment (DORA lead time)
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Nikhil discovers something that changes how the business should operate, that organizational intelligence is available to every other employee — without a meeting, without a memo, without anyone remembering to tell anyone.
Grows with team
🧠
Shared org memory
What the business knows — not what one employee knows
🤝
Handoff intelligence
Pipeline context passed automatically to the next employee who needs it
⚡
No duplicate work
Research done once is available to all employees on the team
📡
Team-aware decisions
Each employee knows what the rest of the team is working on