Time since we first saw it
Day 136
Up longer than most. Similar jobs usually come down between day 1 and day 15.
From 1,376 similar postings that came down. Coming down is not always a hire.
United States
Open 4 months, first seen by us 136 days agoWork setup in the employer’s posting: RemoteFrom the employer’s posting
Employment type in the employer’s posting: Full-TimeFrom the employer’s posting
This role owns the platform that keeps Givzey secure, compliant, reliable, and scalable.
You'll partner closely with engineering, ML, and product to design the platform that powers everything from customer-facing APIs to LLM workflows running on Amazon Bedrock and SageMaker.
Design, build, and maintain our AWS infrastructure
Own our Infrastructure as Code strategy using Pulumi
Build and maintain deployment pipelines for applications and infrastructure
This role owns the platform that keeps Givzey secure, compliant, reliable, and scalable. You'll work across AWS infrastructure, Infrastructure as Code, CI/CD, AI services, observability, and developer tooling to make sure engineers spend their time building product instead of fighting deployments.
You'll partner closely with engineering, ML, and product to design the platform that powers everything from customer-facing APIs to LLM workflows running on Amazon Bedrock and SageMaker.
Cloud infrastructure Design, build, and maintain our AWS infrastructure Manage networking, IAM, compute, storage, databases, and security across environments
Infrastructure as Code Own our Infrastructure as Code strategy using Pulumi Build reusable infrastructure components and shared modules
CI/CD Build and maintain deployment pipelines for applications and infrastructure Improve release automation and deployment safety
5+ years building and operating production software systems
Experience building APIs and backend systems
Experience with some of the following is highly desirable:
Experience supporting AI or ML products
Strong experience with AWS in production environments
Experience designing Infrastructure as Code using Pulumi, Terraform, or CloudFormation
Open 4 monthsWe first saw this posting 136 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 136
Up longer than most. Similar jobs usually come down between day 1 and day 15.
From 1,376 similar postings that came down. Coming down is not always a hire.
3 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Experience building CI/CD pipelines using GitHub Actions - Strong Python experience - Experience building APIs and backend systems
About the role This role owns the platform that keeps Givzey secure, compliant, reliable, and scalable. You'll work across AWS infrastructure, Infrastructure as Code, CI/CD, AI services, observability, and developer tooling to make sure engineers spend their time building product instead of fighting deployments. You'll partner closely with engineering, ML, and product to design the platform that powers everything from customer-facing APIs to LLM workflows running on Amazon Bedrock and SageMaker.
Who thrives here You're the engineer who gets excited about replacing a manual deployment with a one-click pipeline, automating infrastructure instead of clicking around the AWS console, and designing systems that make the rest of engineering move faster. You think in terms of reliability, observability, automation, and repeatability.
Cloud infrastructure - Design, build, and maintain our AWS infrastructure - Manage networking, IAM, compute, storage, databases, and security across environments
- Build and maintain the infrastructure powering our AI systems - Work with services such as Amazon Bedrock, SageMaker, OpenSearch, and supporting AWS services - Support LLM evaluation pipelines, RAG infrastructure, vector search, and model deployment
- 5+ years building and operating production software systems - Strong experience with AWS in production environments - Experience designing Infrastructure as Code using Pulumi, Terraform, or CloudFormation
You should be comfortable working with technologies such as: - AWS (multi-account environments using AWS Organizations) - ECS
- ECS - Docker - IAM
- ECS - PostgreSQL - Redis
- PostgreSQL - Redis - New Relic or modern observability platforms
- RDS - S3 - Lambda
This role owns the platform that keeps Givzey secure, compliant, reliable, and scalable. You'll work across AWS infrastructure, Infrastructure as Code, CI/CD, AI services, observability, and developer tooling to make sure engineers spend their time building product instead of fighting deployments. You'll partner closely with engineering, ML, and product to design the platform that powers everything from customer-facing APIs to LLM workflows running on Amazon Bedrock and SageMaker. This is not a "keep the lights on" devops role. You'll actively shape how we deploy software, provision infrastructure, manage AI workloads, and scale the engineering organization.
You think in terms of reliability, observability, automation, and repeatability. You're comfortable wearing multiple hats. One morning you might be debugging IAM permissions. That afternoon you're building a Pulumi module, improving GitHub Actions, tuning ECS workloads, or helping an ML engineer deploy a SageMaker endpoint. What you'll do
- Amazon Bedrock - SageMaker - Vector databases
- Amazon Bedrock - SageMaker - OpenSearch
- Strong experience with AWS in production environments - Experience designing Infrastructure as Code using Pulumi, Terraform, or CloudFormation - Experience building CI/CD pipelines using GitHub Actions
- ML infrastructure - Dagster or similar orchestration platforms Working Style
- Pulumi experience - Dagster experience - Amazon Bedrock
Complete your application on givzey.breezy.hr. The employer’s form will show what is required.
Already applied? Track this application
Join the Future of Fundraising at Givzey!Givzey is one of the fastest-growing and most innovative technology companies serving the nonprofit sector, on a mission to unlock more generosity through AI-powered donor engagement. At the center of that innovation is Version2.ai, the world’s first Autonomous AI fundraisers—Virtual Engagement Officers (VEOs)—designed to independently manage donor engagement and generate revenue. Unlike traditional AI tools that simply make staff more efficient, VEOs expand fundraising capacity by acting as AI workers that operate donor portfolios, build relationships, and secure gifts on their own. In just three years, Givzey’s platform has already helped organizations raise $10M+ through autonomous engagement, including individual gifts as large as $100,000. Alongside this breakthrough technology, Givzey’s Gift Agreement Platform modernizes the multi-year giving process, enabling nonprofits to secure, manage, and forecast commitments with unprecedented ease.
About the roleThis role owns the platform that keeps Givzey secure, compliant, reliable, and scalable. You'll work across AWS infrastructure, Infrastructure as Code, CI/CD, AI services, observability, and developer tooling to make sure engineers spend their time building product instead of fighting deployments.
You'll partner closely with engineering, ML, and product to design the platform that powers everything from customer-facing APIs to LLM workflows running on Amazon Bedrock and SageMaker.
This is not a "keep the lights on" devops role. You'll actively shape how we deploy software, provision infrastructure, manage AI workloads, and scale the engineering organization.
Who thrives hereYou're the engineer who gets excited about replacing a manual deployment with a one-click pipeline, automating infrastructure instead of clicking around the AWS console, and designing systems that make the rest of engineering move faster.
You think in terms of reliability, observability, automation, and repeatability.
You're comfortable wearing multiple hats. One morning you might be debugging IAM permissions. That afternoon you're building a Pulumi module, improving GitHub Actions, tuning ECS workloads, or helping an ML engineer deploy a SageMaker endpoint.
What you'll do
You should be comfortable working with technologies such as:
Experience with some of the following is highly desirable:
This isn't a traditional DevOps role where tickets get tossed over the wall after development.
This isn't an SRE role focused exclusively on uptime.
This isn't an ML engineering role building models.
You're building the platform that allows all of those disciplines to move faster. You'll own infrastructure decisions, improve how software gets delivered, and help shape the technical foundation of an AI company that's still early enough for your decisions to matter years from now.
New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under AI Engineer, by the work the posting describes.
AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.
Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.
An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.