Principal Software Engineer Lead
- .
- Requirements: The "Do What You Love To be successful in this role you will:" list includes:
- Have 12 years of relevant experience and a Bachelor's degree in Computer Science or its equivalent.
- Have a history of helping your reports excel in their current role, expand their knowledge, and progress to greater responsibility.
- Possess deep familiarity with modern CPU architectures, specifically ARM64 / AArch64 and x86_64 server platforms.
- Be experienced with cross-compilation toolchains, system profiling, and multi-architecture software deployment.
- Have experience with cloud compute virtualization technologies (KVM, QEMU), container runtimes, Linux system APIs, or hypervisor integration.
- Be experienced in technical design, product specification reviews, projects and backlog planning.
- Be able to work productively to identify and resolve issues in a collaborative, transparent manner.
These could be considered Requirements or Qualifications. The instruction says we have sections: Requirements, Qualifications, Skills. We need to decide where to put each piece. Usually Requirements = experience/education; Qualifications = maybe similar; Skills = technical skills. But we can combine.
We need to avoid thin sections. Perhaps we can put all those bullet points under Requirements (or Qualifications). But we need to preserve all substantive info.
We could split: Requirements: education and years experience. Qualifications: history of helping reports, etc. Skills: technical skills (CPU architectures, cross-compilation, virtualization, design, collaborative). But we need to ensure each section has real content.
Let's extract:
Education/Experience: "Have 12 years of relevant experience and a Bachelor's degree in Computer Science or its equivalent."
History of helping reports: "Have a history of helping your reports excel in their current role, expand their knowledge, and progress to greater responsibility."
That could be under Qualifications (leadership experience).
Technical skills: deep familiarity with modern CPU architectures (ARM64/AArch64 and x86_64), experienced with cross-compilation toolchains, system profiling, multi-architecture software deployment, experience with cloud compute virtualization technologies (KVM, QEMU), container runtimes, Linux system APIs, or hypervisor integration, experienced in technical design, product specification reviews, projects and backlog planning, able to work productively to identify and resolve issues collaboratively.
We could put those under Skills.
Now Benefits: The posting includes a Benefits section: "Benefits at Akamai: We support your health, well-being, finances, and life beyond work. See our benefits. FlexBase adapts to your job's needs Akamai's FlexBase program is yet another way we show our commitment to providing employees with an exceptional workplace experience. It's not about telling employees where to work; it's about supporting employees to do their best work. We trust our incredible employees to work in ways that suit them best: at home, in an office, or a combination of both. Connect with us on social and see what life at Akamai is like!"
Also later: "Akamai provides industry-leading benefits including healthcare, 401K savings plan, company holidays, vacation (in the form of PTO), sick time, family friendly benefits including parental leave and an employee assistance program including a focus on mental and financial wellness; Eligibility requirements apply."
Thus we have benefits content.
Pay: "Compensation Akamai is committed to fair and equitable compensation practices. For US based candidates only - the base salary for this position ranges from $169,300 - $304,700/year; a candidate’s salary is determined by various factors including, but not limited to, relevant work experience, skills, certifications and location. Compensation for candidates outside the US will vary. The compensation package may also include incentive compensation opportunities in the form of annual bonus or incentives, equity awards and an Employee Stock Purchase Plan (ESPP)."
Thus we have pay details.
Schedule: Not explicitly mentioned. There's FlexBase program about remote/hybrid work but not schedule specifics like full-time, part-time. The FlexBase program mentions work location flexibility, not schedule. The instruction says do not create Schedule section unless posting actually states them. There's no explicit schedule like "Full-time", "40 hours/week". So we should omit Schedule.
Now we need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We must use
for section headings. Use
- for any list of duties/requirements/benefits, and
for prose. We need to decide which content goes in which section. Let's craft: not needed; just headings and content. We'll output:
About the role
Do you want to help design and implement the next generation of cloud computing? Do you want to lead the expansion of compute architectures across the Akamai Connected Cloud? Join our Compute team! As a member of Akamai's Cloud Compute team, develop scalable services linking on-premises or cloud infrastructure to Akamai Connected Cloud. Contribute to expanding cloud compute products supporting AI and general compute on ARM and x86 workloads. This position provides opportunities to create production-quality software across multiple architectures and layers within Cloud Computing environments. Partner with the best This role provides an opportunity to make a significant impact on Akamai's growing cloud offerings. You must have a passion to get things done quickly and get them done right. As a Principal Software Engineer Lead, you will be responsible for:
But note that the responsibilities list follows; we might want to separate responsibilities into its own section. So the About the role could end before the list. Actually the sentence "As a Principal Software Engineer Lead, you will be responsible for:" is introductory to responsibilities. So we could put that sentence in About the role, then responsibilities list in its own section. Thus About the role paragraph ends before the colon? Let's include the sentence up to "responsible for:" as part of About the role? Might be okay. Better: About the role: all paragraphs before the list. That includes up to "You must have a passion to get things done quickly and get them done right." Then we start Responsibilities heading. Thus:About the role
Do you want to help design and implement the next generation of cloud computing? Do you want to lead the expansion of compute architectures across the Akamai Connected Cloud? Join our Compute team! As a member of Akamai's Cloud Compute team, develop scalable services linking on-premises or cloud infrastructure to Akamai Connected Cloud. Contribute to expanding cloud compute products supporting AI and general compute on ARM and x86 workloads. This position provides opportunities to create production-quality software across multiple architectures and layers within Cloud Computing environments. Partner with the best This role provides an opportunity to make a significant impact on Akamai's growing cloud offerings. You must have a passion to get things done quickly and get them done right.
Then Responsibilities:Responsibilities
- Architecting and scaling high-density ARM64 compute platform functionality and hypervisor layers across ACC.
- Designing, implementing, reviewing, documenting, and testing high-quality code in close collaboration with your team.
- Leading technical strategy for hardware enablement, cross-platform build pipelines, and workload performance optimization.
- Working closely with peers and coordinating with global teams to build new compute features or resolve low-level software bugs.
- Providing organizational and functional leadership to a team of engineers.
Requirements
- Have 12 years of relevant experience and a Bachelor's degree in Computer Science or its equivalent.
Qualifications
- Have a history of helping your reports excel in their current role, expand their knowledge, and progress to greater responsibility.
Skills
- Possess deep familiarity with modern CPU architectures, specifically ARM64 / AArch64 and x86_64 server platforms.
- Be experienced with cross-compilation toolchains, system profiling, and multi-architecture software deployment.
- Have experience with cloud compute virtualization technologies (KVM, QEMU), container runtimes, Linux system APIs, or hypervisor integration.
- Be experienced in technical design, product specification reviews, projects and backlog planning.
- Be able to work productively to identify and resolve issues in a collaborative, transparent manner.
maybe with
- for list of specific benefits.
We have: "Benefits at Akamai: We support your health, well-being, finances, and life beyond work. See our benefits. FlexBase adapts to your job's needs Akamai's FlexBase program is yet another way we show our commitment to providing employees with an exceptional workplace experience. It's not about telling employees where to work; it's about supporting employees to do their best work. We trust our incredible employees to work in ways that suit them best: at home, in an office, or a combination of both. Connect with us on social and see what life at Akamai is like!"
And later: "Akamai provides industry-leading benefits including healthcare, 401K savings plan, company holidays, vacation (in the form of PTO), sick time, family friendly benefits including parental leave and an employee assistance program including a focus on mental and financial wellness; Eligibility requirements apply."
We can make a
for the descriptive part, and a
- for the list of specific benefits.
Thus:
Benefits
Benefits at Akamai: We support your health, well-being, finances, and life beyond work. See our benefits. FlexBase adapts to your job's needs Akamai's FlexBase program is yet another way we
- for any list of duties/requirements/benefits, and