How to Deliver It Without Sounding Robotic

Don’t memorize the full script word by word. Keep this cue card near the camera:

1. Role
SRE / DBRE + Scrum Master

2. Reliability
Automation, resilience, stability

3. Impact
BCM, LGTM, health checks, backup reporting, governance

4. Scrum Master value
Clarity, blockers, accountability, technical understanding

5. Strengths
Ownership, learning, collaboration, follow-through

6. Closing
Improve reliability and delivery maturity

---

Camera-Shy Recording Method

Record in 6 small parts, then merge if allowed. This is much easier than doing one perfect take.

Part 1: Introduction
Part 2: Current role
Part 3: Contributions
Part 4: Scrum Master value
Part 5: Learning and strengths
Part 6: Closing

Speak slowly. A 3–4 minute video should feel slightly slower than normal conversation. Pause after each paragraph. Pauses look confident.

Use this tone: calm, sincere, prepared — not dramatic, not overly energetic.

Before recording, say this twice:

“I don’t need to sound perfect. I only need to sound clear, sincere and structured.”

That mindset will help your delivery.

Posted By Nikhil09:03

0

Continue Reading

Shorter 3-Minute Version

 

Use this if you feel the above is too long:

Hi, I am Nikhil. I currently work as a Site Reliability Engineer / Database Reliability Engineer, and I also support the Emerging DB POD as Scrum Master.

My role is focused on database reliability, automation, operational resilience and platform stability. I work across Oracle, PostgreSQL and emerging database technologies such as Cosmos DB, Redis, MongoDB and DocumentDB.

In my view, reliability is not only about fixing issues. It is also about identifying patterns, reducing repeat problems, improving visibility and converting manual work into structured and repeatable solutions.

Some areas where I have contributed include PostgreSQL BCM automation, Oracle and LGTM onboarding support, standard ID remediation analysis, database health-check automation, backup reporting improvements and governance tracking. These contributions helped reduce manual effort, improve evidence collection, strengthen BCM readiness and bring better visibility to operational risks.

What I try to bring into my work is ownership. When I see an issue, I try to understand whether it is just a one-time problem or part of a wider gap. If there is a pattern, I try to convert it into an improvement action, automation opportunity or better tracking process.

As a Scrum Master, I see my contribution beyond running ceremonies. I use my technical background to bring clarity to discussions, help surface blockers early, and support outcome-focused conversations. Because I understand the database engineering side, I can help connect technical challenges with delivery priorities and stakeholder expectations.

I also try to create a transparent and constructive environment where people can raise risks early, while still keeping the focus on accountability and practical next steps. I believe this balance of empathy, clarity and ownership is important for any team.

Continuous learning is also very important to me. Certifications, technical blogging and involvement in the database community have helped me improve my technical depth and confidence. I try to bring that learning mindset into my daily work and share knowledge where possible.

I would describe myself as dependable, curious, collaborative and improvement-focused. I may not always be the loudest person in the room, but I believe in preparation, consistency and follow-through.

Overall, I see my contribution as a mix of technical reliability, automation mindset, structured delivery support and collaborative leadership. My goal is to continue improving platform stability, reducing manual effort, supporting the team better and contributing to the organization with stronger impact.

Thank you.

Posted By Nikhil09:02

0

Continue Reading

#####################

Question 1: Current Role

The candidate is currently working as a Site Reliability Engineer and Scrum Master for the Emerging Database team, contributing to database reliability, automation, operational resilience and platform stability across enterprise database technologies.

The role includes individual ownership across:

• Production reliability, business continuity readiness and operational resilience.

• Database automation, patching support, backup governance and operational reporting.

• PostgreSQL Site Reliability Engineering responsibilities.

• Scrum Master responsibilities for the Emerging Database team.

• Coordination with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders.

The candidate stepped into PostgreSQL SRE responsibilities when PostgreSQL was introduced as a strategic database platform within the bank. More recently, the candidate also took on Scrum Master responsibilities for Emerging Database, covering areas previously handled or supported by individuals operating at the desired rank.

As Scrum Master, the candidate’s contribution goes beyond routine facilitation. They bring technical understanding, delivery discipline and stakeholder management to create clarity, surface risks early, convert unclear issues into trackable actions and improve delivery transparency.

This demonstrates target-rank behavior by combining hands-on engineering depth with broader ownership, cross-team influence and delivery accountability.

Candidate has been in this role since: [add month/year]

---

Question 2: Contribution and Impact

The candidate has delivered strong individual impact across reliability, automation and operational maturity.

Key contributions include:

• Independently designed and developed PostgreSQL BCM automation using deep PostgreSQL engineering knowledge built since PostgreSQL was introduced within the bank.

• Supported 7+ BCM BigRock events through automation coverage across 200+ Oracle databases and 40+ PostgreSQL databases.

• Reduced BCM manual effort by approximately 95% through automated validation, execution support and evidence collection.

• Converted PostgreSQL HA checks, validation points, operational risks and evidence requirements into repeatable automation.

• Analysed Oracle/LGTM onboarding blockers related to standard ID and certificates, identified recurring host-level issues and drove structured remediation actions.

