Fundraise Up provides an embeddable donation platform for nonprofits via campaign pages, to accept multiple payment types, track donation analytics, and use AI personalization for suggested amounts and retention.
<h4>Highlights:</h4> <ul> <li>Location: Georgia Remote</li> <li>Language: Russian-speaking team</li> </ul> <h4>About Fundraise Up</h4> <p>We’re Fundraise Up - a global fundraising platform built to make donating to nonprofits fast, seamless, and accessible to all. Every month, our technology powers tens of millions of dollars in donations across the globe. We focus on innovation that directly impacts results: faster load times, higher conversion rates, global payment support, and accessibility-first design.</p> <p>Our platform is trusted by many of the world’s leading nonprofits, including UNICEF, the Alzheimer’s Association, and a wide range of global NGOs. With a 4.9/5 rating across top software review platforms, we’re recognized not just for our impact - but for the quality of the product we deliver.</p> <h4>A Truly Global Product</h4> <p>We operate in the enterprise segment, serving nonprofit organizations across North America, the United Kingdom, Australia, and Europe.</p> <p>We’re building a <strong>large and complex product ecosystem</strong> that serves nonprofits, donors, and partners around the world. The platform includes a modern <strong>checkout experience and customizable widgets</strong> (each a standalone SPA), <strong>donor, organization, and partner portals</strong>, <strong>admin tools</strong>, and several internal apps.</p> <p>Our backend is powered by <strong>Node.js</strong> (Koa, NestJS) and <strong>MongoDB</strong>. The frontend stack includes <strong>Webpack, Vue.js, and React</strong>, with nearly all code written in <strong>TypeScript</strong>. For high-throughput messaging and background processing, we use <strong>Kafka</strong> (for millions of events) and <strong>Bull (Redis)</strong>. Analytics data is stored in <strong>ClickHouse</strong>, and we use <strong>Elasticsearch</strong> for search.</p> <h4>The Team</h4> <p>We are a distributed team of 160+ product professionals, including 80+ engineers. Our team members are mainly based across Spain, Poland, Portugal, Georgia, Armenia, Serbia, Turkey, and Cyprus. Many of our developers bring 5 - 10+ years of experience, and we foster a culture of deep technical curiosity and knowledge sharing.</p> <p>Despite our scale, we operate like a focused team - where every task matters and every voice is heard. We value thoughtful collaboration, strong engineering practices, and a product mindset. You’ll be joining a team where quality, mentorship, and mutual respect come first.</p> <h4>About the Role</h4> <p>You will join the DevOps team responsible for the platforms our engineering teams rely on daily: CI/CD, observability, logging, and developer tooling. Our philosophy is simple: the team owns its systems end-to-end, and every engineer should be able to diagnose and fix issues in their area of responsibility.</p> <p><strong>This is a senior-only role.</strong> We are looking for an engineer we can hand an entire area — observability or CI/CD — and trust to run it: from requirements and technical design through rollout, operations, and mentoring others. You will be the go-to technical reference for your area and the senior escalation point for complex incidents in it.</p> <h4><strong>What You’ll Do</strong></h4> <ul> <li><strong>Own one of our core platform areas end-to-end</strong>: observability (VictoriaMetrics, Grafana, Graylog / VictoriaLogs, fluent bit, exporters, alerting) or CI/CD (Jenkins scripted pipelines, Harbor, Nexus, build agents) — you drive its architecture, reliability, and roadmap.</li> <li><strong>Drive technical initiatives end-to-end</strong>: gather requirements, write the design doc, decompose into tasks, implement, deliver to production, and own the operational health afterwards.</li> <li><strong>Drive clarity in ambiguous situations</strong> by defining requirements, assumptions, and next steps.</li> <li><strong>Design for reliability and scale</strong>: evolve the architecture of our platforms — topology, integration points, scaling approach, and reliability model.</li> <li><strong>Support developers</strong>: deploy and monitor applications on both on-premise servers and Kubernetes (Helm), troubleshoot builds and deploys, help teams with metrics, alerts, and logs; participate in chat duty in developer support channels.</li> <li><strong>Automate away toil</strong>: repetitive operations, provisioning, and maintenance should be codified, not performed by hand.</li> <li><strong>Investigate production incidents</strong> as the senior escalation point for your area: drive resolution, lead post-mortems, implement systemic fixes. Participate in <strong>on-call</strong> rotations and raise the bar for how on-call works.</li> <li><strong>Mentor</strong> less experienced engineers through design discussions, reviews, and pairing; catch debt-inducing shortcuts at the review stage.</li> <li>Use <strong>AI</strong> in all aspects of day-to-day work: researching, troubleshooting, developing.</li> </ul> <h4><strong>Requirements</strong></h4> <ul> <li><strong>6+ years</strong> as a DevOps Engineer / SRE (or very close responsibilities).</li> <li><strong>Track record of owning technical initiatives end-to-end</strong> — from requirements and technical design through production delivery. You can showcase initiatives that were yours, not just tasks you completed.</li> <li>Confident <strong>Linux</strong> skills (we use Ubuntu).</li> <li><strong>Working knowledge of the Prometheus stack</strong>: metric types, exporters, and how alerting works — enough to navigate and extend an existing setup.</li> <li>Hands-on experience with <strong>CI/CD</strong>: pipeline design, build orchestration, artifact delivery.</li> <li><strong>Containers</strong>: Docker, image building, registries.</li> <li><strong>Ansible.</strong></li> <li><strong>Git</strong>.</li> <li>Experience with <strong>Bash</strong> or <strong>Python</strong> scripting for automation and observability (writing exporters, eliminating routine work).</li> <