Senior · Technology

IT Lead & Tech Manager Training That Fuses Human Leadership, Engineering Discipline, and Risk Governance

Q: Is the program suited to Engineering Managers freshly promoted from Senior Engineer?

Yes — most of our cohort participants are Engineering Managers with 3–18 months of tenure. The program calibrates so foundational leadership material (1-on-1, GROW, delegation) gets covered, while still delivering the DORA, SRE, and DevSecOps rigour the senior role demands.

Q: How does this program differ from technical certifications such as AWS or Kubernetes?

Technical certifications focus on 'how the technology works'. This program focuses on 'how to lead a team that uses the technology' — DORA metrics, SLO/SLI, blameless post-mortem, threat modeling, career ladder, and service governance. The two are complementary; many of our participants already hold vendor certifications.

Q: Can it run for a single Engineering Manager?

For a single participant we recommend hour-based embedded coaching (a separate package). The core cohort benefits — peer-coaching with Engineering Managers from different domains, live blameless post-mortem between participants, and joint thematic workshops — need a minimum of 6 participants. The sweet spot is 8–14 managers per cohort.

Q: Can Neksus tailor the modules for banking / BUMN contexts with tight regulation?

Yes. The ITIL 4 and COBIT 2019 governance module is always mapped to the audit framework that applies to the client's sector (POJK for banking, Kominfo regulations for telecommunications, BPK audits for BUMN). Our senior facilitators carry direct external-audit experience in those sectors.

Q: Is the training certified?

A Neksus participation certificate is available to every participant who completes the capstone (available on request). International certifications such as ITIL 4 Foundation/Managing Professional, AWS Certified Solutions Architect, or ICF ACC/PCC are examined and issued directly by the bodies that own them, and this program gives participants a footing if they choose to sit for them.

Q: What is the typical investment for a cohort of 12 Engineering Managers?

The DORA instrumentation lab is the most decisive component: the deeper it reaches into your deployment pipeline and incident data, the larger its share of the design. Cohort length, in-person or online sessions, and audit readiness or FinOps modules add to it. Sessions for 12 Engineering Managers are scheduled outside major releases and on-call rotations. Standard gives every manager one way to measure lead time and change failure rate, Premium brings a senior facilitator into labs built on your data, and Private 1-on-1 suits a VP Engineering or CTO reshaping the technology organization. Please bring the engineering development budget to our 60-minute scoping call.

Q: How does Neksus measure program impact?

The full Kirkpatrick 4-level framework with engineering-specific KPIs: L1 satisfaction, L2 competency (DORA + NIST CSF + ITIL 4 pre/post assessment), L3 behavior (peer and subordinate feedback at 3 months), L4 impact (four DORA metrics, SLO compliance, MTTR, engineer churn — measured at 6 months against the baseline instrumented in Weeks 2–4). Details confirmed during scoping.

Q: Does the CIO / CTO need to join sessions?

The CIO/CTO skips the cohort sessions and joins the mid-program check-in (60 minutes, Week 7) and the capstone presentation (Week 13). With this engagement, program impact typically rises substantially since the 90-day participant plans receive direct technology-board support.

Q: What happens if an Engineering Manager resigns mid-program?

Financial consequences follow the contract terms (typically no per-participant refund since cohort costs are pre-blocked plus the client-specific instrumentation lab). Mitigation: select participants with at least 18 months of remaining tenure post-program; include a performance-plan clause when low engagement surfaces in pre-assessment.

Q: Can Neksus help after an external IT audit finds engineering-practice issues?

Yes. We offer an 'Audit Remediation for Engineering Org' engagement — mapping auditor findings to the ITIL 4 + COBIT 2019 frameworks, designing a remediation plan with timeline and owner, and providing 90-day implementation accompaniment. This engagement often becomes the entry point into a full engineering leadership cohort.

A modern tech manager carries three loads at once: delivery rhythm (DORA), system health (SRE / error budget), and security governance (DevSecOps, NIST CSF 2.0). The Neksus 10–14 week program builds integrated competencies for IT Leads, Engineering Managers, and Heads of Engineering across enterprise, banking, BUMN, and tech-enabled organizations.

