- Location: Remote (GMT-3)
- Willing to relocate: no
- Technologies: Currently my focus is: General Linux troubleshooting, Chef, Ansible, Terraform, Terragrunt, Git/Github/Gitlab and their pipelines, Grafana, AWS, Python, Bash, documentation, Kubernetes and Openshift.
- R\u00e9sum\u00e9/CV: https://www.linkedin.com/in/eitch/
- Email: eitch at naovouler.com.br
I have 25+ years of experience using Linux and working as all these titles that are kind the same: BOFH, Support Engineer, Sysadmin, DevOps, Infrastructure specialist, SRE, Platform Engineer, etc. My main focus is configuration management and creating self-services for the company, along the default CI/CD workflows and monitoring of everyday. Check this page to see what I'm providing/working nowadays: https://www.eitch-consulting.com/services/
Also, If you want more information, you could schedule a meeting with me and I'll be glad to help you and show what I'm capable of. Satisfaction guaranteeed! :D"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (August 2026)"}},"_tags":["comment","author_eitchugo","story_49156682"],"author":"eitchugo","comment_text":"SEEKING CONTRACT WORK | System Administrator/SRE/DevOps/Platform Engineering
- Location: Remote (GMT-3)
- Willing to relocate: no
- Technologies: Currently my focus is: General Linux troubleshooting, Chef, Ansible, Terraform, Terragrunt, Git/Github/Gitlab and their pipelines, Grafana, AWS, Python, Bash, documentation, Kubernetes and Openshift.
- R\u00e9sum\u00e9/CV: https://www.linkedin.com/in/eitch/
- Email: eitch at naovouler.com.br
I have 25+ years of experience using Linux and working as all these titles that are kind the same: BOFH, Support Engineer, Sysadmin, DevOps, Infrastructure specialist, SRE, Platform Engineer, etc. My main focus is configuration management and creating self-services for the company, along the default CI/CD workflows and monitoring of everyday. Check this page to see what I'm providing/working nowadays: https://www.eitch-consulting.com/services/
Also, If you want more information, you could schedule a meeting with me and I'll be glad to help you and show what I'm capable of. Satisfaction guaranteeed! :D","created_at":"2026-08-05T16:53:33Z","created_at_i":1785948813,"objectID":"49185477","parent_id":49156682,"story_id":49156682,"story_title":"Ask HN: Who wants to be hired? (August 2026)","updated_at":"2026-08-05T16:54:36Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"Makau_Juan"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Senior DevOps / Platform Engineer
Location: Nairobi, Kenya
Remote: Yes
Willing to relocate: Yes
I harden Kubernetes supply chains: Cosign keyless image signing, SLSA provenance, SBOM generation (SPDX/CycloneDX), and dual-layer admission enforcement (Kyverno + OPA Gatekeeper/Ratify), enforced through GitOps delivery with ArgoCD on AWS EKS. I also run production platform work with HashiCorp Vault (secrets injection, least-privilege policies) and Terraform/Terragrunt for infra-as-code.
Repos:\n- musaumakau/supply-chain-security -- signs, attests, and enforces: blocks unsigned images at Kubernetes admission time\n- musaumakau/infrastructure-live -- Terragrunt-based multi-environment AWS deployments with OIDC auth and verified CI/CD pipelines\n- musaumakau/kyverno-policy-pack -- tested Kyverno policies for image signing/attestation with a JMESPath test framework
Wrote up the full supply chain pipeline here: https://medium.com/@Juan_Makau/securing-the-software-supply-...
R\u00e9sum\u00e9/CV: https://drive.google.com/file/d/1qd7pGaKwzHvlpWl4ntiWsfyRV4-...\nEmail: makaujuan@gmail.com\nGitHub: https://github.com/musaumakau\nLinkedIn: https://www.linkedin.com/in/juan-musau"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (August 2026)"}},"_tags":["comment","author_Makau_Juan","story_49156682"],"author":"Makau_Juan","comment_text":"Senior DevOps / Platform Engineer
Location: Nairobi, Kenya
Remote: Yes
Willing to relocate: Yes
I harden Kubernetes supply chains: Cosign keyless image signing, SLSA provenance, SBOM generation (SPDX/CycloneDX), and dual-layer admission enforcement (Kyverno + OPA Gatekeeper/Ratify), enforced through GitOps delivery with ArgoCD on AWS EKS. I also run production platform work with HashiCorp Vault (secrets injection, least-privilege policies) and Terraform/Terragrunt for infra-as-code.
Repos:\n- musaumakau/supply-chain-security -- signs, attests, and enforces: blocks unsigned images at Kubernetes admission time\n- musaumakau/infrastructure-live -- Terragrunt-based multi-environment AWS deployments with OIDC auth and verified CI/CD pipelines\n- musaumakau/kyverno-policy-pack -- tested Kyverno policies for image signing/attestation with a JMESPath test framework
Wrote up the full supply chain pipeline here: https://medium.com/@Juan_Makau/securing-the-software-supply-...
R\u00e9sum\u00e9/CV: https://drive.google.com/file/d/1qd7pGaKwzHvlpWl4ntiWsfyRV4-...\nEmail: makaujuan@gmail.com\nGitHub: https://github.com/musaumakau\nLinkedIn: https://www.linkedin.com/in/juan-musau","created_at":"2026-08-04T09:22:14Z","created_at_i":1785835334,"objectID":"49166139","parent_id":49156682,"story_id":49156682,"story_title":"Ask HN: Who wants to be hired? (August 2026)","updated_at":"2026-08-10T09:18:22Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"l5870uoo9y"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Location: Copenhagen, Denmark
Remote: Yes
Willing to relocate: No
Technologies: TypeScript, React, Next/Astro/Tanstack, Postgres/MySQL, devops, platform (CF/AWS/Linux), AI
R\u00e9sum\u00e9/CV: Tech lead and full-stack developer with 15+ years of experience planning, architecting, and building web and mobile products. I have spent most of my career inside international startups and scale-ups in Berlin and Copenhagen \u2014 leading teams, owning architecture decisions, and helping early-stage companies grow into successful businesses. Please see: https://www.lassetange.com
Email: contact@lassetange.com"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (August 2026)"}},"_tags":["comment","author_l5870uoo9y","story_49156682"],"author":"l5870uoo9y","comment_text":"Location: Copenhagen, Denmark
Remote: Yes
Willing to relocate: No
Technologies: TypeScript, React, Next/Astro/Tanstack, Postgres/MySQL, devops, platform (CF/AWS/Linux), AI
R\u00e9sum\u00e9/CV: Tech lead and full-stack developer with 15+ years of experience planning, architecting, and building web and mobile products. I have spent most of my career inside international startups and scale-ups in Berlin and Copenhagen \u2014 leading teams, owning architecture decisions, and helping early-stage companies grow into successful businesses. Please see: https://www.lassetange.com
Email: contact@lassetange.com","created_at":"2026-08-04T07:07:48Z","created_at_i":1785827268,"objectID":"49165216","parent_id":49156682,"story_id":49156682,"story_title":"Ask HN: Who wants to be hired? (August 2026)","updated_at":"2026-08-04T07:09:59Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"JKFSOM"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"DRIVE is essentially DORA metrics expanded into a broader engineering-management framework.
There are some sensible ideas in it, but it is not a major new technical concept. It is largely a repackaging of existing DevOps, platform-engineering, FinOps, security, and portfolio-management practices into a Cortex-branded operating model."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"DRIVE \u2013 Operational Excellence for AI-accelerated engineering"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://www.cortex.io/drive"}},"_tags":["comment","author_JKFSOM","story_48968067"],"author":"JKFSOM","comment_text":"DRIVE is essentially DORA metrics expanded into a broader engineering-management framework.
There are some sensible ideas in it, but it is not a major new technical concept. It is largely a repackaging of existing DevOps, platform-engineering, FinOps, security, and portfolio-management practices into a Cortex-branded operating model.","created_at":"2026-07-19T15:16:31Z","created_at_i":1784474191,"objectID":"48968918","parent_id":48968067,"story_id":48968067,"story_title":"DRIVE \u2013 Operational Excellence for AI-accelerated engineering","story_url":"https://www.cortex.io/drive","updated_at":"2026-07-19T15:19:35Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"dagnai"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"
Location: Poland (EU)\n Remote: Yes\n Willing to relocate: Open to discussion\n Technologies: Kubernetes (EKS/AKS/Rancher) , AWS, Azure, GCP , Terraform, Terragrunt, Helm, FluxCD, CI/CD (GitLab, GitHub Actions), AI-Assisted Engineering (Claude Code)\n R\u00e9sum\u00e9/CV: https://canva.link/obalqbzoml3wuny AND https://www.linkedin.com/in/dagnai/\n Email: dagnai (at) proton.me\nLooking for platform, DevOps, or infrastructure roles where I can drive automation, reliability, and architectural clarity."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (June 2026)"}},"_tags":["comment","author_dagnai","story_48357724"],"author":"dagnai","comment_text":"
Location: Poland (EU)\n Remote: Yes\n Willing to relocate: Open to discussion\n Technologies: Kubernetes (EKS/AKS/Rancher) , AWS, Azure, GCP , Terraform, Terragrunt, Helm, FluxCD, CI/CD (GitLab, GitHub Actions), AI-Assisted Engineering (Claude Code)\n R\u00e9sum\u00e9/CV: https://canva.link/obalqbzoml3wuny AND https://www.linkedin.com/in/dagnai/\n Email: dagnai (at) proton.me\nLooking for platform, DevOps, or infrastructure roles where I can drive automation, reliability, and architectural clarity.","created_at":"2026-06-14T09:25:43Z","created_at_i":1781429143,"objectID":"48525572","parent_id":48357724,"story_id":48357724,"story_title":"Ask HN: Who wants to be hired? (June 2026)","updated_at":"2026-06-14T09:28:55Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tenaka"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"
Location: Quebec, Canada\n Remote: Yes\n Willing to relocate: No\n Work authorization: US citizen and Canadian permanent resident. No US visa sponsorship required.\n Technologies: AWS, GCP, Linux, Docker, IaC (Terraform/Pulumi), CI/CD, GitHub Actions, Cloudflare, MySQL, PostgreSQL, PHP/Laravel, Vue, Sentry, New Relic, Grafana\nI focus on reliable production systems: cloud infrastructure, data center to cloud migrations, deployment automation, CI/CD pipelines, observability, incident reduction, cost optimization, and modernization of legacy platforms.
Recent work includes migrating servers and data from data center infrastructure to AWS, modernizing EC2/AMI infrastructure, moving traffic behind ALBs, performing PHP and MySQL version upgrades, improving deployment workflows, adding/cleaning up monitoring and alerting, and using Cloudflare Workers for edge caching and traffic reduction.
Looking for DevOps, Platform Engineering, SRE, Infrastructure Engineering, Cloud Engineering, or cloud automation roles.
R\u00e9sum\u00e9: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1H...
Email: michael@michaeldelle.com"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (June 2026)"}},"_tags":["comment","author_tenaka","story_48357724"],"author":"tenaka","comment_text":"
Location: Quebec, Canada\n Remote: Yes\n Willing to relocate: No\n Work authorization: US citizen and Canadian permanent resident. No US visa sponsorship required.\n Technologies: AWS, GCP, Linux, Docker, IaC (Terraform/Pulumi), CI/CD, GitHub Actions, Cloudflare, MySQL, PostgreSQL, PHP/Laravel, Vue, Sentry, New Relic, Grafana\nI focus on reliable production systems: cloud infrastructure, data center to cloud migrations, deployment automation, CI/CD pipelines, observability, incident reduction, cost optimization, and modernization of legacy platforms.
Recent work includes migrating servers and data from data center infrastructure to AWS, modernizing EC2/AMI infrastructure, moving traffic behind ALBs, performing PHP and MySQL version upgrades, improving deployment workflows, adding/cleaning up monitoring and alerting, and using Cloudflare Workers for edge caching and traffic reduction.
Looking for DevOps, Platform Engineering, SRE, Infrastructure Engineering, Cloud Engineering, or cloud automation roles.
R\u00e9sum\u00e9: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1H...
Email: michael@michaeldelle.com","created_at":"2026-06-08T15:48:42Z","created_at_i":1780933722,"objectID":"48446920","parent_id":48357724,"story_id":48357724,"story_title":"Ask HN: Who wants to be hired? (June 2026)","updated_at":"2026-06-09T02:10:50Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"aspectop"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Location: India
Remote: Yes
Willing to relocate: Yes
Technologies: AWS, Python, TypeScript, FastAPI, Next.js, PostgreSQL, Terraform, Docker, Cloud Security
Resume: https://drive.google.com/file/d/19od48rlgRadrIrUGosrloe1LctC...
GitHub: https://github.com/theanshsonkar
I\u2019m a CS student who spends most of his time building cloud infrastructure and security tools.
I have built Emfirge, A Cloud Infrastructure Reasoning platform that helps teams understand attack paths, blast radius, risky configurations, before they deploy the infra and how to fix them.
I also built Carto, an open-source tool that helps AI agents understand codebases. It maps architecture, detects domains, traces dependencies, and shows what parts of a system might be affected by a change. It's giving AI the ability to think architecturally.
I have been working on cloud infrastructure, security, developer tools, DevOps, platform engineering, and backend system from the past 2 years. Also got seleced in Accelerator program Canopy by Founders Inc.
Looking for internships, research opportunities , or full time opportunities where I can contribute to infrastructure, security, or developer tooling."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (June 2026)"}},"_tags":["comment","author_aspectop","story_48357724"],"author":"aspectop","comment_text":"Location: India
Remote: Yes
Willing to relocate: Yes
Technologies: AWS, Python, TypeScript, FastAPI, Next.js, PostgreSQL, Terraform, Docker, Cloud Security
Resume: https://drive.google.com/file/d/19od48rlgRadrIrUGosrloe1LctC...
GitHub: https://github.com/theanshsonkar
I\u2019m a CS student who spends most of his time building cloud infrastructure and security tools.
I have built Emfirge, A Cloud Infrastructure Reasoning platform that helps teams understand attack paths, blast radius, risky configurations, before they deploy the infra and how to fix them.
I also built Carto, an open-source tool that helps AI agents understand codebases. It maps architecture, detects domains, traces dependencies, and shows what parts of a system might be affected by a change. It's giving AI the ability to think architecturally.
I have been working on cloud infrastructure, security, developer tools, DevOps, platform engineering, and backend system from the past 2 years. Also got seleced in Accelerator program Canopy by Founders Inc.
Looking for internships, research opportunities , or full time opportunities where I can contribute to infrastructure, security, or developer tooling.","created_at":"2026-06-01T19:12:36Z","created_at_i":1780341156,"objectID":"48361269","parent_id":48357724,"story_id":48357724,"story_title":"Ask HN: Who wants to be hired? (June 2026)","updated_at":"2026-06-02T06:08:51Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"jun-uen0"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Location: Japan (currently in Thailand, GMT+7)
Remote: Yes
Willing to relocate: No
Technologies: AWS, GCP, Terraform, Ansible, CloudFormation, Docker, Kubernetes, ECS Fargate, Lambda, Python, Bash, Go, TypeScript, Next.js, C#, Java (Apache Beam), GitLab CI/CD, GitHub Actions, Cloud Spanner, BigQuery, GCP Dataflow, RDS, Aurora, DocumentDB, Redis, Prometheus, Grafana, CloudWatch, JP1, WAF, Claude Code
R\u00e9sum\u00e9/CV: https://junueno.dev/resume.html
PDF: https://junueno.dev/resume.pdf
LLM-friendly: https://junueno.dev/llms.txt
Email: hello@junueno.dev
GitHub: github.com/jun-uen0
LinkedIn: linkedin.com/in/jun-uen0
Senior Cloud Infrastructure Engineer with 6+ years across backend, AWS infrastructure, and FinOps. Realized 30-40% AWS cost reduction. Translates executive intent into infrastructure decisions and surfaces platform constraints back to the C-suite. Sole inventor of a 0-RTT VPN handshake (USPTO pending). Currently expanding into Cloud Security architecture.
Sole CI/CD owner for a major Japanese megabank's web platform at Deloitte (Next.js + Sitecore on AWS ECS, GitLab CI/CD). Built GCP Dataflow ETL pipelines with Java and Apache Beam for a connected-vehicle program. Built AI-augmented infrastructure operations on Claude Code, delivering one engineer-year of capacity in production ops. DDoS mitigation 3x including SYN-flood, root-cause analysis through WAF deployment.
Looking for: ~60-80h / month additional engagement alongside my current role, async-friendly. SRE / DevOps / Platform Engineer / Security Engineer / Technical Advisor. Rate negotiable by scope and engagement length; reach out via email."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (June 2026)"}},"_tags":["comment","author_jun-uen0","story_48357724"],"author":"jun-uen0","comment_text":"Location: Japan (currently in Thailand, GMT+7)
Remote: Yes
Willing to relocate: No
Technologies: AWS, GCP, Terraform, Ansible, CloudFormation, Docker, Kubernetes, ECS Fargate, Lambda, Python, Bash, Go, TypeScript, Next.js, C#, Java (Apache Beam), GitLab CI/CD, GitHub Actions, Cloud Spanner, BigQuery, GCP Dataflow, RDS, Aurora, DocumentDB, Redis, Prometheus, Grafana, CloudWatch, JP1, WAF, Claude Code
R\u00e9sum\u00e9/CV: https://junueno.dev/resume.html
PDF: https://junueno.dev/resume.pdf
LLM-friendly: https://junueno.dev/llms.txt
Email: hello@junueno.dev
GitHub: github.com/jun-uen0
LinkedIn: linkedin.com/in/jun-uen0
Senior Cloud Infrastructure Engineer with 6+ years across backend, AWS infrastructure, and FinOps. Realized 30-40% AWS cost reduction. Translates executive intent into infrastructure decisions and surfaces platform constraints back to the C-suite. Sole inventor of a 0-RTT VPN handshake (USPTO pending). Currently expanding into Cloud Security architecture.
Sole CI/CD owner for a major Japanese megabank's web platform at Deloitte (Next.js + Sitecore on AWS ECS, GitLab CI/CD). Built GCP Dataflow ETL pipelines with Java and Apache Beam for a connected-vehicle program. Built AI-augmented infrastructure operations on Claude Code, delivering one engineer-year of capacity in production ops. DDoS mitigation 3x including SYN-flood, root-cause analysis through WAF deployment.
Looking for: ~60-80h / month additional engagement alongside my current role, async-friendly. SRE / DevOps / Platform Engineer / Security Engineer / Technical Advisor. Rate negotiable by scope and engagement length; reach out via email.","created_at":"2026-06-01T15:02:02Z","created_at_i":1780326122,"objectID":"48357749","parent_id":48357724,"story_id":48357724,"story_title":"Ask HN: Who wants to be hired? (June 2026)","updated_at":"2026-06-01T15:07:36Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tenaka"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"I\u2019m a Senior DevOps / Platform Engineer with about 8 years focused on infrastructure, and a 15 year background in PHP before that. I\u2019ve spent time on both the application and infrastructure sides of production systems, which helps when debugging or designing changes. Over the years I\u2019ve moved deeper into cloud infrastructure, CI/CD, and reliability work - mostly trying to eliminate recurring failure points instead of layering on quick fixes. I care a lot about long-term system health and building platforms that stay stable as they grow.
Location: Montreal, QC, Canada\n Remote: Yes. Open to hybrid\n Willing to relocate: No\n Technologies:\n - Infrastructure & Cloud: AWS, GCP, Terraform, Vagrant, Ansible, Packer\n - CI/CD & Automation: Jenkins, Bitbucket Cloud, CI/CD, Git, SVN\n - Programming & Scripting: Python, Bash, PHP, JavaScript, HTML, CSS\n - Testing & Quality: PHPUnit, Behat, Selenium\n - Databases & Cache: MySQL, Redis, Memcache\n - Networking & Security: Nginx, Apache, Cloudflare (WAF, Workers, Zero Trust)\n R\u00e9sum\u00e9/CV: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1Hy0cznC-BnFQ8biN_nGI/edit?usp=sharing\n Email: michael@michaeldelle.com Location: Montreal, QC, Canada\n Remote: Yes. Open to hybrid\n Willing to relocate: No\n Technologies:\n - Infrastructure & Cloud: AWS, GCP, Terraform, Vagrant, Ansible, Packer\n - CI/CD & Automation: Jenkins, Bitbucket Cloud, CI/CD, Git, SVN\n - Programming & Scripting: Python, Bash, PHP, JavaScript, HTML, CSS\n - Testing & Quality: PHPUnit, Behat, Selenium\n - Databases & Cache: MySQL, Redis, Memcache\n - Networking & Security: Nginx, Apache, Cloudflare (WAF, Workers, Zero Trust)\n R\u00e9sum\u00e9/CV: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1Hy0cznC-BnFQ8biN_nGI/edit?usp=sharing\n Email: michael@michaeldelle.comRemote: Only. Open-minded to occasional travel.
Willing to relocate: No
Technologies: Python, Postgres, Flask, Containers, k8s, Ansible, Terraform, Helm, Linux, various clouds. Currently learning Rust. Etc...
Resume/CV: https://www.linkedin.com/in/kurtismullins or https://www.kurtismullins.com (WIP)
Email: hire@kurtismullins.com
18 Years Web, SaaS, Full-Stack, Backend, and SRE/DevOps/Platform Engineering.
Looking for freelance clients/projects and part-time opportunities.
Would love to work with universities, research institutes, public good non-profits, and so forth but open to working with all kinds of wonderful people!
Work-life balance is my goal over getting rich; if you support my lifestyle then I am happy to reciprocate with my time & skills.
At home, you can find me homesteading and exploring merging tech knowledge with the natural, real world. Currently refreshing my old electronics skills to build sensors and automation systems for various projects around the house (e.g. growing food, rain water collection, etc..)
I have recently traveled to Boston a few times (its ~3 hours by train) and its amazing! Would love to make some connections down there as well. I can't come down every day but am open-minded to dropping in every once in a while.
I also really want to check out MIT (swap meet & library!), FSF, and all of this super cool culture in Boston that was too far away when I used to live in Ohio.
Thanks!"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (May 2026)"}},"_tags":["comment","author_pigsinzen","story_47975570"],"author":"pigsinzen","comment_text":"Location: Maine (USA)
Remote: Only. Open-minded to occasional travel.
Willing to relocate: No
Technologies: Python, Postgres, Flask, Containers, k8s, Ansible, Terraform, Helm, Linux, various clouds. Currently learning Rust. Etc...
Resume/CV: https://www.linkedin.com/in/kurtismullins or https://www.kurtismullins.com (WIP)
Email: hire@kurtismullins.com
18 Years Web, SaaS, Full-Stack, Backend, and SRE/DevOps/Platform Engineering.
Looking for freelance clients/projects and part-time opportunities.
Would love to work with universities, research institutes, public good non-profits, and so forth but open to working with all kinds of wonderful people!
Work-life balance is my goal over getting rich; if you support my lifestyle then I am happy to reciprocate with my time & skills.
At home, you can find me homesteading and exploring merging tech knowledge with the natural, real world. Currently refreshing my old electronics skills to build sensors and automation systems for various projects around the house (e.g. growing food, rain water collection, etc..)
I have recently traveled to Boston a few times (its ~3 hours by train) and its amazing! Would love to make some connections down there as well. I can't come down every day but am open-minded to dropping in every once in a while.
I also really want to check out MIT (swap meet & library!), FSF, and all of this super cool culture in Boston that was too far away when I used to live in Ohio.
Thanks!","created_at":"2026-05-02T14:54:40Z","created_at_i":1777733680,"objectID":"47986932","parent_id":47975570,"story_id":47975570,"story_title":"Ask HN: Who wants to be hired? (May 2026)","updated_at":"2026-05-02T14:57:44Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"evaneykelen"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Return | REMOTE | DevOps / Platform engineer | Full-time
Return (https://return.energy) is hiring a DevOps engineer who will build and run the infrastructure behind platforms that accelerate the transition to carbon-free energy. Return's main activity is building and operating industrial-size Battery Energy Storage Systems. Our operations are located in the Netherlands, Germany, Belgium, and Spain. You will be making a measurable (country-level) impact on the transition to renewable energy. Return recently raised \u20ac300M to support its growth.
While we employ over 120 people, Return's technical team is still small (15 people). Our platform automates processes in energy storage, monitoring, market optimization, sales, project management, procurement, construction, and customer service. Behind it sits a mix of EU cloud and on-site compute at our battery sites, with strict uptime and security requirements.
During the first four years of operation, we laid the foundation for our platforms, and we are ready to scale up. This is why we are looking for an experienced DevOps engineer who can own the full picture: cloud environments, self-hosted infrastructure at our BESS sites, and the operations centers in Amsterdam and Eindhoven from which we run the fleet.
Your primary focus will be to design, automate, and operate the infrastructure that our virtual battery platform runs on. That means EU-only cloud providers for application workloads, hardened on-premise setups at our sites, and the connectivity in between. You will be the person who decides what gets deployed where, and who makes sure it stays up and stays secure.
https://jobs.polymer.co/return/39863"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who is hiring? (May 2026)"}},"_tags":["comment","author_evaneykelen","story_47975571"],"author":"evaneykelen","children":[47997362],"comment_text":"Return | REMOTE | DevOps / Platform engineer | Full-time
Return (https://return.energy) is hiring a DevOps engineer who will build and run the infrastructure behind platforms that accelerate the transition to carbon-free energy. Return's main activity is building and operating industrial-size Battery Energy Storage Systems. Our operations are located in the Netherlands, Germany, Belgium, and Spain. You will be making a measurable (country-level) impact on the transition to renewable energy. Return recently raised \u20ac300M to support its growth.
While we employ over 120 people, Return's technical team is still small (15 people). Our platform automates processes in energy storage, monitoring, market optimization, sales, project management, procurement, construction, and customer service. Behind it sits a mix of EU cloud and on-site compute at our battery sites, with strict uptime and security requirements.
During the first four years of operation, we laid the foundation for our platforms, and we are ready to scale up. This is why we are looking for an experienced DevOps engineer who can own the full picture: cloud environments, self-hosted infrastructure at our BESS sites, and the operations centers in Amsterdam and Eindhoven from which we run the fleet.
Your primary focus will be to design, automate, and operate the infrastructure that our virtual battery platform runs on. That means EU-only cloud providers for application workloads, hardened on-premise setups at our sites, and the connectivity in between. You will be the person who decides what gets deployed where, and who makes sure it stays up and stays secure.
https://jobs.polymer.co/return/39863","created_at":"2026-05-01T16:36:08Z","created_at_i":1777653368,"objectID":"47976769","parent_id":47975571,"story_id":47975571,"story_title":"Ask HN: Who is hiring? (May 2026)","updated_at":"2026-05-03T14:37:33Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"wutwutwat"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"It's not just low level, in most cases, it's also overkill.
Most companies aren't "web scale" \u2122 and don't need an orchestrator built for google level elasticity, they need a vm autoscaling group if anything.
Most apps don't need such granular control over fs access, network policies, root access, etc, they need `ufw allow 80 && ufw enable`
Most apps don't need a 15 stage, docker layer caching optimized, archive promotion build pipeline that takes 30 minutes to get a copy change shipped to prod, they need a `git clone me@github.com:me/mine.git release_01 && ln -s release_01 /var/www/me/mine/current`
This is coming from someone who has had roles both as a backend product engineer and as a devops/platform engineer, who has been around long enough to remember "deploy" to prod was eclipse ftping php files straight to the prod server on file save. I manage clusters for a living for companies that went full k8s and never should have gone full k8s. ECS would have worked for 99% of these apps, if they even needed that.
Just like the js ecosystem went bat shit insane until things started to swing back towards sanity and people started to trim the needless bloat, the same is coming or due for the overcomplexity of devops/backend deployments"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"I am building a cloud"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://crawshaw.io/blog/building-a-cloud"}},"_tags":["comment","author_wutwutwat","story_47872324"],"author":"wutwutwat","children":[47875677,47890997],"comment_text":"It's not just low level, in most cases, it's also overkill.
Most companies aren't "web scale" \u2122 and don't need an orchestrator built for google level elasticity, they need a vm autoscaling group if anything.
Most apps don't need such granular control over fs access, network policies, root access, etc, they need `ufw allow 80 && ufw enable`
Most apps don't need a 15 stage, docker layer caching optimized, archive promotion build pipeline that takes 30 minutes to get a copy change shipped to prod, they need a `git clone me@github.com:me/mine.git release_01 && ln -s release_01 /var/www/me/mine/current`
This is coming from someone who has had roles both as a backend product engineer and as a devops/platform engineer, who has been around long enough to remember "deploy" to prod was eclipse ftping php files straight to the prod server on file save. I manage clusters for a living for companies that went full k8s and never should have gone full k8s. ECS would have worked for 99% of these apps, if they even needed that.
Just like the js ecosystem went bat shit insane until things started to swing back towards sanity and people started to trim the needless bloat, the same is coming or due for the overcomplexity of devops/backend deployments","created_at":"2026-04-23T11:15:16Z","created_at_i":1776942916,"objectID":"47874351","parent_id":47874237,"story_id":47872324,"story_title":"I am building a cloud","story_url":"https://crawshaw.io/blog/building-a-cloud","updated_at":"2026-04-24T17:42:33Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"SOLAR_FIELDS"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Indeed. The use case is like this: I'm a Devops/Platform/SRE/Infra/WhateverYouCallAWSAdminInYourOrg at BigCorp and end users are asking me to use software XYZ. It's on the AWS Marketplace. I have two choices. I could either
1. Go through a 1-2 month procurement process where I have to deal with not only the vendor's sales team on who I'm buying from but also probably multiple teams in my BigCorp. Vendor sales team wants to feel relevant and so I'm sitting in at least one meeting where I'm telling them I just want to buy your shit make it as fast as possible. But then the people in my BigCorp likely not only don't understand why the software is necessary, but need to feel relevant and as such will make me fight through bureaucratic hurdles. I have to get compliance involved. Finance involved. If there's a procurement team I have to get them involved. Probably there's a security questionnaire that my bigcorp's security team uses. I have to send that to the vendor's sales people. They have to send it to their security folks. Security folks on their end have to complete it and send it back. I have to send approvals up the chain on my end, after I've successfully convinced some clueless nontechnical user why software XYZ is important and no, the shit half baked thing we already have doesn't work.
OR alternatively:
2. I can go to the AWS marketplace, click a button, and now my AWS bill goes up X thousands of dollars per month and none of the bullshit from 1 is required. Because AWS is already an approved vendor. Everyone except perhaps someone monitoring the AWS bill for large increases is happy and doesn't care (well, maybe the security team does, but hopefully they aren't tattling on you to the procurement people who have nothing to do and want to stick their fingers in the process and we can make that process go quick), and I just need to tell that person that we are doing it.
It's not always the exact narrative I just laid out, but the gist of it is pretty much procurement at every bigcorp."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Changes to GitHub Copilot individual plans"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://github.blog/news-insights/company-news/changes-to-github-copilot-individual-plans/"}},"_tags":["comment","author_SOLAR_FIELDS","story_47838508"],"author":"SOLAR_FIELDS","comment_text":"Indeed. The use case is like this: I'm a Devops/Platform/SRE/Infra/WhateverYouCallAWSAdminInYourOrg at BigCorp and end users are asking me to use software XYZ. It's on the AWS Marketplace. I have two choices. I could either
1. Go through a 1-2 month procurement process where I have to deal with not only the vendor's sales team on who I'm buying from but also probably multiple teams in my BigCorp. Vendor sales team wants to feel relevant and so I'm sitting in at least one meeting where I'm telling them I just want to buy your shit make it as fast as possible. But then the people in my BigCorp likely not only don't understand why the software is necessary, but need to feel relevant and as such will make me fight through bureaucratic hurdles. I have to get compliance involved. Finance involved. If there's a procurement team I have to get them involved. Probably there's a security questionnaire that my bigcorp's security team uses. I have to send that to the vendor's sales people. They have to send it to their security folks. Security folks on their end have to complete it and send it back. I have to send approvals up the chain on my end, after I've successfully convinced some clueless nontechnical user why software XYZ is important and no, the shit half baked thing we already have doesn't work.
OR alternatively:
2. I can go to the AWS marketplace, click a button, and now my AWS bill goes up X thousands of dollars per month and none of the bullshit from 1 is required. Because AWS is already an approved vendor. Everyone except perhaps someone monitoring the AWS bill for large increases is happy and doesn't care (well, maybe the security team does, but hopefully they aren't tattling on you to the procurement people who have nothing to do and want to stick their fingers in the process and we can make that process go quick), and I just need to tell that person that we are doing it.
It's not always the exact narrative I just laid out, but the gist of it is pretty much procurement at every bigcorp.","created_at":"2026-04-22T15:31:44Z","created_at_i":1776871904,"objectID":"47865060","parent_id":47862074,"story_id":47838508,"story_title":"Changes to GitHub Copilot individual plans","story_url":"https://github.blog/news-insights/company-news/changes-to-github-copilot-individual-plans/","updated_at":"2026-04-24T20:01:15Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tenaka"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"I\u2019m a Senior DevOps / Platform Engineer with about 8 years focused on infrastructure, and a 15 year background in PHP before that. I\u2019ve spent time on both the application and infrastructure sides of production systems, which helps when debugging or designing changes. Over the years I\u2019ve moved deeper into cloud infrastructure, CI/CD, and reliability work \u2014 mostly trying to eliminate recurring failure points instead of layering on quick fixes. I care a lot about long-term system health and building platforms that stay stable as they grow.
Location: Montreal, QC, Canada\n Remote: Yes. Open to hybrid\n Willing to relocate: No\n Technologies:\n - Infrastructure & Cloud: AWS, GCP, Terraform, Vagrant, Ansible, Packer\n - CI/CD & Automation: Jenkins, Bitbucket Cloud, CI/CD, Git, SVN\n - Programming & Scripting: Python, Bash, PHP, JavaScript, HTML, CSS\n - Testing & Quality: PHPUnit, Behat, Selenium\n - Databases & Cache: MySQL, Redis, Memcache\n - Networking & Security: Nginx, Apache, Cloudflare (WAF, Workers, Zero Trust)\n R\u00e9sum\u00e9/CV: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1Hy0cznC-BnFQ8biN_nGI/edit?usp=sharing\n Email: michael@michaeldelle.com Location: Montreal, QC, Canada\n Remote: Yes. Open to hybrid\n Willing to relocate: No\n Technologies:\n - Infrastructure & Cloud: AWS, GCP, Terraform, Vagrant, Ansible, Packer\n - CI/CD & Automation: Jenkins, Bitbucket Cloud, CI/CD, Git, SVN\n - Programming & Scripting: Python, Bash, PHP, JavaScript, HTML, CSS\n - Testing & Quality: PHPUnit, Behat, Selenium\n - Databases & Cache: MySQL, Redis, Memcache\n - Networking & Security: Nginx, Apache, Cloudflare (WAF, Workers, Zero Trust)\n R\u00e9sum\u00e9/CV: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1Hy0cznC-BnFQ8biN_nGI/edit?usp=sharing\n Email: michael@michaeldelle.com- ETH Watchtower: a real-time EVM monitoring tool with heuristics and classification of contracts and transactions: https://ethwatchtower.xyz
- P2P SSL VPN provider/consumer tools using a blockchain as announcement and settlement layer: https://github.com/rnts08/blockchain-vpn
- OrdexNetwork: https://ordexnetwork.org, I've built https://ordexswap.online and https://ordexswap.online/wallet/ as well as an Umbrel variant of a self-hosted wallet.
- Waya Wolf Coin v3: Helped the team to compile binaries for linux, and modernizing the libraries: https://github.com/rnts08/WWC3-Linux-binaries / https://github.com/Waya-Wolf/WWC3
- Low Cap Exchange algorithmic trading bots with machine learning and automatic ghost trading, because I wanted to see what the most common shapes are on smaller exchanges: https://github.com/rnts08/low-cap-exchange-trading-bot
However, I am really looking for Sr. DevOps/Platform Eng/SRE/System/Network Admin/Infra Engineering or similar, full-time or contract work, see https://timhbergstrom.pro for contact details."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: What Are You Working On? (April 2026)"}},"_tags":["comment","author_rnts08","story_47741527"],"author":"rnts08","comment_text":"Since blacksmith labs and phoenix ai - the ai assisted automotive r&d, security and compliance engineering tool has been on the backburner for a while, I've been helping a couple of blockchain projects and built some tools, besides tinkering with my real-time EVM contract and transaction heuristics and classification engine.
- ETH Watchtower: a real-time EVM monitoring tool with heuristics and classification of contracts and transactions: https://ethwatchtower.xyz
- P2P SSL VPN provider/consumer tools using a blockchain as announcement and settlement layer: https://github.com/rnts08/blockchain-vpn
- OrdexNetwork: https://ordexnetwork.org, I've built https://ordexswap.online and https://ordexswap.online/wallet/ as well as an Umbrel variant of a self-hosted wallet.
- Waya Wolf Coin v3: Helped the team to compile binaries for linux, and modernizing the libraries: https://github.com/rnts08/WWC3-Linux-binaries / https://github.com/Waya-Wolf/WWC3
- Low Cap Exchange algorithmic trading bots with machine learning and automatic ghost trading, because I wanted to see what the most common shapes are on smaller exchanges: https://github.com/rnts08/low-cap-exchange-trading-bot
However, I am really looking for Sr. DevOps/Platform Eng/SRE/System/Network Admin/Infra Engineering or similar, full-time or contract work, see https://timhbergstrom.pro for contact details.","created_at":"2026-04-13T05:16:23Z","created_at_i":1776057383,"objectID":"47747864","parent_id":47741527,"story_id":47741527,"story_title":"Ask HN: What Are You Working On? (April 2026)","updated_at":"2026-04-13T05:39:31Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"Uncle-iroh"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Location: Texas (open to relocation anywhere in US)
Remote: Yes
Willing to relocate: Yes
Technologies: AWS, Kubernetes, Helm, Terraform, Ansible, GitHub Actions, Docker, Linux, Python, Bash, Prometheus, Grafana\nR\u00e9sum\u00e9/CV: https://drive.google.com/file/d/1sjewwU4Vjs9rXhkoHNvNIrJt1ZC...
Email: dm2606700@gmail.com
Brief: DevOps/Platform Engineer focused on automation. Cut deployment times 75% (20min to 5min) by implementing a GitHub Actions CI/CD pipeline for a K3s cluster. I build production ready IaC with Terraform and manage containerized workloads with Helm. Zero hand holding required on the Linux/CLI side."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (April 2026)"}},"_tags":["comment","author_Uncle-iroh","story_47601858"],"author":"Uncle-iroh","comment_text":"Location: Texas (open to relocation anywhere in US)
Remote: Yes
Willing to relocate: Yes
Technologies: AWS, Kubernetes, Helm, Terraform, Ansible, GitHub Actions, Docker, Linux, Python, Bash, Prometheus, Grafana\nR\u00e9sum\u00e9/CV: https://drive.google.com/file/d/1sjewwU4Vjs9rXhkoHNvNIrJt1ZC...
Email: dm2606700@gmail.com
Brief: DevOps/Platform Engineer focused on automation. Cut deployment times 75% (20min to 5min) by implementing a GitHub Actions CI/CD pipeline for a K3s cluster. I build production ready IaC with Terraform and manage containerized workloads with Helm. Zero hand holding required on the Linux/CLI side.","created_at":"2026-04-09T00:28:31Z","created_at_i":1775694511,"objectID":"47697885","parent_id":47601858,"story_id":47601858,"story_title":"Ask HN: Who wants to be hired? (April 2026)","updated_at":"2026-04-14T08:27:50Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"TamasSzigeti"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Backstory: At work I had to build an AI pipeline to run millions of prompts. First I just put the prompts into string consts and integrated directly with api, chaining one run onto the output of another \u2013 but it quickly became a maintenance nightmare. Iterating on prompts, testing them over datasets, experimenting with different chaining did not fit into the regular sdlc and running them at our scale was quite difficult as most of the time is spent on waiting for the api response while holding on to dear server resources.
So we started using PromptLayer in order for the prompt engineer to build evals there, edit-improve prompts outside the code and chaining them together however he likes, and we were also running them on their infra. But the UI was cumbersome and the latency was disappointing and given other issues and having found no better alternative it triggered me into starting to build a better alternative.
One year and countless nights and weekends later I have what I like to call an IDE for AI, or more like a full DevOps platform as it goes from development of prompts and workflows through testing them all the way through the running infra. I tried to squeeze every nanosecond out of the stack, hyper-optimising every part of it to have as little overhead above the AI calls themselves as possible.
Docs: https://docs.promptjuggler.com
App: https://promptjuggler.com
I built this with love and it's my first post here, so please be gentle (:"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: PromptJuggler \u2013 A dev env and runner for prompts, workflows, agents"},"url":{"matchLevel":"none","matchedWords":[],"value":"https://promptjuggler.com"}},"_tags":["story","author_TamasSzigeti","story_47679019","show_hn"],"author":"TamasSzigeti","created_at":"2026-04-07T18:01:29Z","created_at_i":1775584889,"num_comments":0,"objectID":"47679019","points":3,"story_id":47679019,"story_text":"Backstory: At work I had to build an AI pipeline to run millions of prompts. First I just put the prompts into string consts and integrated directly with api, chaining one run onto the output of another \u2013 but it quickly became a maintenance nightmare. Iterating on prompts, testing them over datasets, experimenting with different chaining did not fit into the regular sdlc and running them at our scale was quite difficult as most of the time is spent on waiting for the api response while holding on to dear server resources.
So we started using PromptLayer in order for the prompt engineer to build evals there, edit-improve prompts outside the code and chaining them together however he likes, and we were also running them on their infra. But the UI was cumbersome and the latency was disappointing and given other issues and having found no better alternative it triggered me into starting to build a better alternative.
One year and countless nights and weekends later I have what I like to call an IDE for AI, or more like a full DevOps platform as it goes from development of prompts and workflows through testing them all the way through the running infra. I tried to squeeze every nanosecond out of the stack, hyper-optimising every part of it to have as little overhead above the AI calls themselves as possible.
Docs: https://docs.promptjuggler.com
App: https://promptjuggler.com
I built this with love and it's my first post here, so please be gentle (:","title":"Show HN: PromptJuggler \u2013 A dev env and runner for prompts, workflows, agents","updated_at":"2026-04-08T05:20:11Z","url":"https://promptjuggler.com"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"anon7000"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Yeah, I mean Deno\u2019s success is predicated on enterprises moving production apps from NodeJS to Deno. Node is extremely established and entrenched, and migrating the goddamn runtime of a large production server is not usually an easy project. If I have a 5-10 year old Node project, it might work well on Deno, but almost no one has the time to champion a migration when it just doesn\u2019t have that many benefits.
Yes, it comes with batteries included, but a big node project already has setups handling things like testing, linting, formatting, and dependencies. Moving to Deno for any of those might actually be easy, but migrations in the JS ecosystem never end up being easy, so people who could sway the company to change tools don\u2019t have the appetite to tell leadership about migration projects with minimal upside and unknown duration. And under a startup with an unknown future.
NodeJS succeeded at undermining existing server toolchains, because web devs were easily sold on writing JS for their servers, so tons of successful startups built with Node, and when Node got pretty well established, it was easier to adopt for greenfield projects in the enterprise.
Deno is Node, but better. So it\u2019s not giving a whole market of devs access to a tool that is way easier to write for. It\u2019s marginally easier to manage and you could maybe drop some other toolchain dependencies. But again, those toolchain things are automated/hidden away from developers directly\u2026 like they don\u2019t care we use eslint, they just care CI catches problems before they hit prod and that the linter throws an error early in the process. It\u2019s already easy for them to run locally. So it\u2019s not like Deno lint changes anything about the dev user experience, it just changes what DevOps/platform teams have to manage."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"404 Deno CEO not found"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://dbushell.com/2026/03/20/denos-decline-and-layoffs/"}},"_tags":["comment","author_anon7000","story_47467746"],"author":"anon7000","children":[47476421],"comment_text":"Yeah, I mean Deno\u2019s success is predicated on enterprises moving production apps from NodeJS to Deno. Node is extremely established and entrenched, and migrating the goddamn runtime of a large production server is not usually an easy project. If I have a 5-10 year old Node project, it might work well on Deno, but almost no one has the time to champion a migration when it just doesn\u2019t have that many benefits.
Yes, it comes with batteries included, but a big node project already has setups handling things like testing, linting, formatting, and dependencies. Moving to Deno for any of those might actually be easy, but migrations in the JS ecosystem never end up being easy, so people who could sway the company to change tools don\u2019t have the appetite to tell leadership about migration projects with minimal upside and unknown duration. And under a startup with an unknown future.
NodeJS succeeded at undermining existing server toolchains, because web devs were easily sold on writing JS for their servers, so tons of successful startups built with Node, and when Node got pretty well established, it was easier to adopt for greenfield projects in the enterprise.
Deno is Node, but better. So it\u2019s not giving a whole market of devs access to a tool that is way easier to write for. It\u2019s marginally easier to manage and you could maybe drop some other toolchain dependencies. But again, those toolchain things are automated/hidden away from developers directly\u2026 like they don\u2019t care we use eslint, they just care CI catches problems before they hit prod and that the linter throws an error early in the process. It\u2019s already easy for them to run locally. So it\u2019s not like Deno lint changes anything about the dev user experience, it just changes what DevOps/platform teams have to manage.","created_at":"2026-03-21T20:42:01Z","created_at_i":1774125721,"objectID":"47471081","parent_id":47468403,"story_id":47467746,"story_title":"404 Deno CEO not found","story_url":"https://dbushell.com/2026/03/20/denos-decline-and-layoffs/","updated_at":"2026-03-22T11:30:16Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"christopherAs"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Hi HN,
Most DevOps tools are good at observing \u2014 they collect data, surface metrics, and send alerts. But the actual decision and action still falls on the engineer.
So I built Riventa.Dev \u2014 a DevOps platform where the AI (Riv) doesn't just surface data, it acts.
What Riv does today:\n- Automatic PR review on every push \u2014 no manual trigger, no GitHub Actions boilerplate\n- Predictive failure detection \u2014 catches patterns that historically cause prod failures\n- DORA metrics dashboard with real pipeline data (MTTR, Deployment Frequency, Change Failure Rate)\n- Security scanning: SAST, SBOM, dependency analysis \u2014 built in, not bolted on\n- Works with GitHub, GitLab, and Bitbucket
Built solo, from scratch, with a focus on keeping things simple for the end user.
What I'd love feedback on: Is the AI-first positioning clear? Where does the UX feel rough?
Free to try \u2014 no credit card required."},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: Riventa.Dev \u2013 AI-native DevOps that acts, not just alerts"},"url":{"matchLevel":"none","matchedWords":[],"value":"https://www.riventa.dev/"}},"_tags":["story","author_christopherAs","story_47351940","show_hn"],"author":"christopherAs","created_at":"2026-03-12T15:17:48Z","created_at_i":1773328668,"num_comments":0,"objectID":"47351940","points":3,"story_id":47351940,"story_text":"Hi HN,
Most DevOps tools are good at observing \u2014 they collect data, surface metrics, and send alerts. But the actual decision and action still falls on the engineer.
So I built Riventa.Dev \u2014 a DevOps platform where the AI (Riv) doesn't just surface data, it acts.
What Riv does today:\n- Automatic PR review on every push \u2014 no manual trigger, no GitHub Actions boilerplate\n- Predictive failure detection \u2014 catches patterns that historically cause prod failures\n- DORA metrics dashboard with real pipeline data (MTTR, Deployment Frequency, Change Failure Rate)\n- Security scanning: SAST, SBOM, dependency analysis \u2014 built in, not bolted on\n- Works with GitHub, GitLab, and Bitbucket
Built solo, from scratch, with a focus on keeping things simple for the end user.
What I'd love feedback on: Is the AI-first positioning clear? Where does the UX feel rough?
Free to try \u2014 no credit card required.","title":"Show HN: Riventa.Dev \u2013 AI-native DevOps that acts, not just alerts","updated_at":"2026-03-12T19:04:08Z","url":"https://www.riventa.dev/"}],"hitsPerPage":20,"nbHits":284,"nbPages":15,"page":0,"params":"query=%22devops+platform%22&advancedSyntax=true&analyticsTags=backend","processingTimeMS":4,"processingTimingsMS":{"_request":{"roundTrip":16},"afterFetch":{"format":{"highlighting":1,"total":2}},"fetch":{"scanning":2,"total":3},"total":4},"query":"\"devops platform\"","serverTimeMS":6}