Fractional Technical Steward - T Nagar, Chennai, Tamil Nadu

Company Overview · Atman Artificial Intelligence FZCO is a Dubai-based Hybrid Digital Company operating under a governance-first model. The company builds AI-driven products through a controlled execution framework (AI Factory), while maintaining strict authority boundaries and i ...

Job description

1. Company Overview

Atman Artificial Intelligence FZCO is a Dubai-based Hybrid Digital Company operating under a governance-first model. The company builds AI-driven products through a controlled execution framework (AI Factory), while maintaining strict authority boundaries and irreversible decision controls.

The company operates remotely under structured governance discipline. All irreversible actions (money, contracts, production releases, access grants, hiring offers) require explicit Founder approval.

The Technical Steward is responsible for protecting the integrity, safety, and long-term stability of the technical foundation.

1. Role Summary

Title: Fractional Technical Steward (CTO-Type)

Type: Fractional / Contract (20–30 hours per week initially)

Reports To: Founder

Works Closely With: Execution Operator

Location: Remote

Contract Duration: Initial 3–6 months, renewable based on performance

1. Role Purpose

The Technical Steward protects engineering integrity.

This role ensures:

· No unsafe code reaches production

· No uncontrolled dependency changes occur

· No irreversible technical action bypasses governance

· The canonical repository remains clean and coherent

· Technical decisions align with long-term architecture

This role does NOT:

· Define product vision independently

· Ship releases without approval

· Grant production access without governance

· Perform large-scale refactors without scope approval

· Override governance rails

The Technical Steward is the structural engineer of the company.

1. Core Objectives (First 90 Days)

Within 90 days, the Technical Steward must:

1. Protect the canonical repository (no direct pushes to main).

2. Enforce mandatory pull request review discipline.

3. Block unsafe dependency drift.

4. Ensure no production release occurs without DecisionID.

5. Establish clear branching and CI discipline.

6. Begin ANIMA backend skeleton under structured architecture.

Failure to achieve these indicates role misalignment.

1. Detailed ResponsibilitiesA. Repository Governance

· Enforce protected main branch.

· Require pull request reviews before merge.

· Block direct commits to production branches.

· Ensure all merges are traceable.

Definition: Canonical Repository = Official source-of-truth codebase controlled by FZCO.

B. Dependency & Environment Control

· Review all dependency changes.

· Block lockfile drift unless justified.

· Prevent unauthorized environment configuration changes.

· Maintain predictable development environments.

Definition: Dependency Drift = Silent or uncontrolled change in external libraries or versions.

C. Release Governance

· Ensure no production deployment without DecisionID.

· Verify commit hashes before release.

· Maintain rollback procedures.

· Validate release notes and test coverage.

Definition: Irreversible Technical Action = Production deploy, database migration, infrastructure modification.

D. Access Control

· Maintain least-privilege access discipline.

· Approve or deny engineering access requests.

· Maintain access logs.

· Revoke access within defined timeframe upon exit.

Definition: Least Privilege = Minimum required access for role function.

E. Architecture Integrity

· Review major technical proposals.

· Prevent unapproved large-scale refactors.

· Ensure modular, scalable architecture.

· Align backend skeleton to long-term roadmap.

F. Engineering Reporting

· Provide weekly engineering update for Executive Brief.

· Identify technical risks.

· Flag governance violations.

1. KPIs (Quantifiable Metrics)

· 0 unauthorized production deployments

· 0 dependency drift incidents without review

· 100% PR review compliance

· Stable CI/CD pipeline

· Rollback readiness verified

· Clean repository audit trail

1. Tools & Systems Used

· GitHub / GitLab

· CI/CD pipelines

· Branch protection rules

· Cloud infrastructure dashboard

· Code review tools

Must be comfortable operating structured version control environments.

1. Required QualificationsMandatory

· 5+ years backend engineering experience

· Experience with repository governance

· Strong understanding of CI/CD discipline

· Experience enforcing engineering process

· Clear written communication

Preferred

· Experience in early-stage startups

· Exposure to AI or distributed systems

· Familiarity with compliance-driven engineering environments

1. Behavioral Profile

Ideal candidate:

· Calm under pressure

· Highly disciplined

· Technically conservative

· Strong reviewer mindset

· Comfortable blocking unsafe changes

Not suitable for:

· Experimental hackers

· Rapid-refactor enthusiasts

· High-risk builders

· Engineers who bypass process

1. Authority Boundaries (Non-Negotiable)

Technical Steward MUST NOT:

· Deploy to production without DecisionID

· Grant unrestricted access

· Perform large refactors without scope approval

· Override governance rules

· Commit directly to protected branches

Violation may result in immediate termination.

1. 30–60–90 Day Performance PlanFirst 30 Days

· Protect main branch

· Establish PR discipline

· Validate CI/CD pipeline

· Begin ANIMA backend scaffold

60 Days

· Stable release workflow

· Dependency discipline proven

· Rollback procedure documented

90 Days

· Engineering cadence predictable

· Zero governance bypass

· Architecture foundation stable

1. Compensation Structure

· Monthly retainer (market-aligned)

· Performance incentive tied to technical stability

· No automatic equity in Phase 1

1. Reporting & Review

· Weekly sync with Founder

· Weekly coordination with Execution Operator

· 30-day review

· 60-day review

· 90-day performance assessment

1. Confidentiality & Compliance

· NDA required before access

· IP assignment mandatory

· Strict credential handling discipline

· No external code sharing without authorization

1. Summary

The Fractional Technical Steward ensures technical stability, security, and discipline.

They protect the engineering foundation. They do not hold financial authority. They enforce structural integrity.

Without this role, technical governance collapses.

Job Type: Full-time

Pay: ₹150, ₹250,000.00 per month

Benefits:

• Health insurance

Work Location: Hybrid remote in T Nagar, Chennai, Tamil Nadu