4.9/5 · 287 reviews
300+ clients nationwide
2,000+ trainers
1 to hundreds of participants
Standard · Premium · Private 1-on-1

Target audience: Tech Lead · Engineering Manager · IT Lead · Head of EngineeringTarget audience
Typical duration: 10–14 weeks (cohort)Typical duration
Core focus: DORA · SRE · DevSecOps · ITIL 4 · LeadershipCore focus
Format: Hybrid: workshop, lab, peer-coachingFormat

2,000+ trainers and experts

Our group's teaching network, matched to what your team needs.

See class documentation

You see your trainer first

The trainer's profile, track record and field come with the proposal, before you decide.

4.9 out of 5

287 participant reviews.

300+ clients nationwide and 180,000+ private training sessions completed. Among them: MPR RI, Akademi Militer Magelang, DPRD Provinsi Jawa Timur.

One person to hundreds

Private coaching for one participant, a class for one team, or several cohorts at once.

Three budget levels

Standard: core class, material fitted to the participants’ work
Premium: senior trainer, deeper material design
Private 1-on-1: one participant, one trainer, schedule set by the participant

Tell us your budget

Quick answer

The Neksus IT Lead / Tech Manager program builds five foundations: context-driven engineering team leadership, delivery rhythm using the four DORA metrics (Forsgren-Humble-Kim Accelerate), Google SRE reliability discipline with SLO/SLI/error budget, a DevSecOps security posture aligned to NIST CSF 2.0, and ITIL 4 service governance. Delivered as a 10–14 week cohort with workshops, hands-on lab in the client's stack, and weekly peer-coaching.

Role Context

Why the modern IT Lead carries a different load from the waterfall era

The Engineering Manager and IT Lead roles in Indonesian enterprises have shifted sharply since cloud and microservices adoption. Accelerate research (Forsgren, Humble, Kim) shows high-performing engineering organizations ship 208x more frequently with 106x shorter lead times and 2604x faster recovery than low-performing peers. The distinguishing factor is measured cultural-technical discipline; team size becomes secondary. A modern IT Lead owns the four DORA metrics (deployment frequency, lead time, change failure rate, MTTR), the team's error budget, the DevSecOps security posture, and ITIL 4 service governance — while still leading humans. The Neksus program integrates all five domains in a single cohort, with hands-on lab on the client's stack and practice on real team KPIs.

Accelerate (Forsgren-Humble-Kim) proves the four DORA metrics correlate directly with business performance and engineer satisfaction
Google SRE introduced the error budget — a measured failure allowance that balances delivery against reliability
NIST Cybersecurity Framework 2.0 (February 2024) adds a Govern function alongside Identify-Protect-Detect-Respond-Recover
ISO/IEC 20000-1:2018 and the ITIL 4 Service Value System are the reference frames for IT service governance in enterprise and BUMN contexts
OWASP Top 10 (2021 release) is the application security literacy baseline for every engineering team

Promoting an engineer with no role transition equals burnout and team churn

The strongest senior engineer is often promoted to Engineering Manager with zero framework for the new role. The result: micro-management of code, 1-on-1s collapsing into code review, and engineers leaving within 6–12 months. The Stack Overflow Developer Survey 2024 lists 'bad management' as the #2 driver of engineer churn across Southeast Asia.

Reference frameworks

Neksus modules integrate Accelerate (DORA), the Google SRE Book (SLO/SLI/error budget), NIST CSF 2.0, OWASP Top 10 2021, the ITIL 4 Service Value System, COBIT 2019 (for BUMN/banking audit context), and SAFe / Scrum at Scale for multi-team contexts. Leadership practice follows The Manager's Path (Camille Fournier) and An Elegant Puzzle (Will Larson).

Engineering leadership is a measured discipline

DORA metrics, SLO compliance, and MTTR can be tracked weekly. A Tech Manager who leads without a numeric baseline leads by intuition alone. The Neksus program begins with instrumenting a 30-day baseline of the four DORA metrics on the client's stack.

