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.…