A photo representing this article.
A photo representing this article.
A photo representing this article.

On People, Culture, and Stories

This month, I will be celebrating my fourth work anniversary here at OpsWerks. It will be  the longest I have ever stayed at any job in my young career. This led me to ask myself:  What sets OpsWerks apart from other companies? I believe it’s the value it puts into  building a culture that focuses on community-building and self-development. These are  some of my reflections after four incredible years. 


New beginnings 

I remember my first onsite interview during the hiring process. I was only a few years  into my tech career after changing industries. The long conversation opened my eyes  about the possibility of working with emerging trends like microservices architecture and  distributed systems. During that time, I was working with monolithic applications and the  thought of working with new stuff seemed thrilling. At the end of the interview, I was  handed a business card with the following text plastered at the back.  


“To help those next to us and in front of us live better lives” 


  • Gratitude in every encounter 

  • Choosing Positivity 

  • Looking for Hope 

  • Compassion in Action 

  • Generosity to All 

  • Building a Healthy Community 

  • Continuous Self-improvement  


This was my first encounter with the OpsWerks’ mission and methods. I didn’t think  much about it at first. I had my own ideals as a young professional and while the  mission resonated with me, a part of me was also skeptical. I had to see it for myself. 

I joined the team a few weeks later. Immediately, I noticed that a lot of focus was put  around culture. On my first day, I was given a book titled “Obstacle is the Way”. This  was an aptly titled book, I thought. A new job was a big change for me, and I was  already facing some challenges. People who know me would usually describe me as a  reserved and quiet person. It would usually take me a long time to warm up to new  people and a new environment. I didn’t know anyone in the company and, in contrast,  everybody else seemed to know everyone well. They would even commonly refer to the  team as “family”. To add to that, there were also a lot of new tools and complex systems  that I was unfamiliar with. Learning everything was daunting.  

But OpsWerks, staying true to its mission, helped me overcome all those things. I wasn’t  left to my own devices. I always had senior members whom I could reach out to during  my shift but, at the same time, they also gave me space to explore things by myself. 

Our leaders always find time to check in on me even though they are 14 time zones  away. After just a few weeks, I felt a sense of belongingness because of the support of  the people around me.



Stories that bind us

One of the most anticipated company events every year is called Unity. During this  week-long gathering, everyone is invited to share their stories and promote the values  that guide us in our daily work. When I was asked to become one of the keynote  speakers, I was initially hesitant because I didn’t have any profound experiences to  share and wasn’t sure if I was ready to open up about myself. 

Eventually, I just went for it and it happened to be one of my more memorable  experiences. I realized that being vulnerable can help build trust with others. OpsWerks  always encourage us to create safe spaces for telling our stories. It may happen in little  moments during our weekly meetings, 1-on-1s, blog posts, team building events, or  even in Slack messages—we are always called on to inspire courage to express our  thoughts and emotions. It helps us to connect and learn from our members. I remember  that during our team huddles, one of the questions that will be thrown at the start is:  “How is your heart today?” I learned that everyone indeed has a story to tell and we  become better people by telling stories. It helps us cherish special moments and it’s one  of the most effective ways in building affinity and relationships. This is also one of the  things that I liked most about OpsWerks. It’s the chance to celebrate our values and  empathize with others through storytelling. 


Final thoughts

As the years went on, it turned out that everything about OpsWerks is rooted in its core  values. The concept of a people-centric organization wasn’t new to me. I have been  with companies that would claim to be people-centric, but the size of these companies  makes this harder to execute. OpsWerks, being a small company, was the ideal  environment to implement this, I thought. But one of the biggest reasons is the  leadership’s dedication to touch people’s lives. I am also glad that I found the courage to  start with the company because I definitely became a better person because of it. 

Looking back, it wasn’t really the tech that made me stay. The culture was probably the  biggest cause. Yes, the opportunity to work with fancy new technology was exciting but  experiencing a truly people-centric company that also empowered me to pay it forward  was fulfilling on another level. 