Indonesian enterprise buyers already speak the metric language

CIOs and CTOs in Indonesia are now fluent in Accelerate and SRE frameworks. A Tech Manager fluent in DORA, error budget, and NIST CSF 2.0 speaks on the same wavelength as their technology directors.

Starting Point

The TNA pattern we most often find in IT Leads / Tech Managers

These patterns emerge consistently from initial Neksus diagnostics across banking, BUMN, manufacturing, and tech-enabled enterprises.

Gap

No DORA metrics baseline

Symptom: The engineering team ships without measuring deployment frequency, lead time, change failure rate, or MTTR. Performance discussions run on intuition.

Business impact: The board doubts the ROI of engineering investment; engineers lose the compass for continuous improvement.

Gap

Unfamiliar with SLO / SLI / error budget

Symptom: Reliability requests and delivery requests are treated as permanent conflict. Every incident is handled reactively with no error budget frame.

Business impact: The team oscillates between over-engineering and extreme tech debt; the CIO struggles to prioritize the roadmap.

Gap

DevSecOps still runs as a parallel process

Symptom: Security review happens post-development; OWASP Top 10 is no part of standard checklists; threat modeling is missing from the backlog.

Business impact: Vulnerabilities surface during external audit; releases slip due to late-stage fixes; remediation cost runs 10–100x higher.

Gap

1-on-1s collapse into code review

Symptom: A newly promoted Tech Lead still dominates every technical decision; engineers receive no room to grow.

Business impact: Senior engineers fail to progress; the team becomes single-point-of-failure dependent; psychological safety stays low.

Gap

Weak IT service governance

Symptom: Incident management runs without runbooks; change management is ad-hoc; problem management is missing. ITIL 4 or ISO/IEC 20000-1 has yet to map onto daily practice.

Business impact: IT audits (BPK / external KAP / regulator) produce many findings; internal service SLAs are hard to meet.

Gap

No engineering operating cadence

Symptom: Backlog grooming is ad-hoc; sprint review becomes a formality; retros are absent or yield action items with no follow-through.

Business impact: The team runs without rhythm; the learning loop fails to form; continuous improvement stalls.

Everyday Problems

Pain points IT Leads / Tech Managers feel on the ground

Boardroom pressure: 'why is the feature slow, you already have 30 engineers?'

Root: The board sees output as the count of features per quarter, with zero visibility into lead time or change failure rate.

What we do: The 'DORA Storytelling for the Boardroom' module turns the four metrics into a narrative CFOs and CEOs understand, using a 30-day baseline from the client's stack as evidence.

Every production incident triggers a Slack blame game

Root: There is no blameless post-mortem ritual; SLO / error budget remain undefined, so every incident feels like a personal failure.

What we do: The 'Blameless Post-Mortem + Error Budget' module installs the Google SRE ritual: 5-why, contributing factors, action items with owner and due date.

The security team is seen as a blocker by engineering

Root: Security review happens after PR readiness; engineering feels security throttles delivery.

What we do: The 'Shift-Left DevSecOps' module embeds threat modeling into sprint planning, SAST/DAST in CI, a security champion per team, and OWASP Top 10 as a code-review checklist.

IT audits (BPK / KAP / regulator) keep producing many findings

Root: Daily practice has yet to map to ITIL 4 / ISO/IEC 20000-1 / COBIT 2019; documentation is thin.

What we do: The 'Audit-Ready Engineering Org' module maps practice to ITIL 4 and COBIT 2019 controls and provides runbook, change log, and evidence trail templates.

Tech Leads resign because they feel stuck

Root: There is no technical career ladder (IC track) alongside the management track; the only path up is becoming a manager.

What we do: The 'Engineering Career Ladder Design' module installs a dual-track IC ladder (Senior → Staff → Principal → Distinguished) plus a Manager ladder (EM → Director → VP) based on Patterson and Camille Fournier.

Cloud adoption goes chaotic: cost out of control, weak governance

Root: Migration runs team-by-team with no landing zone, tagging policy, or FinOps discipline.

