Responsibilities
- Run the engineering leadership cadence. Own director-level syncs and the leadership rhythm end to end: agenda, documented decisions, follow-through.
- Take over the quarterly OKR and QBR cycle. Drive teams to set and update objectives, chase the follow-ups, surface where they slip, and prepare the reviews.
- Keep one live record of leadership decisions and commitments, and chase every one to closure by its agreed date.
- Scan continuously for stalled or ownerless cross-team work — the kind that quietly dies when a delegated project's loop never closes — and bring it back on track with a named owner.
- Drive special projects to a chartered state, then hand them off — and stop holding them.
- Turn complex organizational and project inputs into concise, decision-ready material for the CTO, the executive team, and board-level audiences.
- Facilitate delegated decisions to closure — documented, escalated when they stall, communicated to the people they affect — so nothing waits on a calendar slot or gets re-litigated.
- Standardize how engineering leadership plans, tracks, and communicates. Build the rituals, templates, and operating rhythm that keep the org coordinated without being prescriptive at the team level.
- Partner across the organization on cross-cutting initiatives, procurement, pilot contracts, and engineering tool budgeting.
Requirements
- Engineering-operations / TPM leadership. A track record running the operating system of an engineering organization — most likely as a TPM lead, head of engineering operations, or equivalent. You have owned cadence, planning, and cross-team coordination at org scale.
- Cross-functional delivery. Demonstrated ownership of ambiguous, multi-team initiatives that you coordinated, drove, and landed through influence without direct authority.
- Executive synthesis. A track record of turning raw, complex information into brief, decisive, executive-level material.
- Operating discipline. You build durable systems and follow-up loops, not just meetings.
- Works well with engineers. You operate effectively alongside engineers, EMs, and directors and earn their trust through reliability and follow-through. Enough fluency to follow technical discussions and coordinate them — without needing to be the technical authority or make architecture calls.
- Fluent English (C1+) and Russian for internal and external technical communications.
Nice to Have
- Prior Chief of Staff, Engineering Operations, or TPM-lead experience reporting into engineering leadership.
- Experience driving operational efficiency in engineering orgs of 100+ people, including use of automation and AI tooling to keep teams lean.
- Procurement, vendor-contracting, or budgeting experience.
- Nonprofit-tech or payments-domain familiarity.
- Familiarity with our environment is an advantage: Node.js/NestJS, React, MongoDB, ClickHouse, Kafka, Cloudflare; PCI DSS 4.0.1, SOC 2 Type II, ISO 27001.
Team
Team size: 160. Structure: Distributed team of 160+ product professionals, including 80+ engineers. Engineering directors report to the CTO. The role works through influence rather than line authority.
Additional Information
- AI is a default tool at Fundraise Up. Every team member is expected 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.
- Fluent in English and Russian.
- Remote working.
- Company operates in English across European and US hours.
- Home Office Setup Assistance: the company offers assistance with purchasing furniture (office chair, office desk, monitor) and other items to create a comfortable workspace.
- Co-working.
- €50 monthly allowance to cover internet and mobile phone expenses.