• Improved database health checks, backup reporting and operational tracking for audit and governance needs.

• Applied technical judgement as Scrum Master to clarify ambiguous work, expose blockers early, manage dependencies and keep delivery focused on outcomes.

These contributions improved BCM consistency, auditability, risk visibility and confidence during continuity events.

The candidate’s impact is comparable to the next rank because they independently own complex areas, solve systemic issues and influence delivery beyond assigned technical tasks.

---

Question 3: Principles & Behaviors

The candidate demonstrates ownership, collaboration, learning agility and a reliability-first mindset.

Role-model behaviors include:

• Takes ownership of unclear and evolving areas, including PostgreSQL reliability automation and Emerging Database Scrum Master responsibilities.

• Translates technical issues into clear actions, risks and decisions.

• Collaborates effectively with engineers, Product Owners, Reliability Owners, vendor teams and management stakeholders.

• Creates transparency by surfacing blockers early and keeping focus on commitments and outcomes.

• Balances empathy with accountability while supporting a constructive team environment.

• Uses technical judgement to connect engineering details with business priorities.

• Drives continuous improvement through automation, certifications, technical blogging and knowledge sharing.

• Recognized by Oracle through its community/ACE program for technical contributions, providing early exposure to Oracle product direction, new features and industry practices that can be brought back into the organization.

• Transforms manual, repetitive and evidence-heavy operational work into reliable automated processes.

These behaviors show maturity beyond routine execution. The candidate demonstrates target-rank expectations through collaboration, innovation, transformation, mobility and growth, while consistently contributing to team reliability and delivery outcomes.

Posted By Nikhil08:56

0

Continue Reading

 

Hi [PO Name], this ask is part of the UBS Model Identification process to confirm whether our applications qualify as a model under the model governance policy.

Based on the details, Azure Cache for Redis and Azure Cosmos DB are infrastructure/data storage services. Redis is used for caching, and Cosmos DB is a managed NoSQL database service. They do not themselves perform prediction, scoring, forecasting, risk calculation, optimization, or decision-making.

So our product appears to fall under application/database infrastructure and should not qualify as a model candidate. We can affirm the portal details with this justification.

Posted By Nikhil03:44

0

Continue Reading

 Hi Team, sharing a quick update from today’s BCM event — all PostgreSQL BCM activities have been completed successfully.

This time, the PostgreSQL switchover/switchback was executed via automation, and all validations were successful. Thanks everyone for the support.

Posted By Nikhil23:08

0

Continue Reading

 We are currently working on LGTM deployment, where the deployment activity involves certificate installation on the target hosts.

The deployment was successful in the Development environment. However, for Production and TE2 environments, the deployment did not proceed directly as it went for approval. To avoid approval dependency, the required hosts were whitelisted under reference number: .

Even after whitelisting the hosts, the deployment still went for approval. We have now scheduled a call with the CREDS team to understand what additional configuration or mapping is required.

As per the available FAQ, the technical account may also need to be mapped in ISAAC for the deployment to proceed without approval. We need support to confirm the complete requirement and identify what is currently missing, so that future LGTM deployments to Production and TE2 can proceed without manual approval for this account.

Request:

Please help review the current setup and confirm:

Whether the host whitelisting has been correctly applied.

Whether the technical account needs to be mapped in ISAAC.

Any additional approval bypass configuration required for Production and TE2.

What changes are needed so that LGTM certificate deployment can proceed without approval for this account. :::

A shorter title could be:

LGTM deployment going for approval despite host whitelisting

Posted By Nikhil01:37

0

Continue Reading

 Here is a clean 2–3 line release summary for each item:

:::writing{variant="document" id="73924"} 1. Policy to disable HA for lower environments — Audit Mode

Introduced an audit-mode policy to identify HA-enabled instances across AMR, Redis, Cosmos DB, and DocumentDB in dev/test environments. This will help review unnecessary HA usage in lower environments and support future cost-optimization actions.

2. Azure Cosmos — ICC Evidence Document Update

Updated the Azure Cosmos ICC evidence documentation with the latest required evidence triggered by MERs. This ensures the relevant compliance artefacts remain current and aligned with ICC requirements.

3. Cosmos — Prod Database Refresh Script

Developed a script to copy required metadata from production to lower environments. This helps provide a more production-like setup in non-prod, improving testing reliability and validation quality.

4. Azure Cosmos vCore & AMR — Migration to Python / AKS Analysis

Completed analysis to support role assignment for Azure Cosmos vCore and Azure Managed Redis using a Python-based application approach. This is a step towards enabling Azure Function-based execution and reducing dependency on ADO pipelines.

5. Automation Solution for Pipeline Failure — Analysis

Performed analysis for improving the solution design around pipeline failure detection. The objective is to reduce false positives and improve identification of actual pipeline failures.

6. Agent Pool Fix — Invoke Pyfunc Pipeline

Worked on the agent pool fix required for the Invoke Pyfunc pipeline execution. This helps improve pipeline stability and ensures smoother automation runs. :::

Posted By Nikhil22:14

0

Continue Reading