DevOps Engineer

If your instinct when something breaks is to fix the pipeline before fixing the symptom — this role was built for you.

To apply please fill out the application form here: ---------- /bepartofourteam.

About the company

We're a family-owned business with all-local Philippines leadership and team. We've been 100% work-from-home since day one — not a pandemic pivot. We've grown by valuing our people, building long-term relationships, and doing great work for great clients.

The Role

You're not here to deploy code and move on. You're here to make sure the systems that deliver that code are reliable, secure, automated, and continuously improving.
We're looking for a DevOps Engineer who thinks in pipelines, not tasks. You'll own the infrastructure that keeps our development and client environments running — CI/CD pipelines, Linux systems, cloud platforms, monitoring, and security. When something breaks, you find the root cause. When something works, you ask how to make it more reliable, more automated, and less dependent on human intervention next time.

The Mindset We're Looking For

The best DevOps engineers we've worked with share a few traits:
They treat manual processes as technical debt. If something requires a human to do it repeatedly, their instinct is to eliminate that dependency — not just document it
They take ownership. From the ---------- nt an infrastructure problem is theirs, it's theirs until it's resolved, documented, and hardened against happening again
They think in systems. They don't just fix what's broken — they ask what else could break, and why, and build accordingly
They communicate clearly. Status, blockers, and deployment risks are shared openly — before being asked for
They keep learning. The DevOps landscape moves fast. Twelve months from now they know more than they do today — because they made sure of it

Who Thrives Here

People who are technically sharp, operationally minded, and genuinely excited by the challenge of building infrastructure that just works. You don't wait to be handed a list of things to automate — you find them. You're comfortable with ambiguity, resourceful under pressure, and you care more about system reliability than staying in a defined lane.
We're a growing MSP, which means not every pipeline is optimized and not every process is documented yet. For the right engineer, that's not a warning — it's the opportunity to build things the right way from the ground up.

What You'll Do

You'll walk into an environment where development pipelines, Linux infrastructure, cloud systems, and client integrations all need an engineer who can own them end-to-end. Your job isn't just to keep things running — it's to make them run better, more reliably, and with less human intervention every month.
That looks like:

Designing, building, and maintaining CI/CD pipelines that make deployments fast, reliable, and repeatable — so shipping code is a non-event, not a risk
Managing and administering Linux servers (Ubuntu, CentOS, Debian) across development and client environments — knowing these systems well enough to troubleshoot them at any layer
Administering web servers (Nginx, Apache) and databases — keeping them performant, secure, and maintainable
Implementing client-requested integrations — understanding what's being asked, translating it into a reliable technical solution, and delivering it cleanly
Conducting root cause analysis on production errors — not just fixing what's visible, but understanding what allowed it to happen and building the safeguard that prevents it
Building scripts and automation (Bash required; Python and PHP a plus) that eliminate repetitive manual work from the team's daily operations
Monitoring infrastructure, resource utilization, and security events — building alerting systems that catch problems before they become i ----------
Designing and enforcing DevSecOps practices — making security a built-in part of the pipeline, not an afterthought
Working with cloud platforms and virtualization — managing hypervisors and cloud service providers with the confidence of someone who's done it in production

What We're Looking For

Proven experience in Linux server administration (Ubuntu, CentOS, Debian) — you know these systems well enough to manage, troubleshoot, and optimize them without a guide
Hands-on CI/CD experience — you've built and maintained real pipelines, not just used them; you know what makes a deployment safe and what makes it a liability
Strong version control administration — Git, remote repositories, branching strategies, code review workflows; you manage these with intention, not just habit
Web server administration experience — Nginx and Apache, configuration, performance tuning, and troubleshooting
Database administration experience — you can manage database servers, optimize queries, and keep data environments healthy
Bash scripting proficiency (required) — you write automation that works, that others can read, and that makes the team faster; Python and PHP experience is a plus
Solid cloud computing and virtualization experience — working with hypervisors and cloud service providers (AWS, GCP, Azure, or equivalent) in real production environments
Infrastructure and event monitoring experience — you build alerting systems that surface the right information at the right time, not noise
Understanding of DevSecOps — you treat security as part of the build, not something bolted on at the end
Strong diagnostic skills — you find the root cause of a production issue, not just the fastest path to closing the ticket
Self-directed once you understand the environment — but you ask smart questions early to get there
Honest communicator — you surface risks and blockers clearly and early, even when the news isn't good
Long-term mindset — you want to build something that lasts, not move on when things get complex


How Onboarding Works (And How That Changes)

We're honest about how we work with new tea ---------- mbers.
In your first weeks and months, you'll have real hands-on support from the team. We'll work closely with you to understand our infrastructure, our standards, our tools, and how we operate. We expect questions — and we'll give you the time to learn.
As you show what you can do — and you will — that involvement steps back quickly. Trust grows fast here. People who demonstrate ownership, judgment, and quality work earn autonomy quickly. People who consistently deliver end up with significant latitude to shape the infrastructure, the pipelines, and how we build.
We don't want to over-direct people who don't need it. But we also don't believe in throwing someone in without context and calling it autonomy. We earn each other's trust through real work — then we get out of the way.


What Success Looks Like

At three months: You have a clear picture of the infrastructure landscape — what's healthy, what's fragile, and what needs to be rebuilt. At least one significant manual process has been automated. Your documentation is already what the team references.
At six months: Deployments are more reliable and less stressful than when you joined. Monitoring is catching problems before they become i ---------- . The team is spending less time on reactive firefighting and more time building.
At twelve months: The infrastructure is measurably more stable, secure, and automated than before you joined. You've built systems the team depends on — and you're already identifying the next layer of improvement. The company is investing in your next step.


How We Work

We trust our people to do great work and we give them the space to do it. There's real work to be done — clients and internal teams depend on the infrastructure you manage — but we understand that doing meaningful work means making decisions, and sometimes those decisions won't be right on the first try. That's how we find the right path. We don't punish thoughtful mistakes. We learn from them and move forward.
We're a growing MSP, so not every pipeline is optimized and not every process is documented yet. That's part of why we need someone like you — to help us build the infrastructure, automations, and systems that make us better as we grow.


This Role Is Not for You If:

You need a defined list of tasks to know what to work on
You deploy the fix without asking what caused the failure
You treat documentation and runbooks as someone else's job
You're comfortable with fragile systems as long as they're currently running
Your outside commitments regularly affect your availability and focus
You're looking for a low-pressure remote role with predictable, well-defined work
There's no judgment in that list — it's just not the environment. We'd rather be honest now than waste each other's time.


What We Offer


Competitive salary based on experience
100% remote — no corporate commute, ever
Weekly pay
Tech and internet allowance
Paid vacation leave
HMO
Access to the latest AI tools (Claude, Code, and more) to work smarter and automate more
Career growth