Strategy & Operations Lead

Revyse exists to help multifamily operators discover the best vendor partners, manage contracts and compliance, and reduce financial risk. Our AI-powered platform helps the industry turn vendor and supplier data into a strategic advantage. We are a fast-moving, early-stage tech company with a big vision. Founded by industry experts and financially supported by industry veterans - we're overhauling the relationship between operators and suppliers.

In 2026, Revyse was acquired by Get Covered LLC, pairing our vendor and compliance platform with Get Covered's reach across the multifamily industry. The team, mission, and roadmap continue under the Revyse name, now backed by a larger platform.

We're hiring a Strategy and Operations Lead to own the company's highest-priority cross-functional problems, specifically the ones that don't have an obvious owner. You will diagnose the issue, build the solution, drive it through implementation, and establish durable ownership before moving on. This role is in-person, on-site in Bend, Oregon, but may be remote within the US for the perfect candidate.

The scope is deliberately unbounded. In a given quarter it might be a product decision stalled between engineering and sales, a partnership that has gone quiet, a pricing structure that needs rebuilding, or the operational plumbing nobody has touched in six months. What stays constant is the standard: once a problem lands with you, the founders stop carrying it.

• Diagnose Before You Build :
  Find the actual constraint rather than the symptom that was handed to you. Talk to the people closest to the work, look at the data, and be willing to come back and tell us the problem we described is not the problem worth solving.
• Build the Solution :
  Produce the artifacts that make the fix real: the spec, the model, the process, the pricing structure, the partner agreement. You are not writing recommendations for somebody else to execute.
• Drive It Through Implementation :
  Carry the work across engineering, sales, CX, and finance until it is live and functioning. These problems are cross-functional precisely because they stall in the handoffs. Owning the handoffs is the job.
• Establish Durable Ownership :
  Nothing is done until a named person owns it, with a documented process and a way to tell whether it is still working. Then you move to the next problem. Success is measured by what holds up six months after you left it.
• Work Across the Full Range :
  Some quarters that means pricing architecture or a marketplace launch. Some weeks it is managing the PO Box, a benefits question, or a vendor account nobody has logged into since January. Both count, and we will not pretend otherwise in the interview.
• Bring Answers, Not Status : “Still working on it” is not an update. Tell us what you found, what you decided, and what you need from us.
• Use AI Aggressively :
  We use AI a lot. Research, diagnosis, drafting, analysis, and workflow automation should let one person cover the ground of three. If you are not already working this way, you will be within a month.
• Represent the Company Well :
  You will sit in front of customers, partners, and vendors on the Company’s behalf. How you show up is how Revyse shows up.

• We believe in giving people opportunities, so if you don't check all of the boxes below, don't let that hold you back.
• Evidence of ownership from start to finish :
  You can name specific problems you inherited, describe how you diagnosed them, and point to what is still standing after you moved on. This is what we screen hardest for. Somewhere around 3 to 5+ years of experience is a reasonable benchmark, but we have left the band wide on purpose and will weigh evidence over tenure.
• Product background :
  You have shipped software. You have written specs, sat in engineering standups, argued about scope, and made tradeoffs on incomplete information. Even on problems that are not product problems, that instinct: define it, cut it down, ship it: is the one we are hiring for.
• Structured thinking under ambiguity :
  There is no 100-page spec. Often there is no spec  should be able to impose structure on a vague…