A photo representing this article.
A photo representing this article.

On People, Culture, and Stories

This month, I will be celebrating my fourth work anniversary here at OpsWerks. It will be  the longest I have ever stayed at any job in my young career. This led me to ask myself:  What sets OpsWerks apart from other companies? I believe it’s the value it puts into  building a culture that focuses on community-building and self-development. These are  some of my reflections after four incredible years. 


New beginnings 

I remember my first onsite interview during the hiring process. I was only a few years  into my tech career after changing industries. The long conversation opened my eyes  about the possibility of working with emerging trends like microservices architecture and  distributed systems. During that time, I was working with monolithic applications and the  thought of working with new stuff seemed thrilling. At the end of the interview, I was  handed a business card with the following text plastered at the back.  


“To help those next to us and in front of us live better lives” 


  • Gratitude in every encounter 

  • Choosing Positivity 

  • Looking for Hope 

  • Compassion in Action 

  • Generosity to All 

  • Building a Healthy Community 

  • Continuous Self-improvement  


This was my first encounter with the OpsWerks’ mission and methods. I didn’t think  much about it at first. I had my own ideals as a young professional and while the  mission resonated with me, a part of me was also skeptical. I had to see it for myself. 

I joined the team a few weeks later. Immediately, I noticed that a lot of focus was put  around culture. On my first day, I was given a book titled “Obstacle is the Way”. This  was an aptly titled book, I thought. A new job was a big change for me, and I was  already facing some challenges. People who know me would usually describe me as a  reserved and quiet person. It would usually take me a long time to warm up to new  people and a new environment. I didn’t know anyone in the company and, in contrast,  everybody else seemed to know everyone well. They would even commonly refer to the  team as “family”. To add to that, there were also a lot of new tools and complex systems  that I was unfamiliar with. Learning everything was daunting.  

But OpsWerks, staying true to its mission, helped me overcome all those things. I wasn’t  left to my own devices. I always had senior members whom I could reach out to during  my shift but, at the same time, they also gave me space to explore things by myself. 

Our leaders always find time to check in on me even though they are 14 time zones  away. After just a few weeks, I felt a sense of belongingness because of the support of  the people around me.



Stories that bind us

One of the most anticipated company events every year is called Unity. During this  week-long gathering, everyone is invited to share their stories and promote the values  that guide us in our daily work. When I was asked to become one of the keynote  speakers, I was initially hesitant because I didn’t have any profound experiences to  share and wasn’t sure if I was ready to open up about myself. 

Eventually, I just went for it and it happened to be one of my more memorable  experiences. I realized that being vulnerable can help build trust with others. OpsWerks  always encourage us to create safe spaces for telling our stories. It may happen in little  moments during our weekly meetings, 1-on-1s, blog posts, team building events, or  even in Slack messages—we are always called on to inspire courage to express our  thoughts and emotions. It helps us to connect and learn from our members. I remember  that during our team huddles, one of the questions that will be thrown at the start is:  “How is your heart today?” I learned that everyone indeed has a story to tell and we  become better people by telling stories. It helps us cherish special moments and it’s one  of the most effective ways in building affinity and relationships. This is also one of the  things that I liked most about OpsWerks. It’s the chance to celebrate our values and  empathize with others through storytelling. 


Final thoughts

As the years went on, it turned out that everything about OpsWerks is rooted in its core  values. The concept of a people-centric organization wasn’t new to me. I have been  with companies that would claim to be people-centric, but the size of these companies  makes this harder to execute. OpsWerks, being a small company, was the ideal  environment to implement this, I thought. But one of the biggest reasons is the  leadership’s dedication to touch people’s lives. I am also glad that I found the courage to  start with the company because I definitely became a better person because of it. 

Looking back, it wasn’t really the tech that made me stay. The culture was probably the  biggest cause. Yes, the opportunity to work with fancy new technology was exciting but  experiencing a truly people-centric company that also empowered me to pay it forward  was fulfilling on another level. 

