61 Google Corporate Operations Engineer Jobs Hiring Near You

Make Alpaca scale by owning and resolving the operating constraints Corporate Operations prioritizes.

Your mission is to take high-impact operating constraints from discovery through measurable outcome: drive them to resolution, establish durable ownership with the right long-term owner, then move to the next priority. You parachute into unfamiliar domains (HR, Finance, Engineering capacity, regional operating models, broker dealer bottlenecks, and more), diagnose what's actually limiting scale, create the solution, and stay accountable until the outcome actually changes. You are a builder-operator, not a coordinator. You work on the problems Corporate Operations has prioritized as highest-value for the company right now.

Things You Get To Do:

• Own prioritized constraints end-to-end. Take cross-functional operating problems from zero context through measurable outcome. When the constraint is removed and the fix persists, you move on. You do not hold permanent territory in any function.
• Work in any domain, including BD ops when it's the bottleneck. This month that might be HR automation or Finance close; next quarter decision delegation or Engineering throughput; later a broker dealer constraint (AML scale, reconciliations, operational readiness) if that's where Alpaca is stuck. Domain expertise is not the job. Systems thinking across unfamiliar domains is.
• Sense → Design → Build → Drive. Measure what's happening, redesign what's broken, create the processes/automation/governance/infrastructure needed (or mobilize Engineering, Product, ORE, or functional teams when that's the right answer), and drive adoption until the outcome changes.
• Partner across the company. Work directly with functional leaders and their teams to mobilize resources and drive adoption. You influence priorities and surface capacity needs; you do not absorb the function or run their day-to-day execution.
• Create non-linear leverage. Ask whether workflow redesign, automation, org design, better decisions, vendor changes, or hiring is the right lever, and use whichever applies. Success means creating leverage so Alpaca needs fewer incremental people to support the same growth in the areas you touch.
• Contribute to company deep-dives. Help establish baselines for velocity, capacity, and friction in the areas you work in.
• Communicate capacity honestly. Be explicit about trade-offs and escalate when scope or priority needs Director or VP input, including when work should be deferred.

Who You Are (Must-Haves):

• Builder-operator with end-to-end ownership. Proven track record taking ambiguous, high-stakes problems from zero context to measurable outcome. You don't hand off recommendations and walk away.
• Systems thinker who learns fast. Able to parachute into unfamiliar domains, map workflows/capacity/decision systems, diagnose root cause, and become effective without deep prior subject-matter expertise.
• Influence without authority. Proven ability to mobilize cross-functional teams, partner with senior stakeholders, and drive adoption among people who don't report to you.
• Prioritization and judgment. Able to distinguish root cause from symptoms, focus on what matters, and push back with evidence when scope drifts.
• Analytical rigor. Comfortable establishing metrics, measuring before/after, and using data, not anecdotes, to diagnose problems and prove impact.
• High ownership through implementation. You finish what you start. Adoption and lasting change matter as much as the design.
• 7+ years of relevant professional experience, including demonstrated ownership of complex, cross-functional operating initiatives from diagnosis through implementation and measurable outcome.

Who You Might Be (Nice-to-Haves):

• Experience in internal product, strategy/ops, business operations, or operational transformation with strong builder instincts.
• Strong fluency in AI and automation as tools for creating operating leverage.
• FinTech or brokerage exposure is helpful in BD ops contexts. The job is operating pattern recognition, not securities expertise.
• Capability spikes in systems/product build, executive orchestration, or quantitative capacity analysis.

What This Role Is Not:

A PMO project manager, business analyst who hands off recommendations, permanently embedded functional ops leader, process documentation role, product manager owning a product roadmap, or coordinator who stops at diagnoses and handoff. Functional leaders retain their teams and recurring execution; you own the constraint until it is resolved and durable ownership is established.