Senior Cloud Software Engineer
Alaska Airlines · SeaTac, WA · 3 wk ago
On-siteEngineering$118k–$177k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also we must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Salary Range and details, so Pay section is appropriate. Benefits: there is a "Total Rewards" section with benefits listed: free stand-by travel privileges, comprehensive well-being programs, generous 401k match, annual bonus plans, generous holiday and paid time off. So Benefits section is appropriate. Schedule: Not explicitly stated; only mentions Full-Time. Could we infer schedule? The posting includes "Employment Type Full-Time". That's not schedule details like hours. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Full-Time but not schedule specifics. Should we include Schedule? Probably not, because no explicit schedule like "Monday-Friday, 9-5". So we omit Schedule.
We need sections: About the role (role summary), Responsibilities (Key Duties), Requirements (Job-Specific Experience, Education & Skills Required), Qualifications maybe overlapping with Requirements? The instruction says use headings for those categories. We can combine some. We need to avoid filler. We'll include About the role (role summary paragraph). Responsibilities (Key Duties). Requirements (Job-Specific Experience, Education & Skills Required). Skills maybe separate? The posting includes "Job-Specific Experience, Education & Skills Required" which includes skills. Could split into Requirements (experience/education) and Skills (specific skills). But we must not create thin sections. Might combine into one Requirements section covering both. However we have also "Preferred" section which is additional preferred qualifications. Could treat as Qualifications (preferred). But we need to decide.
We have: Role Summary paragraph. Key Duties list. Job-Specific Experience, Education & Skills Required list (required). Preferred list (preferred). Job-Specific Leadership Expectations (values). Salary Range. Total Rewards benefits.
We need to map to headings: About the role (role summary). Responsibilities (Key Duties). Requirements (Job-Specific Experience, Education & Skills Required). Qualifications (Preferred). Skills maybe not separate. Benefits (Total Rewards). Pay (Salary Range). Possibly also Leadership Expectations could be part of About the role or Responsibilities? Could be its own section but not in list of allowed headings; we could omit or fold into About the role. The instruction: use headings for those specific section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Likely we should only use those headings. So we need to map content accordingly.
Thus:
- About the role: role summary paragraph (maybe also include team description? The first paragraph about company and team could be considered About the role? Actually "About the role" should describe the role. The initial paragraph about company and team is more about company. Could we include that as part of About the role? It's not role-specific but could be considered context. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that company/team paragraph somewhere. Could put it in About the role as introductory context. That seems okay.
- Responsibilities: Key Duties list.
- Requirements: Job-Specific Experience, Education & Skills Required (required). Could also include Minimum age, HS diploma, work authorization etc. Those are also requirements.
- Qualifications: Preferred (preferred experience). Could also include Job-Specific Leadership Expectations? Might be considered qualifications but it's about values. Could include under Qualifications as well.
- Skills: maybe we could separate technical skills from the required list? But we might not need separate Skills section if we already covered in Requirements. However the instruction says we can use Skills heading if we have real specific content. We could extract skills from required list: Test Automation, cloud computing, building custom high scale n-tier apps, web/mobile apps, design patterns, Git, TDD, unit testing, pair programming, XP techniques, interpersonal skills, communication, collaboration. That's a list of skills. Could put them under Skills heading. But then Requirements would be experience/education only. That might be better to avoid thin sections. Let's see: Required list includes both experience and skills. We could split: Requirements: experience/education (4 years experience, BS or equivalent, HS diploma, min age, work auth). Skills: list of technical and soft skills. That seems reasonable and both have substantive content.
- Benefits: Total Rewards benefits.
- Pay: Salary Range and details.
- Schedule: Not present, omit.
We must not include boilerplate like EEO, regulatory, application instructions, etc. Remove duplicated lines. Also remove "Apply by 7:00 PM Pacific Time on 10/5/2026" etc. Also remove "Note: We don’t typically hire at the top of the range." That's part of Pay details maybe we can keep? It's about pay, but it's not boilerplate; it's substantive about pay. We can keep.
We must not include "Job-Specific Leadership Expectations" maybe we can incorporate into Qualities or About the role. Could include under Qualities? But we don't have a heading for Leadership Expectations. Could fold into Qualifications (as preferred qualities) or About the role. Let's add a bullet under Qualifications about embodying values.
Now produce HTML fragment:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also we must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Salary Range and details, so Pay section is appropriate. Benefits: there is a "Total Rewards" section with benefits listed: free stand-by travel privileges, comprehensive well-being programs, generous 401k match, annual bonus plans, generous holiday and paid time off. So Benefits section is appropriate. Schedule: Not explicitly stated; only mentions Full-Time. Could we infer schedule? The posting includes "Employment Type Full-Time". That's not schedule details like hours. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Full-Time but not schedule specifics. Should we include Schedule? Probably not, because no explicit schedule like "Monday-Friday, 9-5". So we omit Schedule.
We need sections: About the role (role summary), Responsibilities (Key Duties), Requirements (Job-Specific Experience, Education & Skills Required), Qualifications maybe overlapping with Requirements? The instruction says use headings for those categories. We can combine some. We need to avoid filler. We'll include About the role (role summary paragraph). Responsibilities (Key Duties). Requirements (Job-Specific Experience, Education & Skills Required). Skills maybe separate? The posting includes "Job-Specific Experience, Education & Skills Required" which includes skills. Could split into Requirements (experience/education) and Skills (specific skills). But we must not create thin sections. Might combine into one Requirements section covering both. However we have also "Preferred" section which is additional preferred qualifications. Could treat as Qualifications (preferred). But we need to decide.
We have: Role Summary paragraph. Key Duties list. Job-Specific Experience, Education & Skills Required list (required). Preferred list (preferred). Job-Specific Leadership Expectations (values). Salary Range. Total Rewards benefits.
We need to map to headings: About the role (role summary). Responsibilities (Key Duties). Requirements (Job-Specific Experience, Education & Skills Required). Qualifications (Preferred). Skills maybe not separate. Benefits (Total Rewards). Pay (Salary Range). Possibly also Leadership Expectations could be part of About the role or Responsibilities? Could be its own section but not in list of allowed headings; we could omit or fold into About the role. The instruction: use headings for those specific section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Likely we should only use those headings. So we need to map content accordingly.
Thus:
- About the role: role summary paragraph (maybe also include team description? The first paragraph about company and team could be considered About the role? Actually "About the role" should describe the role. The initial paragraph about company and team is more about company. Could we include that as part of About the role? It's not role-specific but could be considered context. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that company/team paragraph somewhere. Could put it in About the role as introductory context. That seems okay.
- Responsibilities: Key Duties list.
- Requirements: Job-Specific Experience, Education & Skills Required (required). Could also include Minimum age, HS diploma, work authorization etc. Those are also requirements.
- Qualifications: Preferred (preferred experience). Could also include Job-Specific Leadership Expectations? Might be considered qualifications but it's about values. Could include under Qualifications as well.
- Skills: maybe we could separate technical skills from the required list? But we might not need separate Skills section if we already covered in Requirements. However the instruction says we can use Skills heading if we have real specific content. We could extract skills from required list: Test Automation, cloud computing, building custom high scale n-tier apps, web/mobile apps, design patterns, Git, TDD, unit testing, pair programming, XP techniques, interpersonal skills, communication, collaboration. That's a list of skills. Could put them under Skills heading. But then Requirements would be experience/education only. That might be better to avoid thin sections. Let's see: Required list includes both experience and skills. We could split: Requirements: experience/education (4 years experience, BS or equivalent, HS diploma, min age, work auth). Skills: list of technical and soft skills. That seems reasonable and both have substantive content.
- Benefits: Total Rewards benefits.
- Pay: Salary Range and details.
- Schedule: Not present, omit.
We must not include boilerplate like EEO, regulatory, application instructions, etc. Remove duplicated lines. Also remove "Apply by 7:00 PM Pacific Time on 10/5/2026" etc. Also remove "Note: We don’t typically hire at the top of the range." That's part of Pay details maybe we can keep? It's about pay, but it's not boilerplate; it's substantive about pay. We can keep.
We must not include "Job-Specific Leadership Expectations" maybe we can incorporate into Qualities or About the role. Could include under Qualities? But we don't have a heading for Leadership Expectations. Could fold into Qualifications (as preferred qualities) or About the role. Let's add a bullet under Qualifications about embodying values.
Now produce HTML fragment:
About the role
... company paragraph + role summary paragraph ...
ThenResponsibilities
- ... each duty ...
Requirements
- ... experience/education items ...
Skills
- ... skill items ...
Qualifications
- ... preferred items ...
Benefits
- ... benefit items ...
Pay
... salary range and details ...
Make sure not to include any extra text. Now extract content precisely. Company paragraph: "Company Alaska Airlines The Team Guided by our purpose, core values, and leadership principles, we are creating an airline people love. Our corporate teams set the strategies and operational plans to ensure the success of our company. Whether we use our expertise in accounting, human resources, finance, planning, legal, marketing, or any of our operational divisions, our shared passion for travel and our guests is what motivates us to achieve excellence each day. If you share our passion for creating an airline people love, we want to hear from you." We need to preserve that. Might be a bit redundant but okay. Role Summary paragraph: "Role Summary The Senior Software Engineer is a subject matter expert in full-stack software engineering with Alaska Airlines (AS) and Hawaiian Airlines (HA). As an individual contributor, this role exercises considerable judgment to make decisions that support our products top-to-bottom and ship software on a regular basis (anywhere from daily to every two weeks). This role also provides recommendations to address challenges while working in an agile environment with product owners." Combine them maybe as one paragraph. Now Responsibilities (Key Duties) list: - Act as a subject matter expert in full-stack engineering on a scrum delivery team, collaborating with product owners, designers, and other engineers to deliver business value on an iterative basis. - Coach and influences team members on best practices and emerging technologies. - Solve complex technology and business problems with new and creative methods. - Architect, engineer, test, deploy, and support highly scalable and maintainable complex, end-to-end custom software applications. - Ensure delivery of high-quality software by writing clean code and utilizing pair programming, test-driven development (TDD), and continuous integration. - Actively engage in the technology industry, networks and understands how evolving technologies can benefit our organization. - Influence cross-functionality and partner with other disciplines to develop strategy. - Develop a solid understanding of the team’s guest experience, business, and systems. Note: Some grammar issues but keep as is. Now Requirements (experience/education): List from "Job-Specific Experience, Education & Skills Required": - 4 years of experience in software engineering, or related area. - Bachelor’s degree with a focus in Computer Science or a related field, or an additional two years of relevant training/experience in lieu of this degree. - High school diploma or equivalent. - Minimum age of 18. - Must be authorized to work in the U.S. Also maybe include "Experience in the following:" but that's skills; we will move to Skills. Now Skills list (from the "Experience in the following:" bullet points): - Test Automation. - Utilizing cloud computing. - Acting as a software engineer building custom, high scale, n-tier applications using object-oriented languages. - Developing web or mobile applications using modern technologies. - Utilizing appropriate design patterns to create clean, maintainable, and performant code. - Interacting with Git version control to maintain organization and logging of codebase changes. - Performing TDD, unit testing, pair programming, and other XP techniques. - Strong interpersonal skills and proven ability introducing new ideas and technologies to communities of developers. - High degree of professionalism and customer service orientation. - Excellent communication skills and proven ability to collaborate with a variety of teams. We could also include the leadership expectations? Might be separate but we can add to Qualifications. Now Qualifications (Preferred) list: From "Preferred": - Hands-on experience with Azure cloud services and enterprise-scale cloud patterns, including networking, identity, access management, policy, security controls, and governance. - Experience with infrastructure as code, automation, and scripting using Terraform, Bicep, ARM templates, CloudFormation, PowerShell, Python, YAML, Bash, or similar technologies in production environments. - Experience building internal platforms, shared services, reusable engineering patterns, or self-service cloud capabilities for application teams, including partnering with platform-owning teams and cloud providers to troubleshoot issues and drive practical solutions. - Experience with observability and monitoring platforms such as Dynatrace, Azure Monitor, Application Insights, Log Analytics, or similar tools to support troubleshooting, reliability, and operational insight. - Experience with cloud cost management, tagging, governance, or FinOps practices to improve visibility, accountability, and efficient use of cloud resources. - Exposure to generative AI or AI-assisted development tools, with an interest in applying them responsibly to improve engineering productivity, documentation, automation, or troubleshooting. Also maybe include "Job-Specific Leadership Expectations Embody our values to own safety, do the right thing, be caring and kind, and deliver performance." Could add as a bullet under Qualifications. Now Benefits list from "Total Rewards": - Free stand-by travel privileges on Alaska Airlines, Hawaiian Airlines & Horizon Air - Comprehensive well-being programs including medical, dental and vision benefits - Generous 401k match program - Annual bonus plans - Generous holiday and paid time off We could also include "Alaska Airlines, Hawaiian Airlines and Horizon Air pay and benefits can vary by company, location, number of regularly scheduled hours worked, length of employment, and employment status." That's more description; could include as a paragraph before list. Now Pay details: "Salary Range $117,700-$176,550 / year Salary Details Pay will be based on multiple factors, including and not limited to location, relevant experience/level and skillset while balancing internal equity relative to other Alaska/Hawaiian/Horizon employees. Alaska/Hawaiian/Horizon is committed to fair, unbiased compensation along with competitive benefits in all locations in which we operate. Note: We don’t typically hire at the top of the range." We'll put