Manager, Solution Development & Innovation
- .
Then "Qualifications:" followed by a list of bullet-like sentences (some with semicolons). We need to put them in
- . Possibly separate "Requirements" vs "Qualifications"? The instruction says we can have sections like Requirements, Qualifications, Skills. The posting lumps qualifications and requirements together. We could put them under "Qualifications". Or we could split: "Requirements" for mandatory items (like Bachelor's degree required, work authorization) and "Qualifications" for preferred (Master's preferred, notable experience, etc). But we must not invent sections if content is thin. Better to have one "Qualifications" section containing all.
Then after qualifications, there is a paragraph about salary ranges: "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors such as applicant's skills, job responsibilities, prior relevant experience, certain degrees and certifications and market considerations." This is about Pay but does not give actual numbers or range. It says "If required, the ranges displayed below or via the URL below..." but no actual range displayed in text. It mentions a link to obtain salary ranges by city outside of CA. This is somewhat pay info but not a specific range. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Does stating that they comply with salary range regulations count as stating them? It does not give actual numbers. It says "If required, the ranges displayed below or via the URL below are specifically for those potential hires..." but we don't see the ranges displayed in the posting. The link is provided. Might be considered stating that salary info is available via link. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It might be ambiguous. Safer to not include Pay section because no explicit salary range is given. The instruction says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The text about salary ranges is not filler but it's a statement about compliance. However it doesn't give actual numbers. I'd lean to not include Pay section.
Benefits: Later: "In addition, KPMG is proud to offer a comprehensive, competitive benefits package, with options designed to help you make the best decisions for yourself, your family, and your lifestyle. Available benefits are based on eligibility. Our Total Rewards package includes a variety of medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, and a robust suite of personal well-being benefits to support your mental health. Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday. Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work."
This is substantive benefits info. So we should include a Benefits section with that content (maybe as
paragraphs). Also note there is a link to benefits details; we can keep that as part of the paragraph. Schedule: Not mentioned explicitly. There's mention of standard work hours, personal time off, holidays, breaks. That is somewhat schedule-related but not explicit schedule like "full-time", "Monday-Friday". The instruction says never create Schedule section unless posting actually states them. It does mention standard work hours, but not a specific schedule. Might be considered schedule info. However it's vague. Safer to omit Schedule section. Skills: Not explicitly listed as a separate section; qualifications include skills like "Proficient experience with Microsoft and Azure technology ecosystems", "ability to rapidly learn and apply emerging technologies", "product-oriented mindset", "sound technical judgment", "independent prioritization", "strong communication skills". Could be considered skills. But we already have Qualifications section that includes these. We could split out Skills but risk thin sections. Better to keep Qualifications. About the role: We'll include the introductory paragraph about KPMG and the role. Now we must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes many EEO statements, visa sponsorship statement, etc. We need to remove those. Also remove lines like "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges." That's not EEO but it's about pay transparency; we might keep it if we include Pay section, but we decided not to. So we can remove that paragraph. Also remove: "Applicant must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)". That's boilerplate about visa; remove. Remove: "KPMG offers a comprehensive compensation and benefits package." (some duplication). Actually that line appears before benefits description; we might keep part of it but it's generic. Might be considered boilerplate. But we already have benefits description; we can keep the substantive benefits lines and drop the generic line. Remove: "KPMG is an equal opportunity employer. KPMG complies with all applicable federal, state and local laws regarding recruitment and hiring. All qualified applicants are considered for employment without regard to race, color, religion, age, sex, sexual orientation, gender identity, national origin, citizenship status, disability, protected veteran status, or any other category protected by applicable federal, state or local laws. The attached link contains further information regarding KPMG's compliance with federal, state and local recruitment and hiring laws." Remove. Remove: "No phone calls or agencies please. KPMG recruits on a rolling basis. Candidates are considered as they apply, until the opportunity is filled. Candidates are encouraged to apply expeditiously to any role(s) for which they are qualified that is also of interest to them." Remove. Remove: "Los Angeles County applicants: Material job duties for this position are listed above. Criminal history may have a direct, adverse, and negative relationship with some of the material job duties of this position. These include the duties and responsibilities listed above, as well as the abilities to adhere to company policies, exercise sound judgment, effectively manage stress and work safely and respectfully with others, exhibit trustworthiness, and safeguard business operations and company reputation. Pursuant to the California Fair Chance Act, Los Angeles County Fair Chance Ordinance for Employers, Fair Chance Initiative for Hiring Ordinance, and San Francisco Fair Chance Ordinance, we will consider for employment qualified applicants with arrest and conviction records." This is legal boilerplate; remove. Also remove duplicated lines: The posting repeats "KPMG offers a comprehensive compensation and benefits package." and later "In addition, KPMG is proud to offer a comprehensive, competitive benefits package". We'll keep the latter. Now compile sections. About the role: Combine first paragraph and the role-seeking sentence. First paragraph: "Known for being a great place to work and build a career, KPMG provides audit, tax and advisory services for organizations in today's most important industries. Our growth is driven by delivering real results for our clients. It's also enabled by our culture, which encourages individual development, embraces an inclusive environment, rewards innovative excellence and supports our communities. With qualities like those, it's no wonder we're consistently ranked among the best companies to work for by Fortune Magazine, Consulting Magazine, Seramount, Fair360 and others. If you're as passionate about your future as we are, join our team." Then role sentence: "KPMG is currently seeking a Manager, Solution Development & Innovation to join our Digital Office within the Legal, Risk Management and Compliance organization." We can combine into a
maybe two paragraphs. Responsibilities: list each bullet. Let's extract responsibilities lines: - Lead clients from problem definition through solution design, prototyping, development, testing, and implementation, translating business challenges and user needs into product visions, solution concepts, technical requirements, and actionable delivery plans - Evaluate and apply technologies across application development, data, automation, AI, cloud, and enterprise platforms to determine the most effective solution approach, partnering with developers, architects, designers, data and AI resources to shape scalable, practical, and business-focused solutions - Serve as a day-to-day leadership backup across technical delivery, projects, resources, and client engagements, maintaining sufficient technical depth to evaluate tradeoffs, identify constraints, and support informed product, solution, and delivery decisions - Provide technical direction and oversight, ensuring solutions are feasible, appropriately scoped, scalable, and aligned with enterprise technology standards, while guiding multidisciplinary onshore and offshore teams through solution delivery and managing priorities, dependencies, risks, and resource needs - Partner with enterprise architecture, technology, security, data, and platform teams to transition solutions from concept to production, building trusted relationships with clients and stakeholders to facilitate discovery, decision-making, and solution adoption - Represent LRMC Digital in business and technical forums, communicating complex concepts to both technical and non-technical audiences, while coaching and developing technical resources and fostering collaboration, accountability, and continuous improvement across delivery teams - Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment We'll put each as
- . Qualifications: extract bullet lines. - Minimum five years of recent experience in technology consulting, software product development, solution architecture, digital transformation, or related technology leadership roles, with demonstrated experience delivering technology solutions from concept through implementation - Master's degree from an accredited college or university in technology management, information systems, business administration, or related discipline preferred; Bachelor's degree from an accredited college or university in computer science, information systems, engineering, business technology, information management, or a related field required - Notable experience leading cross-functional development teams and technical professionals in complex business and technology environments, alongside experience leading and developing technical professionals - Proven experience working directly with business stakeholders to define requirements, shape solutions, and manage delivery outcomes, combined with strong stakeholder engagement and client relationship management skills - Experience with both Agile and iterative solution
- . Possibly separate "Requirements" vs "Qualifications"? The instruction says we can have sections like Requirements, Qualifications, Skills. The posting lumps qualifications and requirements together. We could put them under "Qualifications". Or we could split: "Requirements" for mandatory items (like Bachelor's degree required, work authorization) and "Qualifications" for preferred (Master's preferred, notable experience, etc). But we must not invent sections if content is thin. Better to have one "Qualifications" section containing all.
Then after qualifications, there is a paragraph about salary ranges: "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors such as applicant's skills, job responsibilities, prior relevant experience, certain degrees and certifications and market considerations." This is about Pay but does not give actual numbers or range. It says "If required, the ranges displayed below or via the URL below..." but no actual range displayed in text. It mentions a link to obtain salary ranges by city outside of CA. This is somewhat pay info but not a specific range. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Does stating that they comply with salary range regulations count as stating them? It does not give actual numbers. It says "If required, the ranges displayed below or via the URL below are specifically for those potential hires..." but we don't see the ranges displayed in the posting. The link is provided. Might be considered stating that salary info is available via link. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It might be ambiguous. Safer to not include Pay section because no explicit salary range is given. The instruction says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The text about salary ranges is not filler but it's a statement about compliance. However it doesn't give actual numbers. I'd lean to not include Pay section.
Benefits: Later: "In addition, KPMG is proud to offer a comprehensive, competitive benefits package, with options designed to help you make the best decisions for yourself, your family, and your lifestyle. Available benefits are based on eligibility. Our Total Rewards package includes a variety of medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, and a robust suite of personal well-being benefits to support your mental health. Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. Additionally, each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday. Additional details about our benefits can be found towards the bottom of our KPMG US Careers site at Benefits & How We Work."
This is substantive benefits info. So we should include a Benefits section with that content (maybe as