Product Analytics - Developer Experience, Bridge

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who we are About Bridge", "What you’ll do", "Responsibilities", "Who you are", "Minimum Requirements", "Preferred Qualifications", "In-office expectations", "Pay and benefits". We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Who we are About Bridge: description of company. Could be "About the role"? Actually "About the role" is typical heading. But we have "Who we are About Bridge". Could treat as "About the role" or "About Bridge". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for the company description and role overview. Or we could have "About Bridge". But they gave examples; we can choose any appropriate heading. Probably "About the role" is appropriate for describing the role and company. - What you’ll do: description of responsibilities (but also separate Responsibilities section). Could combine? The posting has "What you’ll do" then "Responsibilities". Both contain similar content. We need to preserve all substantive info, not duplicate. We could merge them under a single "Responsibilities" section, as that is a heading we can use. Or we could have "What you’ll do" as a prose section and then "Responsibilities" as a list. But they said prefer few substantive sections over many thin ones. So maybe combine into one "Responsibilities" section that includes both narrative and bullet list. - Who you are: includes Minimum Requirements and Preferred Qualifications. Could be split into "Requirements" and "Qualifications". The instruction says use headings like Requirements, Qualifications. So we can have

  Requirements

  for minimum requirements, and

  Qualifications

  for preferred qualifications. Or combine? Better separate. - In-office expectations: could be under "Schedule"? Actually schedule refers to work schedule (remote/in-office). The instruction mentions Schedule heading. So we could use

  Schedule

  for in-office expectations. - Pay and benefits: we have Pay and benefits section with salary range and benefits. So we can have

  Pay

  and

  Benefits

  maybe combined? They said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay and benefits. So we can have separate Pay and Benefits headings, or combine into one "Pay and benefits". The examples list Pay and Benefits separate. We'll follow that:

  Pay

  for salary range,

  Benefits

  for benefits list. We must not include filler like "commensurate with experience". Not present. We need to remove boilerplate like "At Stripe, we're looking for people..." etc. That's at the end. Also "Please find our California applicant personal information notice here." and "Apply now". Also "We look forward to hearing from you." etc. Those are boilerplate/application instructions; we should remove them. Also remove duplicated lines. We need to preserve all substantive information: company description, role description, responsibilities, requirements, qualifications, in-office expectations, pay, benefits. Let's extract substantive content. From posting: Who we are About Bridge: We’re creating an entirely new payments platform, built with stablecoins, to simplify global money movement. Bridge enables faster, cheaper payments and borderless access to dollars via stablecoins. Through our APIs, businesses can send and receive funds across borders faster / cheaper vs. SWIFT and other fiat-only rails. Our virtual accounts enable international consumers and businesses to easily access, store and spend US dollars. Our payouts infrastructure enables platforms to disburse USD to anyone globally. We believe many trillions of dollars will move and settle through stablecoin payment rails. Bridge is pulling this future forward. We have a small team of people who have previously built financial infrastructure at some of the world’s leading companies (Coinbase, Stripe, Square, Brex, Upstart, DoorDash, Airbnb) and each and every one of them chose Bridge because they fundamentally believe that stablecoins will be a critical piece of financial infrastructure that allows for the improvement of global money movement. What you’ll do: We Are Looking For a Product Analyst To Join Our Data Team At Bridge. You'll Own The Data Strategy For Customer Experience At Bridge, Spanning Two Closely Linked Areas Payments quality — transaction speed, uptime/reliability, error rates, and support ticket trends across our payment rails and products. Product experience — how customers interact with Bridge's dashboard, onboarding flows, and other surfaces, and where friction is costing us adoption or trust. This focus area may shift over time as the business evolves, and we're looking for someone who can adapt their scope accordingly — spinning up their knowledge of different product areas, creating new analyses and instrumentation as priorities emerge or change. This is a high-ownership seat: you'll be the primary data voice for your focal area, expected to identify what matters, build the pipelines and analysis to prove it, and drive decisions from insight through to shipped outcomes — with real latitude to define how you get there. Responsibilities: Own the data needs for your focal area end-to-end: define and refine the right metrics, build the pipelines to source them, and drive them into decisions — without needing significant hand-holding. Analyze payments quality signals (latency, uptime, failure/error rates, support ticket volume and themes) to identify where customers are experiencing friction and quantify the business impact. Analyze product and UX data (dashboard usage, onboarding funnels, feature adoption) to find opportunities to improve the customer journey. Design, build, and maintain robust, well-documented data pipelines and ETL processes that make customer experience data easy to access, trust, and query across the company. Write and maintain production-quality SQL and pipeline code in Databricks, with work version-controlled and reviewed via GitHub. Build and maintain dashboards and self-serve tools that let Product, Engineering, and Support teams monitor customer experience metrics without depending on ad hoc requests. Partner cross-functionally with Product, Engineering, and Support/Operations to translate findings into concrete product and process improvements. Proactively flag emerging issues or trends in payments quality or product experience before they become customer-facing problems. Continuously improve data quality, documentation, and tooling for your focal area as Bridge's product and scale evolve. Who you are: We’re looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement. Minimum Requirements 6+ years of experience as a data analyst or in a similar analytics role, ideally at a payments, fintech, or high-growth technology company. Excellent SQL skills, with experience querying and modeling data in a modern warehouse/lakehouse environment (e.g., Databricks). Hands-on experience building and maintaining data pipelines and ETL processes, and comfort working with version control (GitHub) as part of a technical workflow. Strong analytical and diagnostic skills — able to independently investigate a problem, identify root cause, and turn findings into a clear recommendation. Experience building dashboards and visualizations that communicate insights clearly to both technical and non-technical stakeholders. Demonstrated ability to work independently, take ownership of a focal area, and manage multiple concurrent priorities with minimal oversight. Strong written and verbal communication skills, with the ability to explain technical or data-driven findings to non-technical audiences. Preferred Qualifications Experience analyzing payments data specifically (transaction quality, uptime/reliability, support ticket trends) or product/UX data (onboarding, dashboard engagement, funnels). Programming experience (e.g., Python) and familiarity with data manipulation libraries (e.g., pandas). Experience working in a fast-paced startup or high-growth environment where priorities and scope shift with the business. In-office expectations Office-assigned Stripes in most of our locations are currently expected to spend at least 50% of the time in a given month in their local office or with users. This expectation may vary depending on role, team and location. For example, Stripes in Stripe Delivery Center roles in Mexico City, Mexico, Bengaluru, India, and Dublin, Ireland work 100% from the office. Also, some teams have greater in-office attendance requirements, to appropriately support our users and workflows, which the hiring manager will discuss. This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while supporting flexibility when possible. Pay and benefits The annual US base salary range for this role is $161,600 - $242,400. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. This salary range may be inclusive of several career levels at Stripe and will be narrowed during the interview process based on a number of factors, including the candidate’s experience, qualifications, and location. Applicants interested in this role and who are not located in the US may request the annual salary range for their location during the interview process. Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends. We need to remove boilerplate like "We look forward to hearing from you. At Stripe, we're looking for people with passion, grit, and integrity. You're encouraged to apply even if your experience doesn't precisely match the job description. Your skills and passion will stand out—and set you apart—especially if your career has taken some extraordinary twists and turns. At Stripe, we welcome diverse perspectives and people who think rigorously and aren't afraid to challenge assumptions. Join us. Apply now Please find our California applicant personal information notice here." Also remove duplicated lines like "We Are Looking For a Product Analyst To Join Our Data Team At Bridge." maybe keep as part of role description. Now decide sections: - About the role: combine Who we are About Bridge and What you’ll do (maybe a brief intro). Could be a

  with company description and role overview. - Responsibilities: list bullet points from Responsibilities section. - Requirements: list bullet points from Minimum Requirements. - Qualifications: list bullet points from Preferred Qualifications. - Schedule: in-office expectations paragraph. - Pay: salary range paragraph. - Benefits: list bullet points of benefits. We must not create sections with filler. All have content. Now produce HTML fragment. Use

  for each heading. Inside each section, use

  for prose,

  • for lists. We need to ensure