You apply on AutoRABIT Holding's website. CoreHRx takes you there after you sign in.
CoreHRx never asks candidates for money. If anyone does, .
Role at a glance
You will
Accountable execution.
Translate agreed priorities into plans with owners, capacity assumptions, dependencies, risks and measurable outcomes.
Challenge commitments that lack a credible delivery path.
Experience
8–12 years
Must-have skills
JIRAKanban
Work mode
Hybrid
How well do your skills match this job?
Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Job description
Company Overview AutoRABIT is an enterprise platform for Salesforce DevSecOps that enables organizations to manage AI-accelerated Salesforce development with greater security, governance, visibility, and control. Its integrated product suite supports the complete Salesforce DevSecOps lifecycle through AutoRABIT ARM for CI/CD and release management, CodeScan for static code analysis and application security, Vault for data backup and recovery, and Guard for security posture management. The platform helps enterprises automate deployments, improve code quality, protect critical Salesforce data, monitor access risks, and strengthen compliance. AutoRABIT official website
Purpose-built for complex enterprise Salesforce environments, AutoRABIT helps development teams increase productivity, accelerate delivery, and innovate without compromising security or reliability. Its metadata-aware capabilities, scalable platform, flexible hosting options, and integrations provide organizations with the structure and control required to manage Salesforce changes across teams, environments, and global operations. Headquartered in San Francisco, California, AutoRABIT serves customers worldwide and offers employees the opportunity to contribute to products at the intersection of Salesforce, DevSecOps, security, governance, and AI-enabled development. AutoRABIT platform overview
Job Role
Engineering Operations and Pod Delivery
Delivery model: cross-functional pods using Kanban. Pod composition and decision rights are agreed with Engineering and Product leadership
Partner with the VP of Engineering to improve how engineering priorities move from planning to customer-ready delivery. Own the operating mechanisms that create visibility, resolve dependencies and support realistic commitments. This is a hands-on role requiring technical understanding, practical execution and influence across teams.
Key Responsibilities
Accountable execution. Translate agreed priorities into plans with owners, capacity assumptions, dependencies, risks and measurable outcomes. Challenge commitments that lack a credible delivery path. Drive decisions and follow-through, escalating trade-offs to the right leaders before they become blockers.
Customer and release readiness. Connect engineering plans to customer commitments and product outcomes. Coordinate readiness across Product, Engineering, QA, Security, SRE, Support and relevant enablement teams. Ensure release decisions have the required evidence and that unresolved risks have accountable owners.
Pod working structure. Coordinate cross-functional pods around agreed product or customer outcomes. Establish each pod’s mission, accountable owner, required engineering and QA participation, and shared-service dependencies. Align Product, Security, SRE and Support involvement as needed. Coordinate capacity and cross-pod handoffs without creating duplicate reporting lines.
Kanban delivery. Establish Jira Kanban boards with explicit workflow policies, entry and completion criteria, work-in-progress limits and visible blocked work. Facilitate replenishment, flow reviews and delivery forecasts using actual throughput and cycle-time evidence. Manage urgent work through an agreed expedite policy and help pods finish work before starting more.
Operational insight. Establish baselines for lead time, cycle time, work ageing, delivery predictability and relevant quality indicators. Explain the causes behind trends and drive agreed interventions. Avoid treating story points or activity counts as stand-alone measures of individual productivity.
AI and continuous improvement. Use approved AI and automation for reporting, documentation, follow-up and workflow analysis. Validate outputs, protect sensitive information and measure time saved or decision quality improved. Apply Lean, Agile and Kanban practices where they remove friction and help delivery.
Decision boundaries. Facilitate prioritisation, dependency resolution and operating reviews. Product leaders remain accountable for product priorities, engineering leaders for technical execution and people management, and designated release owners for release decisions. Create clarity across these responsibilities rather than parallel authority.
Responsibility to adhere to set internal controls.
Pride of Ownership Take pride in the customer outcomes delivered by the pods you support. Understand the product and its customer commitments, form evidence-based opinions about delivery priorities and risks, and drive decisions through to completion. Use AI and operational data thoughtfully while remaining accountable for their accuracy. Challenge assumptions constructively, listen to teams and adjust the operating model when evidence shows a better approach.
Typically 8 to 12 years in engineering operations, technical program management or a comparable software-delivery role, with demonstrated responsibility across multiple teams.
Experience partnering directly with engineering leadership and turning ambiguous priorities into executable plans.
Strong Jira and Kanban expertise, including workflow policies, work-in-progress limits, replenishment, blocked-work management and flow metrics.
Experience coordinating cross-functional pods or comparable product teams, including ownership, capacity and dependencies.
Understanding of software delivery, quality engineering, security, SRE and release processes.
Evidence of resolving dependencies, improving delivery outcomes and influencing without direct authority.
Strong analytical and written communication skills, including concise executive reporting.
Practical use of AI or automation with evidence that it improved an operational workflow.
Ability to work from the Hyderabad office under the agreed hybrid arrangement and collaborate with global teams.
Preferred Skills (Good to Have)
Enterprise SaaS, developer tools, DevSecOps or other technically complex product organisations.
Experience with quarterly capacity planning, release readiness, Lean flow improvement and cross-region programs.
What success looks like
Within 90 days, agree pod charters and ownership, establish Kanban flow policies and baseline cycle time, throughput, ageing work and dependencies.
Within six months, demonstrate improved flow and delivery reliability across pods against agreed baselines, without sacrificing release quality.
Show that operating reviews lead to decisions and that automation reduces avoidable administration without weakening visibility.
Why join AutoRABIT You will directly influence how AutoRABIT delivers customer value. The opportunity is to build simple, useful ways of working that help teams make decisions earlier and follow through on their commitments.
Experience: 8-12 Years Compensation: 32 - 40 Lakhs per annum Location: Hyderabad Work Mode: Hybrid - 3 days Work from Office Work Timings: IST timings - General Flexible Shift
Preparing for an IT or software developer interview in India? This guide covers the rounds companies run, the technical and HR interview questions asked most often for freshers and experienced developers, sample answers you can adapt, and a simple preparation plan.
Questions you may be asked
Tell me about yourself.
Explain the four pillars of object-oriented programming.
What is the difference between a process and a thread?
