Staff Software Engineer, PostgreSQL

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting and extract sections. Let's identify content: - Intro about company: "Beacon Biosignals is transforming precision medicine..." This is about the role? Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have description of role: "Beacon Biosignals is seeking a Software Engineer IV to join our Datastore team." Then description of Datastore, responsibilities, etc. We have "What success looks like" bullet points (list). That could be Responsibilities? Or maybe "What you will bring" is Requirements/Qualifications. We have "What you will bring" list of qualifications/experience. We have "For The Datastore Systems Role" and "For The PostgreSQL & Data Modeling Role" - these are sub-focus areas; maybe they go under Responsibilities or Skills? Could be separate sections? But we should only include headings when there is real specific content. Could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay: "The US-based salary range for this role is $170,000 – $190,000." Also mention equity, PTO, other benefits. So we can have Pay section with that salary range. Benefits: mention equity, PTO, other benefits. Also mention remote work, office hubs. Could be Benefits. Schedule: mention "This role is 100% remote from anywhere in the U.S." Also mention asynchronous work practices, office hubs. That could be Schedule? Actually schedule is about work hours/remote. Could be Schedule section. We need to avoid filler like "commensurate with experience". Not present. We must not invent or summarize away detail. Must preserve all substantive information. So we need to include all details from the posting, but we can format them into sections. We need to decide what goes where. Let's extract sections: **About the role**: Could include company mission and role context: "Beacon Biosignals is transforming precision medicine... Beacon Biosignals is seeking a Software Engineer IV to join our Datastore team. The Datastore sits at the heart..." etc. That seems appropriate. **Responsibilities**: Could include "What success looks like" bullet points (lead design, partner, debug, mentor, etc.) Also the two focus areas (breadth vs depth) maybe responsibilities. Also "You will lead design and architecture..." etc. Also "You partner with product managers..." etc. Also "You debug and profile..." etc. Also "You teach and mentor..." etc. Also "You leverage feedback..." etc. Also "You plan your own work..." etc. Also "You may act as tech lead..." etc. Also "You leverage feedback..." etc. Also "You draft RFCs..." etc. Also "You plan your own work..." etc. Also "You teach and mentor..." etc. Also "You leverage feedback..." etc. Also "You plan your own work..." etc. Actually many duplicates. We need to capture all bullet points under "What success looks like". Also the two focus areas descriptions maybe under Responsibilities or Skills. **Requirements / Qualifications**: Could be "What you will bring" list: 7+ years backend dev, 3 years data platforms, proficiency in SQL/PostgreSQL, experience with Kafka, proficiency in Julia or Python, experience deploying services in containerized environments with Kubernetes/IaC, track record of mentoring, collaborative mindset, excellent communication, self-directed, experience with LLM-assisted coding tools. Also maybe "core requirements are the same" for both foci. **Skills**: Could list technical skills: SQL, PostgreSQL, Kafka, Julia/Python, Kubernetes, Terraform/Helm, GraphQL, TypeScript/JavaScript, Node.js, event pipelines, data modeling, distributed systems, API design, database engineering, etc. But we might avoid duplication. **Benefits**: equity, PTO, other benefits, remote work, office hubs (Boston, NYC, Paris), asynchronous work practices. **Pay**: salary range $170k-$190k. **Schedule**: 100% remote, asynchronous work, office hubs. We need to ensure we don't create sections with placeholder text. All sections must have real content. We must not include boilerplate like EEO, legal, etc. Not present. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment, no /, no markdown fences. Let's craft. We'll use

for each section heading. Inside sections, use

for prose,