Stop toil. Start scaling.

To break this cycle, enterprises often need outside help. By shifting the load, you can free full-time employees (FTEs) to focus on strategic initiatives — and restore morale. The question is, what kind of help?

In this blog, we'll compare two outsourcing options: staff augmentation vs. managed services. But first, why not just hire more FTEs to relieve overworked teams and solve underlying problems? It often comes down to time and money:

Time

It can take 44 to 67 days to hire the right

candidate, depending on the role.

It can take 44 to 67 days to hire the right candidate, depending on the role.

Recruiting

The search and interview process costs up to $4,700.

The search and interview process costs up to $4,700.

Onboarding

Initial set-up and training adds up to $28,000.

Initial set-up and training adds up to $28,000.

Ramp-up

New hires take up to 8 months to reach full productivity.

New hires take up to 8 months to reach full productivity.

Improving DevOps and SRE with outsourcing

When done correctly, outsourcing can do more than fill gaps — it helps DevOps and SRE teams catapult from average to elite results. Does your team meet the top performance and reliability benchmarks set by Google's DevOps Research and Assessment (DORA)? Most enterprises, weighed down by technical debt and slow hiring cycles, fall short of elite DORA standards.

The result: delays, hidden costs, and performance gaps you can measure:

When done correctly, outsourcing can do more than fill gaps — it helps DevOps and SRE teams catapult from average to elite results. Does your team meet the top performance and reliability benchmarks set by Google's DevOps Research and Assessment (DORA)? Most enterprises, weighed down by technical debt and slow hiring cycles, fall short of elite DORA standards.

The result: delays, hidden costs, and performance gaps you can measure:

Elite teams deploy 182× more frequently than low performers.

Elite teams deploy 182× more frequently than low performers.

Elite teams also

recover 2,293× faster.

Elite teams also

recover 2,293× faster.

Outsourcing not only accelerates time-to-value — it puts elite DORA metrics within reach.

Outsourcing not only accelerates time-to-value — it puts elite DORA metrics within reach.

Staff augmentation vs. managed services: a guide for outsourcing DevOps or SRE

Once you’ve decided to outsource, you face two choices:

1)
Managed service providers (MSP) take responsibility for critical operations, managing a specific project or ongoing operations end to end — from tooling and staffing to delivery of agreed-upon outcomes.

2)
Staff augmentation provides contractors who work as part of your existing in-house team under your direct management and oversight.

The choice between the two depends on your strategic goals, internal capabilities, project complexity, and other considerations. Let’s compare side-by-side.

Factors

Goals

Incentives

Best Fit When

Use cases

Responsibility

Expertise

Management Overhead

Pricing

Managed Services

Add short-term headcount to quickly meet tight, unexpected deadlines or fill a temporary skills gap in DevOps or SRE.

Individual contractors and staffing vendors are incentivized by billable time (headcount × hours), not long-term efficiencies or automation.

You have an urgent short-term project with a narrow scope. For clarity, ask yourself if adding a few extra hands will make a measurable difference. Also be sure you have time to train and manage the contractors since they will be under your direct supervision.

Smaller, short-term projects:

Filling temporary skills gaps

Performing limited-scope work

Scaling for demand surges

Supporting seasonal spikes

Your team manages and executes the work — from interviewing and onboarding contractors to strategic planning and implementation. You own outcomes and assume the risks.

You recruit, hire, and train skilled DevOps or SRE contractors to fill specific gaps or supplement your team.

The flexibility to quickly scale your headcount comes with a tradeoff: higher management overhead. It requires your time and money to recruit, onboard, align, and oversee contractors. This is further complicated by turnover, inconsistent team composition, sick days, and vacations. Vendor pressure to add more headcount results in more of the same overhead costs.

Pricing is variable, based on pay rates and hours worked, so as the scope expands, so do costs. When pricing by headcount, staffing firms are more likely to focus on growing contracts. In turn, unpredictable costs become another aspect to manage. To counter this problem, some vendors claim to offer a “fixed price model,” but it’s still based on headcount with management overhead scaling linearly.

