Software Engineer
alliantgroup · Houston, TX · 3 wk ago
EngineeringFull-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. The posting includes description about role (first paragraph). That could be "About the role". Responsibilities: many bullet points. Requirements: maybe "Technical Qualifications" and "Qualifications". Skills: maybe list of languages etc. Benefits: there is a paragraph about benefits. Pay: not specified (no salary). So we should not include Pay section. Schedule: mentions "Ability to work full-time onsite in the Houston, Texas office five days per week." That's schedule info (full-time onsite 5 days/week). So we can include Schedule section with that detail.
We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. There's none.
We need to preserve all substantive info. Use for headings. Use
for headings. Use - for lists. Use
for prose.
We need to decide sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe combine Technical Qualifications and Qualifications? Could be separate but we can combine into Requirements). Skills (list of languages/frameworks). Benefits (list). Schedule (full-time onsite). Possibly also Qualifications separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections if content exists. Let's split: Requirements could be the "Technical Qualifications" bullet list? Actually Technical Qualifications is a list of proficiencies. Qualifications is education/experience etc. We'll make Requirements = Technical Qualifications (list). Qualifications = education/experience etc (list). Skills maybe overlapping; but we can treat Skills as the list of languages etc. However Technical Qualifications already includes languages. Might duplicate. Better: Use Skills for languages/frameworks; Requirements for experience/education; Qualifications maybe not needed. But we need to follow instruction: include a section ONLY when posting has real specific content. We can decide to have About the role, Responsibilities, Requirements (technical qualifications), Qualifications (education/experience), Skills (maybe not needed if covered), Benefits, Schedule.
But we must not create thin sections. Let's see content:
- About the role: first paragraph(s) describing role.
- Responsibilities: big list of responsibilities (many sentences). We'll turn each sentence into
- maybe.
- Requirements: could be "Technical Qualifications" list: Strong proficiency in software development languages and frameworks, including C, C#, C++, Python, JavaScript, PHP, React or Angular, HTML, and CSS. Experience with SQL, database and data design, API development, application architecture, distributed systems, and cloud computing. Experience using generative AI and modern software development tools, libraries, IDEs, and debugging tools. Ability to quickly learn and apply new programming languages, technologies, and engineering tools.
- Qualifications: list: Bachelor's degree in Computer Science, Computer Engineering, Software Engineering, or a very closely related technical field. Professional hands-on software engineering experience designing, developing, and supporting production software systems. Experience designing scalable, high-performance, cloud-based applications, with a strong understanding of software architecture and system design. Strong understanding of Agile software development practices. Experience translating technical requirements into engineering tasks, estimating development effort and complexity, and identifying technical risks and dependencies. Strong written and verbal communication skills, including the ability to create and clearly communicate technical designs and software architecture diagrams. Strong quantitative and analytical problem-solving skills. Experience developing and supporting multiple software products or codebases concurrently. Strong technical documentation skills, including the ability to document system designs, technical decisions, and implementation guidance. Proficiency with modern software development and collaboration tools, such as Azure DevOps, Jira, Git, Microsoft Loop, Confluence, Lucid, Figma, IDEs, and AI-assisted development tools. Experience developing or integrating enterprise applications and platforms Experience with Salesforce and Salesforce integrations Experience with mobile applications, if it is preferred rather than required Experience with mobile application development frameworks, such as Flutter, is preferred. Ability to collaborate effectively with distributed, cross-functional engineering teams. High sense of urgency with the ability to meet deadlines and changing priorities. Receptiveness to performance feedback within a team environment is essential. Ability to work full-time onsite in the Houston, Texas office five days per week.
But note the last bullet about schedule could go to Schedule section. We'll extract that.
- Skills: maybe we can list languages/frameworks again but that duplicates Requirements. Could omit Skills section if we consider Requirements covers it. But we could still have Skills as a separate list of languages/frameworks. However that would be thin? It's a list of many items, so substantive. We'll include Skills.
- Benefits: paragraph about benefits: "alliant offers a comprehensive compensation and benefits package including 100% employer paid medical /dental premiums for single coverage for certain options, 401(k) matching, PTO, company provided life insurance and disability, onsite gym and group exercise classes, paid covered parking, and more!" We'll turn into list.
- Schedule: "Ability to work full-time onsite in the Houston, Texas office five days per week." We'll put as
or
- . Probably
.
- Pay: not specified, so omit.
Now we need to ensure we don't include boilerplate like "Do Work That Matters. alliant" at end - that's a tagline maybe but not substantive? It's not boilerplate but could be considered marketing. Might keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Do Work That Matters. alliant" is not boilerplate but maybe a tagline; we could keep as part of About the role? It's at end after benefits. Might be considered a slogan; but we can include as part of About the role? Safer to omit if it's not substantive detail about role. I'd omit.
Now construct HTML.
We'll start with
About the role
then ...
containing the introductory paragraph(s). The intro includes first two sentences? Actually the first paragraph: "As a Software Engineer, you will design, build, and support sophisticated software products and technology platforms across web, native, and mobile environments. This role combines software development and system design with cloud computing, data architecture, generative AI, and enterprise application and integration technologies. You will help deliver scalable, high-quality solutions for internal and customer-facing products spanning web and mobile experiences, enterprise data, search and graph technologies, content publishing, benchmarking tools, and cloud-based architectures. Working closely with Engineering, Product, Project Management, UI/UX, Quality Assurance, Business, and IT teams, you will translate complex requirements into practical technical solutions and contribute throughout the software development lifecycle. Success in this role requires strong technical judgment, clear written and verbal communication, and the ability to collaborate effectively with distributed technology teams in the United States and India. As a premier consulting and technology firm, alliant is focused on providing solutions to help businesses transform and thrive, while serving as their ongoing growth partner."
We'll put that as a single .
Then Responsibilities:
Responsibilities
with each responsibility as - . Need to break the long list into items. We'll split by sentences that start with verbs. Let's extract:
- Own the full software development lifecycle, including requirements analysis, design, coding, unit testing, debugging, deployment, maintenance, and production support for enterprise applications and technology platforms.
- Develop high-quality, secure, scalable, maintainable, and well-documented production code, including reusable components, services, APIs, and frameworks.
- Analyze complex technical problems and troubleshoot application, infrastructure, integration, data, performance, hosting, and deployment issues.
- Review existing systems, emerging technologies, and design patterns to recommend improvements to architecture, performance, security, reliability, and maintainability.
- Participate in requirements, design, code, testing, and deployment reviews while promoting engineering standards, development best practices, and responsible use of generative AI.
- Mentor software engineers and associates at varying experience levels.
- Translate business and functional requirements into technical designs and implementation approaches for new products and major system enhancements.
- Design distributed and cloud-based applications, defining application boundaries, service interfaces, APIs, data flows, integrations, dependencies, and architectural constraints.
- Evaluate design alternatives based on scalability, performance, security, reliability, maintainability, cost, and implementation complexity.
- Create and maintain technical design artifacts, including system diagrams, UML models, data flow diagrams, integration diagrams, and database designs.
- Establish and promote coding standards, architectural patterns, project structures, version-control practices, and software release standards across products.
- Document and communicate key architectural decisions to engineering teams and stakeholders.
- Incorporate security, privacy, identity, access control, and data protection requirements throughout application and system design.
- Develop secure software using established coding practices and identify vulnerabilities and architectural risks across applications, infrastructure, AI, and data systems.
- Collaborate with security and infrastructure teams to define requirements, remediate risks, and support cloud identity solutions using Microsoft Entra ID and Azure DevOps.
- Design and optimize systems for scalability, performance, availability, reliability, fault tolerance, and re-coverability as users, transactions, data volumes, and workloads increase.
- Analyze application and infrastructure performance, identify system bottlenecks, and recommend practical optimization approaches.
- Evaluate architectural tradeoffs among performance, scalability, security, cost, complexity, and participate in functional, performance, and security testing.
- Break complex requirements into manageable engineering tasks, implementation steps, and dependencies.
- Estimate development effort and technical complexity, clearly documenting assumptions, constraints, risks, and uncertainties.
- Identify dependencies across applications, data, infrastructure, teams, and third-party services that could affect delivery.
- Help engineering teams establish realistic delivery commitments and contingency approaches for high-risk technical components.
- Communicate changes to estimates, risks, dependencies, or technical approaches as new information becomes available.
- Communicate significant risks, estimate changes, dependencies, and changes to technical approaches to engineering and product leadership as new information becomes available.
- Contribute to sprint planning, backlog refinement, technical discussions, reviews, and retrospectives within an Agile development environment.
- Partner with product management to clarify requirements, acceptance criteria, priorities, dependencies, and implementation readiness.
- Track sprint objectives, blockers, risks, and delivery commitments while providing technical input into prioritization and sequencing decisions.
- Continuously improve engineering practices, tools, and development processes.
- Create and maintain clear technical documentation throughout the development lifecycle, including system designs, architecture diagrams, UML artifacts, data flows, API specifications, data models, integration requirements, engineering standards, deployment processes, monitoring plans, and test documentation.
- Use collaborative documentation platforms such as Microsoft Loop and Confluence to keep technical decisions, standards, and implementation guidance accessible and current.
- Provide concise, accurate updates on engineering progress, upcoming work, blockers, risks, dependencies, and changes to technical approaches.
- Communicate complex technical information clearly to engineering and non-engineering stakeholders and document key decisions, issues, and outcomes.
- Collaborate effectively with distributed technology teams in the United States and India across multiple time zones.
- Contribute to technical meetings, design reviews, and cross-functional discussions.
- Use engineering and collaboration tools to support requirements, architecture, development, source control, documentation, design, testing, and software delivery.
- Collaborate with product and UI/UX designers to interpret requirements and Figma designs and translate them into responsive, high-quality web, native, and mobile experiences.
- Provide technical guidance on the usability, performance, responsiveness, and implementation feasibility of UI/UX decisions.
- Develop and integrate enterprise applications using REST APIs, web services, event-driven architectures, cloud services, enterprise SaaS platforms, and relational and non-relational data systems.
- Design secure and reliable integrations across applications, mobile solutions, services, data platforms, and third-party systems.
That's many items; okay.
Then Requirements (Technical Qualifications):
Requirements
with items:
- Strong proficiency in software development
for prose. We need to decide sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe combine Technical Qualifications and Qualifications? Could be separate but we can combine into Requirements). Skills (list of languages/frameworks). Benefits (list). Schedule (full-time onsite). Possibly also Qualifications separate? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections if content exists. Let's split: Requirements could be the "Technical Qualifications" bullet list? Actually Technical Qualifications is a list of proficiencies. Qualifications is education/experience etc. We'll make Requirements = Technical Qualifications (list). Qualifications = education/experience etc (list). Skills maybe overlapping; but we can treat Skills as the list of languages etc. However Technical Qualifications already includes languages. Might duplicate. Better: Use Skills for languages/frameworks; Requirements for experience/education; Qualifications maybe not needed. But we need to follow instruction: include a section ONLY when posting has real specific content. We can decide to have About the role, Responsibilities, Requirements (technical qualifications), Qualifications (education/experience), Skills (maybe not needed if covered), Benefits, Schedule. But we must not create thin sections. Let's see content: - About the role: first paragraph(s) describing role. - Responsibilities: big list of responsibilities (many sentences). We'll turn each sentence into
or
. - Pay: not specified, so omit. Now we need to ensure we don't include boilerplate like "Do Work That Matters. alliant" at end - that's a tagline maybe but not substantive? It's not boilerplate but could be considered marketing. Might keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Do Work That Matters. alliant" is not boilerplate but maybe a tagline; we could keep as part of About the role? It's at end after benefits. Might be considered a slogan; but we can include as part of About the role? Safer to omit if it's not substantive detail about role. I'd omit. Now construct HTML. We'll start with
About the role
then...
containing the introductory paragraph(s). The intro includes first two sentences? Actually the first paragraph: "As a Software Engineer, you will design, build, and support sophisticated software products and technology platforms across web, native, and mobile environments. This role combines software development and system design with cloud computing, data architecture, generative AI, and enterprise application and integration technologies. You will help deliver scalable, high-quality solutions for internal and customer-facing products spanning web and mobile experiences, enterprise data, search and graph technologies, content publishing, benchmarking tools, and cloud-based architectures. Working closely with Engineering, Product, Project Management, UI/UX, Quality Assurance, Business, and IT teams, you will translate complex requirements into practical technical solutions and contribute throughout the software development lifecycle. Success in this role requires strong technical judgment, clear written and verbal communication, and the ability to collaborate effectively with distributed technology teams in the United States and India. As a premier consulting and technology firm, alliant is focused on providing solutions to help businesses transform and thrive, while serving as their ongoing growth partner." We'll put that as a single. Then Responsibilities:
Responsibilities
- with each responsibility as
- . Need to break the long list into items. We'll split by sentences that start with verbs. Let's extract:
- Own the full software development lifecycle, including requirements analysis, design, coding, unit testing, debugging, deployment, maintenance, and production support for enterprise applications and technology platforms.
- Develop high-quality, secure, scalable, maintainable, and well-documented production code, including reusable components, services, APIs, and frameworks.
- Analyze complex technical problems and troubleshoot application, infrastructure, integration, data, performance, hosting, and deployment issues.
- Review existing systems, emerging technologies, and design patterns to recommend improvements to architecture, performance, security, reliability, and maintainability.
- Participate in requirements, design, code, testing, and deployment reviews while promoting engineering standards, development best practices, and responsible use of generative AI.
- Mentor software engineers and associates at varying experience levels.
- Translate business and functional requirements into technical designs and implementation approaches for new products and major system enhancements.
- Design distributed and cloud-based applications, defining application boundaries, service interfaces, APIs, data flows, integrations, dependencies, and architectural constraints.
- Evaluate design alternatives based on scalability, performance, security, reliability, maintainability, cost, and implementation complexity.
- Create and maintain technical design artifacts, including system diagrams, UML models, data flow diagrams, integration diagrams, and database designs.
- Establish and promote coding standards, architectural patterns, project structures, version-control practices, and software release standards across products.
- Document and communicate key architectural decisions to engineering teams and stakeholders.
- Incorporate security, privacy, identity, access control, and data protection requirements throughout application and system design.
- Develop secure software using established coding practices and identify vulnerabilities and architectural risks across applications, infrastructure, AI, and data systems.
- Collaborate with security and infrastructure teams to define requirements, remediate risks, and support cloud identity solutions using Microsoft Entra ID and Azure DevOps.
- Design and optimize systems for scalability, performance, availability, reliability, fault tolerance, and re-coverability as users, transactions, data volumes, and workloads increase.
- Analyze application and infrastructure performance, identify system bottlenecks, and recommend practical optimization approaches.
- Evaluate architectural tradeoffs among performance, scalability, security, cost, complexity, and participate in functional, performance, and security testing.
- Break complex requirements into manageable engineering tasks, implementation steps, and dependencies.
- Estimate development effort and technical complexity, clearly documenting assumptions, constraints, risks, and uncertainties.
- Identify dependencies across applications, data, infrastructure, teams, and third-party services that could affect delivery.
- Help engineering teams establish realistic delivery commitments and contingency approaches for high-risk technical components.
- Communicate changes to estimates, risks, dependencies, or technical approaches as new information becomes available.
- Communicate significant risks, estimate changes, dependencies, and changes to technical approaches to engineering and product leadership as new information becomes available.
- Contribute to sprint planning, backlog refinement, technical discussions, reviews, and retrospectives within an Agile development environment.
- Partner with product management to clarify requirements, acceptance criteria, priorities, dependencies, and implementation readiness.
- Track sprint objectives, blockers, risks, and delivery commitments while providing technical input into prioritization and sequencing decisions.
- Continuously improve engineering practices, tools, and development processes.
- Create and maintain clear technical documentation throughout the development lifecycle, including system designs, architecture diagrams, UML artifacts, data flows, API specifications, data models, integration requirements, engineering standards, deployment processes, monitoring plans, and test documentation.
- Use collaborative documentation platforms such as Microsoft Loop and Confluence to keep technical decisions, standards, and implementation guidance accessible and current.
- Provide concise, accurate updates on engineering progress, upcoming work, blockers, risks, dependencies, and changes to technical approaches.
- Communicate complex technical information clearly to engineering and non-engineering stakeholders and document key decisions, issues, and outcomes.
- Collaborate effectively with distributed technology teams in the United States and India across multiple time zones.
- Contribute to technical meetings, design reviews, and cross-functional discussions.
- Use engineering and collaboration tools to support requirements, architecture, development, source control, documentation, design, testing, and software delivery.
- Collaborate with product and UI/UX designers to interpret requirements and Figma designs and translate them into responsive, high-quality web, native, and mobile experiences.
- Provide technical guidance on the usability, performance, responsiveness, and implementation feasibility of UI/UX decisions.
- Develop and integrate enterprise applications using REST APIs, web services, event-driven architectures, cloud services, enterprise SaaS platforms, and relational and non-relational data systems.
- Design secure and reliable integrations across applications, mobile solutions, services, data platforms, and third-party systems.
That's many items; okay.
Then Requirements (Technical Qualifications):
Requirements
- with items:
- Strong proficiency in software development