Staff Full Stack Engineer

Burtch Works β€” United States Β· Posted ~2 hours ago

Senior Full-time Remote

Skills

Full stack development Software engineering Backend development Frontend development Frontend Backend Data platforms

πŸ”“ Log in to save this job, tailor your resume & track your apply process β€” 7 days free, no card needed.

Log in to add to target list

Summary ✨ AI‑Generated

A research and technology organization is seeking a staff full stack engineer to build platforms that leverage data and experimentation. The role involves high-level engineering decisions and rapid product development.

Highlights

Join an advanced engineering team building impactful platforms in a flexible remote environment with significant technical ownership.

Description

Staff Full-Stack Engineer Job Title: Staff Full-Stack Engineer Reports To: VP of R&D Location: Remote (United States) Travel: Not required About The Company Our client is a research-and-technology organization that uses data, experimentation, and applied engineering to help partner organizations operate more effectively. They have run 100+ randomized controlled trials (RCTs) on behavioral data and supported hundreds of partner organizations in increasing their impact. The environment is fast-paced and adaptive β€” the team is comfortable shifting quickly as priorities evolve, and is looking for candidates who thrive in that kind of setting. The client's identity will be shared directly with qualified candidates as they progress through the process. Position Overview Our client is hiring a Staff Full-Stack Engineer to join their R&D team and help build the platforms that put data to work at the speed of thought. The R&D team is where the client places its most ambitious technical bets β€” moonshots (high-upside projects with uncertain payoffs) that need the muscle to break through. Their flagship platform turns warehouse data into searchable, queryable large-scale databases, serves them through fast read-side APIs, and puts an LLM-powered agent in front of internal teams so they can analyze large operational datasets, build targeting segments, and design experiments. It's a Go backend (analytics, search, and geo services over DuckDB, SQLite, and AlloyDB), a React/TypeScript frontend with a type-driven visual grammar, an agent surface, and a CLI/SDK, all deployed on Google Cloud Platform and defined in Terraform. This person will work across all of it. This is a role for an engineer who wants to own a product end-to-end: dbt model to API to UI to deploy, and back again. This role partners closely with the R&D lead, takes on projects that span the whole stack, and grows into owning systems that are already in use across the organization. This role is fully remote and permanent. Job Responsibilities Build and ship features across the platform end-to-end, from the data model and Go API through the React UI and the Terraform that deploys themExtend the read-side platform (the analytics, search, and geo services) and the caching, batching, and connection-pooling that keep them fast under loadWork on the LLM agent surface and the visual grammar that renders its output as interactive, legible blocksMaintain and extend the CLI and Go SDK alongside the UIBuild and operate services and infrastructure on GCP, and participate in on-call and rapid response, including evenings and weekends during high-stakes operational windowsLoad-test and harden systems ahead of key operational deadlines, when the platform serves hundreds of partner organizations on a non-negotiable calendarSelf-review and validate your own work before requesting review; review teammates' code, mentor less-experienced engineers, and document systems so others can use them without spelunking through code How The Team Works Working systems, not code β€” code is a tool, not the job; the team builds systems that solve real problems for the people who use themData is the foundation β€” most of the value created comes from how the data is organized underneath the system; the team invests in the dbt and read-side layers firstTypes are contracts β€” the team leans on a statically-typed backend and generates TypeScript from Go types so the two stay in sync, catching drift at compile time rather than in productionPerformance is a feature β€” fast read paths and fast feedback loops make everything downstream easier, including correctnessBuild it and run it β€” there's no separate ops team; infrastructure is code, and the team deploys what it writes and is on call for it, especially during high-stakes operational windowsSmall changes, shipped constantly β€” small, self-validated pull requests released to production several times a week, catching issues through monitoring rather than from a partnerReproducibility and simplicity β€” consequential operations are driven by immutable, declarative manifests, and the team does the simple thing first, adding complexity only when there's evidence it's needed Requirements (Must-Haves) 7+ years building and operating production software end-to-end, across both backend and frontendStrong proficiency in a statically-typed backend language (the team uses Go) and in modern frontend development with TypeScript and ReactExperience with the data layer: SQL, a transformation framework like dbt, and a cloud data warehouse (BigQuery or similar)Experience deploying and operating services on a cloud platform (the team uses GCP: Cloud Run, GKE, Cloud SQL/AlloyDB) and managing infrastructure as code with TerraformA track record of leading technical work that spans multiple systems, and of scoping ambiguous problems end-to-endStrong written communication: able to document what you build and explain complex systems to non-engineersComfortable operating in a fast-paced, mission-driven environment with shifting priorities Nice To Have Experience building product surfaces on top of LLMs: agent workflows, tool calling, or structured generationExperience with high-performance read paths: columnar/analytical query engines (DuckDB), embedded databases (SQLite), connection pooling, and cachingExperience in mission-driven, advocacy, or nonprofit sectors, including familiarity with the compliance and data-sensitivity considerations common to those environmentsExperience with large-scale behavioral, customer, or public-sector dataExperience in on-call rotations and mentoring less-experienced engineers