> Markdown version of [/jobs/ext/1919594-platform-engineer-ii](https://www.wearedevelopers.com/jobs/ext/1919594-platform-engineer-ii). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Platform Engineer II - **Company:** FeXA LLC - **Location:** United States (Remote available) - **Experience:** Expert - **Salary:** $130,000.0 - $140,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Microsoft Azure, Continuous Integration, Data Infrastructure, Data Warehousing, Software Debugging, DevOps, Disaster Recovery, Domain Name System (DNS), Elasticsearch, Github, Identity and Access Management, Python (Programming Language), PostgreSQL, Performance Tuning, Ruby, Shell Script, Database Engines, Management of Software Versions, Load Balancing, Delivery Pipeline, Large Language Models, Infrastructure as Code (IaC), Amazon Virtual Private Cloud (VPC), Gitlab, Kubernetes, Information Technology, AWS Fargate, Terraform, Jenkins - **Published:** August 4, 2026 - **Apply:** https://app.dover.com/apply/Fexa/5fab4e91-ea6c-4a79-9602-57bdc7f63aae ## About the Role Platform Engineering owns AWS, CI/CD, and the platform our product runs on. We are a small, fast team building the function from the ground up: the standards, the automation, and the infrastructure. We run on Terraform, AWS (EKS, Fargate, Aurora Postgres), GitHub Actions and Jenkins, Jira, Confluence, and Slack, and we are AI-first in how we work., * Bachelor's degree in Computer Science, Engineering, or a related field with 5+ years of relevant experience, or an equivalent combination of education and 8+ years of professional experience in platform engineering, infrastructure, or DevOps., * 5+ years in platform engineering, infrastructure, or DevOps roles, with a proven track record of building internal tooling and Production support. * Strong hands-on experience across AWS infrastructure. * Advanced Terraform: composing and versioning reusable modules; remote state with locking and workspaces/backends; meta-arguments and dynamic blocks (for_each, count, dynamic); safe state operations and refactoring (import, moved blocks, targeted state changes); drift detection; and policy/testing in CI (e.g., Terratest, tflint, Sentinel or OPA). * Building and debugging CI/CD pipelines independently (GitHub Actions and/or Jenkins). * Container orchestration on EKS/Kubernetes and AWS Fargate. * GitOps workflows (e.g., ArgoCD). * Observability in practice: instrumenting services and building meaningful dashboards and alerts across metrics, logs, and APM. * Security fundamentals applied by default: least-privilege IAM, secrets handling, key and certificate rotation. * Strong proficiency with python and shell scripting to automate recurring work and build internal tooling. * Clear written and verbal communication - able to plan a piece of work, document the reasoning, and align with the team before building. * AWS certification, such as Solutions Architect Associate/Professional or SysOps/DevOps Engineer., We run a Kanban board with WIP limits and expect steady flow, not stale tickets. Our Definition of Done includes documentation and written Architecture Decisions, as we record our design decisions. We review each other's pull requests against a shared standard, take structured platform requests from other teams, and keep an eye on cloud cost as we build. Nice to have * Ruby or Postgres performance tuning experience. * FinOps or cloud-cost optimization: right-sizing, cost tagging, and reporting. * OpenSearch/Elasticsearch operation and migration. * Data warehouse / analytics infrastructure on AWS (Redshift, Glue, Step Functions). * Disaster recovery and backup/restore testing; exposure to RTO/RPO planning. * Experience migrating between CI/CD systems or source-control platforms, such as Jenkins to GitHub Actions or GitLab to GitHub. * Networking depth: VPC, DNS, load balancers, and WAF. * Leading or co-leading incident response and postmortems. * Experience on a small platform/DevOps team moving fast on multiple initiatives concurrently. * Building or operating AI/LLM backends on AWS, including Bedrock, agentic/tool-calling services, MCP servers, and vector stores. * Hands-on experience with Azure infrastructure. ## Description You own components and projects end-to-end, and you are ready to take on larger, more ambiguous problems. Given a goal, you design and deliver the "how" yourself with light oversight. On bigger, less-defined work, you shape the approach and contribute to the design. You will work within the team's technical direction and constraints, bringing a plan forward and aligning with the Director and team members before building. What you'll do * Infrastructure as Code (IaC): Author reusable Terraform modules that other engineers build on, and make changes confidently across our AWS infrastructure within our established conventions. * CI/CD Pipelines: Design, optimize, and standardize continuous integration and deployment pipelines to accelerate time-to-market. * Ownership: Own components and projects end-to-end, while taking on larger initiatives such as database engine migrations, cronjobs to EventBridge, or data warehouse infrastructure, shaping the approach with direction and support. * Architecture: Contribute to Architecture Decisions and help refine our Terraform and observability standards. * Observability: Instrument systems, build dashboards and alerts, and begin defining the observability strategy for the systems you work on. * Security & Compliance: Apply security by default, including least-privilege IAM, proper secrets handling, and key and certificate rotation. * Operations and Reliability: Carry a share of the team's day-to-day operational load alongside project work, including production support, escalations, maintenance, and keeping existing systems healthy. This role is not projects alone. * Collaboration: Write the runbooks that let others operate what you build, create documentation for both the team and the broader engineering organization, and help onboard and mentor newer engineers. On-call You will take part in the team's on-call rotation as an escalation point of contact. You will step in when first-line remediation and runbooks haven't resolved an incident, and you will drive the issue to resolution., * Ready to take ambiguous, larger problems from idea to delivery with direction. You will shape the approach and be accountable for the result. * Contributes to Architecture Decisions and design discussions, and communicates and plans clearly. * Proactively automates recurring work rather than absorbing it. * A reliable collaborator who reviews peers' pull requests and helps onboard and mentor newer engineers. * Flexibility to support scheduled off-hours deployments and critical maintenance windows. Working with AI At Fexa, AI isn't just a tool we're testing; it is foundational to how we build and scale. We expect engineers to weave AI deeply into their daily workflows, from architecting infrastructure and automating complex pipelines to rapid troubleshooting and documentation. You aren't just using LLMs; you are authoring custom skills, developing multi-agent workflows, and proactively sharing your prompt engineering breakthroughs to level up the entire team. We value the visible uplift in speed and quality that comes from an AI-augmented engineering culture. How we work ## Related Videos - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Coffee with Developers: David Heinemeier Hansson](https://www.wearedevelopers.com/videos/875-coffee-with-developers-david-heinemeier-hansson) - [Innovating Developer Tools with AI: Insights from GitHub Next](https://www.wearedevelopers.com/videos/1268-innovating-developer-tools-with-ai-insights-from-github-next) - [From DevOps to Scaled DevOps: How We’re Rebuilding Continuous Delivery as a Platform](https://www.wearedevelopers.com/videos/100018-from-devops-to-scaled-devops-how-we-re-rebuilding-continuous-delivery-as-a-platform) - [Platform Engineering vs. DevOps Why not both?](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) - [Coroutine explained yet again 60 years later](https://www.wearedevelopers.com/videos/690-coroutine-explained-yet-again-60-years-later) ## Related Articles - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [From Prototype to Production: Build AI Agents with This Free 4-Course Learning Path](https://www.wearedevelopers.com/magazine/655-from-prototype-to-production-build-ai-agents-with-this-free-4-course-learning-path) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)