Hiring For Delivery Agile Lead -Fulltime- Remote/Royal Cyber Inc

Job description

Greetings!

We have an immediate requirement for Delivery Agile Lead , If interested please share your updated resume along with the required details at the earliest.

Position: Delivery Agile Lead

Experience: 8+ Years

Location: Remote

Employment Type: Full-Time

Role Overview

• Demonstrated success driving complex initiatives across multiple technical and business functions.
• Strong hands-on Jira experience, including boards, workflows, backlogs, epics, dependencies, reporting, and delivery metrics.
• Strong practical understanding of Agile and Scrum, including sprint planning, refinement, stand-ups, retrospectives, release readiness, and continuous improvement.
• Ability to identify delivery risks, clarify ownership, manage dependencies, drive decisions, and maintain follow-through without relying on formal authority.
• Enough technical fluency to understand engineering conversations, delivery dependencies, architecture implications, production concerns, and SDLC practices.
• Strong written and verbal communication skills with engineers, product leaders, executives, business stakeholders, and external partners.
• Experience working in distributed, global, offshore, nearshore, contractor, or partner-based delivery environments.
• Ability to operate effectively in a lean, fast-moving organization where priorities can change and process must remain practical. Preferred Qualifications
• Experience as a Technical Program Manager, Engineering Delivery Lead, Delivery Manager, Scrum Master, Release Train Engineer, Engineering Operations Lead, or similar role.
• Experience supporting SaaS products, cloud platforms, data platforms, APIs, enterprise integrations, or regulated production systems.
• Experience with AWS, Kubernetes, Snowflake, Airflow, dbt, GitHub, CI/CD, Java, Python, or comparable modern engineering environments.
• Experience leading technical debt, platform modernization, data migration, security/compliance, release-management, or other cross-functional technology programs.
• Experience improving poorly functioning retrospectives, backlog hygiene, board discipline, delivery metrics, or multi-team planning practices.
• Agile, Scrum, PMP, SAFe, or related delivery certifications. Certifications are helpful but practical delivery experience is more important.
• Experience in healthcare, pharmacy, payer, benefits, life sciences, financial services, or another regulated environment. Ideal Candidate Profile
• An engineering delivery leader at the core, not simply an administrator of Agile ceremonies.
• Structured and organized enough to create clarity, but pragmatic enough not to over-process a lean organization.
• Technically fluent enough to earn credibility with engineers and identify when a dependency, estimate, handoff, or risk does not make sense.
• Comfortable challenging teams and leaders when ownership, commitments, sequencing, or decisions are unclear.
• Able to move from a Jira board discussion to an executive risk conversation to a cross-functional project working session without losing context.
• Strong at follow-through, action closure, documentation, decision tracking, and making hidden work visible.
• Calm and structured when priorities shift, production issues emerge, or several teams need to coordinate under time pressure.
• Low ego, outcome-oriented, curious, autonomous, and comfortable operating through influence rather than hierarchy. Delivery and Operating Context for Candidates
• Scripta is strengthening its engineering operating model while protecting active roadmap, platform, data, security, QA, and client commitments.
• The role is expected to make existing engineers more effective, not create another layer between engineers and decision-makers.
• Day-to-day Agile discipline and cross-functional program leadership are equally important. The role must be able to operate at both levels.
• Retrospectives should produce measurable learning and follow-through. Jira should reflect real work and real ownership, not become an administrative artifact maintained after the fact.
• Product Management remains responsible for product strategy and prioritization. This role partners with Product to help Engineering translate priorities into executable, visible, and reliable delivery plans.
• Success should be measured by clearer ownership, fewer hidden dependencies, faster issue resolution, stronger follow-through, better delivery predictability, and reduced administrative burden on technical leaders.

Required Details:

Full Name:

Location:

Experience:

Notice Period:

CTC:

E.CTC:

Thanks & Regards,

Rajesh R

Royal Cyber Inc