Staff Augmentation

Offload ownership of daily operations or scoped projects to a self-managed team focused on your long-term goals.

A fixed-price model incentivizes the MSP to deliver outcomes that align with long-term efficiencies and automations, not time spent.

You need a partner to take ownership of outcomes for one or more complex, long-term initiatives. Managed services are well suited for mature DevOps or SRE teams with established processes. It's also ideal for teams that need to reduce toil while improving scalability and reliability.

Larger, long-term initiatives:

Executing legacy migrations

Optimizing AI infrastructure

Leading modernization efforts

Improving scale and reliability

Reducing burnout and attrition

Sustaining delivery amid hiring freeze

The MSP owns the responsibility — and the risk — of delivering agreed-upon outcomes. Shifting the operational load enables FTEs to focus on high-priority initiatives.

You gain ready-made teams of experts who bring skills, structure, and cohesion — guided by best practices and established processes.

Self-managed teams with built-in redundancies provide reliable and consistent 24/7 global coverage that requires less oversight. Team members cross-train each other, reducing your need to train. Full alignment with your desired outcomes, methodical execution, and proven efficiency practices minimize management overhead.

Pricing follows a predictable, fixed-fee model for self-managed teams with built-in redundancies. Instead of paying by headcount, you pay for the managed services team to deliver your pre-defined and agreed upon outcomes. Pricing has been defined so the focus is on automations, improvements, and addresses root causes — not hours billed. Any additional costs are incurred by the managed services provider, so they are motivated to drive efficiencies.

To summarize, staff augmentation can give your team the extra bandwidth or expertise needed for urgent short-term projects if: a) you have the capacity to train and manage individual contractors; b) the challenge is narrow in scope; and c) a few extra hands can make a real difference.

Managed services, by contrast, are the better choice when you need a trusted partner to take ownership of outcomes for complex, ongoing or large-scale initiatives — especially well-suited for hyperscale operations.

If you’re leaning toward managed services, the next step is
selecting the right managed service provider for DevOps or SRE.

Factors

Goals

Incentives

Best Fit When

Use cases

Responsibility

Expertise

Management Overhead

Pricing

Managed Services

Add short-term headcount to quickly meet tight, unexpected deadlines or fill a temporary skills gap in DevOps or SRE.

Individual contractors and staffing vendors are incentivized by billable time (headcount × hours), not long-term efficiencies or automation.

You have an urgent short-term project with a narrow scope. For clarity, ask yourself if adding a few extra hands will make a measurable difference. Also be sure you have time to train and manage the contractors since they will be under your direct supervision.

Smaller, short-term projects:

Filling temporary skills gaps

Performing limited-scope work

Scaling for demand surges

Supporting seasonal spikes

Your team manages and executes the work — from interviewing and onboarding contractors to strategic planning and implementation. You own outcomes and assume the risks.

You recruit, hire, and train skilled DevOps or SRE contractors to fill specific gaps or supplement your team.

The flexibility to quickly scale your headcount comes with a tradeoff: higher management overhead. It requires your time and money to recruit, onboard, align, and oversee contractors. This is further complicated by turnover, inconsistent team composition, sick days, and vacations. Vendor pressure to add more headcount results in more of the same overhead costs.

Pricing is variable, based on pay rates and hours worked, so as the scope expands, so do costs. When pricing by headcount, staffing firms are more likely to focus on growing contracts. In turn, unpredictable costs become another aspect to manage. To counter this problem, some vendors claim to offer a “fixed price model,” but it’s still based on headcount with management overhead scaling linearly.

Staff Augmentation

Offload ownership of daily operations or scoped projects to a self-managed team focused on your long-term goals.

A fixed-price model incentivizes the MSP to deliver outcomes that align with long-term efficiencies and automations, not time spent.

