Technical Business Analyst | Revyse at Get Covered
United States
$80k - $100k
<meta><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><b><strong style="font-size:18pt;white-space:pre-wrap;">How We Build</strong></b></p><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><span style="white-space:pre-wrap;">We don’t run sprints. Our company prioritizes the work together, and Engineers work in cross-functional pods. We leverage AI to draft most of our tickets, and Engineers write some of their own. There is no process layer standing between an idea and the code. That model moves fast, and it is only as good as the context feeding it. A confident, well-structured ticket that is wrong about how insurance requirements vary by trade can be painful. This role’s north star is to fix that. </span></p><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><span style="white-space:pre-wrap;">You are not here to assign work or gate it, you're are here to make sure the right work is the easiest work to pick up. </span><span style="color:rgb(13,13,13);font-size:11pt;white-space:pre-wrap;">Your influence comes entirely from the quality of your context and the clarity of your case, which is either the </span><u><span style="color:rgb(13,13,13);font-size:11pt;text-decoration:underline;white-space:pre-wrap;">best</span></u><span style="color:rgb(13,13,13);font-size:11pt;white-space:pre-wrap;"> part of this job or the wrong job for you.</span></p><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><span style="color:rgb(13,13,13);font-size:11pt;white-space:pre-wrap;">The domain has depth and complexity. Insurance requirements vary by trade, scope of work, and state. Compliance rules vary by customer. You will not be able to reason about our data without learning the domain, but don't worry - we'll give you time to learn it.</span></p><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:18pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><br></p><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:18pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><b><strong style="font-size:18pt;white-space:pre-wrap;">What you'll do</strong></b></p><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><b><strong style="white-space:pre-wrap;">1. Context & Documentation</strong></b></p><ul data-pattern="discCircleSquare" data-depth="1" style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;margin:8px 0px;line-height:1.6;padding:0px 0px 0px 32px;list-style-type:disc;"><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">If AI drafts the tickets, the quality of what gets built is decided by the context it receives. That context is what you’ll optimize. </span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">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.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Build and maintain the reference material that our AI tooling and our engineers pull from, and keep it accurate as the product changes. Stale documentation now produces bad tickets and bad code automatically, at scale.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Review tickets and specs against reality before anyone builds them. This is the part that matters 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.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Capture acceptance criteria, edge cases, failure behavior, and explicit non-goals so a pod can pick something up and build it without a meeting.</span></li></ul><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><b><strong style="white-space:pre-wrap;">2. Product Data & Analysis</strong></b></p><ul data-pattern="discCircleSquare" data-depth="1" style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;margin:8px 0px;line-height:1.6;padding:0px 0px 0px 32px;list-style-type:disc;"><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">You’ll answer product questions with SQL against real data. Things like usage, throughput, drop-off, exception rates, workflow completion, turnaround times.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Quantify shipped work. Did it move the number it was supposed to move, and by how much.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Build and maintain the recurring reporting the pods rely on, so nobody rebuilds the same query every month.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Surface what nobody asked about. Note the distribution, the outliers, and the places where two numbers should reconcile and don't. The anomaly is usually the real finding.</span></li></ul><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><b><strong style="white-space:pre-wrap;">3. Prototyping to Communicate</strong></b></p><ul data-pattern="discCircleSquare" data-depth="1" style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;margin:8px 0px;line-height:1.6;padding:0px 0px 0px 32px;list-style-type:disc;"><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">A working prototype settles an argument that a document might extend. You will build them constantly, and then engineers will rebuild the real thing.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Use AI tooling to build rough, working versions of an idea. A screen, a script, a query tool, a data view, so the team can react to something concrete.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Build small internal tools for yourself and the team where doing so is faster than asking for one.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Hand intent to engineers clearly. Your prototype is the argument, not the implementation.</span></li></ul><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><br></p><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><b><strong style="font-size:18pt;white-space:pre-wrap;">Qualifications</strong></b></p><ul data-pattern="discCircleSquare" data-depth="1" style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;margin:8px 0px;line-height:1.6;padding:0px 0px 0px 32px;list-style-type:disc;"><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">3+ years as a business analyst, technical analyst, product analyst, data analyst, or in product operations, working closely with engineers.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Strong SQL. You write your own queries against a real schema, you understand what a join is doing to your row count, and you sanity-check your results before presenting them.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">You can read a database schema and work out how a product behaves from it.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">You already work with AI as a daily tool, not an experiment. You know how to structure context so output is reliable, you iterate on prompts rather than accepting the first answer, and you know when a model is confidently wrong and you check.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">You can build a rough working thing with AI assistance. Not production code. A prototype good enough that people can react to it instead of imagining it.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">You write clearly. In a setup like ours, written clarity is not a soft skill. It is the input that determines what gets built.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Analytical honesty. You quantify rather than characterize, you name your assumptions, and when numbers don't reconcile you stop and investigate instead of shipping the chart.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Comfort operating without process scaffolding, and comfort saying “not this week, here's why” when three people want the same hour.</span></li><li style="margin:3px 0px;font-size:11pt;line-height:1.6;letter-spacing:0.25px;"><span style="white-space:pre-wrap;">Bonus: B2B SaaS with enterprise customers, compliance- or workflow-heavy products, Python for analysis, or experience maintaining documentation that AI tooling depends on.</span></li></ul><p style="font-family:"Basel Grotesk",Arial,sans-serif;font-size:11pt;font-weight:400;line-height:1.6;letter-spacing:0.25px;margin:4px 0px;padding:0px;"><br></p>
Apply Now