Principal Engineer, Software
Allegiant · Las Vegas, NV · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with 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, not invent. Remove boilerplate like EEO, navigation, cookie, legal, scam warning, duplicated lines, application instructions. Also remove "Physical Requirements", "Essential Services Provider", etc? Those are not required sections but may be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Requirements maybe not required but it's substantive? It's about physical demands; could be considered part of role but not a standard heading. Since we only output sections for headings listed, we can embed that info maybe under About the role or Responsibilities? But we must preserve ALL substantive information. However we cannot create new headings beyond allowed list. We could put physical requirements in a
under About the role or Responsibilities. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine. We need to extract substantive content: Summary paragraph about team, role description, Principal position duties, Visa Sponsorship Available: No, Minimum Requirements (education, experience, languages, technologies, etc), Preferred Requirements, Job Duties (list), Physical Requirements (maybe include), Benefits (Full Time Benefits and Part Time Benefits). Pay and Schedule not mentioned, so we should not include those sections. We must not include headings with filler like "commensurate with experience". Not present. We need to format:
About the role
then... maybe combine summary and principal position description. Then
Responsibilities
with- list of duties from Job Duties.
Then
Requirements
maybe combine Minimum Requirements and Preferred Requirements? Could split but we have Requirements and Qualifications and Skills sections. We need to decide mapping. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to allocate content appropriately. - About the role: summary of team, role purpose, principal position balancing business solution architecture & implementation, etc. - Responsibilities: list of job duties (the bullet list under Job Duties). Could also include some duties from summary? But keep as list. - Requirements: Minimum Requirements (education, experience, languages, technologies, etc). Could be a list. - Qualifications: maybe Preferred Requirements? Or could be "Preferred Requirements" as qualifications. - Skills: maybe specific technical skills list (languages, frameworks). Could be separate. But we must not duplicate content. We need to preserve all substantive info. So we need to split the Minimum Requirements into categories: Education, Experience, Languages Experience, Technologies/Frameworks Experience, etc. Could put under Requirements as a list. Qualifications could be Preferred Requirements (Master's degree plus, airline/hospitality experience, ecommerce, cloud platforms, IoC, domain-driven design). Could be list. Skills could be maybe "Ability to work independently... communication skills, Microsoft Office proficiency". Could be list. But we need to ensure we don't lose any info. Let's extract details: Summary paragraph: "The #G4DEV team within Allegiant Travel Company is responsible the development of our next generation of applications to support our e-commerce, hospitality and airline operations platforms in a fast-moving and challenging environment that is balanced among delivery, innovation, and learning. We develop travel and hospitality management applications for Airline, Hotel & Hospitality, Car and related products from online shopping, booking and logistics while supporting airline operations. As a member of our development team, you’ll analyze and improve the efficiency, scalability, and reliability of our logic and integration systems. You will be an integral part of our development team, working closely with our development and other project teams to power applications that streamline day-to-day processes and bring data to life. The Principal position will balance business solution architecture & implementation with technical architectural necessities; participate in development, implementation and maintenance of business web applications and provide systems support to the company; establish and maintain technical relationships between development team and data architects and improving technical education by facilitating internal technology workshops. This position works closely with others to facilitate platform convergence and when necessary participate in a phased implementation of the new applications using standard development tools and methodologies." Visa Sponsorship Available: No Minimum Requirements: - Combination of Education and Experience will be considered. - Must be authorized to work in the US as defined by the Immigration Act of 1986. - Must pass a Criminal Background Check. - Education: Bachelor’s Degree - Education Details: Bachelor's Degree in Computer Science, Math or MIS. - Years of Experience: Minimum ten (10) years of development experience as a seasoned middleware engineer - Minimum of seven (7) years of software development experience architecting and building multi-tiered, high volume fault-tolerant, high-availability, and globally distributed systems in a Linux environment - Languages Experience: Java (8, 9), server-side JavaScript (under Node.js, Meteor), PHP 7.x, HTML5, CSS3, AJAX, JavaScript, JQuery and latest frameworks (AngularJS, ReactJS/Redux, Backbone) - Technologies/Frameworks Experience: Experience of the following is required: JBoss/Wildfly server, Spring Boot 2.0, Tomcat, Linux, HTTP, SOAP/REST Web Services/Microservices, XML, JSON - Experience working on EJBs and the web layer, Spring Framework, Maven - Experience with Unit Testing Frameworks and Tools, e.g., JUnit, TestNG, Mockito, Jasmine, Mocha, etc - Experience with CI/CD build servers (Jenkins, Bamboo, TravisCI, TeamCity, etc.) - Experience with ORM frameworks for Java, Node, PHP, or Mongo (e.g., Hibernate, ORM2, Sequelize, Doctrine, Mongoose, etc.) is required - Knowledge with fault tolerant message queuing/brokering systems (e.g. AMQ, RabbitMQ, zeromq, Kafka) - Experience with SQL and NoSQL databases, for example, DB2, MySQL, Mongo, Cassandra, etc - Significant and demonstrable experience of implementing Java best practice – especially around scalability, availability and performance - Highly developed design skills with experience in Object-Oriented Design (OOD), and applied enterprise design patterns, and database design - Testing Experience with Automated Unit Testing, Integration Testing, TDD (Test Driven Development) - Ability to work independently as well as perfom as part of a small, close knit development team which offers full ownership of projects in a supportive design environment - Must be able to maintain regular and predictable attendance subject to the leave, PTO, and attendance policies - Excellent written and verbal communication skills required. - Must have the ability to communicate ideas effectively and cross functionally; exhibit creativity, flexibility, adaptability and the drive to achieve results - Proficient in Microsoft Office Products: Word, Excel and Outlook Preferred Requirements: - Master's degree is a plus - Airline and/or hospitality experience preferred - Ecommerce experience is a plus - Knowledge of cloud platforms (AWS, OpenStack, Azure, Google Cloud) is highly desired - Familiarity with Inversion of Control paradigm is highly desired; experience with Java-based IoC frameworks is a definite plus - Domain-driven design, and data modeling is highly desired Job Duties (list): - Manage a large cross-functional team and lead a software project from requirements analysis till deployment, having complete responsibility of all the technical deliverables through the life cycle (requirements analysis, design, implementation, QA support and deployment) of the project with no supervision - Work with other teams such as QA, PMO and IT Operations and provide them technical support and guidance to ensure successful delivery of a software project - Member of architecture team that is responsible for modeling process, and design an n-tier system and scalable architecture. Primarily focused on balancing business solutions with technical architectural necessities - Provide solution architecture for business problems while balancing essential technical guidelines to functional teams - Work with the business analysts to gather and analyze requirements; develop high-level system narratives, storyboards and UI prototypes - Re-factor current application design and/or implementation to enhance the application and align with technology roadmap - Design and implement product enhancements based on business priorities - Assist in framework evaluation, provide recommendations, and plan integration as needed - Participate in typical software maintenance, including quality and stability initiatives - Design and develop domain data models and database schemas to support business requirements - Work with the business analysts to gather and analyze requirements; develop high-level system narratives, storyboards and UI prototypes (duplicate line) - Contribute, adhere to, and enforce standards and best practices in software development - Conduct design and code reviews - Develop prototypes or demos for any strategic business initiative - Develop complex SQL stored procedures and ad-hoc queries - Resolve application performance and scalability issues by identifying the bottle-necks, system resource utilization and key areas of improvement - Other duties as assigned Physical Requirements: (we can include as a paragraph under About the role maybe) "The Physical Demands and Work Environment described here are a representative of those that must be met by a Team Member to successfully perform the essential functions of the role. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions of the role." Essential Services Provider: (maybe not needed but could be included under About the role) "Allegiant as a national air carrier is deemed an essential service provider during declared national and state emergencies. Team Members will be required to report to their assigned trip or work location during national and state emergencies unless prohibited by local, state or federal order." EEO Statement etc to remove. Benefits: Full Time Benefits: Profit Sharing Medical/Dental/Vision/Life/ Disability Insurance Medical Travel Reimbursement Legal, Identity and Pet Insurance 401K with an employer match Employee Stock Purchase Plan Employee Assistance Program Tuition Reimbursement Flight Benefits Paid vacation, holidays, and sick time Part Time Benefits: Profit Sharing Medical Travel Reimbursement Legal, Identity and Pet Insurance 401K with an employer match Employee Stock Purchase Plan Employee Assistance Program Tuition Reimbursement Flight Benefits Sick time We need to include Benefits section with both full and part time? Could combine. Pay and Schedule not present, so omit those sections. Now construct HTML. We'll have:About the role
... summary + principal position + visa sponsorship + physical demands + essential services provider maybe.
Responsibilities
- ... each duty
Requirements
- ... minimum requirements items
Qualifications
- ... preferred requirements
Skills
- ... ability to work independently, communication, Microsoft Office proficiency
- for any list of duties/requirements/benefits, and
for prose." So we can have multiple lists. We need to preserve all substantive info. Let's decide: - About the role: prose summary (including visa sponsorship, physical demands, essential services). No list. - Responsibilities: list of duties. - Requirements: list of minimum requirements (education, experience, languages, technologies, etc). Could be long list. - Qualifications: list of preferred requirements. - Skills: list of soft skills and Microsoft Office proficiency. - Benefits: list of benefits (full-time and part-time). Could combine. We must not include Pay or Schedule. Now craft HTML. We need to be careful not to include duplicated lines (like the duplicate line about work with business analysts appears twice in duties; we should include only once? The instruction: "Remove duplicated lines". So we should deduplicate. The duty appears twice: "Work with the business