You need a partner to take ownership of outcomes for one or more complex, long-term initiatives. Managed services are well suited for mature DevOps or SRE teams with established processes. It's also ideal for teams that need to reduce toil while improving scalability and reliability.

Large, complex, long-term initiatives:

Executing legacy migrations

Optimizing AI infrastructure

Leading modernization efforts

Improving scale and reliability

Reducing burnout and attrition

Sustaining delivery amid hiring freeze

The MSP owns the responsibility — and the risk — of delivering agreed-upon outcomes. Shifting the operational load enables FTEs to focus on high-priority initiatives.

You gain ready-made teams of experts who bring skills, structure, and cohesion — guided by best practices and established processes.

Self-managed teams with built-in redundancies provide reliable and consistent 24/7 global coverage that requires less oversight. Team members cross-train each other, reducing your need to train. Full alignment with your desired outcomes, methodical execution, and proven efficiency practices minimize management overhead.

Pricing follows a predictable, fixed-fee model for self-managed teams with built-in redundancies. Instead of paying by headcount, you pay for the managed services team to deliver your pre-defined and agreed upon outcomes. Pricing has been defined so the focus is on automations, improvements, and addresses root causes — not hours billed. Any additional costs are incurred by the managed services provider, so they are motivated to drive efficiencies.

Why choose OpsWerks managed services for DevOps and SRE?

OpsWerks offers fixed pricing aligned to results. For over a decade, we’ve earned the trust of the world’s leading engineering teams by delivering impactful outcomes. We partner with DevOps and SRE teams to address root causes, drive improvements and lasting operational excellence. Key factors that make this possible:

Outcome Ownership

Outcome Ownership

We take full responsibility for solving issues end-to-end, not just reacting to incidents or adding headcount.

We take full responsibility for solving issues end-to-end, not just reacting to incidents or adding headcount.

Autonomous execution

Autonomous execution

What it means: after jointly defining your desired state, we execute relentlessly, building automation, authoring runbooks, and streamlining operations without constant direction.

What it means: after jointly defining your desired state, we execute relentlessly, building automation, authoring runbooks, and streamlining operations without constant direction.

Predictable partnership

Predictable partnership

OpsWerks delivers resilient, self-managed teams that operate under fixed, transparent pricing, eliminating headcount discussions and reducing risk from turnover or absence.

OpsWerks delivers resilient, self-managed teams that operate under fixed, transparent pricing, eliminating headcount discussions and reducing risk from turnover or absence.

From cloud infrastructure and platform ops to incident response and AI readiness — we do more than support your systems. We evolve them — with stability, scale, and speed.

Proven outcomes with OpsWerks managed services

  • 10x reduction in platform outages and 99.9% uptime . This achievement accelerated a global tech giant’s time-to-market with its CI/CD platform two years earlier than expected.

  • 10x reduction in platform outages and 99.9% uptime . This achievement accelerated a global tech giant’s time-to-market with its CI/CD platform two years earlier than expected.

  • 100,000+ hosts secured in 6 months. The OpsWerks DevOps and SRE teams modernized and secured critical infrastructure without disrupting strategic development.

  • 100,000+ hosts secured in 6 months. The OpsWerks DevOps and SRE teams modernized and secured critical infrastructure without disrupting strategic development.

  • 500+ Kubernetes clusters upgraded in 90 days. Facing instability across clusters, a leading-edge company partnered with OpsWerks to execute seamless upgrades — with zero downtime and significantly improved MTTR.

  • 500+ Kubernetes clusters upgraded in 90 days. Facing instability across clusters, a leading-edge company partnered with OpsWerks to execute seamless upgrades — with zero downtime and significantly improved MTTR.

Why choose OpsWerks managed services for DevOps and SRE?

OpsWerks offers fixed pricing aligned to results. For over a decade, we’ve earned the trust of the world’s leading engineering teams by delivering impactful outcomes. We partner with DevOps and SRE teams to address root causes, drive improvements and lasting operational excellence. Key factors that make this possible:

Outcome Ownership

We take full responsibility for solving issues end-to-end, not just reacting to incidents or adding headcount.

Autonomous execution

What it means: after jointly defining your desired state, we execute relentlessly, building automation, authoring runbooks, and streamlining operations without constant direction.

Predictable partnership

OpsWerks delivers resilient, self-managed teams that operate under fixed, transparent pricing, eliminating headcount discussions and reducing risk from turnover or absence.

From cloud infrastructure and platform ops to incident response and AI readiness — we do more than support your systems. We evolve them — with stability, scale, and speed.

Proven outcomes with OpsWerks managed services

  • 10x reduction in platform outages and 99.9% uptime . This achievement accelerated a global tech giant’s time-to-market with its CI/CD platform two years earlier than expected.

  • 100,000+ hosts secured in 6 months. The OpsWerks DevOps and SRE teams modernized and secured critical infrastructure without disrupting strategic development.

  • 500+ Kubernetes clusters upgraded in 90 days. Facing instability across clusters, a leading-edge company partnered with OpsWerks to execute seamless upgrades — with zero downtime and significantly improved MTTR.

Stop toil. Start scaling.

To break this cycle, enterprises often need outside help. By shifting the load, you can free full-time employees (FTEs) to focus on strategic initiatives — and restore morale. The question is, what kind of help?

In this blog, we'll compare two outsourcing options: staff augmentation vs. managed services. But first, why not just hire more FTEs to relieve overworked teams and solve underlying problems? It often comes down to time and money:

Time

It can take 44 to 67 days to hire the right candidate, depending on the role.

Recruiting

The search and interview process costs up to $4,700.

Onboarding

Initial set-up and training adds up to $28,000.

Ramp-up

New hires take up to 8 months to reach full productivity.

Improving DevOps and SRE with outsourcing

When done correctly, outsourcing can do more than fill gaps — it helps DevOps and SRE teams catapult from average to elite results. Does your team meet the top performance and reliability benchmarks set by Google's DevOps Research and Assessment (DORA)? Most enterprises, weighed down by technical debt and slow hiring cycles, fall short of elite DORA standards.

The result: delays, hidden costs, and performance gaps you can measure:

Elite teams deploy 182× more frequently than low performers.

Elite teams also

recover 2,293× faster.

Outsourcing not only accelerates time-to-value — it puts elite DORA metrics within reach.

Staff augmentation vs. managed services: a guide for outsourcing DevOps or SRE

Once you’ve decided to outsource, you face two choices:

1)
Managed service providers (MSP) take responsibility for critical operations, managing a specific project or ongoing operations end to end — from tooling and staffing to delivery of agreed-upon outcomes.

2)
Staff augmentation provides contractors who work as part of your existing in-house team under your direct management and oversight.

The choice between the two depends on your strategic goals, internal capabilities, project complexity, and other considerations. Let’s compare side-by-side.

To summarize, staff augmentation can give your team the extra bandwidth or expertise needed for urgent short-term projects if: a) you have the capacity to train and manage individual contractors; b) the challenge is narrow in scope; and c) a few extra hands can make a real difference.

Managed services, by contrast, are the better choice when you need a trusted partner to take ownership of outcomes for complex, ongoing or large-scale initiatives — especially well-suited for hyperscale operations.

If you’re leaning toward managed services, the next step is
selecting the right managed service provider for DevOps or SRE.

A photo representing this article.
A photo representing this article.

When every deployment affects hundreds of millions of users and downtime is measured in milliseconds, even world-class DevOps and Site Reliability Engineering (SRE) teams reach their limits. Quick patches, manual overrides, and other short-term fixes add technical debt, increasing the likelihood of future failures.

So how do you reduce toil and improve operational resilience when firefighting itself creates an endless cycle — one that leads to burnout and missed targets?

On People, Culture, and Stories

