Principal Engineer, Flutter
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to decide which sections to include based on content.
We have:
- Role Summary (intro paragraph) – could be part of "About the role" maybe.
- Position Details About The Role: bullet list of responsibilities (hands-on architecture...). That's a list.
- About You: list of qualifications/requirements.
- Company Overview: paragraph about company.
- Company Benefits And Perks: list of benefits.
- Pay Range: specific numbers.
- Location/hybrid: "This is a Hybrid position located in Frisco, TX. You will be required to be on-site on an as-needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time." That's location and schedule info; schedule maybe hybrid.
We should not include sections like "Schedule" unless we have specific schedule details. We have hybrid info; we could put under a "Schedule" section? The rule says we can use headings like Schedule if we have content. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include Schedule if we have content. We have hybrid location details; that could be considered Schedule/Location. But we might also include a "Location" heading? Not in list but we could still use for any heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings but they gave examples. Safer to stick to those examples. So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to avoid thin sections. We have content for About the role (role summary). Responsibilities (the bullet list under About The Role). Requirements/Qualifications/Skills could be combined from About You. Benefits from Company Benefits And Perks. Pay from Pay Range. Schedule from hybrid/location info.
We must not repeat job title as heading. Good.
We must not include boilerplate like Company Overview? That's substantive but not a required heading; we could include as a paragraph under maybe "About the company" but not in list. Could we include it as a paragraph under a generic section? The instruction says prefer a few substantive sections over many thin ones. Could we include Company Overview as a paragraph under "About the role"? Might be odd. Better to include as its own section maybe "Company Overview". But that's not in the examples; but we could still use for any heading; they didn't forbid other headings, just gave examples. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings where applicable, but we could also add others if needed. However to be safe, we could incorporate company overview into a paragraph under "About the role" or maybe under a brief intro. But the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere.
We could create a section "Company Overview" with Company Overview
and a paragraph. That seems fine.
Similarly, we have "Position Details About The Role" heading already; we could treat that as "About the role". We'll use About the role
and then include the paragraph from Role Summary and maybe the bullet list under Responsibilities.
But we also have a separate "About You" section for qualifications.
Thus final HTML:
About the role
Role Summary McAfee is seeking a highly skilled Principal Engineer with deep desktop (Mac/Windows) and Flutter/Dart expertise to help build trusted, high performance security products that protect millions of users and families worldwide. In this hands on technical leadership role, you will architect, implement, and optimize Mac native experiences using Flutter, owning key aspects of our desktop strategy while shaping the long term engineering vision. As a Principal Engineer, you will lead critical architectural decisions, write production level code, and ensure our Flutter desktop applications meet the highest standards of security, reliability, performance, and user experience. You’ll collaborate closely with security engineers, designers, and product partners to transform complex technical and security concepts into intuitive, high quality customer experiences. If you’re energized by impactful, customer centric engineering and want to help shape the future of McAfee’s desktop products, we’d love to meet you. This is a Hybrid position located in Frisco, TX. You will be required to be on-site on an as-needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time.
But we need to separate schedule/hybrid info maybe into Schedule section. However we already included location/hybrid in About the role paragraph; that may be okay. But we might want to separate schedule.
Better: Keep About the role paragraph focusing on role summary (first paragraph). Then schedule/hybrid info in a Schedule section.
Let's parse:
Role Summary paragraph: "McAfee is seeking a highly skilled Principal Engineer with deep desktop (Mac/Windows) and Flutter/Dart expertise to help build trusted, high performance security products that protect millions of users and families worldwide. In this hands on technical leadership role, you will architect, implement, and optimize Mac native experiences using Flutter, owning key aspects of our desktop strategy while shaping the long term engineering vision. As a Principal Engineer, you will lead critical architectural decisions, write production level code, and ensure our Flutter desktop applications meet the highest standards of security, reliability, performance, and user experience. You’ll collaborate closely with security engineers, designers, and product partners to transform complex technical and security concepts into intuitive, high quality customer experiences. If you’re energized by impactful, customer centric engineering and want to help shape the future of McAfee’s desktop products, we’d love to meet you."
Then after that: "This is a Hybrid position located in Frisco, TX. You will be required to be on-site on an as-needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time."
We can put that in Schedule section.
Now "Position Details About The Role" bullet list: we can put under Responsibilities section.
Then "About You": we can split into Requirements, Qualifications, Skills maybe. But we can combine into one section "Requirements" with list.
But we need to avoid thin sections; we have enough content for each.
We also have Company Overview paragraph: we can put under Company Overview section.
Company Benefits And Perks: list under Benefits.
Pay Range: under Pay.
Thus sections: About the role, Responsibilities, Requirements, Company Overview, Benefits, Pay, Schedule.
We should not include Qualifications or Skills separately if we combine.
Now ensure we use - for any list.
We need to preserve all substantive information: ensure we don't lose any details.
Let's extract details.
About the role paragraph (role summary) we have.
Responsibilities list from "Position Details About The Role":
- Hands-on architecture and implementation (60%+ of your time) of high-performance Flutter applications for Windows and macOS used by millions of customers
- Write production code and lead critical technical implementations across the Flutter desktop stack
- Define and own Flutter desktop architectural standards with a focus on security, reliability, and long-term maintainability
- Ensure native desktop experiences across windowing, menus, keyboard shortcuts, accessibility, animations, and system integrations
- Partner with security engineers, designers, and product managers to translate complex security concepts into intuitive user experiences
- Design and implement robust abstractions for secure platform integrations using Flutter platform channels and native Windows/macOS APIs
- Drive best practices around state management, modularization, testing, and CI/CD
- Lead performance tuning efforts (startup time, memory usage, rendering efficiency)
- Mentor senior engineers through design reviews, code reviews, and technical guidance
- Set technical direction and architectural vision for the team
- Evaluate and adopt new Flutter and Windows/macOS capabilities while maintaining a strong security posture
That's a list.
About You list:
- You have 10+ years of software engineering experience with deep expertise in Flutter and Dart on any platform
- Proven track record of hands-on implementation and architecting production Flutter applications at scale, ideally on desktop
- Strong understanding of Windows and macOS application architecture and UX conventions
- Extensive experience integrating Flutter with native macOS code (Swift / Objective-C) via platform channels
- Solid background in system design, with an emphasis on secure, testable, and resilient architectures
- Experience with Flutter state management solutions (e.g., Riverpod, Bloc, Provider)
- Demonstrated ability to mentor senior engineers and set technical direction for teams
- Strong collaboration and communication skills, with the ability to influence across teams
- Passion for delivering polished, trustworthy user experiences through hands-on implementation
- Experience building or integrating security, privacy, or system-level software
- Familiarity with Apple Human Interface Guidelines and macOS accessibility standards
- Experience shipping apps at large scale with millions of users
- Knowledge of secure coding practices, threat modeling, or defense-in-depth
- Familiarity with AI-based coding tools and practices (e.g., Claude Code, AI-assisted development)
We can put these under Requirements.
Company Overview paragraph:
"McAfee is a leader in personal security for consumers. Focused on protecting people, not just devices, McAfee consumer solutions adapt to users’ needs in an always online world, empowering them to live securely through integrated, intuitive solutions that protects their families and communities with the right security at the right moment."
Company Benefits And Perks list:
- We work hard to embrace diversity and inclusion and encourage everyone at McAfee to bring their authentic selves to work every day.
- We offer a variety of social programs, flexible work hours and family-friendly benefits to all of our employees.
- Bonus Program
- 401k Retirement
- Medical, Dental, Vision, Basic Life, Short Term Disability and Long-Term Disability Coverage
- Paid Parental Leave
- Support and Community Involvement
- 14 Paid Company Holidays
- Unlimited Paid Time Off for Exempt Employees
- 96 Hours of Sick Time and 120 Hours of Vacation for Non-Exempt Employees Accrued Each Year
Note: The first two sentences are prose; we could keep them as
then list the specific benefits
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include based on content. We have: - Role Summary (intro paragraph) – could be part of "About the role" maybe. - Position Details About The Role: bullet list of responsibilities (hands-on architecture...). That's a list. - About You: list of qualifications/requirements. - Company Overview: paragraph about company. - Company Benefits And Perks: list of benefits. - Pay Range: specific numbers. - Location/hybrid: "This is a Hybrid position located in Frisco, TX. You will be required to be on-site on an as-needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time." That's location and schedule info; schedule maybe hybrid. We should not include sections like "Schedule" unless we have specific schedule details. We have hybrid info; we could put under a "Schedule" section? The rule says we can use headings like Schedule if we have content. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include Schedule if we have content. We have hybrid location details; that could be considered Schedule/Location. But we might also include a "Location" heading? Not in list but we could still use for any heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings but they gave examples. Safer to stick to those examples. So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to avoid thin sections. We have content for About the role (role summary). Responsibilities (the bullet list under About The Role). Requirements/Qualifications/Skills could be combined from About You. Benefits from Company Benefits And Perks. Pay from Pay Range. Schedule from hybrid/location info.
We must not repeat job title as heading. Good.
We must not include boilerplate like Company Overview? That's substantive but not a required heading; we could include as a paragraph under maybe "About the company" but not in list. Could we include it as a paragraph under a generic section? The instruction says prefer a few substantive sections over many thin ones. Could we include Company Overview as a paragraph under "About the role"? Might be odd. Better to include as its own section maybe "Company Overview". But that's not in the examples; but we could still use for any heading; they didn't forbid other headings, just gave examples. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings where applicable, but we could also add others if needed. However to be safe, we could incorporate company overview into a paragraph under "About the role" or maybe under a brief intro. But the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere.
We could create a section "Company Overview" with Company Overview
and a paragraph. That seems fine.
Similarly, we have "Position Details About The Role" heading already; we could treat that as "About the role". We'll use About the role
and then include the paragraph from Role Summary and maybe the bullet list under Responsibilities.
But we also have a separate "About You" section for qualifications.
Thus final HTML:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings but they gave examples. Safer to stick to those examples. So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to avoid thin sections. We have content for About the role (role summary). Responsibilities (the bullet list under About The Role). Requirements/Qualifications/Skills could be combined from About You. Benefits from Company Benefits And Perks. Pay from Pay Range. Schedule from hybrid/location info.
We must not repeat job title as heading. Good.
We must not include boilerplate like Company Overview? That's substantive but not a required heading; we could include as a paragraph under maybe "About the company" but not in list. Could we include it as a paragraph under a generic section? The instruction says prefer a few substantive sections over many thin ones. Could we include Company Overview as a paragraph under "About the role"? Might be odd. Better to include as its own section maybe "Company Overview". But that's not in the examples; but we could still use for any heading; they didn't forbid other headings, just gave examples. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings where applicable, but we could also add others if needed. However to be safe, we could incorporate company overview into a paragraph under "About the role" or maybe under a brief intro. But the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere.
We could create a section "Company Overview" with Company Overview
and a paragraph. That seems fine.
Similarly, we have "Position Details About The Role" heading already; we could treat that as "About the role". We'll use About the role
and then include the paragraph from Role Summary and maybe the bullet list under Responsibilities.
But we also have a separate "About You" section for qualifications.
Thus final HTML:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings where applicable, but we could also add others if needed. However to be safe, we could incorporate company overview into a paragraph under "About the role" or maybe under a brief intro. But the instruction says preserve ALL substantive information; we cannot drop it. So we need to include it somewhere.
We could create a section "Company Overview" with Company Overview
and a paragraph. That seems fine.
Similarly, we have "Position Details About The Role" heading already; we could treat that as "About the role". We'll use About the role
and then include the paragraph from Role Summary and maybe the bullet list under Responsibilities.
But we also have a separate "About You" section for qualifications.
Thus final HTML:
About the role
Role Summary McAfee is seeking a highly skilled Principal Engineer with deep desktop (Mac/Windows) and Flutter/Dart expertise to help build trusted, high performance security products that protect millions of users and families worldwide. In this hands on technical leadership role, you will architect, implement, and optimize Mac native experiences using Flutter, owning key aspects of our desktop strategy while shaping the long term engineering vision. As a Principal Engineer, you will lead critical architectural decisions, write production level code, and ensure our Flutter desktop applications meet the highest standards of security, reliability, performance, and user experience. You’ll collaborate closely with security engineers, designers, and product partners to transform complex technical and security concepts into intuitive, high quality customer experiences. If you’re energized by impactful, customer centric engineering and want to help shape the future of McAfee’s desktop products, we’d love to meet you. This is a Hybrid position located in Frisco, TX. You will be required to be on-site on an as-needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time.
But we need to separate schedule/hybrid info maybe into Schedule section. However we already included location/hybrid in About the role paragraph; that may be okay. But we might want to separate schedule. Better: Keep About the role paragraph focusing on role summary (first paragraph). Then schedule/hybrid info in a Schedule section. Let's parse: Role Summary paragraph: "McAfee is seeking a highly skilled Principal Engineer with deep desktop (Mac/Windows) and Flutter/Dart expertise to help build trusted, high performance security products that protect millions of users and families worldwide. In this hands on technical leadership role, you will architect, implement, and optimize Mac native experiences using Flutter, owning key aspects of our desktop strategy while shaping the long term engineering vision. As a Principal Engineer, you will lead critical architectural decisions, write production level code, and ensure our Flutter desktop applications meet the highest standards of security, reliability, performance, and user experience. You’ll collaborate closely with security engineers, designers, and product partners to transform complex technical and security concepts into intuitive, high quality customer experiences. If you’re energized by impactful, customer centric engineering and want to help shape the future of McAfee’s desktop products, we’d love to meet you." Then after that: "This is a Hybrid position located in Frisco, TX. You will be required to be on-site on an as-needed basis; when you are not working on-site, you will work from your home office. You must be within commutable distance of Frisco, TX. We are not offering relocation assistance at this time." We can put that in Schedule section. Now "Position Details About The Role" bullet list: we can put under Responsibilities section. Then "About You": we can split into Requirements, Qualifications, Skills maybe. But we can combine into one section "Requirements" with list. But we need to avoid thin sections; we have enough content for each. We also have Company Overview paragraph: we can put under Company Overview section. Company Benefits And Perks: list under Benefits. Pay Range: under Pay. Thus sections: About the role, Responsibilities, Requirements, Company Overview, Benefits, Pay, Schedule. We should not include Qualifications or Skills separately if we combine. Now ensure we use- for any list.
We need to preserve all substantive information: ensure we don't lose any details.
Let's extract details.
About the role paragraph (role summary) we have.
Responsibilities list from "Position Details About The Role":
- Hands-on architecture and implementation (60%+ of your time) of high-performance Flutter applications for Windows and macOS used by millions of customers
- Write production code and lead critical technical implementations across the Flutter desktop stack
- Define and own Flutter desktop architectural standards with a focus on security, reliability, and long-term maintainability
- Ensure native desktop experiences across windowing, menus, keyboard shortcuts, accessibility, animations, and system integrations
- Partner with security engineers, designers, and product managers to translate complex security concepts into intuitive user experiences
- Design and implement robust abstractions for secure platform integrations using Flutter platform channels and native Windows/macOS APIs
- Drive best practices around state management, modularization, testing, and CI/CD
- Lead performance tuning efforts (startup time, memory usage, rendering efficiency)
- Mentor senior engineers through design reviews, code reviews, and technical guidance
- Set technical direction and architectural vision for the team
- Evaluate and adopt new Flutter and Windows/macOS capabilities while maintaining a strong security posture
That's a list.
About You list:
- You have 10+ years of software engineering experience with deep expertise in Flutter and Dart on any platform
- Proven track record of hands-on implementation and architecting production Flutter applications at scale, ideally on desktop
- Strong understanding of Windows and macOS application architecture and UX conventions
- Extensive experience integrating Flutter with native macOS code (Swift / Objective-C) via platform channels
- Solid background in system design, with an emphasis on secure, testable, and resilient architectures
- Experience with Flutter state management solutions (e.g., Riverpod, Bloc, Provider)
- Demonstrated ability to mentor senior engineers and set technical direction for teams
- Strong collaboration and communication skills, with the ability to influence across teams
- Passion for delivering polished, trustworthy user experiences through hands-on implementation
- Experience building or integrating security, privacy, or system-level software
- Familiarity with Apple Human Interface Guidelines and macOS accessibility standards
- Experience shipping apps at large scale with millions of users
- Knowledge of secure coding practices, threat modeling, or defense-in-depth
- Familiarity with AI-based coding tools and practices (e.g., Claude Code, AI-assisted development)
We can put these under Requirements.
Company Overview paragraph:
"McAfee is a leader in personal security for consumers. Focused on protecting people, not just devices, McAfee consumer solutions adapt to users’ needs in an always online world, empowering them to live securely through integrated, intuitive solutions that protects their families and communities with the right security at the right moment."
Company Benefits And Perks list:
- We work hard to embrace diversity and inclusion and encourage everyone at McAfee to bring their authentic selves to work every day.
- We offer a variety of social programs, flexible work hours and family-friendly benefits to all of our employees.
- Bonus Program
- 401k Retirement
- Medical, Dental, Vision, Basic Life, Short Term Disability and Long-Term Disability Coverage
- Paid Parental Leave
- Support and Community Involvement
- 14 Paid Company Holidays
- Unlimited Paid Time Off for Exempt Employees
- 96 Hours of Sick Time and 120 Hours of Vacation for Non-Exempt Employees Accrued Each Year
Note: The first two sentences are prose; we could keep them as
then list the specific benefits