Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Cobre

DevOps Engineer

  • Seen live on Cobre's site today
  • Senior
Pay
Not stated
Location
Colombia
Open for
12+ days
First seen
Oct 23, 2026

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Cobre's site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Cobre, so its true age is longer.

Last checked Nov 4, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What it asks of you

5+ years of experience
“● At least 5 years of experience in Cloud Operations, DevOps, or SRE roles, working with cloud infrastructure in production environments.” (quoted from the posting)

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

Cobre is a corporate treasury and payments platform designed to elevate the way Latin American companies manage their finances. At Cobre, we build CFO-tech on top of owned payment rails in order to give real-time capabilities to domestic and cross-border payments, empowering every peso that our clients move.

We are committed to eliminating friction between companies, their banking partners, their people, and their money– so that money movement becomes a growth driver, rather than a time-consuming task. In this pursuit, Cobre has grown to become a trusted provider of corporates and tech giants in the region, while building a profitable business that has grown 10x in the past 12 months.

What we are looking for

We're looking for a Senior DevOps Engineer to join Cobre's Infrastructure team. The Cobre Infrastructure team is made up of Cloud Operations and DevOps engineers who take on the daily challenges of keeping our platform reliable, secure, and running at scale. We enjoy every project and task, giving 100% and learning from each other. Our main goal is to keep our systems reliable and cost-efficient, and to make deployments fast and safe through well-designed CI/CD pipelines and solid automation. To achieve this, we collaborate with other teams to find the most effective solutions, adopt the necessary security measures, and optimize time and cost in every decision.

What would you be doing

● Design, implement, and maintain CI/CD pipelines (e.g., CircleCI, Jenkins) that enable fast, safe, and repeatable deployments across our services.

● Apply and promote DevOps best practices such as automation, version control, GitOps, and declarative configuration to reduce manual work and deployment risk.

● Operate and support the cloud infrastructure (AWS services and Kubernetes clusters) that powers our products, working toward zero-downtime deployments.

● Support teams in defining the infrastructure that will support the solutionarchitecture.

● Set up and maintain monitoring, logging, and alerting, and make sure the right dashboards exist to observe system health and performance.

● Help troubleshoot application and infrastructure issues, and take part in incident response, postmortems, and reliability reviews.

● Keep infrastructure secure and cost-efficient by applying security best practices and identifying optimization opportunities.

● Support periodic load, scalability, and peak-readiness testing to establish baselines and plan capacity for high-volume periods.

● Document and maintain runbooks and procedures, and use AI tools in your day-to-day work to speed up automation, troubleshooting, and documentation.

What do you need

● At least 5 years of experience in Cloud Operations, DevOps, or SRE roles, working with cloud infrastructure in production environments.

● Hands-on experience designing, implementing, and maintaining CI/CD pipelines with tools such as CircleCI or Jenkins.

● Solid understanding of DevOps best practices: automation, version control (Git), GitOps, and declarative configuration.

● Working knowledge of cloud platforms and containers (e.g., AWS, Kubernetes) and of Infrastructure as Code tools (e.g., Terraform, Pulumi).

● Experience with monitoring, logging, and alerting tools (e.g., New Relic, Datadog, CloudWatch) and a good grasp of observability.

● A strong automation mindset and genuine interest in AIOps (e.g., n8n, AWS Bedrock, Python scripting).

● Practical, day-to-day use of AI tools in engineering work; today this is a must-have,not a nice-to-have.

● Awareness of security best practices (secure-by-design) and of cost optimization in the cloud.

● Experience troubleshooting, mitigating, and resolving issues in distributed systems.

● Good communication skills to convey technical concepts to both technical and non-technical stakeholders.

● A fail-fast, learn-fast attitude, with willingness to learn, experiment, and collaborate across teams

Something wrong with this posting?