Senior Cloud Infrastructure Engineer
for each section heading. Only include sections where there is real specific content. Must not repeat job title as heading. Must not put Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove the "Applicants must submit a cover letter — see section 7." and the numbered sections? Those are part of description but we need to extract content.
We need to parse the posting.
Key info:
- Title: Senior Cloud Infrastructure Engineer (Azure/Networking) US Remote | Offices in Los Angeles, CA & Houston, TX Senior Role (5+ years of experience) Compensation: $160,000 - $180,000 base + bonus + benefits
- About the role: "Are you looking for a project to be proud of, one that sets you apart? Have you ever thought to yourself I wish we had setup our cloud environment this way from the start, it would have been so much cleaner and more efficient. We help serve the community through public transportation software and we need an expert to help us move from an on prem location to the cloud (Azure)."
- Responsibilities: Not explicitly listed but we have description of role: "You'll join a small, experienced DevOps team preparing for a major project: migrating our infrastructure to the cloud. Your expertise in both cloud infrastructure and IT/networking will make you a key voice in how that migration is designed and executed, and you'll help maintain the environment once we're there. Along the way, you'll help keep our current colocation environment healthy and stable until the migration is complete. Beyond the migration, you'll help us solution customer infrastructure requirements and drive future improvements to our platform, keeping our systems running smoothly and efficiently as we scale."
Also earlier: "We help serve the community through public transportation software and we need an expert to help us move from an on prem location to the cloud (Azure)." That's more about role.
- Requirements: Listed after "Requirements:" bullet list.
- Qualifications: Might be same as requirements? The posting includes "AZ-700 Azure Network Engineer Associate certification, or the demonstrated ability to pass it." That's a qualification. Also "Preferred:" list.
- Skills: Could be extracted from requirements and preferred.
- Benefits: Section "What we offer:" includes benefits: great benefits, $160k - $180k plus 15% bonus potential, Generous medical, dental, vision and voluntary benefits, Generous paid parental leave after one year, 401k plan with company match, Flexible hours and work location, Most of our work happens on Slack, but a few times per year we get together in person to collaborate within and across our teams. Our company is a small one with great culture, and you're going to have fun being a part of it. Our team is passionate; our product makes a difference.
- Pay: Already included in compensation line: $160,000 - $180,000 base + bonus + benefits. Also in benefits: $160k - $180k plus 15% bonus potential. We need Pay section only if posting actually states them. It does. So we can include Pay with that range.
- Schedule: Not explicitly stated; maybe "Flexible hours and work location" implies schedule flexibility. Could be considered schedule. But we need to include Schedule only if posting actually states them. It says "Flexible hours and work location". That's schedule info. So we can include Schedule.
We must not include placeholder text like "commensurate with experience". Not present.
We must not repeat job title as heading. So we will not have Senior Cloud Infrastructure Engineer... etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
Maybe combine certifications etc. Could list AZ-700 etc.Skills
About the roleAre you looking for a project to be proud of, one that sets you apart? Have you ever thought to yourself I wish we had setup our cloud environment this way from the start, it would have been so much cleaner and more efficient. We help serve the community through public transportation software and we need an expert to help us move from an on prem location to the cloud (Azure). GMV is a multinational group with global presence in different high-tech sectors. In the US, our company was originally founded as Syncromatics in 2006 and joined GMV Global in 2015. We specialize in all things technical for public transit systems. This means we design, manufacture, and manage all kinds of different products and features, including driver interfaces, dispatch communications, passenger counters, announcers, GPS tracking, and reporting & data analytics. It also means we build real-time information systems for riders, including apps and digital signage found at bus stops. We have relationships with Apple Maps, Google Maps, Transit app, and our work goes out to millions of riders on those platforms. Our product is like air traffic control, but for buses. There are a mix of hardware and software products in this role. Our team in the US has approximately 70 people across the US, with 15 in the product/engineering department. It’s the best of both worlds: small company feel with big company support. To learn more about the US-based intelligent transportation systems division of GMV, visit www.gmvtransit.com. Our mission is to Make Transit Work for them, and we take this mission very seriously. Our team thrives on