Query Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We only include sections that have real specific content. We have About the role (the paragraph after "About the role"). We have Responsibilities? The posting includes "What you'll build" bullet list (connections, functionality, query layer, smart data preparation, data modeling). That could be considered Responsibilities. We'll map that to Responsibilities. We have Requirements/Qualifications/Skills: The "What we're looking for" bullet list includes many items: AI tools, coding agents, shipped AI-enabled products, etc. Also technical experience: 5+ years, SQL, cloud DB, etc. Full stack dev experience, AI/ML, track record, product thinking, comfort with ambiguity. We could split into Requirements and Skills perhaps. But we can combine into Requirements (or Qualifications). Since we prefer few substantive sections, we could have Requirements covering all those bullet points. Or we could have Skills for technical stack. But we need to avoid thin sections. Let's decide: Use Requirements for the bullet list under "What we're looking for". That includes both experience and skills. That's fine. Location: Not a standard heading; we could fold into a short p under About the role or maybe not needed. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata? Could be placed in a p after About the role. But we could also include a separate section? Not in list of allowed headings. So we should not create a heading for Location; just include it in a p. Hiring process: Not a standard heading; could be omitted or folded into a p. Probably we can include a short p about hiring process. Benefits: We have Benefits and perks paragraph with details. So we create Benefits section. Pay: compensation line. Schedule: Not given; we should not create Schedule section if not specified. Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3), Benefits (h3), Pay (h3). Possibly also Skills? But we can incorporate skills into Requirements. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given, maybe rephrase? We should preserve content but can format as
- . Must not omit any bullet. Let's extract bullet points: Under "What you'll build": - Connections to a wide variety of data platforms - Functionality to ingest, transform, and analyze data at scale - A query layer that can talk to a wide variety of databases and express rich operations - Smart data preparation and enrichment - Data modeling for analysis Under "What we're looking for": - You don't just use AI tools, you geek out over them. - Coding agents are part of how you work every day, you've shipped AI-enabled products, and you encode what you learn in ways your development tools can use. - You know where this technology falls short. You push it anyway. - There's no barrier between you and the people using what you build. You're comfortable jumping on a customer call, gathering feedback, and translating it directly into the next release. - You think like a founder: the best code delivers the most customer value and is still code you can reliably maintain. - You prioritize ruthlessly, decide quickly, and know when to optimize for delivery speed and when a problem deserves more time. - 5+ years of experience working on the internals of data products, with strong development experience at the data layer: SQL, cloud-based database systems, data lakes, and data interchange formats and techniques. You have built these layers, not just used them as a data engineer. - Full stack development experience and integration with cloud-deployed, customer-facing applications: Vite, Node, TypeScript, React, Postgres, Vercel, and Supabase, with more as we grow. - Experience building with AI/ML technologies such as LLMs, vector databases, and coding agents. - A track record of shipping rich, data-focused products. - Product thinking and customer orientation. - Comfort with ambiguity and rapid iteration. We need to keep each as separate
- . Some are sentences; fine.
Location paragraph: "This is an in-person role based in Bellevue, WA. We will consider relocation for exceptional candidates. H-1B visa transfers are supported; we are not sponsoring new H-1B visas at this time."
Hiring process paragraph: "Provn is our hiring partner, which provides an opportunity to showcase your capabilities to do the job through the application process. This application requires a short practical challenge built around the kind of query and data-connection problem this role solves. Build your solution, then create a video walking us through your approach and execution and how you used AI to be efficient, resourceful, and iterative. There's no time limit and no restrictions on using AI. Most candidates apply with a resume alone. Your application carries finished work on a task you would do on the job, plus a walkthrough that shows how you present, how you approach a problem, and how far you take it without being asked. Applications close October 10th."
Benefits paragraph: list of benefits. We need to keep details. Could format as
- each benefit.
Let's extract benefits:
- Health, fully covered. We cover 100% of employee medical, dental, and vision premiums, and 50% for your dependents. Our medical plan is a PPO with low copays and no primary care gatekeeping.
- Time off you control. Self-managed vacation time with no cap for salaried full-time employees. Plus ten paid company holidays a year.
- Real parental leave. Twelve weeks of fully paid leave for a new baby, adoption, or foster placement, coordinated with Washington's paid family and medical leave program.
- Life and peace of mind. Company paid life and AD&D coverage, paid sick leave, and paid time for jury duty and bereavement.
- Support when life gets complicated. A confidential Employee Assistance Program and 24/7 nurse line for you and your family. Counselors, nurses, and mental health resources any time.
- Stay healthy, get rewarded. Access to a nationwide fitness network, plus the ability to earn up to $1,000 a year in wellness rewards.
- Extras that make life easier. Paid parking at the Bellevue office, optional pet insurance, and modern tools to do your best work—including the AI tools we use every day.
Pay: "Compensation: $100,000 - $200,000 plus equity"
We need to output only HTML fragment, no markdown fences.
Let's construct:
About the role
... paragraph from About the role ...
Then maybe include location and hiring process asafter About the role? Could be separate
sections. We need to preserve all substantive info, so include location and hiring process paragraphs. Thus:
About the role
The Query Engineer builds and owns Golden's connections to the world: files, databases, cloud services, and data lakes. Golden goes to where its customers' data lives, and the connectors and query systems you build are what make "connect your data" work on the first try. Those systems have to balance expressiveness and speed, so customers can ask richer questions of their data without waiting longer for the answer. This isn't a role where you hand off specs and wait for feedback. You'll work directly with the founders and with customers, hear about their data issues firsthand, propose and build the fix, and get it out to them quickly. You'll also help shape product decisions and company culture. Every generation gets a new way to understand their data. We think this is that moment. If you want to work on a problem that's genuinely unsolved, at a company small enough that your fingerprints are on everything, come build it with us.
Location: This is an in-person role based in Bellevue, WA. We will consider relocation for exceptional candidates. H-1B visa transfers are supported; we are not sponsoring new H-1B visas at this time.
Hiring process: Provn is our hiring partner, which provides an opportunity to showcase your capabilities to do the job through the application process. This application requires a short practical challenge built around the kind of query and data-connection problem this role solves. Build your solution, then create a video walking us through your approach and execution and how you used AI to be efficient, resourceful, and iterative. There's no time limit and no restrictions on using AI. Most candidates apply with a resume alone. Your application carries finished work on a task you would do on the job, plus a walkthrough that shows how you present, how you approach a problem, and how far you take it without being asked. Applications close October 10th.
Then Responsibilities:Responsibilities
- Connections to a wide variety of data platforms
- Functionality to ingest, transform, and analyze data at scale
- A query layer that can talk to a wide variety of databases and express rich operations
- Smart data preparation and enrichment
- Data modeling for analysis
Requirements
- You don't just use AI tools, you geek out over them.
- Coding agents are part of how you work every day, you've shipped AI-enabled products, and you encode what you learn in ways your development tools can use.
- You know where this technology falls short. You push it anyway.
- There's no barrier between you and the people using what you build. You're comfortable jumping on a customer call, gathering feedback, and translating it directly into the next release.
- You think like a founder: the best code delivers the most customer value and is still code you can reliably maintain.
- You prioritize ruthlessly, decide quickly, and know when to optimize for delivery speed and when a problem deserves more time.
- 5+ years of experience working on the internals of data products, with strong development experience at the data layer: SQL, cloud-based database systems, data lakes, and data interchange formats and techniques. You have built these layers, not just used them as a data engineer.
- Full stack development experience and integration with cloud-deployed, customer-facing applications: Vite, Node, TypeScript, React, Postgres, Vercel, and Supabase, with more as we grow.
- Experience building with AI/ML technologies such as LLMs, vector databases, and coding agents.
- A track record of shipping rich, data-focused products.
- Product thinking and customer orientation.
- Comfort with ambiguity and rapid iteration.
Benefits
- Health, fully covered. We cover 100% of employee medical, dental, and vision premiums, and 50% for your dependents. Our medical plan is a PPO with low copays and no primary care gatekeeping.
- Time off you control. Self-managed vacation time with no cap for salaried full-time employees. Plus ten paid company holidays a year.
- Real parental leave. Twelve weeks of fully paid leave for a new baby, adoption
- each benefit.
Let's extract benefits:
- Health, fully covered. We cover 100% of employee medical, dental, and vision premiums, and 50% for your dependents. Our medical plan is a PPO with low copays and no primary care gatekeeping.
- Time off you control. Self-managed vacation time with no cap for salaried full-time employees. Plus ten paid company holidays a year.
- Real parental leave. Twelve weeks of fully paid leave for a new baby, adoption, or foster placement, coordinated with Washington's paid family and medical leave program.
- Life and peace of mind. Company paid life and AD&D coverage, paid sick leave, and paid time for jury duty and bereavement.
- Support when life gets complicated. A confidential Employee Assistance Program and 24/7 nurse line for you and your family. Counselors, nurses, and mental health resources any time.
- Stay healthy, get rewarded. Access to a nationwide fitness network, plus the ability to earn up to $1,000 a year in wellness rewards.
- Extras that make life easier. Paid parking at the Bellevue office, optional pet insurance, and modern tools to do your best work—including the AI tools we use every day.
Pay: "Compensation: $100,000 - $200,000 plus equity"
We need to output only HTML fragment, no markdown fences.
Let's construct: