Interested in this AI/ML Engineer role at GiveCampus?
Apply Now →Skills & Technologies
About This Role
GiveCampus is the world's leading fundraising platform for non-profit educational institutions. Trusted by millions of donors and 1,300+ colleges, universities, and K-12 schools, our mission is to help advance the quality, the affordability, and the accessibility of education. At our current pace, we will facilitate $100 billion in charitable giving over the next decade–enough money to send more than 1 million students to college, tuition-free.
GiveCampus is backed by leading investors including Y Combinator, but we're also practitioners of Sustainable Growth: we've made the Inc. 5000 list of America's fastest-growing private companies each of the last five years and we've been profitable nine of the last 10. In 2025, we celebrated a $140 million growth investment that included a major liquidity event for GiveCampus employees–the second in less than three years.
Our purpose-driven team of 130+ is located in 30+ states across the US: team members work from anywhere they choose. We have a beautiful 12,000sf office in Washington, DC that is available for people to use whenever they want, and we regularly organize team meet-ups, visit partner institutions, and host retreats in various locations.
While we operate at meaningful scale, we're still small relative to the commercial and social good opportunities in front of us. Every GiveCampus employee plays a meaningful role in shaping what comes next, and we're growing the team in support of our ambitious plans–including a $100 million investment in AI product development. If you believe in the transformative power of education and want to join a fast-growing, mission-driven company, you'll fit right in.
Location: This is a remote-first role based in the U.S. While we embrace flexible, distributed work, we also value in-person connection. Team members are expected to attend multiple company-wide and team-specific onsites throughout the year.
The role
GiveCampus has spent the last 18 months getting good at using AI. People use it every day, and we've shipped agents and apps that changed how work gets done: a codebase agent that answers questions no doc can, an RFP agent, a support knowledge bot, a feature request agent, and a data integrations assistant for our Partners.
Now, we are ready to take it to the next level. You'll design, build, and operate the next generation of AI Infrastructure at GiveCampus, including sources of company and Partner context, a clear model for who and what can access which data, a registry of what's already been built, memory that carries across agents, and the guardrails that let us move fast without losing track of what our agents are doing.
This is a platform role. You'll work alongside a product partner and co-builder (the AI Transformation Lead) who owns prioritization, stakeholder management, and adoption, so you can spend your time on architecture and engineering.
What we're driving
The AI Transformation team exists to change how GiveCampus operates, so that every team runs on connected workflows and agents by default, and output grows without headcount growing alongside it. Over the next year, that means:
- Field teams spend most of their time with customers instead of on meeting prep, research, CRM updates, and follow ups
- Every customer interaction is backed by context (school data, usage, relationship history, and peer benchmarks) delivered before the conversation starts
- Managers act on AI generated briefings and alerts instead of assembling reports by hand
- Finance, People, and Ops teams manage agents that run their recurring processes, stepping in only on exceptions and approvals
- The enablement infrastructure and operating model that make the change last: standard toolkits, a governed agent lifecycle, and measurement of impact by department
You'll contribute directly to every one of these outcomes by owning the platform that makes them possible. The agents doing this work are only as good as the context, access, and controls underneath them, and that's what you'll build.
What you'll own
You'll start by building the foundation that makes the outcomes above possible. After that, the role grows with the company and with AI itself, so treat the later stages as direction, not a fixed scope.
First 6 months: build the foundation
- Shared context and memory: one source of company and Partner knowledge that every agent reads from, so a change is made once and reaches every tool
- Identity and access: auditable permissions for agents, one view of credentials and MCP connections, and a registry of what's already built
- Governance: an evaluation gate before production, an audit trail, monitoring, and protection against prompt injection and data leaks, with build versus buy calls made alongside Infrastructure
- A paved road for builders: templates and guardrails for Taskforce builders, plus measurement of impact by department
6 to 18 months: from platform to operating layer
Things like agents that run whole processes end to end, more autonomy for agents that have proven themselves, an internal deployment platform for apps and agents, and model and cost strategy.
Long term: an AI native GiveCampus
Things like becoming the technical lead for AI across the company, setting the architecture standards internal AI work builds on, and being a thought partner to Product and AI Product, sharing foundations where it makes sense.
What this role is, and what it isn't
Your primary focus is the platform. You'll own the architecture and the engineering, and you'll make the technical calls. On a small team, you'll also pitch in on adjacent work when it helps: a front end for an internal tool, an adoption build, or getting deep on a business workflow to understand what the platform needs to support. That work is shared, not yours alone. The AI Transformation Lead owns product decisions, prioritization, enablement, and change management, and builds adoption tooling alongside you.
What you bring
Must have
- Six or more years of software engineering experience, including meaningful time owning platform, infrastructure, or backend systems in production
- Hands on experience shipping LLM systems with real users: retrieval, tool use, evaluations, and MCP or similar integration patterns
- Strong Python, plus experience with cloud infrastructure (AWS preferred), authentication, and observability
- A security mindset: you think about access, data boundaries, and failure modes before something ships
- A record of building internal platforms or shared services that other people adopted
- Experience growing a system from an early version into something a whole company depends on
- Appetite to grow into the technical lead for AI across the company
- Real excitement about AI and a drive to keep learning: you follow what's new, try things early, and stay current. You don't need to know everything yet, but AI moves fast enough that this role only works if you're engaged with it
- You judge your work by business results (hours given back to teams, faster cycle times, tools people use every day), not by what shipped
- Comfort working from requirements set with a product partner, and the judgment to push back when the technical answer is different
- Clear written communication with technical and non technical teammates
Nice to have
- Experience with agent orchestration, multi agent systems, or agent governance tooling
- Familiarity with Snowflake, dbt, or a semantic layer
- Experience with Salesforce data and APIs
- Time at a startup or small team where you were the first person to own a system
How we work
You'll report to the AI Transformation Lead. Together you form a small pod: they act as product lead and build for adoption, and you own the platform.
You'll partner closely with Engineering and Product through AI Plumbers, our cross team working group for AI architecture, agent orchestration, data access, and governance. You'll also work with our AI Taskforce, the builders in each department who will use what you build.
GiveCampus has a strong written culture built on Notion, Slack, and async work. We move quickly, document what we do, and give people real autonomy and direct access to leadership. We're remote first, and this role can be based anywhere in the US.
Why this role
- The groundwork is done. People already use AI every day and we have working agents in production. You're building the layer that makes them work together.
- Clear ownership. You own the platform, with a product partner who owns prioritization and adoption.
- Room to grow. You'll start with the foundation and grow into the technical lead for AI at GiveCampus as the work and the field change.
- Leadership investment. AI is a company priority, with executive sponsorship behind this work.
- A mission that matters. GiveCampus helps schools raise money to advance education.
Ready to apply?
Be sure to keep an eye on your spam and promotions boxes in case our emails end up there!
At GiveCampus, we value diversity and we pledge to foster an environment of support, inclusivity, and learning, both on the job and throughout the application process. In this spirit, we encourage candidates of all backgrounds to apply.
GiveCampus is an Equal Opportunity Employer. Applicants and employees are not discriminated against because of race, color, creed, sex, sexual orientation, gender identity or expression, age, religion, national origin, citizenship status, disability, ancestry, marital status, veteran status, medical condition or any protected category prohibited by local, state or federal laws.
If you feel like you don't meet all of the requirements for this role, please apply anyways. We know confidence gaps and imposter syndrome often get in the way of connecting with incredible people, and we don't want them to prevent us from meeting you.
Role Details
About This Role
AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.
Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.
Across the 10,419 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At GiveCampus, this role fits into their broader AI and engineering organization.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
What the Work Looks Like
A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
Skills Required
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.
Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
Compensation Benchmarks
AI/ML Engineer roles pay a median of $213,800 based on 16,346 positions with disclosed compensation. Mid-level AI roles across all categories have a median of $193,200.
Across all AI roles, the market median is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. For comparison, the highest-paying categories include AI Safety ($274,500) and Research Engineer ($252,000). By seniority level: Entry: $114,400; Mid: $193,200; Senior: $230,000; Director: $272,100; VP: $235,000.
GiveCampus AI Hiring
GiveCampus has 1 open AI role right now. They're hiring across AI/ML Engineer. Based in Remote, US.
Remote Work Context
Remote AI roles pay a median of $188,000 across 2,811 positions. About 6% of all AI roles offer remote work.
Career Path
Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.
From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.
The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.
What to Expect in Interviews
Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.
When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
AI Hiring Overview
The AI job market has 10,419 open positions tracked in our dataset. By seniority: 117 entry-level, 4,975 mid-level, 3,840 senior, and 1,487 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (580 positions). The remaining 9,776 roles require on-site or hybrid attendance.
The market median for AI roles is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. Highest-paying categories: AI Safety ($274,500 median, 90 roles); Research Engineer ($252,000 median, 580 roles); AI Engineering Manager ($250,811 median, 72 roles).
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
The AI Job Market Today
The AI job market spans 10,419 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,849), AI Product Manager (516), AI Software Engineer (513). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.
The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (117) are outnumbered by mid-level (4,975) and senior (3,840) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,487 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 6% of all AI roles (580 positions), with 9,776 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.
AI compensation is structured in clear tiers. The market median sits at $214,834. Top-quartile roles start at $266,000, and the 90th percentile reaches $321,730. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.
Category matters for compensation. AI Safety roles lead at $274,500 median, while Prompt Engineer roles sit at $140,000. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.
The most in-demand skills across all AI postings: Python (2,350 postings), Aws (1,173 postings), Azure (1,030 postings), Rag (986 postings), Gcp (714 postings), Pytorch (649 postings), Kubernetes (583 postings), Claude (581 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.
Frequently Asked Questions
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.