Software Engineer – Query Engines
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
The estimated salary range for this position is $135,000 - $200,000/year. Total compensation may also include Restricted Stock units, sign-on bonus and other potential future incentives.
Schedule
Palantir encourages in‑office work to foster connectivity and innovation; many teams offer hybrid options (WFH a day or two a week). Remote work is permitted on an exceptional basis, requiring the employee to work from the state in which they are employed. If the role is designated Onsite, office attendance is required.
We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information from the posting. Let's extract details. About the role: The paragraph after "The Role" includes: "We are a software engineering team applying open-source data technologies to some of the world’s hardest and most important problems. We build the data processing infrastructure that underpins Palantir Foundry, supporting applications that help hospitals care for more patients, help clinical teams coordinate timely diagnoses, and keep essential supplies moving through global disruption. You will work deep inside the systems that make this possible: how computations are represented, how query plans are optimized, how operators execute, and how data is read and written efficiently. We build on and extend Apache Spark, Apache DataFusion, and Apache Iceberg, bringing advances in open-source engines and table formats into the demanding environments our customers operate in. Our work serves many products and workloads across Foundry, including no-code pipelines, interactive analysis, and the processing that keeps the Ontology up to date. You will own improvements from design through production, whether that means developing a planning rule, extending a native execution engine, or improving the way large tables are scanned and updated. Correctness, compatibility, and predictable performance are central to everything we build. A change in a shared engine can benefit applications across the platform and the people who rely on them. Join us if you want to advance the capabilities of modern data systems and apply that work to consequential problems." We'll put that in. Technologies We Use: list of languages and tools. Could be part of Skills section. Core Responsibilities: list bullet points. What We Value: bullet points (ownership mindset, curiosity, debugging skills, practical approach to performance, interest in applying deep systems engineering, experience building or extending systems such as Spark, DataFusion, Iceberg, ability to collaborate across teams, experience contributing to open-source projects valued but not required). Could be Qualifications or Skills. What We Require: bullet list. Benefits: list. Pay: salary range. Schedule: as described. We need to avoid duplication: maybe Skills section includes languages and tools; Qualifications includes experience and traits. Let's decide: - About the role: paragraph. - Responsibilities: bullet list from Core Responsibilities. - Requirements: bullet list from What We Require. - Qualifications: bullet list from What We Value (ownership mindset, curiosity, debugging, practical performance approach, interest in applying deep systems engineering, experience building/extending systems such as Spark, DataFusion, Iceberg, ability to collaborate across teams, open-source contribution experience valued but not required). Also maybe "Engineering background in Computer Science, Mathematics, Software Engineering, Physics, or similar field, or equivalent practical experience." That is in Requirements though. Actually that is in Requirements. So Qualifications could be the "What We Value" items. - Skills: bullet list of technologies: Java, Scala, Rust, Python; Apache Spark, Apache DataFusion, Apache Comet, Velox; Apache Iceberg; Apache Arrow, Apache Parquet; Gradle, Cargo, GitHub. - Benefits: bullet list from Benefits. - Pay: paragraph. - Schedule: paragraph. We must ensure we don't include any boilerplate like "Life at Palantir" etc. That's not needed. We need to preserve all substantive information: The "Life at Palantir" paragraph about culture, in-person work, hybrid options, remote exceptional basis. That's schedule info; we captured that. We also need to preserve the note about "Total compensation for this position will be determined by each individual’s relevant qualifications, work experience, skills, and other factors." That's part of Pay section. We also need to preserve "This estimate excludes the value of any potential sign-on bonus; the value of any benefits offered; and the potential future value of any long-term incentives." That's also Pay. We also need to preserve "Our benefits aim to promote health and wellbeing across all areas of Palantirians’ lives. We work to continuously improve our offerings and listen to our community as we design and update them." That's part of Benefits intro. We also need to preserve the list of benefits items. We also need to preserve "Employees (and their eligible dependents) can enroll in medical, dental, and vision insurance as well as voluntary life insurance Employees are automatically covered by Palantir’s basic life, AD&D and disability insurance Commuter benefits Relocation assistance Take what you need paid time off, not accrual based 2 weeks paid time off built into the end of each year (subject to team and business needs) 10 paid holidays throughout the calendar year Supportive leave of absence program including time off for military service and medical events Paid leave for new parents and subsidized back-up care for all parents Fertility and family building benefits including but not limited to adoption, surrogacy, and preservation Stipend to help with expenses that come with a new child Employees can enroll in Palantir’s 401k plan" We need to format as bullet list. We also need to preserve "Life at Palantir We want every Palantirian to achieve their best outcomes, that’s why we celebrate individuals’ strengths, skills, and interests, from your first interview to your longterm growth, rather than rely on traditional career ladders. Paying attention to the needs of our community enables us to optimize our opportunities to grow and helps ensure many pathways to success at Palantir. Promoting health and well-being across all areas of Palantirians’ lives is just one of the ways we’re investing in our community. Learn more at Life at Palantir and note that our offerings may vary by region." That's more about culture; maybe we can include in Schedule or a separate section? But we have no heading for culture; we could incorporate into Schedule or maybe a "Culture" section but not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." So we could omit culture details if they are not covered by allowed headings. However we must preserve ALL substantive information. If we omit culture details, we lose substantive info. But maybe we can incorporate into Schedule or Benefits? The culture paragraph is about work philosophy, not benefits or schedule. Could be part of About the role? It describes team values. Could be added to About the role paragraph. That would preserve it. Thus we can extend About the role to include that culture paragraph. Let's extract that paragraph: "Life at Palantir We want every Palantirian to achieve their best outcomes, that’s why we celebrate individuals’ strengths, skills, and interests, from your first interview to your longterm growth, rather than rely on traditional career ladders. Paying attention to the needs of our community enables us to optimize our opportunities to grow and helps ensure many pathways to success at Palantir. Promoting health and well-being across all areas of Palantirians’ lives is just one of the ways we’re investing in our community. Learn more at Life at Palantir and note that our offerings may vary by region." We can append to About the role. Now we need to ensure we don't include the EEO etc. Now produce HTML. We'll need to escape any HTML special characters? The text includes ampersands etc. We'll just output as is; it's fine. Let's craft.
About the role
We are a software engineering team applying open-source data technologies to some of the world’s hardest and most important problems. We build the data processing infrastructure that underpins Palantir Foundry, supporting applications that help hospitals care for more patients, help clinical teams coordinate timely diagnoses, and keep essential supplies moving through global disruption. You will work deep inside the systems that make this possible: how computations are represented, how query plans are optimized, how operators execute, and how data is read and written efficiently. We build on and extend Apache Spark, Apache DataFusion, and Apache Iceberg, bringing advances in open-source engines and table formats into the demanding environments