• for lists. We need to preserve all substantive information. That's a lot; we need to ensure we don't omit any detail. Let's list all substantive sentences from posting. I'll copy the text and parse. Original: "Beacon Biosignals is transforming precision medicine for the brain, from clinical development to clinical care. For Life Sciences partners, we offer the leading at-home EEG platform for clinical development of novel therapeutics for neurological, psychiatric, and sleep disorders. Our Diagnostics business is building the most comprehensive at-home platform for precision diagnostics, combining EEG and cardiopulmonary signals to deliver reimbursable assessments for sleep and central nervous system disorders. Together, we're changing the way patients are diagnosed and treated for any disorder that affects brain physiology. Beacon Biosignals is seeking a Software Engineer IV to join our Datastore team. The Datastore sits at the heart of Beacon's platform. It defines our foundational data model and serves as the centralized repository and API for brain data collected from clinical studies, supporting the analytical tools, services, and applications used by our scientists, clinicians, and partners. This role emphasizes the design and scaling of backend systems for data infrastructure: PostgreSQL data models, Kafka-driven event pipelines, and the GraphQL API that makes scientific and clinical data usable - distinct from frontend development or end-user product surfaces. At this level you will lead the design of complex systems within the Datastore rather than individual components, own the pipelines that deliver dataset snapshots into our warehouse, and collaborate across platform, application and scientific teams to implement APIs that unlock new workflows in Beacon's expanding portfolio of clinical studies and digital health products. You should have experience writing complex SQL queries by hand, and should be prepared to reason about schema design, indexes, and query behavior as a matter of course. Two properties of our system that shape our work may influence your application. Our GraphQL API is generated from the PostgreSQL schema using PostGraphile, so a schema decision is an API decision. Secondly, row-level security is in force on effectively every table, because clinical data from different studies and partners shares one schema, with some rows shared for access by multiple internal teams. RLS predicates get injected into your queries, which makes reasoning about query plans genuinely harder here than it is in most places. If that sounds interesting rather than tedious, you'll enjoy this team. We are hiring two engineers into this role, with two different centers of gravity. One will focus on the breadth of the Datastore: the event pipelines, the GraphQL API, core data models, and third-party integrations. The other will focus on depth in PostgreSQL (data modeling, performance tuning, operations) and supporting all engineers in developing schemas and the access controls that protect clinical data. The core requirements are the same. Tell us which one you are most drawn to in your application. This role is 100% remote from anywhere in the U.S. Beacon's robust asynchronous work practices ensure a first-class remote work experience, but we also have in-person office hubs in Boston, New York City, and Paris. What success looks like You lead design and architecture for complex projects and systems within the Datastore, weighing implementation trade-offs with engineering principles and backing your decisions with data rather than preferenceYou partner with product managers, scientific and clinical stakeholders, and other development and support teams to translate their requirements into new integrations, services, and solutions for scaling Beacon's data platform - contributing to broader product and technical decisions, not simply implementing themYou debug and profile ambiguous problems that cross system boundaries, including codebases beyond the Datastore's purview, and you leave what you touch better than you found it — structure, test coverage, toolingPeers look to your work as an example: you implement features with attention to detail, demonstrating product awareness and high standards for data integrity, design soundness, and maintainability across the lifespan of the systemYou draft RFCs to lead complex feature discovery and technical design phases, soliciting and incorporating input, and helping your team align on a set of decisions to guide developmentYou plan your own work and contribute to planning the team's, making reasoned trade-offs between speed, generalizability, and technical debt, and accounting for the needs of multiple stakeholder teamsYou teach and mentor other engineers regularly, give feedback that people act on, and are sought out for it. You may act as tech lead on a project or as the coordination point for engineering practice within the teamYou leverage feedback from internal stakeholders and external partners to improve operational robustness and ease of use of the Datastore and its services via new documentation, tools, and dashboards What you will bring 7+ years of backend development experience, including at least 3 years focused on data platforms and backend infrastructure for data-centric applications: transactional systems, event pipelines, and the APIs that serve themHighly proficient in at least one technical area relevant to this work: data modeling, distributed systems, API design, or database engineering, with the depth that others on a team come to you forStrong proficiency in SQL, with production experience working with PostgreSQL as an application database; you write and tune queries fluently and are comfortable reasoning about schema design, indexes, and query plansHands-on experience with data streaming and event processing, using Kafka (our event bus) or an equivalent such as RabbitMQ, Pulsar, or a cloud-based equivalent like Amazon KinesisProficiency in Julia or Python; Julia is a core Datastore language, and experience with Julia is a strong plus, but not required — we welcome candidates eager to learn it!Experience deploying and operating services in containerized environments, with familiarity in Kubernetes and Infrastructure as Code (IaC) tools such as Terraform and/or HelmA track record of mentoring engineers and improving how a team works - practices, tooling, test coverage, or documentation that outlasted your involvementA collaborative mindset: you enjoy working across disciplines and believe people achieve more together than aloneExcellent written and verbal communication skills, especially in asynchronous and remote-friendly environmentsA self-directed approach, with a track record of thriving in hybrid or fully remote teamsExperience with, or interest in, using LLM-assisted or agentic coding tools in a production setting, with good judgment about what guardrails are needed For The Datastore Systems Role You can lead design across the breadth of the platform.GraphQL and TypeScript/JavaScript (Node.js) - GraphQL is the Datastore's primary interface, and this profile owns significant parts of itDesigning event-driven pipelines end to end: producers, consumers, replay, idempotency, and what happens when a consumer falls behindLeading the design of complex systems rather than individual components, across the API, the pipelines, and the services that depend on them For The PostgreSQL & Data Modeling Role You can be the person the rest of the team comes to about the database.Deep PostgreSQL: you reason fluently about the query planner, index selection, and EXPLAIN (ANALYZE), and why a query that should be fast isn'tData modeling: you design the schema itself: entities, relationships, and the constraints that make invalid states impossible. Including how to model time, since clinical results get re-scored and corrected and we need to answer "what did this look like when the report was signed?"Schema evolution under load: zero-downtime migrations, dual-write transitions, lock