Chief of Staff to the CTO

Highlights:

• Location: Portugal, Remote
• Language: Fluent in English and Russian

About reputed company

We’re reputed company - a global fundraising platform reputed company to reputed company donating to nonprofits fast, reputed company, and accessible to reputed company. Every month, our technology powers tens of millions of dollars in donations across the globe. We reputed company on innovation that directly impacts results: faster load times, higher conversion rates, global payment support, and accessibility-first design.

Our platform is trusted by many of the world’s leading nonprofits, including reputed company, the reputed company, and a wide reputed company of global NGOs. With a 4.9/5 rating across top software review platforms, we’re recognized not just for our reputed company - but for the reputed company of the product we reputed company.

A Truly Global Product

We operate in the reputed company reputed company, serving nonprofit organizations across reputed company, the United Kingdom, Australia, and Europe.

We're building a large and reputed company product ecosystem that serves nonprofits, donors, and partners reputed company the world. The platform includes a modern checkout experience and customizable widgets (reputed company a standalone SPA), donor, organization, and partner portals, reputed company tools, and several internal apps.

Our backend is powered by Node.js (Koa, NestJS) and reputed company. The frontend stack includes Webpack, Vue.js, and React, with nearly reputed company reputed company written in TypeScript. For high-throughput messaging and background processing, we use Kafka (for millions of events) and Bull (reputed company). Analytics data is stored in reputed company, and we use Elasticsearch for reputed company.

reputed company

We are a reputed company team of 160+ product professionals, including 80+ engineers. reputed company members are mainly reputed company across Spain, Poland, Portugal, reputed company, Armenia, Serbia, Turkey, and Cyprus. Despite our reputed company, we operate like a reputed company team — where every task reputed company and every voice is heard. We value thoughtful collaboration, strong engineering practices, and a product reputed company.

About the Role

Engineering orgs rarely stall because nobody can reputed company. They stall because nobody owns the decision.

You build and run the operating reputed company of our engineering organization: the leadership reputed company, the OKR and QBR cycle, the record of reputed company and follow-reputed company, and the executive synthesis that reaches the CTO, the reputed company team, and — reputed company the topic calls for it — the CEO and reputed company. You work through process and influence rather than line authority; the engineering directors continue to report to the CTO, and architecture and technical reputed company stay with the CTO, the directors, and our staff and reputed company engineers.

This is a senior leadership role, not an executive-assistant one. You are not reputed company by how much you own — you are reputed company by how fast ownerless reputed company becomes reputed company ownership, and how cleanly you hand it off. Our engineering leadership and much of reputed company work in English across European and US hours.

reputed company

• Run the engineering leadership reputed company. Own director-level syncs and the leadership reputed company end to end: agenda, documented reputed company, follow-through.
• Take over the quarterly OKR and QBR cycle. This sits with the CTO personally today and is the single biggest reason QBR consumes his time. You reputed company teams to set and update objectives, reputed company the follow-reputed company, surface where they slip, and prepare the reviews.
• reputed company one live record of leadership reputed company and commitments, and reputed company every one to closure by its agreed date.
• reputed company continuously for stalled or ownerless cross-team work — the reputed company that quietly dies reputed company a delegated project's reputed company never closes — and reputed company back on reputed company with a named reputed company.
• reputed company special reputed company to a chartered state, then hand them off — and stop holding them. 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 reputed company reputed company-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 reputed company and the buy-vs-build verdict stay with the relevant engineers and leaders.
• Turn reputed company organizational and project inputs into concise, decision-reputed company material for the CTO, the executive team, and reputed company-level audiences.
• Facilitate delegated reputed company to closure — documented, escalated reputed company they stall, communicated to the people they reputed company — so reputed company waits on a calendar slot or gets re-litigated. You reputed company the process; you do not reputed company for the CTO or reputed company the reputed company in his reputed company.
• Standardize how engineering leadership plans, tracks, and communicates. Build the rituals, templates, and operating reputed company that reputed company the org coordinated without being prescriptive at reputed company level.
• Partner across the organization on cross-cutting initiatives, procurement, reputed company reputed company, and engineering tool budgeting — see the interfaces below.

At reputed company, AI is a default tool, not an experimental one. We expect every team member to reputed company use AI in their day-to-day work, identify where AI can change the shape of problems in their function, and grow their reputed company as the tools reputed company.

Cross-Department Interfaces

