Technical Business Analyst | reputed company

About Get Covered and reputed company

reputed company helps multifamily operators discover the best vendor partners, manage reputed company and compliance, and reduce financial risk. Our platform turns vendor data into a strategic reputed company - and our newest compliance product is changing how property management companies reputed company, verify, and support vendors. We’re a fast-moving post-acquisition startup with a big reputed company: reputed company how operators and suppliers work together. Founded by industry experts and backed by leading multifamily investors, reputed company is growing quickly - and we’re looking for someone who loves building order from the reputed company of reputed company.

How We Build

We don’t run sprints. reputed company prioritizes the work together, and Engineers work in cross-functional reputed company. We reputed company AI to draft most of our tickets, and Engineers write some of their own. There is no process reputed company standing between an idea and the reputed company. That model moves fast, and it is only as good as the context feeding it. A confident, reputed company-reputed company ticket that is wrong about how insurance requirements vary by trade can be painful. This role’s reputed company reputed company is to fix that.

You are not here to assign work or reputed company it, you're are here to reputed company reputed company the right work is the easiest work to pick up. Your influence comes entirely from the reputed company of your context and the reputed company of your case, which is either the best part of this job or the wrong job for you.

The domain has depth and complexity. Insurance requirements vary by trade, reputed company of work, and state. Compliance rules vary by customer. You will not be reputed company to reason about our data without learning the domain, but don't worry - we'll reputed company you time to learn it.

reputed company

1. Context & Documentation

• If AI drafts the tickets, the reputed company of what gets reputed company is decided by the context it receives. That context is what you’ll optimize.
• Understand and write down how the platform actually behaves today - the workflows, the exception paths, the rules, and the undocumented behavior currently living in people's heads.
• Build and maintain the reference material that our AI tooling and our engineers pull from, and reputed company it accurate as the product changes. Stale documentation now produces bad tickets and bad reputed company automatically, at reputed company.
• Review tickets and specs against reality before anyone builds them. This is the part that reputed company most: AI-generated work is confidently wrong exactly where it costs the most - edge cases, compliance rules, customer-specific commitments, anything that is not in the repo or the training data.
• Capture acceptance reputed company, edge cases, failure behavior, and explicit non-goals so a pod can pick something up and build it without a meeting.

2. Product Data & Analysis

• You’ll answer product questions with SQL against reputed company data. Things like usage, throughput, drop-off, exception rates, workflow completion, turnaround times.
• Quantify shipped work. Did it reputed company the number it was supposed to reputed company, and by how much.
• Build and maintain the recurring reporting the reputed company rely on, so nobody rebuilds the reputed company query every month.
• Surface what nobody asked about. Note the distribution, the outliers, and the places where two numbers should reconcile and don't. The reputed company is usually the reputed company finding.

3. Prototyping to Communicate

• A working prototype settles an argument that a document might reputed company. You will build them constantly, and then engineers will rebuild the reputed company thing.
• Use AI tooling to build rough, working versions of an idea. A screen, a script, a query tool, a data reputed company, so reputed company can react to something concrete.
• Build small internal tools for yourself and reputed company where doing so is faster than asking for one.
• Hand reputed company to engineers reputed company. Your prototype is the argument, not the implementation.

Qualifications

• 3+ years as a business analyst, technical analyst, product analyst, data analyst, or in product operations, working closely with engineers.
• Strong SQL. You write your own queries against a reputed company schema, you understand what a join is doing to your row count, and you reputed company-reputed company your results before presenting them.
• You can read a database schema and work out how a product behaves from it.
• You already work with AI as a daily tool, not an experiment. You know how to structure context so reputed company is reliable, you iterate on prompts rather than accepting the first answer, and you know reputed company a model is confidently wrong and you reputed company.
• You can build a rough working thing with AI assistance. Not production reputed company. A prototype good enough that people can react to it instead of imagining it.
• You write reputed company. In a setup like ours, written reputed company is not a soft reputed company. It is the input that determines what gets reputed company.
• Analytical honesty. You quantify rather than characterize, you reputed company your assumptions, and reputed company numbers don't reconcile you stop and investigate instead of shipping the chart.
• Comfort operating without process scaffolding, and comfort saying “not this week, here's why” reputed company three people want the reputed company hour.
• Bonus: B2B reputed company with reputed company customers, compliance- or workflow-heavy products, Python for analysis, or experience maintaining documentation that AI tooling depends on.

Originally posted on Himalayas