What we do: The 'Cloud Governance & FinOps Foundations' module installs landing zone, tagging convention, cost allocation, and RACI with the Infra and Finance teams.

Skill Ladder

The IT Lead / Tech Manager capability ladder — first 14 months

Each stage lists the core competencies and the KPI signal that the next stage is ready to enter.

Months 1–3: Role identity and baseline instrumentation

12 weeks

Internalize the shift from hands-on engineer to leader of engineers
Map the stakeholder graph: Product, Security, Infra, Finance, Compliance
Establish weekly 1-on-1 with every engineer (GROW + technical mentoring split)
Instrument a DORA metrics baseline on the client's stack (deployment frequency, lead time, CFR, MTTR)

100% of engineers have a weekly 1-on-1; the DORA baseline dashboard has run for at least 30 days

Months 4–7: SRE discipline + DevSecOps

16 weeks

Define SLO/SLI for 2–3 critical team services
Apply an error budget policy with a board-agreed 'freeze release' trigger
Embed threat modeling into routine sprint planning
Implement SAST/DAST in CI; OWASP Top 10 as a code-review checklist
Run a blameless post-mortem ritual for every P0/P1 incident

SLO compliance ≥ 99.9% for critical services; MTTR down 30–50%; critical/high vulnerabilities closed within 7 days

Months 8–11: Service governance + audit-ready

16 weeks

Map daily practice onto the ITIL 4 Service Value System
Author standard runbooks for the top 10 incident types
Stand up a lightweight change advisory board (CAB) for high-risk changes
Integrate governance with COBIT 2019 controls for BUMN/banking audit context
Lead audit response (BPK / KAP / regulator) with an evidence trail prepared

Latest IT audit shows typical findings down ≥ 50%; internal service SLAs met ≥ 95%

Months 12–14: Engineering org as a system

12 weeks

Design a dual-track engineering career ladder (IC + Manager)
Build the engineering operating cadence: quarterly planning, monthly review, weekly sync, bi-weekly retro
Cultivate engineering brand: tech blog, open-source contribution policy, hiring playbook
Prepare a successor (manager-once-removed thinking)

Engineer churn under 12% annualized; at least one Tech Lead ready to step into Engineering Manager

KPI Targets

KPIs that should shift while this program runs

Pick 3–5 KPIs from the list before the program starts so impact is measured with numbers, with anecdote kept as a supporting layer.

