Chief of Staff to the CTO
<h4>Highlights:</h4>
<ul>
<li>Location: Portugal, Remote</li>
<li>Language: Fluent in English and Russian</li>
</ul>
<h4 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="7:1-7:22;316-337">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 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="11:1-11:26;855-880">A Truly Global Product</h4>
<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="13:1-13:135;882-1016">We operate in the enterprise segment, serving nonprofit organizations across North America, the United Kingdom, Australia, and Europe.</p>
<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="15:1-15:299;1018-1316">We're building a large and complex product ecosystem that serves nonprofits, donors, and partners around the world. The platform includes a modern checkout experience and customizable widgets (each a standalone SPA), donor, organization, and partner portals, admin tools, and several internal apps.</p>
<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="17:1-17:351;1318-1668">Our backend is powered by Node.js (Koa, NestJS) and MongoDB. The frontend stack includes Webpack, Vue.js, and React, with nearly all code written in TypeScript. For high-throughput messaging and background processing, we use Kafka (for millions of events) and Bull (Redis). Analytics data is stored in ClickHouse, and we use Elasticsearch for search.</p>
<h4 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="19:1-19:12;1670-1681">The Team</h4>
<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="21:1-21:385;1683-2067">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. 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.</p>
<h4 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="23:1-23:18;2069-2086">About the Role</h4>
<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="25:1-25:102;2088-2189">Engineering orgs rarely stall because nobody can decide. They stall because nobody owns the decision.</p>
<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="27:1-27:516;2191-2706">You build and run the operating system of our engineering organization: the leadership cadence, the OKR and QBR cycle, the record of decisions and follow-ups, and the executive synthesis that reaches the CTO, the exec team, and — when the topic calls for it — the CEO and board. You work through process and influence rather than line authority; the engineering directors continue to report to the CTO, and architecture and technical strategy stay with the CTO, the directors, and our staff and principal engineers.</p>
<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="29:1-29:309;2708-3016">This is a senior leadership role, not an executive-assistant one. You are not measured by how much you own — you are measured by how fast ownerless chaos becomes clear ownership, and how cleanly you hand it off. Our engineering leadership and much of the company work in English across European and US hours.</p>
<h4 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="31:1-31:18;3018-3035">What You'll Do</h4>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1" data-sourcepos="33:1-41:157;3037-5283">
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="33:1-33:155;3037-3191"><strong>Run the engineering leadership cadence.</strong> Own director-level syncs and the leadership rhythm end to end: agenda, documented decisions, follow-through.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="34:1-34:263;3192-3454"><strong>Take over the quarterly OKR and QBR cycle.</strong> This sits with the CTO personally today and is the single biggest reason QBR consumes his time. You drive teams to set and update objectives, chase the follow-ups, surface where they slip, and prepare the reviews.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="35:1-35:119;3455-3573"><strong>Keep one live record of leadership decisions and commitments,</strong> and chase every one to closure by its agreed date.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="36:1-36:188;3574-3761"><strong>Scan continuously for stalled or ownerless cross-team work</strong> — the kind that quietly dies when a delegated project's loop never closes — and bring it back on track with a named owner.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="37:1-37:738;3762-4499"><strong>Drive special projects to a chartered state, then hand them off — and stop holding them.</strong> Recent live examples: rolling out a new product-defined work-distribution model and its org-structure documentation; standing up a cross-departmental data team and driving the Analytics-vs-Engineering ownership question to a decision; running vendor selection, procurement, and the CEO-facing business case for an external security-consulting engagement; coordinating an internal AI-agent platform program across several teams; running technical audits, platform evaluations, and tool pilots. You own the coordination, planning, and tracking — the technical substance and the buy-vs-build verdict stay with the relevant engineers and leaders.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="38:1-38:151;4500-4650"><strong>Turn complex organizational and project inputs into concise, decision-ready material</strong> for the CTO, the executive team, and board-level audiences.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="39:1-39:271;4651-4921"><strong>Facilitate delegated decisions to closure</strong> — documented, escalated when they stall, communicated to the people they affect — so nothing waits on a calendar slot or gets re-litigated. You drive the process; you do not speak for the CTO or make the call in his place.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="40:1-40:205;4922-5126"><strong>Standardize how engineering leadership plans, tracks, and communicates.</strong> Build the rituals, templates, and operating rhythm that keep the org coordinated without being prescriptive at the team level.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="41:1-41:157;5127-5283"><strong>Partner across the organization</strong> on cross-cutting initiatives, procurement, pilot contracts, and engineering tool budgeting — see the interfaces below.</li>
</ul>
<p class="font-claude-response-body break-words whitespace-normal" data-sourcepos="43:1-43:251;5285-5535">At Fundraise Up, AI is a default tool, not an experimental one. We expect every team member to actively use AI in their day-to-day work, identify where AI can change the shape of problems in their function, and grow their fluency as the tools evolve.</p>
<h4 class="mt-3 -mb-1 text-[1.125rem] font-bold" data-sourcepos="45:1-45:31;5537-5567">Cross-Department Interfaces</h4>
<ul class="[li_&]:mb-0 [li_&]:mt-1 [li_&]:gap-1 [&:not(:last-child)_ul]:pb-1 [&:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3 print:block print:space-y-1" data-sourcepos="47:1-52:106;5569-6264">
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="47:1-47:172;5569-5740"><strong>Engineering Directors</strong> — alignment on execution, OKRs, and resolution of systemic bottlenecks. These are the people whose initiatives you coordinate without managing.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="48:1-48:133;5741-5873"><strong>Product</strong> — new work-distribution models, the AI-agent platform, and most cross-cutting initiatives originate or terminate here.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="49:1-49:112;5874-5985"><strong>Data / Analytics</strong> — the data-team ownership question and the data/agent platform sit across this boundary.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="50:1-50:96;5986-6081"><strong>Executive Team</strong> — data gathering and synthesis for board meetings and executive reporting.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="51:1-51:77;6082-6158"><strong>BizOps</strong> — co-stakeholder on security and other operational initiatives.</li>
<li class="font-claude-response-body whitespace-normal break-words pl-2" data-sourcepos="52:1-52:106;6159-6264"><strong>Finance, Legal & IT</strong> — procurement, contract negotiation for pilots, and engineeri
Este anúncio é de Greenhouse. Ver anúncio original ↗