Jobs · Arizona

Principal Software Engineer

Cognite · Phoenix, AZ · 1 mo ago
Hybrid$100/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: description of Cognite, mission, etc. Could be "What Cognite is: ..." and "How you’ll demonstrate Ownership". That seems like about the role. - Responsibilities: The Impact you bring to Cognite bullet list. - Requirements: maybe "Relevant and hands-on concentrated experience..." etc. Also "Expert knowledge of computer science..." etc. - Qualifications: maybe "As we're hiring across several teams..."? Actually that's more like preferred experience. - Skills: list of technologies: JavaScript/TypeScript, React etc, cloud, Kubernetes, etc. - Benefits: "A snapshot of our many perks and benefits as a Cogniter" list: Competitive compensation, 401(k) with employer matching, Competitive health, dental, vision & disability coverages, Unlimited PTO, Paid Parental Leave Program, Employee Referral Program. - Pay: Not explicitly stated. There's "Competitive compensation" but that's vague. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. "Competitive compensation" is not a specific number; but it's still a statement about pay. However they said never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive compensation" is vague but maybe considered filler? It's not a specific amount. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Competitive compensation could be considered filler? It's not a specific number but it's still a statement. Might be okay? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive compensation". So we could include Pay section with that line. However they also said "Prefer a few substantive sections over many thin ones." Might combine Benefits and Pay? But they want separate sections if content exists. We'll include Pay with that line. - Schedule: Not mentioned. No schedule info. So omit Schedule. Now we need to format. Use

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

    for prose. We must not repeat job title. No markdown. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Equal Opportunity Cognite is committed..." that's EEO, remove. Also "Learn More About Us Impact 2025..." maybe not needed? It's about company info but could be part of About the role? Might be considered boilerplate? It's about locations and moonshot. Might be substantive? It's about company presence. Could keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn More About Us Impact 2025..." is not clearly boilerplate; it's about company presence. Might keep. But we need to avoid duplication. The posting repeats some sentences. We'll craft sections: About the role: combine the introductory paragraphs about Cognite, mission, moonshot, and "How you’ll demonstrate Ownership". Also maybe the "Learn More About Us Impact 2025..." part. Responsibilities: The Impact you bring to Cognite bullet list (starting with "As a Principal Full Stack Engineer, You'll Be a Key Player..."). Requirements: maybe the list of "You'll have the opportunity to drive architectural decisions..."? Actually that's responsibilities. Requirements: "Relevant and hands-on concentrated experience with software development in one or more programming languages (e.g., Kotlin, Java, Python, or Rust)." etc. Also "Expert knowledge of computer science with strong competencies in data structures, algorithms, and software design." Also "You possess deep expertise in modern JavaScript and TypeScript..." etc. Also "Hands-on experience with large-scale cloud deployments (AWS, GCP, or Azure) and Kubernetes." Also "Strong problem-solving skills, technical troubleshooting, and diagnosing complex system issues..." Also "Proven ability to prioritize work for maximum impact." Also "You're comfortable learning new coding languages and choosing the best tool for the job." Also "You're accustomed to working in an English-speaking environment." Qualifications: maybe "As we're hiring across several teams, many past experiences can be a bonus, for example: Experience mentoring junior engineers, leading significant projects, or designing and scaling complex full stack architectures will be a distinct advantage. Prior experience in industrial software, IoT, or large-scale data visualization projects is a plus. Experience in a SaaS product environment is an advantage but not a requirement. Experience building mobile applications." Skills: maybe list of technologies: Kotlin, Java, Python, Rust, JavaScript, TypeScript, React, Angular, Vue, component-based architectures, state management patterns, build tooling (Webpack, Vite), testing frameworks, AWS, GCP, Azure, Kubernetes. But we already have many of those in Requirements/Qualifications. To avoid duplication, we could separate: Requirements = core mandatory skills; Qualifications = preferred/experience; Skills = specific tech stack. But we must not repeat same content across sections? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid repetition, but we should try to avoid duplication. However we need to include all info; we can place each piece in appropriate section. Let's extract bullet points: From "How you’ll demonstrate Ownership": It's a paragraph describing the role. From "The Impact you bring to Cognite": list of responsibilities. From "You'll have the opportunity to drive architectural decisions..." etc. That's also responsibilities. Actually the "Impact you bring" paragraph includes many responsibilities. Let's parse that paragraph: "As a Principal Full Stack Engineer, You'll Be a Key Player In Designing, Building, And Maintaining Both The Frontend And Backend Of Industrial Data Platforms And Applications. You'll Have The Opportunity To Drive architectural decisions and lead the implementation of scalable full stack solutions across a diverse technology landscape, taking ownership of complex problems from concept to deployment.Collaborate in a fast-paced environment involving different stakeholders and subject matter experts.Design and implement elegant APIs, intuitive user experiences, and the underlying infrastructure.Influence and shape the strategic product roadmap and technical direction for key areas of our platform, working collaboratively with cross-functional leadership.Work closely with our skilled users to understand their needs and build products that help them succeed.Design, build, and maintain large-scale infrastructure and web services to ensure optimal performance and reliability.Work with peers across teams to support and leverage a shared technical stack." That's responsibilities. Then after that: "We're seeking a proactive and skilled engineer who is passionate about quality, user satisfaction, and building robust, end-to-end solutions. You love making users happy and are committed to creating products they truly want to use 😄You're skilled at prioritizing your tasks and distributing your time and resources most efficiently to optimize for impact.You write well-structured, efficient, and maintainable code and actively champion code quality.Expert knowledge of computer science with strong competencies in data structures, algorithms, and software design.Relevant and hands-on concentrated experience with software development in one or more programming languages (e.g., Kotlin, Java, Python, or Rust).You possess deep expertise in modern JavaScript and TypeScript, with extensive experience in leading frontend frameworks (e.g., React, Angular, Vue, or similar component-based architectures). Familiarity with state management patterns, build tooling (Webpack, Vite), and testing frameworks is highly valued.Hands-on experience with large-scale cloud deployments (AWS, GCP, or Azure) and Kubernetes.Strong problem-solving skills, technical troubleshooting, and diagnosing complex system issues to ensure optimal performance and minimal downtime.Proven ability to prioritize work for maximum impact.You're comfortable learning new coding languages and choosing the best tool for the job.You're accustomed to working in an English-speaking environment." That's requirements/qualifications. Then: "As we're hiring across several teams, many past experiences can be a bonus, for example: Experience mentoring junior engineers, leading significant projects, or designing and scaling complex full stack architectures will be a distinct advantage.Prior experience in industrial software, IoT, or large-scale data visualization projects is a plus.Experience in a SaaS product environment is an advantage but not a requirement.Experience building mobile applications." That's qualifications (preferred). Then benefits list. Now we need to output HTML. We'll create sections:

    About the role

    with paragraphs: combine the initial description of Cognite, mission, moonshot, and "How you’ll demonstrate Ownership". Also maybe the "Learn More About Us Impact 2025..." part. Let's extract that: "What Cognite is: Relentless to achieve Cognite operates at the forefront of industrial digitalization, building AI, and data solutions that solve the world’s hardest, highest-impact problems. With unmatched industrial heritage and a comprehensive suite of AI capabilities, including low-code AI agents, Cognite accelerates the digital transformation to drive operational improvements. We thrive in challenges. We challenge assumptions. We execute with speed and ownership. If you view obstacles as signals to step forward - not backwards - you’ll feel right at home here. Our Moonshot is bold: Unlock $100B in customer value by 2035, and redefine how global industry works. Join us in this venture where AI and data meet ingenuity, and together, we will forge the path to a smarter, more connected industrial future. How you’ll demonstrate Ownership Are you a visionary Principal Full Stack Engineer eager to architect, build, and lead the development of intuitive user experiences and robust backend systems that transform industrial operations? At Cognite, we're not just building software; we're pioneering the future of industrial data with our award-winning Cognite Data Fusion® platform, recognized as the 2022 Technology Innovation Leader for Global Digital Industrial Platforms. Our Product team is at the core of developing Cognite Data Fusion® into a robust and scalable platform for solving critical industrial data problems. This work is central to transforming asset-intensive industries – making them safer, more sustainable, and more profitable. Cognite Data Fusion® makes operational data available at scale, adding immense value through advanced data processing. This empowers industries to make truly data-driven decisions. Our platform leverages many different technologies, each chosen for its ability to solve specific challenges effectively. To build the best possible product, we believe in autonomous teams where developers, designers, and product managers work closely together. Our teams are focused on building the next-generation industrial data platform and applications across diverse industries like Oil & Gas, Manufacturing, and Power & Utility. This includes enabling all types of workflows, from advanced analytics to assisting in critical decision-making. We're a strong mix of engineers, product managers, and designers, united by a deep commitment to user experience and creating products users genuinely want to use. Our work environment is exciting, dynamic, and intense. You'll collaborate with top-tier domain and industry experts: designers, product managers, backend developers, ML engineers, 3D developers, and business leaders. We support one another, ask incisive questions, and give constructive feedback. Our goal is to leverage our diverse strengths and backgrounds to build innovative products, think outside the ordinary, and nurture a truly great culture." That's a lot; we can keep as paragraphs. Then Responsibilities: the Impact you bring paragraph. We'll put that in

Similar jobs