This month, I will be celebrating my fourth work anniversary here at OpsWerks. It will be  the longest I have ever stayed at any job in my young career. This led me to ask myself:  What sets OpsWerks apart from other companies? I believe it’s the value it puts into  building a culture that focuses on community-building and self-development. These are  some of my reflections after four incredible years. 


New beginnings 

I remember my first onsite interview during the hiring process. I was only a few years  into my tech career after changing industries. The long conversation opened my eyes  about the possibility of working with emerging trends like microservices architecture and  distributed systems. During that time, I was working with monolithic applications and the  thought of working with new stuff seemed thrilling. At the end of the interview, I was  handed a business card with the following text plastered at the back.  


“To help those next to us and in front of us live better lives” 


  • Gratitude in every encounter 

  • Choosing Positivity 

  • Looking for Hope 

  • Compassion in Action 

  • Generosity to All 

  • Building a Healthy Community 

  • Continuous Self-improvement  


This was my first encounter with the OpsWerks’ mission and methods. I didn’t think  much about it at first. I had my own ideals as a young professional and while the  mission resonated with me, a part of me was also skeptical. I had to see it for myself. 

I joined the team a few weeks later. Immediately, I noticed that a lot of focus was put  around culture. On my first day, I was given a book titled “Obstacle is the Way”. This  was an aptly titled book, I thought. A new job was a big change for me, and I was  already facing some challenges. People who know me would usually describe me as a  reserved and quiet person. It would usually take me a long time to warm up to new  people and a new environment. I didn’t know anyone in the company and, in contrast,  everybody else seemed to know everyone well. They would even commonly refer to the  team as “family”. To add to that, there were also a lot of new tools and complex systems  that I was unfamiliar with. Learning everything was daunting.  

But OpsWerks, staying true to its mission, helped me overcome all those things. I wasn’t  left to my own devices. I always had senior members whom I could reach out to during  my shift but, at the same time, they also gave me space to explore things by myself. 

Our leaders always find time to check in on me even though they are 14 time zones  away. After just a few weeks, I felt a sense of belongingness because of the support of  the people around me.



Stories that bind us

One of the most anticipated company events every year is called Unity. During this  week-long gathering, everyone is invited to share their stories and promote the values  that guide us in our daily work. When I was asked to become one of the keynote  speakers, I was initially hesitant because I didn’t have any profound experiences to  share and wasn’t sure if I was ready to open up about myself. 

Eventually, I just went for it and it happened to be one of my more memorable  experiences. I realized that being vulnerable can help build trust with others. OpsWerks  always encourage us to create safe spaces for telling our stories. It may happen in little  moments during our weekly meetings, 1-on-1s, blog posts, team building events, or  even in Slack messages—we are always called on to inspire courage to express our  thoughts and emotions. It helps us to connect and learn from our members. I remember  that during our team huddles, one of the questions that will be thrown at the start is:  “How is your heart today?” I learned that everyone indeed has a story to tell and we  become better people by telling stories. It helps us cherish special moments and it’s one  of the most effective ways in building affinity and relationships. This is also one of the  things that I liked most about OpsWerks. It’s the chance to celebrate our values and  empathize with others through storytelling. 


Final thoughts

As the years went on, it turned out that everything about OpsWerks is rooted in its core  values. The concept of a people-centric organization wasn’t new to me. I have been  with companies that would claim to be people-centric, but the size of these companies  makes this harder to execute. OpsWerks, being a small company, was the ideal  environment to implement this, I thought. But one of the biggest reasons is the  leadership’s dedication to touch people’s lives. I am also glad that I found the courage to  start with the company because I definitely became a better person because of it. 

Looking back, it wasn’t really the tech that made me stay. The culture was probably the  biggest cause. Yes, the opportunity to work with fancy new technology was exciting but  experiencing a truly people-centric company that also empowered me to pay it forward  was fulfilling on another level. 

A photo representing this article.
A photo representing this article.
A photo representing this article.
A photo representing this article.
A photo representing this article.
A photo representing this article.

