Senior Principal Engineer - Platform and SRE (Hybrid - Seattle)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse the job description. We need to extract: - About the role: likely the introductory paragraph describing role. Could be "A Senior Principal Engineer at Nordstrom serves as a strategic technical consultant..." etc. We'll include that as prose
. - Responsibilities: list of duties. The description includes many responsibilities: "Own the north star architecture...", "Establish the design principles...", "Identify where the platform limits...", etc. We'll need to capture them as bullet list. - Requirements/Qualifications/Skills: The posting includes "You own this if you have..." with bullet list of requirements (15+ years experience, degree, deep hands-on architectural experience, etc). Also includes "Ability to write and speak clearly..." etc. We'll need to decide which sections to use. The instruction: use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements and Qualifications maybe, but we need to decide based on content. The posting has a list of requirements under "You own this if you have...". That could be Requirements. Also there are skills like "Ability to write and speak clearly". Could be Skills. But we can also put all under Requirements. However we need to avoid thin sections. Probably better to have Requirements (including experience, education, technical expertise) and Skills (soft skills like communication, influence). But we need to see if there is enough content for each. Let's extract: About the role: first paragraph(s) up to "You will set the technical direction for Platform and SRE and make the operational bar easier to meet as you raise it, through intelligent systems that deliver more with greater efficiency." That's description. Responsibilities: bullet list after "A day in the life..." includes many items. We'll capture each sentence as bullet. Requirements: the list under "You own this if you have..." includes: - 15+ years of professional software or infrastructure engineering experience and a Bachelor's or Master's degree in Computer Science, Engineering, or related field. - Deep, hands-on architectural experience with large-scale cloud platforms, including containerized workloads on Kubernetes in production, multi-account cloud estates, and shared services owned centrally but consumed by many teams. - Demonstrated depth in continuous delivery at enterprise scale: progressive delivery and canary analysis, immutable artifact identity and promotion-over-rebuild discipline, configuration as versioned deployment, and rollback design that holds up when state is forward-incompatible. - Experience with software supply chain security beyond scanning, including build provenance, artifact signing or attestation, and policy enforcement at deploy time. - A track record establishing SRE practice at scale: SLOs and error budgets that influence release decisions, observability standards, incident command, and an informed view of why measures of central tendency are weak signals for reliability. - Architectural experience with resilience posture, covering blast-radius isolation patterns such as cell-based architecture, multi-region active-passive and active/active trade-offs, data consistency under concurrent writes, and rehearsed failover. - Experience engineering for large, predictable traffic peaks in retail, e-commerce, marketplace, or a comparably seasonal environment, including capacity forecasting, load and scale testing, and chaos exercises against revenue-critical journeys. - Sound cost judgment, with a history of recommending reliability investment that leadership can defend financially, and the willingness to argue against expensive architecture that the organization cannot yet operate. - A record of influence without authority: setting standards that teams adopt because they are useful, resolving cross-team technical conflict in a way both sides can live with, and moving organizations you do not manage. - Informed, skeptical perspective on AI for operations and delivery, including where agent-based investigation and automated remediation currently work and where published results do not yet support autonomy. - Judgment about organizational design in engineering, including the failure modes of centralized operations functions and how ownership boundaries shape whether reliability improves. - Ability to write and speak clearly enough that a standard, a trade-off, or a risk lands with engineers and with executives in the same room and the same document. That's a lot; could be Requirements. Skills: maybe we could separate "Ability to write and speak clearly" as Skills, but it's already in the list. Could also include "Mentor principal and senior engineers", "Serve as a trendsetter in hiring", "Represent Nordstrom's platform engineering externally" - those are responsibilities though. We could have Skills section for things like "Mentoring", "Influence without authority", "Communication". But we already have many. Given instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section (Requirements) and maybe Skills not needed. But we need to follow headings list: we can include only those headings that have content. So we could have About the role, Responsibilities, Requirements, Benefits, Pay. Possibly Schedule (hybrid in Seattle, WA, must be in office 4 days/week). That's schedule info. Thus sections: - About the role: prose. - Responsibilities: ul li. - Requirements: ul li (the "You own this if you have..." list). - Benefits: ul li (list of benefits). - Pay: p with pay range. - Schedule: p with hybrid info. We must not include headings with filler. Ensure we don't include empty sections. Now we need to strip boilerplate: remove cookie/navigation/legal/EEO etc. Also remove application instructions, duplicated lines, etc. Also remove the "A few more important points..." etc. Also remove the "Pay Range Details" heading? We'll just include Pay section. We need to preserve all substantive information. Let's craft HTML. We'll start with
About the role
then...
. ThenResponsibilities
- ...
Requirements
- ...
Benefits
- ...
Pay
$200,500.00 - $332,000.00 Annual
. ThenSchedule
This role is offered as hybrid in Seattle, WA. Candidates must be available to work in office at the Nordstrom corporate headquarters a minimum of 4 days/week to be considered for this position.
. Now we need to ensure we captured all responsibilities from "A day in the life..." section. Let's extract responsibilities bullet points: From text: "A day in the life... Own the north star architecture for cloud platform, CI/CD, and SRE, and hold a view that runs two to three years out, deliberately past the current product cycle. Establish the design principles that let teams make sound calls without needing you in the room. Identify where the platform limits the business before it surfaces as an incident or a missed date. Own the problems that sit between teams and lack clear ownership and carry them to a solution. Attach reliability targets to what the business does rather than to the services that happen to carry it. A single system often supports capabilities with different availability needs, and it is rarely worth building everything to the highest tier a system touches. Make deliberate degradation, where the most critical capabilities keep running, the expectation in design reviews. Drive consensus on direction across Platform, SRE, Security, and the product and engineering teams that consume what we build. Make standards hold by enforcing them in the pipeline and in production validation gating, so everyone meets the same expectations. Resolve technical disagreement without being divisive. Guide design reviews inside and outside your own organization and set SRE up to do the same at scale, so delivered systems match the design that was agreed. When reality argues against a standard, change the standard. Identify the industry trends and emerging capabilities worth adopting, and decide which ones Nordstrom should move on now, wait on, or skip entirely. Separate documented production practice from vendor claims and conference aspiration. Act as a technical decision maker during significant incidents regardless of which systems are involved, and turn what those incidents teach into platform defaults, not one-team fixes. Mentor principal and senior engineers across the organization, encourage open technical debate, and help teams think past the problem currently in front of them. Serve as a trendsetter in hiring for senior technical roles. Represent Nordstrom's platform engineering externally." We need to ensure we keep all. Now Benefits: list includes: "Medical/Vision, Dental, Retirement and Paid Time Away Life Insurance and Disability Merchandise Discount and EAP Resources" Also later: "Benefits include 401k, medical/vision/dental/life/disability insurance options, PTO accruals, Holidays, and more." We should combine into a list without duplication. Let's list unique benefits: - Medical/Vision - Dental - Retirement - Paid Time Away (PTO) - Life Insurance - Disability - Merchandise Discount - EAP Resources - 401k - PTO accruals (maybe same as Paid Time Away) - Holidays - More (but we can just list the specifics). We'll avoid vague "and more". We'll list the concrete ones. Now Requirements list: we need to convert each bullet into