Deployment frequency (DORA #1)

Rise 3–10x within 6 months (client baseline typically weekly → daily)

The most sensitive indicator of CI/CD pipeline health and trunk-based development discipline.

Lead time for changes (DORA #2)

Down 50–80% (elite tier target: < 1 day)

Measures speed from idea to production; correlates directly with business responsiveness.

Change failure rate (DORA #3)

≤ 15% (elite tier target: 0–15%)

Validates the quality of test automation and code review discipline.

MTTR / mean time to restore (DORA #4)

Down 50% (elite tier target: < 1 hour)

Measures observability maturity, incident response, and runbook discipline.

SLO compliance for critical services

≥ 99.9% (or service-specific SLO target)

Provides an error budget that funds aggressive delivery.

12-month engineer retention

≥ 88% (tech industry baseline ~75–82%)

The direct manager is the #1 factor in engineer retention (Stack Overflow Developer Survey 2024).

Mean time to detect (MTTD) for critical vulnerabilities

≤ 24 hours from CVE publication

Evidence of DevSecOps maturity and NIST CSF 2.0 Detect-function posture.

Decision Aid

Three-day intensive vs 10–14 week cohort vs embedded coaching

Three intervention shapes with distinct ROI profiles. The 10–14 week cohort is the Neksus default recommendation for Engineering Managers and IT Leads.

Criterion	Three-day workshop	10–14 week cohort ★	Embedded coaching
Budget level	Standard	Standard or Premium	Premium, or Private 1-on-1 for the CTO
DORA baseline instrumentation on client stack	None	Yes — 30-day real baseline	Yes — 90-day deep instrumentation
Scalability to 15+ engineering managers	High — parallel cohorts	High in cohort format	Low — limited by senior coach capacity
Practice on real incidents + audit	None	Yes — assignments + live blameless post-mortem	Yes — on every P0/P1 incident during engagement
Best fit	DORA / NIST CSF awareness for the board	Default for Engineering Managers and IT Leads	Heads of Engineering / VP Eng transitioning to a C-level role

Engagement Path

The 10–14 week engagement flow — from kickoff to sustaining

1
Diagnostic and technical assessment
Week 0
Online pre-assessment (DORA self-assessment, NIST CSF 2.0 maturity questionnaire, ITIL 4 readiness check) plus 1:1 interview with every participant plus a walkthrough of the client engineering stack. Output: DORA baseline + team capability heatmap.
2
Three-day onsite kickoff workshop
Weeks 1–2
Day 1: Engineering Manager role identity + DORA framework + storytelling for the boardroom. Day 2: SRE foundation (SLO/SLI/error budget) + blameless post-mortem. Day 3: shift-left DevSecOps + OWASP Top 10 + threat modeling. Assignment: each participant drafts a 90-day plan.
3
DORA baseline instrumentation lab
Weeks 2–4
The Neksus team plus client tech leads instrument the four DORA metrics on the client pipeline (GitHub/GitLab + CI/CD tooling). The 30-day baseline dashboard is signed off before moving into the SRE module.
4
Thematic live workshops (bi-weekly, 3 hours)
Weeks 3–12
Rolling topics: SLO Workshop (defining SLO for 2–3 critical services), Error Budget Policy, Practical Threat Modeling, ITIL 4 mapping, COBIT 2019 audit readiness, Engineering Career Ladder Design. Each session ends with a two-week practice assignment.
5
Peer-coaching pods (four managers per pod)
Weeks 3–13
Weekly 60-minute sessions between participants with a peer-coaching frame (problem framing, GROW peer-questioning, accountability check). A Neksus coach facilitates the first three sessions remotely; the pod runs self-managed afterwards.
6
Mid-program check-in with CIO / CTO
Week 7
Participants plus CIO/CTO plus a Neksus coach in a 60-minute session. Review the 90-day plan, DORA baseline, SLO definitions, and calibrate delivery-vs-reliability expectations.
7
Capstone presentation — engineering org transformation
Week 13
Each participant presents: DORA baseline → 90-day target, one incident handled via blameless post-mortem, one running SLO, one vulnerability closed through shift-left DevSecOps, and the career ladder plan for the team.
8
Sustaining: quarterly clinic + audit-readiness review
Week 14 → 12 months
A 90-minute quarterly clinic with a Neksus coach to work through live cases (DORA regression, major incident, upcoming audit). Access to the Engineering Manager Indonesia alumni network.

Who Decides

Decision-makers in an engineering leadership program

Five stakeholder rings that must align before the program succeeds.

CIO / CTO

Sponsor + mid-program check-in

Justifies engineering investment ROI, connects the program to the corporate technology roadmap, and secures audit-readiness.

Head of Engineering / VP Engineering

Co-design

Cross-team consistency of engineering practice, dual-track career ladder standards, and Tech Lead → Engineering Manager succession readiness.

CISO / Head of Security

Co-coach for the DevSecOps module

DevSecOps posture, NIST CSF 2.0 / ISO 27001 compliance, and security champion integration per engineering team.

L&D / Training Manager

Program owner

Operational logistics, Kirkpatrick evaluation, LMS integration, and reporting up to the CHRO.

Internal Audit / SPI (BUMN) / Compliance

Beneficiary + evidence trail reviewer

Mapping engineering practice to ITIL 4, COBIT 2019, and ISO/IEC 20000-1:2018 controls.

Procurement

Process owner

Vendor scoring, contracting, e-procurement (BUMN/government via SPSE LKPP) for multi-cohort engagement.

Program Design Notes

Design notes — why we built it this way

Hybrid format (live + lab + async)
50% live cohort, 30% lab instrumentation on the client stack, 20% async assignment
Engineering leadership demands practice on a real stack. Theory workshops without a lab create awareness that evaporates within 30 days.
Cohort size
8–14 Engineering Managers / IT Leads per cohort
Small enough for deep 1:1 role-play, large enough for cross-domain diversity (microservices, legacy monolith, data platform).
Total duration
10–14 weeks (SRE + DevSecOps + ITIL 4 modules need repeated practice)
Kirkpatrick L3 research shows meaningful impact emerges after at least 8 weeks of practice with feedback; engineering leadership adds extra latency for natural incident cycles to surface.
Facilitator profile
Facilitators with at least 12 years of field engineering leadership experience plus one credential of ICF ACC/PCC, AWS/GCP/Azure Professional, ITIL 4 Managing Professional, or CISSP
Field experience earns credibility; the vendor credential enforces methodological discipline.
Language of delivery
Bilingual ID/EN — engineering jargon stays in English (DORA, SLO, error budget, blameless post-mortem); contextual discussion in Bahasa Indonesia
Indonesian engineers speak mixed-language daily; forcing every term into Indonesian adds friction. Leadership discussion runs deeper in the mother tongue.
Effectiveness measurement
Kirkpatrick L1 (satisfaction) + L2 (competency) + L3 (behavior, 3 months post) + L4 (DORA + SLO + engineer churn, 6 months post)
L4 for engineering leadership is clearly measurable via DORA and SLO compliance; an engineering leadership program has no excuse to stop at L2.

Training Topics

Neksus topics most often paired with an IT Lead / Tech Manager program

Picked for this role

Cloud Basics for IT Teams

Tech Managers need the same cloud literacy as their team. The cloud foundation module accelerates cloud-native onboarding for Engineering Managers with an on-premise background.

See detail

Picked for this role

Kubernetes for IT Teams

Containers and Kubernetes are the new deployment standard. This module gives Engineering Managers the depth to discuss capacity, cost, and reliability with the platform team.

See detail

Picked for this role

Secure Software Delivery

The flagship DevSecOps module for Engineering Managers — threat modeling, SAST/DAST CI integration, OWASP Top 10 as a code-review checklist, security champion per team.

See detail

Picked for this role

Employee Cybersecurity Awareness

Tech Managers lead security awareness within engineering. This module supports onboarding security awareness for new engineers.

See detail

Picked for this role

Agile & Scrum for Product Teams

DORA delivery rhythm cannot be separated from product rhythm. The Agile/Scrum module for Engineering Managers reinforces prioritization discussions with the Product Manager.

See detail

Procurement Info

Procurement information

Contract format
Inhouse fixed cohort (10–14 weeks), multi-cohort continuous program (3–4 cohorts per year), or long-term engagement (12 months with periodic refresh + quarterly clinic).
Location
Onsite at client offices, regional onsite for multi-city BUMN, hybrid (onsite kickoff + bi-weekly online sessions), or fully online.
Language of delivery
Bilingual ID/EN (default); full English for multinational corporates; full Bahasa Indonesia for selected BUMN/government contexts.
Participant materials and certificate
Modules, workbook, runbook + SLO + threat modeling + RACI templates, 12-month access to the Engineering Manager Indonesia alumni resource hub, Neksus participation certificate. Onward certifications (ITIL 4 Foundation / AWS / GCP) available via a separate track.
Tax documentation and e-procurement
VAT (PPN) tax invoice, official receipt, BAST. Support for BUMN/government e-procurement (SPSE LKPP). Comprehensive vendor scoring document available for internal evaluation.
Payment terms
A down payment at contract signing, a milestone payment after kickoff + instrumentation lab, the balance after capstone. The size of each payment is agreed in the contract under the client's procurement rules.
Optional add-ons
Personal 1-on-1 coaching for Head of Engineering / VP Eng (separate hour-based package) plus a 90-minute executive briefing for CIO / CTO / Board IT Committee on engineering capability roadmap.
NDA and confidentiality
Standard or client-specific NDA; the Neksus team is accustomed to working with confidential engineering stacks (mobile banking, core banking, regulator systems).

Frequently Asked Questions