On People, Culture, and Stories

This month, I will be celebrating my fourth work anniversary here at OpsWerks. It will be  the longest I have ever stayed at any job in my young career. This led me to ask myself:  What sets OpsWerks apart from other companies? I believe it’s the value it puts into  building a culture that focuses on community-building and self-development. These are  some of my reflections after four incredible years. 


New beginnings 

I remember my first onsite interview during the hiring process. I was only a few years  into my tech career after changing industries. The long conversation opened my eyes  about the possibility of working with emerging trends like microservices architecture and  distributed systems. During that time, I was working with monolithic applications and the  thought of working with new stuff seemed thrilling. At the end of the interview, I was  handed a business card with the following text plastered at the back.  


“To help those next to us and in front of us live better lives” 


  • Gratitude in every encounter 

  • Choosing Positivity 

  • Looking for Hope 

  • Compassion in Action 

  • Generosity to All 

  • Building a Healthy Community 

  • Continuous Self-improvement  


This was my first encounter with the OpsWerks’ mission and methods. I didn’t think  much about it at first. I had my own ideals as a young professional and while the  mission resonated with me, a part of me was also skeptical. I had to see it for myself. 

I joined the team a few weeks later. Immediately, I noticed that a lot of focus was put  around culture. On my first day, I was given a book titled “Obstacle is the Way”. This  was an aptly titled book, I thought. A new job was a big change for me, and I was  already facing some challenges. People who know me would usually describe me as a  reserved and quiet person. It would usually take me a long time to warm up to new  people and a new environment. I didn’t know anyone in the company and, in contrast,  everybody else seemed to know everyone well. They would even commonly refer to the  team as “family”. To add to that, there were also a lot of new tools and complex systems  that I was unfamiliar with. Learning everything was daunting.  

But OpsWerks, staying true to its mission, helped me overcome all those things. I wasn’t  left to my own devices. I always had senior members whom I could reach out to during  my shift but, at the same time, they also gave me space to explore things by myself. 

Our leaders always find time to check in on me even though they are 14 time zones  away. After just a few weeks, I felt a sense of belongingness because of the support of  the people around me.



Stories that bind us

One of the most anticipated company events every year is called Unity. During this  week-long gathering, everyone is invited to share their stories and promote the values  that guide us in our daily work. When I was asked to become one of the keynote  speakers, I was initially hesitant because I didn’t have any profound experiences to  share and wasn’t sure if I was ready to open up about myself. 

Eventually, I just went for it and it happened to be one of my more memorable  experiences. I realized that being vulnerable can help build trust with others. OpsWerks  always encourage us to create safe spaces for telling our stories. It may happen in little  moments during our weekly meetings, 1-on-1s, blog posts, team building events, or  even in Slack messages—we are always called on to inspire courage to express our  thoughts and emotions. It helps us to connect and learn from our members. I remember  that during our team huddles, one of the questions that will be thrown at the start is:  “How is your heart today?” I learned that everyone indeed has a story to tell and we  become better people by telling stories. It helps us cherish special moments and it’s one  of the most effective ways in building affinity and relationships. This is also one of the  things that I liked most about OpsWerks. It’s the chance to celebrate our values and  empathize with others through storytelling. 


Final thoughts

As the years went on, it turned out that everything about OpsWerks is rooted in its core  values. The concept of a people-centric organization wasn’t new to me. I have been  with companies that would claim to be people-centric, but the size of these companies  makes this harder to execute. OpsWerks, being a small company, was the ideal  environment to implement this, I thought. But one of the biggest reasons is the  leadership’s dedication to touch people’s lives. I am also glad that I found the courage to  start with the company because I definitely became a better person because of it. 

Looking back, it wasn’t really the tech that made me stay. The culture was probably the  biggest cause. Yes, the opportunity to work with fancy new technology was exciting but  experiencing a truly people-centric company that also empowered me to pay it forward  was fulfilling on another level. 

A photo representing this article.
A photo representing this article.