Manogna Sammeta is a seasoned Site Reliability Engineer and Atlassian expert based in Sunnyvale, California. With a strong educational foundation, including a Master of Science in Computer Science from the University of Central Missouri and a Bachelor of Technology in Electronics and Instrumentation Engineering from Jawaharlal Nehru Technological University (JNTU), Manogna combines academic knowledge with extensive practical experience. Her professional journey has been marked by significant contributions to major enterprise systems, where she has honed her skills in cloud infrastructure, Atlassian tool administration, and implementing robust DevOps practices.
Q 1: What motivated you to pursue a career in Site Reliability Engineering and Atlassian administration?
A: My interest in Site Reliability Engineering stems from my passion for building resilient systems that can scale efficiently while maintaining high performance. I’ve always been fascinated by the intersection of development and operations, and how proper tooling can streamline workflows. The Atlassian ecosystem particularly captured my attention because of its comprehensive approach to collaboration, project management, and code versioning. Being able to optimize these tools and create automated solutions that enhance productivity gives me a sense of accomplishment, knowing that I’m making a tangible impact on how teams work together.
Q 2: How do you approach complex migrations, such as moving from on-premises to cloud environments?
A: Complex migrations require meticulous planning and execution. My approach begins with a comprehensive assessment of the current environment, including dependencies, customizations, and user workflows. I create a detailed migration plan with clearly defined phases, testing strategies, and rollback procedures. Communication is crucial – I ensure all stakeholders understand the timeline, potential impacts, and benefits. During implementation, I focus on minimizing downtime by using parallel environments and incremental transitions where possible. Post-migration validation is equally important, verifying that all functionality, data integrity, and performance meet expectations. Throughout the process, I document everything meticulously to build institutional knowledge and provide a reference for future migrations.
Q 3: Can you describe a challenging project you managed and how you overcame obstacles?
A: One of the most challenging projects I managed was upgrading a mission-critical JIRA instance from version 6.4 to 8.5 for a large enterprise with numerous customizations and plugins. The complexity stemmed from the significant version gap and the thousands of active users relying on the system daily. We faced compatibility issues with several essential plugins and custom scripts. To overcome this, I developed a comprehensive testing environment that mirrored production and methodically tested each plugin and customization. For incompatible plugins, I either found alternatives or developed custom solutions using Groovy scripts. I also implemented a phased upgrade approach, moving through intermediate versions to isolate and address issues incrementally. Through careful planning, extensive testing, and clear communication with stakeholders, we completed the upgrade with minimal disruption and even improved overall system performance.
Q 4: What role does automation play in your approach to infrastructure management?
A: Automation is the cornerstone of modern infrastructure management and a fundamental aspect of my approach. It eliminates manual errors, ensures consistency, and frees up time for higher-value work. I leverage automation extensively for repetitive tasks like user management, license cleanup, certificate renewals, and deployment processes. For instance, I’ve developed Groovy scripts and REST APIs that automate JIRA workflows based on specific triggers and conditions. I also implement Infrastructure as Code (IaC) principles using tools like OneOps and Azure Resource Manager templates to provision and configure environments consistently. Automation not only improves operational efficiency but also enhances security through standardized processes and reduces the mean time to recovery during incidents by enabling quick, reliable deployment of solutions.
Q 5: How do you ensure high availability and disaster recovery for critical systems?
A: Ensuring high availability and effective disaster recovery requires a multi-layered approach. I design redundant architectures with no single points of failure, implementing load balancing and automatic failover mechanisms. For cloud deployments, I leverage availability zones and regions to protect against localized outages. Regular backup and recovery testing is essential – I schedule routine disaster recovery drills to validate procedures and identify improvement areas. Monitoring and alerting systems provide early warning of potential issues, allowing for proactive intervention. For database systems like Azure SQL, I implement replication and point-in-time recovery options. I also establish clear RPO (Recovery Point Objective) and RTO (Recovery Time Objective) metrics based on business requirements, ensuring we build systems that meet those standards. This comprehensive approach has enabled me to achieve 99.99% uptime for mission-critical services.
Q 6: What tools or software do you rely on for system monitoring and performance optimization?
A: I employ a diverse monitoring stack to gain comprehensive visibility into system health and performance. Prometheus provides powerful time-series data collection with a focus on metrics, while Nagios helps with infrastructure monitoring and alerting. Splunk is invaluable for log aggregation and analysis, especially for troubleshooting complex issues across distributed systems. For performance optimization, I analyze trends in these monitoring tools to identify bottlenecks and areas for improvement. I also use custom dashboards to visualize key performance indicators relevant to specific business functions. Beyond tools, I follow SRE practices like establishing SLOs (Service Level Objectives) and error budgets to maintain a balance between system reliability and deployment velocity. This approach ensures we’re focusing optimization efforts where they’ll have the most significant impact on user experience.
Q 7: How do you manage team dynamics and ensure effective collaboration across different technical groups?
A: Effective collaboration across technical groups requires both cultural and tooling approaches. I focus on building a shared understanding of objectives and ensuring that specialized teams don’t operate in silos. Regular cross-functional meetings help align priorities and increase awareness of interdependencies. I leverage Atlassian tools to create visibility – using JIRA to track work across teams and Confluence to document decisions and share knowledge. I’ve found that implementing standardized workflows and integrating systems (like connecting JIRA with ServiceNow for example) significantly improves cross-team coordination. Training sessions are another essential component; I’ve personally trained over 1,000 users on JIRA and Confluence best practices, which creates a common language and methodology across teams. By fostering a culture of transparency and providing integrated tools, teams can collaborate more effectively despite having different technical focuses.
Q 8: What advice would you give to someone aspiring to enter the SRE or Atlassian administration field?
A: My advice would be to build a solid foundation in both technical skills and systems thinking. Start by understanding fundamental concepts like Linux administration, networking, and at least one scripting language. For Atlassian administration specifically, set up a local instance to practice customizations and automations. Beyond technical skills, develop a mindset focused on reliability and scalability – always consider how solutions will perform at scale and under stress. Stay current with industry trends through blogs, forums, and certification programs. Equally important is building communication skills, as explaining complex technical concepts to non-technical stakeholders is a crucial part of the role. Finally, don’t underestimate the value of understanding business objectives – the most effective SREs and administrators align their technical decisions with organizational goals, making them strategic partners rather than just technical resources.
Q 9: How do you stay current with industry trends and advancements in technology?
A: Staying current in rapidly evolving fields like cloud infrastructure and DevOps requires a multi-faceted approach. I actively participate in the IEEE community, which provides access to research papers and networking opportunities with other professionals. I follow key thought leaders on platforms like LinkedIn and Twitter, and regularly participate in webinars and virtual conferences focused on SRE practices, cloud technologies, and Atlassian updates. Hands-on learning is equally important – I often set up test environments to experiment with new tools or features before implementing them in production. I’m also a firm believer in the value of formal education and certifications to validate knowledge in specific areas. Additionally, being part of online communities and discussion forums allows me to learn from others’ experiences and challenges, providing insights I might not gain through my work alone.
Q 10: What are your long-term goals in your career, and how do you plan to achieve them?
A: My long-term goal is to evolve into a technology leadership role where I can drive strategic initiatives that transform how organizations leverage infrastructure and tooling to achieve business outcomes. I’m particularly interested in leading cloud transformation strategies and building highly automated, reliable systems at scale. To achieve this, I’m focusing on expanding my expertise beyond technical implementation to include areas like architecture design, team leadership, and strategic planning. I plan to pursue additional certifications in cloud architecture and IT service management to formalize this knowledge. I’m also seeking opportunities to lead larger initiatives and cross-functional teams to develop my leadership skills. Additionally, I want to contribute more to the technical community through mentoring, speaking engagements, and knowledge sharing, which will help me refine my ability to communicate complex technical concepts effectively – a crucial skill for technology leaders.
About Manogna Sammeta
Manogna Sammeta is a Site Reliability Engineer with over 8 years of IT experience specializing in Atlassian tools and cloud infrastructure. Currently based in Sunnyvale, California, Manogna has a proven track record in system administration, migration projects, and implementing DevOps practices. Her expertise includes high-availability system design, automation using multiple scripting languages, and JIRA and Confluence administration. With a Master’s degree in Computer Science and as an IEEE Member, Manogna is dedicated to advancing technology solutions that enhance reliability, scalability, and efficiency in enterprise environments.
