Software Engineer III - Enterprise Intelligence
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "About Electronic Arts" maybe? The instruction says use headings for sections like About the role, Responsibilities, etc. The posting includes "Description & Requirements" then description, then Responsibilities, Qualifications, then later "Pay Transparency - North America Compensation And Benefits" includes pay ranges and benefits. Also "About Electronic Arts" is a section about company; could map to "About the role"? Actually "About the role" is typical heading for role description. The description paragraph at start could be considered About the role. We'll put that under About the role
with
containing the description paragraphs (the first paragraph about EA, then about EI Group, Data Group, role). We'll need to preserve all substantive info. We must not create sections with filler like "commensurate with experience". Not needed. We need to include Pay and Benefits sections if posting states them. It does: Pay ranges and benefits described. So we will have
Pay
withcontaining pay range info. And
Benefits
withcontaining benefits list. We also need Responsibilities and Qualifications sections. Possibly also Skills? The qualifications list includes many items; we could treat them as Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which to use. The posting has "Responsibilities" and "Qualifications". It also has a description that could be About the role. It does not have explicit Skills section, but we could embed skills within Qualifications. Better to follow the posting: Use Responsibilities and Qualifications headings. Also maybe Requirements? The qualifications list could be considered Requirements. But we already have Qualifications heading. We'll not duplicate. We need to output only HTML fragment, no /. Use
and
,
- for lists.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from Responsibilities and Qualifications.
Let's extract.
Description paragraph(s):
"Electronic Arts creates next-level entertainment experiences that inspire players and fans around the world. Here, everyone is part of the story. Part of a community that connects across the globe. A place where creativity thrives, new perspectives are invited, and ideas matter. A team where everyone makes play happen. The Enterprise Intelligence (EI) Group develops a unified Big Data pipeline across all franchises at Electronic Arts. Our live service platform incorporates data collection, ingestion, processing, real-time streaming analytics, access, and visualization - all built on a modern, cloud-based tech stack with cutting-edge tools. The Data Group provides the tools and platform that power the future of game development, marketing, sales, accounting, and customer experience. As a Software Engineer III (SE III), you will take ownership of complex systems and lead the design and delivery of scalable solutions. You will work with teams to define technical direction, ensure operational excellence, and drive best practices while mentoring junior engineers and contributing to the broader engineering culture. The SE III will report to the Senior Manager, Engineering."
That's the description.
Responsibilities bullet list (the lines start with "You will ..."):
- design, implement, and own large-scale, distributed systems and services with high availability, scalability, and performance requirements.
- lead the end-to-end development of complex features and systems, from design through deployment and ongoing operation.
- drive architectural decisions, evaluating trade-offs in scalability, reliability, cost, and maintainability.
- build and maintain robust data pipelines and real-time streaming systems using modern distributed technologies.
- ensure operational excellence by implementing monitoring, alerting, and observability best practices; participate in on-call rotations as needed.
- Improve system performance through profiling, benchmarking, and optimization of compute, memory, and I/O.
- establish and enforce coding standards, testing strategies, and CI/CD best practices.
- mentor junior engineers, provide technical guidance, and contribute to team growth and knowledge sharing.
- identify technical debt and drive initiatives to improve system health, reliability, and developer productivity.
Note capitalization: "You will Improve" maybe typo; we keep as is.
Qualifications bullet list:
- 7+ years of professional software engineering experience building and operating production systems.
- Expertise in software design, distributed systems, data structures, and algorithms.
- Proficiency Java, with the ability to write production-grade, maintainable code.
- Experience designing and building scalable backend systems and APIs.
- Hands-on experience with data pipelines, streaming frameworks (e.g., Kafka, Flink, Storm), or large-scale data processing systems.
- Experience working with cloud platforms (preferably AWS) and distributed architectures.
- Experience with system reliability, observability, and performance optimization.
- Experience with relational databases (e.g., MySQL, PostgreSQL, Amazon RDS), NoSQL databases, or columnar databases, and data modeling.
- Familiarity with containerization and orchestration tools (e.g., Docker, Kubernetes).
Pay section:
"Pay Transparency - North America Compensation And Benefits The ranges listed below are what EA in good faith expects to pay applicants for this role in these locations at the time of this posting. If you reside in a different location, a recruiter will advise on the applicable range and benefits. Pay offered will be determined based on a number of relevant business and candidate factors (e.g. education, qualifications, certifications, experience, skills, geographic location, or business needs). PAY RANGES Washington (depending on location e.g. Seattle vs. Spokane) *$133,100 - $178,400 USD Pay is just one part of the overall compensation at EA. In the US, we offer a package of benefits including paid time off (3 weeks per year to start), 80 hours per year of sick time, 16 paid company holidays per year, 10 weeks paid time off to bond with baby, medical/dental/vision insurance, life insurance, disability insurance, and 401(k) to regular full-time employees. Certain roles may also be eligible for bonus and other incentive programs."
We need to separate Pay and Benefits. The Pay section includes the pay range and statement about pay being part of compensation. Benefits list follows.
Thus:
Pay
The ranges listed below are what EA in good faith expects to pay applicants for this role in these locations at the time of this posting. If you reside in a different location, a recruiter will advise on the applicable range and benefits. Pay offered will be determined based on a number of relevant business and candidate factors (e.g. education, qualifications, certifications, experience, skills, geographic location, or business needs). PAY RANGES Washington (depending on location e.g. Seattle vs. Spokane) *$133,100 - $178,400 USD. Pay is just one part of the overall compensation at EA.
Then Benefits:Benefits
In the US, we offer a package of benefits including paid time off (3 weeks per year to start), 80 hours per year of sick time, 16 paid company holidays per year, 10 weeks paid time off to bond with baby, medical/dental/vision insurance, life insurance, disability insurance, and 401(k) to regular full-time employees. Certain roles may also be eligible for bonus and other incentive programs.
We could also make a- for benefits list, but the instruction says use
- for any list of duties/requirements/benefits. So we should convert benefits to list. Similarly responsibilities and qualifications to lists.
Thus:
Responsibilities:
- each bullet.
Qualifications:
- each bullet.
Benefits:
- each benefit item.
Pay: just a paragraph with range.
About the role: paragraph(s) maybe multiple
but we can combine into one
with the description text. We must not repeat job title as heading. No mention of Job ID etc. We must remove boilerplate: The "About Electronic Arts" section after benefits is boilerplate/EEO etc. We should remove that entirely. Also remove "Electronic Arts is an equal opportunity employer..." etc. Also remove "We will also consider employment qualified applicants with criminal records..." etc. Also remove "EA also makes workplace accommodations..." etc. Also remove "About Electronic Arts" heading and its content. Also remove "Pay Transparency - North America Compensation And Benefits" heading? We already used Pay and Benefits headings; we can drop that line. Also remove "This is a hybrid role located in Kirkland, WA" maybe? That's location info; could be considered metadata; but we could include as a short paragraph maybe under About the role? The instruction says fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short p after About the role. But we must not create a Schedule section unless specified. Location is not schedule. We could include a short p: "This is a hybrid role located in Kirkland, WA." That's fine. We must not include "Pay Transparency - North America Compensation And Benefits" as heading; we already have Pay and Benefits. Now construct HTML. We'll start with
About the role
... description ...
This is a hybrid role located in Kirkland, WA.
ThenResponsibilities
- ...
Qualifications
- ...
Pay
...
ThenBenefits
- ...
- each benefit item.
Pay: just a paragraph with range.
About the role: paragraph(s) maybe multiple
- each bullet.
Benefits:
- each bullet.
Qualifications:
- for any list of duties/requirements/benefits. So we should convert benefits to list. Similarly responsibilities and qualifications to lists.
Thus:
Responsibilities:
- for benefits list, but the instruction says use