DirectJobHub
Jobs · Engineering · New York

Director, Full-Stack Engineer

BNY · New York, NY · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job description. The description includes: - Intro: "We’re seeking a future team member for the role of Director, Full Stack Engineer to join our Digital Assets and Post-Trade Technology team. This role is located in New York, NY." - Then bullet-like list of responsibilities (starting with "In this role, you’ll make an impact in the following ways:" then a series of sentences each starting with a verb). Those are responsibilities. - Then "To be successful in this role, we’re seeking the following:" then list of qualifications/requirements: Bachelor’s degree..., 12+ years..., Deep expertise..., Strong domain knowledge..., Proven leadership..., Demonstrated ability in FinOps..., clear technical communication..., proactive innovation. - Then "About Us" paragraph about BNY. - Then "About The Team" with some text about culture, newsroom, awards. - Then "Our Benefits And Rewards" paragraph describing benefits, compensation, etc. Also mentions base salary info in Job Info section at bottom (not provided). It says "The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting." So we don't have actual salary figure; we should not create Pay section unless posting actually states them. Since no specific salary given, we should not include Pay section. - Benefits: they talk about highly competitive compensation, benefits, wellbeing programs, flexible global resources, health, personal resilience, financial goals, generous paid leaves, paid volunteer time, 401(k), medical/dental/vision/life insurance, other benefits, paid time off. That's substantive benefits content. So we can include Benefits section. - Schedule: not mentioned. No mention of work schedule (full-time, remote, etc). So we should not include Schedule. - Skills: Could extract from responsibilities and requirements: maybe we can include a Skills section summarizing technical skills: Java 17+, Spring Boot, Kubernetes, reactive design, circuit breakers, Kafka, etc. But we need to ensure we don't invent or summarize away detail; we can list them as bullet list from the responsibilities. That's okay because it's derived from content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing is okay as long as we don't lose detail? It says do NOT invent or summarize away detail. That suggests we should not omit details; we should keep them. But we can still list them as bullet points; that's not summarizing away detail, it's just extracting. However we already have responsibilities section with those details. Having a separate Skills section might duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine skills into Responsibilities or Requirements. Probably better to have sections: About the role (intro), Responsibilities (the list), Requirements (education/experience), Qualifications (maybe same as Requirements?), Skills (maybe technical skills), Benefits. But we need to avoid duplication and thin sections. Let's think: The posting includes: - Intro paragraph (location, role). That could be "About the role" section. - Responsibilities: the bullet list after "In this role, you’ll make an impact in the following ways:" (multiple sentences). We'll put each as
  • . - Requirements/Qualifications: The list after "To be successful in this role, we’re seeking the following:" includes education, experience, expertise, domain knowledge, leadership, FinOps, communication, innovation. That's a mix of qualifications and skills. Could split into Requirements (education/experience) and Qualifications (domain knowledge, leadership, etc.) but we can just have one "Requirements" section containing all. - Benefits: the paragraph under "Our Benefits And Rewards". We'll put as

    maybe with bullet list for specific benefits. - About Us and About The Team: Could be considered "About the company" but not requested as a section. The instruction only lists specific headings; we should not add extra headings like About Us. So we should omit those paragraphs because they are not requested headings. However we must preserve ALL substantive information; but we cannot add extra headings not in list. The instruction says: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should only use those headings. It also says: "include a section ONLY when the posting has real, specific content for it". So we can omit About Us and About The Team because they are not requested headings. However that would drop substantive info. But maybe we can incorporate that info into "About the role" or "Benefits"? Not appropriate. The instruction says we should not invent headings; but we could still include that content as

    without a heading? The instruction says output ONLY the HTML fragment; we can include

    elements anywhere. It didn't say we must wrap everything under headings. It said use

    for section headings (e.g. About the role, Responsibilities...). So we can have headings for those sections, and we can also have other

    elements not under a heading? Probably they expect the fragment to consist of sections with headings and content under them. But we could also include a leading

    for the intro before any heading? The intro is about the role; we could put that under

    About the role

    . That seems fine. Thus we will produce:

    About the role

    We’re seeking a future team member for the role of Director, Full Stack Engineer to join our Digital Assets and Post-Trade Technology team. This role is located in New York, NY.

    Responsibilities

    • Set architecture strategy and reference patterns for resilient, high throughput platforms bridging post trade/ledgering with institutional digital assets, owning reliability, performance, and regulatory compliance end to end.
    • Lead multiple Agile pods and their managers (20+ engineers), instituting bar-raising standards, hands-on design/code reviews, secure-by-default practices, and measurable SDLC outcomes.
    • Define Java 17+ Spring Boot microservices on Kubernetes with reactive designs, circuit breakers/bulkheads/backpressure, multi-region active-active HA/DR, and BCP alignment.
    • Own the API platform: low latency REST/GraphQL/gRPC with strict versioning, OAuth2/OIDC, mTLS, signed request verification, RBAC/least privilege, rate limits/abuse controls, and consistent contracts.
    • Champion event-driven architectures (Kafka, CQRS/event sourcing) with idempotency, replay safety, deterministic processing, and strong data consistency across transactional and streaming paths.
    • Architect secure digital asset custody at scale: MPC/HSM key lifecycle (generation/rotation/recovery), wallet orchestration and policy controls, tamper-evident audit logs, segregation of duties, and break glass governance.
    • Integrate off-chain services with Ethereum/Web3 and permissioned ledgers; operationalize AML/KYC/Travel Rule exchanges, sanctions screening, and auditable compliance workflows.
    • Drive secure delivery for Web/UI and Mobile: Angular/TypeScript and native apps with device attestation, secure storage/keystores, jailbreak/root detection, protected approval flows, CSP, and WebCrypto where appropriate.
    • Enforce holistic security and operability: secure SDLC (threat modeling, SAST/DAST/IAST, dependency scanning/SBOM, container/image signing), secrets hygiene and KMS, WAF/DDoS protections, runtime hardening, vulnerability management/patch SLAs, pen tests, incident response, and tabletop exercises.

    Requirements

    • Bachelor’s degree in computer science, Engineering, or a related field (or equivalent experience).
    • 12+ years of experience in high volume/low latency systems and platform ownership.
    • Deep expertise in Java 17+ and Spring Boot, and API design/architecture.
    • Strong domain knowledge in securities, post-trade processing, and digital assets.
    • Proven leadership experience managing multiple Agile teams and mentoring senior technical talent.
    • Demonstrated ability in FinOps, clear technical communication, and proactive innovation.
    We could also have a Skills section but it's covered. However we might want to extract technical skills: Java 17+, Spring Boot, Kubernetes, reactive design, circuit breakers, Kafka, etc. But that would duplicate content from responsibilities. The instruction: "Prefer a few substantive sections over many thin ones." So we should not create a Skills section if it's thin. We'll skip Skills. Benefits section: we need to capture the benefits paragraph. Let's extract the substantive benefits: "BNY offers highly competitive compensation, benefits, and wellbeing programs rooted in a strong culture of excellence and our pay-for-performance philosophy. We provide access to flexible global resources and tools for your life’s journey. Focus on your health, foster your personal resilience, and reach your financial goals as a valued member of our team, along with generous paid leaves, including paid volunteer time, that can support you and your family through moments that matter. BNY is an Equal Employment Opportunity/Affirmative Action Employer - Underrepresented racial and ethnic groups/Females/Individuals with Disabilities/Protected Veterans. BNY assesses market data to ensure a competitive compensation package for our employees. The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting. Base salary offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. Base salary is only part of the total rewards package, which may include eligibility for an annual discretionary incentive award. Subject to the terms and conditions of the applicable plans then in effect, eligible employees may enroll in a 401(k) plan as well as participate in Company-sponsored medical, dental, vision, and basic life insurance plans for the employee and the employee’s eligible dependents. Eligible employees also may receive other benefits (including various paid time off benefits, such as vacation and sick time), dependent on the position offered. Details of participation in these benefit plans will be provided if an employee receives an offer of employment. If hired, the employee will be in an “at will” position and the Company reserves the right to modify base salary (as well as any other discretionary payments or compensation programs) at any time, including for reasons related to individual performance, Company or individual department/team performance, and market factors." We need to remove boilerplate like EEO statement? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the EEO line: "BNY is an Equal Employment Opportunity/Affirmative Action Employer - Underrepresented racial and ethnic groups/Females/Individuals with Disabilities/Protected Veterans." That's boilerplate. Also maybe remove the sentence about at-will employment? That's also legal boilerplate. The instruction says remove legal/EEO boilerplate. So we should remove those sentences. Also remove the line about base salary being found in Job Info section (since we don't have that). That's maybe not boilerplate but it's a reference to missing info; we could keep it? It's not substantive; it's a placeholder. Better to omit because it's not actual salary info. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The sentence about base salary being found in Job Info section is placeholder; we should omit it. Also the sentence about base salary may vary depending on factors is generic but still substantive? It's somewhat generic

    • Similar jobs