# Rania_Nassar's Manager Readme

**Senior Platform Engineer at Fadata**

# Motivation for this document

This document explains how I work and how we can collaborate effectively.

Platform engineering works best when expectations are clear. My goal is to make infrastructure reliable and easy to use so teams can focus on building products.

# My role

I work as a Platform / Cloud Engineer responsible for building and maintaining reliable and secure infrastructure.

My main focus areas include:

- Kubernetes platforms

- Cloud infrastructure (AWS and Azure)

- Infrastructure as Code

- CI/CD automation

- Observability and monitoring

- Platform security

  

**How I Measure Success**

Success means:

- Stable and reliable systems

- Smooth deployments

- Good documentation

- Automated processes

- Secure environments

I aim to reduce operational work and make the platform easier to use.

# What do I value most?

**Simplicity**

Simple solutions are easier to maintain and troubleshoot.

**Automation**

Manual work should be minimized whenever possible.

Automation improves reliability and consistency.

**Reliability**

Production systems should be predictable and stable.

Safe changes are better than fast changes.

**Documentation**

Systems should be understandable by others.

Documentation is part of the work, not an extra task.

## How to Work With Me

**Communication**

Best ways to reach me:

- Chat for quick questions

- Tickets for tasks

- Calls for urgent issues

Production problems should be reported immediately.

**Asking for Help**

Helpful information includes:

- What you tried

- Error messages

- Logs

- Expected result

This makes troubleshooting faster.

**Mistakes and Issues**

- Problems happen in complex systems.
- Report issues early.
- The goal is to fix problems and learn from them.

# My Expectations

**Definition of Done**

Work is complete when:

- It works reliably

- It is documented

- It is repeatable

- Monitoring is in place if needed

**Availability**

Available during normal working hours.

Reachable via chat most of the time.

Urgent issues can be escalated directly.

# 1:1s

1:1 meetings can be used for:

- Technical discussions

- Feedback

- Knowledge sharing

Anyone can request one if needed.

# Personality quirks

**I like structured work**  
I work best when tasks have clear goals and defined scope. Well-written tickets and documented requirements make collaboration much smoother.

**I prefer planned changes**  
Last-minute production changes make me uncomfortable unless there is a clear urgency. Planned work usually leads to safer and more reliable outcomes.

**I enjoy solving complex problems**  
I like digging into technical issues and understanding root causes. Sometimes I may spend extra time making sure the solution is correct and sustainable.

**Direct communication works best**  
I appreciate clear and honest communication. If something is unclear or not working well, I prefer discussing it openly.

**Documentation makes me happy**  
Good documentation saves time for everyone. I appreciate when decisions,  
 configurations, and processes are written down and kept up to date

# Where to focus on your first 90 days?

**First Month**

Focus on:

- Understanding the platform

- Reading documentation

- Learning workflows

**First 3 Months**

Goal:

- Work independently on small tasks

- Understand the system

- Contribute improvements