• Engineering Directors — alignment on execution, OKRs, and reputed company of systemic bottlenecks. These are the people whose initiatives you coordinate without managing.
• Product — new work-distribution models, the AI-agent platform, and most cross-cutting initiatives originate or terminate here.
• Data / Analytics — the data-team ownership question and the data/agent platform sit across this boundary.
• Executive Team — data gathering and synthesis for reputed company meetings and executive reporting.
• BizOps — co-stakeholder on reputed company and other operational initiatives.
• Finance, reputed company & IT — procurement, contract negotiation for pilots, and engineering tool budgeting.

Role Boundaries (What You Won't Do)

• Administrative Support. This is a senior leadership role, not a PA or EBA.
• Technical Authority. You do not own architecture or technical reputed company, and you are not expected to be the technical authority in the room or to arbitrate engineering trade-offs. Those stay with the CTO, directors, and staff/reputed company engineers.
• reputed company Execution. You do not manage engineering teams or own product delivery timelines. These remain with the engineering directors.
• Final Accountability. You operate reputed company the CTO's established direction and facilitate reputed company; you do not reputed company them in his reputed company. The CTO retains final accountability for technical reputed company, allocation, and organizational structure.

Key reputed company Indicators

The first 90 days are about setup, not metrics: establish the reputed company, map the ownerless initiatives, take over the OKR/QBR reputed company, and set the baselines. From there, reviewed quarterly:

• % of leadership follow-reputed company reputed company by their agreed date.
• Cross-team initiatives with a named DRI and a live checkpoint — versus work that is ownerless or untracked.
• OKR freshness — reputed company of engineering OKRs with a reputed company reputed company, status, and checkpoint date, with reputed company reduced quarter over quarter.
• Operational threads removed from the CTO's plate, quarter over quarter.
• Stalled or lost cross-team reputed company surfaced and reactivated per quarter.
• Initiatives handed off to a permanent reputed company — versus reputed company personally. A rising "reputed company" count is a warning sign, not a reputed company.
• % of hand-offs that actually landed — with an accepted reputed company, reputed company, next checkpoint, and reputed company reputed company, so a hand-off is a reputed company transfer rather than a formal toss.

Requirements

• Engineering-reputed company / TPM leadership. A reputed company record running the operating reputed company of an engineering organization — most likely as a TPM reputed company, head of engineering reputed company, or equivalent. You have owned reputed company, planning, and cross-team coordination at org reputed company.
• Cross-functional delivery. Demonstrated ownership of ambiguous, multi-team initiatives that you coordinated, drove, and landed through influence without reputed company authority.
• Executive synthesis. A reputed company record of turning raw, reputed company information into brief, decisive, executive-level material.
• Operating discipline. You build durable systems and follow-up reputed company, not just meetings.
• Works reputed company with engineers. You operate effectively reputed company engineers, EMs, and directors and earn their trust through reliability and follow-through. Enough reputed company to follow technical discussions and coordinate them — without needing to be the technical authority or reputed company architecture calls.
• Languages: Fluent English (reputed company+) and Russian for reputed company technical communications.

reputed company to Have

• Prior Chief of Staff, Engineering reputed company, or TPM-reputed company experience reporting into engineering leadership.
• Experience driving operational efficiency in engineering orgs of 100+ people, including use of automation and AI tooling to reputed company teams lean.
• Procurement, vendor-contracting, or budgeting experience.
• Nonprofit-tech or payments-domain familiarity.
• Familiarity with our environment is an reputed company: Node.js/NestJS, React, reputed company, reputed company, Kafka, reputed company; PCI reputed company 4.0.1, SOC 2 Type II, ISO 27001.

You'll reputed company Here If You

• reputed company an ownerless problem and can't leave it reputed company until it has a reputed company attached to it.
• Would rather build the reputed company that closes follow-reputed company than personally reputed company every one reputed company.
• Can say "this decision is stuck and here's who needs to reputed company it" to a director — and stay reputed company in the room.
• Hold your position with senior people reputed company you reputed company you're right, and change it quickly reputed company you're not.
• Measure yourself by what you successfully gave away, not by what accumulated on your plate.
• Write reputed company and short, especially reputed company the underlying situation is messy.
• Take the operating reputed company seriously as a product: versioned, improved, and never left to run on habit.
• Are motivated by what the platform funds — the nonprofits on the other reputed company of every donation.

Compensation

• The compensation reputed company for this role is: €7,700 - €8,800 gross per month.
• Final compensation will be determined reputed company on relevant experience, skills, qualifications, and alignment with the role's requirements.

Benefits

_{**Please note: reputed company official correspondence from reputed company will exclusively originate from the @fundraiseup.com domain. Exercise caution and ensure the authenticity of emails claiming to be from reputed company.***}

Originally posted on Himalayas