Principal Software Engineer, High Value Send

We need to output HTML fragment with sections: About the role? Actually we have sections: About High Value Senders, The Role, What You'll Do, You Have, Nice to Have, Our Benefits, Our Connected Work Culture (maybe schedule). Also we have Pay? Not present. Schedule? The hybrid work expectation is schedule info: employees work onsite Tuesday through Thursday each week. That's schedule info. So we can include a Schedule section. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Remove duplicated lines (the equal opportunity repeated). Remove navigation/cookie etc. Not present. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information. Not invent or summarize away detail. Must not include placeholder sections like Pay if not present. We need to decide which sections to include based on content. Sections present: - About High Value Senders (description) - The Role (description) - What You'll Do (list of responsibilities) - You Have (requirements) - Nice to Have (preferred qualifications) - Our Benefits (list) - Our Connected Work Culture (includes hybrid work schedule (schedule) Potentially also "About High Value Senders" could be considered "About the role"? But we should follow headings as they appear: "About High Value Senders", "The Role", "What You'll Do", "You Have", "Nice to Have", "Our Benefits", "Our Connected Work Culture". Use

  for each. We need to ensure we don't create sections with filler. All have content. We need to format lists: For responsibilities under "What You'll Do": there are bullet-like sentences separated by periods. We'll convert each sentence into

  . The text includes line breaks? We'll parse. Responsibilities text: "Build New Products and Lead AI Adoption Create new HVS propositions. Enable teams to test and launch 0-to-1 experiences with measurable customer outcomes, extensible foundations and safe rollout controls.Operate AI-natively and evaluate emerging capabilities for step-change improvements in customer experience and software delivery. Turn effective approaches into repeatable domain practices and reflect demonstrated gains in delivery and capacity planning.Establish domain-level AI accountability: appropriate use boundaries, evaluation methods, and review standards for correctness, security, and maintainability. Build these practices into technical design, code, testing, and delivery workflows. Set Technical Vision and Strategy for High Value Senders Own HVS technology strategy and architecture, connecting core experiences, customer growth, and emerging propositions. Use customer signals, product judgment, and data to guide investments and technical decisions.Connect technical strategy to business outcomes, including transfer success, conversion, retention, and cost to serve. Advise leadership on roadmap priorities, technical risks, talent needs, and investment trade-offs.Lead domain-level design reviews that align with Remitly’s long-term architecture. Make expected business value, ownership, dependencies, and critical trade-offs clear to technical and non-technical leaders. Build the Foundations for High Value Transfers Define architecture across web, mobile, and backend services for high-value transfer journeys. Segment systems and ownership so teams can build independently while delivering a coherent customer experience.Partner with identity and trust, money movement, pricing, and Core Transfer Experience teams to resolve shared architecture and ownership questions. Decide where to extend existing foundations and where new capabilities are needed.Solve the domain’s hardest architectural problems, including persistent bottlenecks, excessive dependencies, and scaling limits. Balance speed, maintainability, and technology viability through incremental launches and migrations. Make Customer Trust an Engineering Standard Establish and refine reliability, security, privacy, and quality standards with functional experts. Drive consistent testing, observability, deployment, and maintenance practices across HVS, supported by clear availability and latency SLOs.Design resilient integrations and recovery paths for asynchronous financial workflows. Make transaction state, retries, and failure handling explicit so customers and support teams can understand what happens next.Make clear pricing, accurate status, and secure handling of customer data architectural requirements. Address root causes of operational failures and mitigate risks to systems’ ability to scale and support new business needs. Multiply the Engineering Organization Proactively mentor staff and senior engineers and raise the quality of technical leadership across HVS. Advise on team boundaries and ownership models that improve autonomy and productivity.Stay close to the code through deep system analysis, meaningful reviews, prototypes, and production contributions. Apply hands-on expertise where it resolves critical needs and sets direction for the domain.Build relationships across engineering and product leadership to resolve cross-org problems. Recognize stalled decisions, surface competing constraints, and drive timely alignment and delivery." We need to split into list items. Each sentence ends with a period. Some sentences have no space after period before next sentence (e.g., "...controls.Operate"). We'll need to handle that. We'll just split by period followed by space or capital letter? Simpler: we can manually create list items based on the logical groupings: The responsibilities are grouped under headings: Build New Products and Lead AI Adoption, Set Technical Vision and Strategy..., Build the Foundations..., Make Customer Trust an Engineering Standard..., Multiply the Engineering Organization... We could keep each heading as a subheading? But spec says use

  for section headings only; we can't add extra headings beyond those sections. However we can still have

  • with the heading text as part of the li? Might be okay but better to keep each responsibility as separate li, maybe starting with the bold phrase. We'll produce li items like: - Build New Products and Lead AI Adoption: Create new HVS propositions. Enable teams to test and launch 0-to-1 experiences with measurable customer outcomes, extensible foundations and safe rollout controls. Operate AI-natively and evaluate emerging capabilities for step-change improvements in customer experience and software delivery. Turn effective approaches into repeatable domain practices and reflect demonstrated gains in delivery and capacity planning. Establish domain-level AI accountability: appropriate use boundaries, evaluation methods, and review standards for correctness, security, and maintainability. Build these practices into technical design, code, testing, and delivery workflows. But that lumps many sentences. Could break each sentence. Given the instruction: "Use
    • for any list of duties/requirements/benefits". It doesn't forbid multiple sentences inside a li. So we can group logically. We'll produce li for each major bullet: Build New Products and Lead AI Adoption (with its subpoints), Set Technical Vision and Strategy..., Build the Foundations..., Make Customer Trust an Engineering Standard..., Multiply the Engineering Organization... Similarly for Requirements (You Have) we have a paragraph with multiple sentences; we can break into li each requirement. Let's extract You Have sentences: "You Have: 12+ years of software engineering experience, including significant time designing and operating large-scale, customer-facing distributed systems.Deep backend expertise in languages such as Java, Kotlin, Go, or Python, plus experience shaping customer-facing web and mobile systems with technologies such as TypeScript, React, or native mobile frameworks.Advanced distributed-systems design expertise, including cloud infrastructure, safe architecture evolution, and resolving root causes of scaling, latency, data-quality, or dependency problems in production.A track record of setting domain-level technical strategy, leading large-system design reviews, and segmenting architecture and ownership to enable autonomous teams. Experience informing organizational design and growing technical leaders.Experience establishing engineering and operational standards across teams, with sound judgment about reliability, security, privacy, maintainability, and the business risks of technical decisions.Strong customer and product judgment. Proven ability to resolve ambiguous cross-org problems, influence roadmaps and investment decisions, and connect technical proposals to business outcomes for technical and non-technical leaders.Hands-on use of AI in software delivery and experience scaling effective practices beyond your own work, including validation, review standards, and evaluating gains in speed, quality, or efficiency." We need to split sentences. Some missing spaces after periods. We'll manually split. List items: - 12+ years of software engineering experience, including significant time designing and operating large-scale, customer-facing distributed systems. - Deep backend expertise in languages such as Java, Kotlin, Go, or Python, plus experience shaping customer-facing web and mobile systems with technologies such as TypeScript, React, or native mobile frameworks. - Advanced distributed-systems design expertise, including cloud infrastructure, safe architecture evolution, and resolving root causes of scaling, latency, data-quality, or dependency problems in production. - A track record of setting domain-level technical strategy, leading large-system design reviews, and segmenting architecture and ownership to enable autonomous teams. - Experience informing organizational design and growing technical leaders. - Experience establishing engineering and operational standards across teams, with sound judgment about reliability, security, privacy, maintainability, and the business risks of technical decisions. - Strong customer and product judgment. - Proven ability to resolve ambiguous cross-org problems, influence roadmaps and investment decisions, and connect technical proposals to business outcomes for technical and non-technical leaders. - Hands-on use of AI in software delivery and experience scaling effective practices beyond your own work, including validation, review standards, and evaluating gains in speed, quality, or efficiency. Nice to Have sentences: "Nice to Have Experience in cross-border payments, high-value transactions, or other regulated financial services, including integrations with funding, identity, risk, or compliance systems.Experience building premium financial experiences, wealth-related products, or other services that require high customer confidence and complex workflows.Experience with experimentation, customer acquisition and retention, or personalized product experiences.Experience serving global customers across markets with different payment methods, regulatory requirements, and customer expectations." Split: - Experience in cross-border payments, high-value transactions, or other regulated financial services, including integrations with funding, identity, risk, or compliance systems. - Experience building premium financial experiences, wealth-related products, or other services that require high customer confidence and complex workflows. - Experience with experimentation, customer acquisition and retention, or personalized product experiences. - Experience serving global customers across markets with different payment methods, regulatory requirements, and customer expectations. Benefits list: "Our Benefits: Flexible paid time offHealth, dental, and vision + 401k plan with company matchingPaid parental, medical, military and family care leaveMental Health & Family Forming BenefitsEmployee Stock Purchase Plan (ESPP)Continuing education benefits" We need to split: There's missing spaces. Let's parse: - Flexible paid time off - Health, dental, and vision + 401k plan with company matching - Paid parental, medical, military and family care leave - Mental Health & Family Forming Benefits - Employee Stock Purchase Plan (ESPP) - Continuing education benefits Schedule/hybrid work: "Under the Company's current hybrid-work expectations, employees in this position work onsite Tuesday through Thursday each week. Additional onsite attendance may be required based on business needs, and the Company may modify its hybrid-work expectations from time to time." We'll make a Schedule section with that paragraph. Now About High Value Senders paragraph: we need to preserve. "The High Value Senders team helps customers move larger sums of money across borders with confidence. These transfers represent significant life decisions, from buying a home and funding education, to supporting investments and long-term financial goals. Our scope spans the high-value send experience, customer growth, and new product workstreams such as wealth building. We partner closely with Core Transfer Experience and shared platform teams to turn complex financial journeys into clear, dependable experiences." We'll put in

      . The Role paragraph: "As Principal Engineer for High Value Senders, you will own technology strategy and architecture across the HVS domain. You will partner with engineering, product, design, marketing and analytics to define how we earn customer trust on their most consequential transfers. You will solve the domain’s hardest technical problems, shape how systems are divided and owned across teams, and align decisions with Remitly’s long-term architecture and business goals. This full-stack role spans customer-facing web and mobile experiences, backend systems, and deep partnership with foundational teams across identity and trust, money movement, pricing, and Core Transfer Experience. You will turn ambiguous, greenfield opportunities into new products while evolving shared systems safely. You will remain hands-on through system analysis, meaningful code contributions, and reviews