Sr Python Software Engineer

We need to output HTML fragment with sections only when there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job posting. Job Summary: "Responsible for designing and building scalable, low-latency Python-based systems supporting front-office Short End Trading front to back systems Ensures robust handling of trade lifecycle, validation, and downstream system integration (Risk, Finance, Ops) Implements strong engineering practices to prevent data inconsistencies, trade capture errors, and lifecycle breaks Addresses scalability challenges through well-architected services, efficient data models, and event-driven design Acts as a key engineering link across Trading, Risk, Finance, and technology teams ensuring seamless data flow and system integration Enables high-quality, predictable delivery supporting GFF growth, faster product onboarding, and reduced execution risk" That's essentially the job summary. Could be placed under "About the role" or maybe "Responsibilities". The posting also repeats responsibilities later. We have location: Jersey City, New Jersey; job type: Contract; salary: $57.78 - 67.78 per hour; work hours: 8am to 5pm; education: Bachelors. We need to include Pay and Schedule sections only if posting actually states them. Yes, salary and work hours given. So we can have Pay section with that salary range. Schedule section with work hours. Benefits: The posting mentions "Randstad Digital offers a comprehensive benefits package, including: medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility)." That's specific benefits. So we can include Benefits section with that list. Qualifications: There's a "Qualifications" heading in the posting with a list of qualifications. We'll output that as Qualifications section. Skills: There's a "Skills" line: "trading systems,analytics platforms,data analysis,Python,Quartz,Debugging,troubleshooting,analytical solutions,calculations,Corporate Bonds,Fixed Income products,Interest Rate Derivatives,financing,finance,financial products,market data,investigation,Investigating,Quantitative Risk,Risk Analytics,Risk,Root cause analysis,stress testing,risk technology,Total Return Swaps". That's a list of skills. We'll output Skills section. Responsibilities: There's a "Responsibilities" heading with bullet list (though it's repeated). We'll output Responsibilities section with list items. About the role: Could be the job summary paragraph. We'll put that under About the role. We must not repeat job title as heading. No Job ID etc. We must not include boilerplate like EEO, accommodation, etc. Remove those. We must not include application instructions. We must not include duplicated lines. We need to preserve all substantive information. Let's extract content. Job Summary paragraph: "Responsible for designing and building scalable, low-latency Python-based systems supporting front-office Short End Trading front to back systems Ensures robust handling of trade lifecycle, validation, and downstream system integration (Risk, Finance, Ops) Implements strong engineering practices to prevent data inconsistencies, trade capture errors, and lifecycle breaks Addresses scalability challenges through well-architected services, efficient data models, and event-driven design Acts as a key engineering link across Trading, Risk, Finance, and technology teams ensuring seamless data flow and system integration Enables high-quality, predictable delivery supporting GFF growth, faster product onboarding, and reduced execution risk" We can keep as a paragraph. Responsibilities: The posting includes a "Responsibilities" heading then list items: "Degrees in any of the following: Computer Science, Computational Finance, Financial Mathematics, Computer Science, Applied Mathematics / Statistics, Financial Engineering" Wait that seems like education requirement but placed under Responsibilities? Actually the text: "Responsibilities Degrees in any of the following: Computer Science, Computational Finance, Financial Mathematics, Computer Science, Applied Mathematics / Statistics, Financial Engineering Responsible for designing and building scalable, low-latency Python-based systems supporting front-office Short End Trading front to back systems Ensures robust handling of trade lifecycle, validation, and downstream system integration (Risk, Finance, Ops) Implements strong engineering practices to prevent data inconsistencies, trade capture errors, and lifecycle breaks Addresses scalability challenges through well-architected services, efficient data models, and event-driven design Acts as a key engineering link across Trading, Risk, Finance, and technology teams ensuring seamless data flow and system integration Enables high-quality, predictable delivery supporting GFF growth, faster product onboarding, and reduced execution risk" So the responsibilities list includes the degree line? That seems odd; maybe it's a mistake. But we must preserve all substantive information. So we include that line as a responsibility? Actually it's under Responsibilities heading but it's about degrees. Could be mis-placed. We'll treat it as a responsibility item: "Degrees in any of the following: Computer Science, Computational Finance, Financial Mathematics, Applied Mathematics / Statistics, Financial Engineering". Note duplicate Computer Science appears twice; we can keep as is or deduplicate? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The duplicate "Computer Science" appears twice in that list; we should deduplicate? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we should deduplicate the list: Computer Science, Computational Finance, Financial Mathematics, Applied Mathematics / Statistics, Financial Engineering. Then the rest of responsibilities are the same as the job summary sentences. We'll list each as separate

. Qualifications: The posting has "Qualifications" then a block of text: "Python / ReactJS / Functional Programming Strong domain expertise in Global Markets, with deep understanding of trade lifecycle including capture, margining, collateral management, lifecycle events, and settlement flows Proven hands-on experience in end-to-end development using Python, covering design, development, testing, deployment, and production support Strong application of object-oriented programming (OOPS) principles with focus on modular, scalable, and maintainable architecture Experience designing and implementing object-based data models and working with object-oriented / NoSQL / distributed databases for trade, position, pricing, and risk data Hands-on experience building front-office trade capture systems (Repo, TRS, SFT), including real-time trade ingestion, validation, enrichment, and processing Strong understanding of system integration patterns including APIs, messaging, and event-driven architectures across FO, Risk, Finance, and Ops systems Experience implementing data quality controls, reconciliation frameworks, auditability, and lineage for downstream Risk, PL, and Finance accuracy Prior experience within GFF / FICC environments, with understanding of products, workflows, and operating models Experience building high-performance, low-latency systems with focus on scalability, concurrency, caching, and distributed processing Strong architectural and design skills with ability to build extensible, reusable, and loosely coupled systems Ability to translate business requirements from Trading, Risk, and Operations into scalable technical solutions Strong focus on automated testing (unit, integration, regression) and CI/CD pipeline implementation Experience with large-scale platform buildouts, modernization, or re-platforming initiatives in active trading environments" We need to turn that into list items. Each sentence separated by period. We'll split. Skills: list of skills separated by commas. We'll output as

• each skill. Benefits: list: medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan. We'll output each as
• . Pay: salary range: $57.78 - 67.78 per hour. Schedule: work hours: 8am to 5pm. Location and job type and education: maybe we can include in About the role or a separate section? There's no heading for location etc. Could be included in About the role paragraph. But we have no specific heading for location; we could add a short

  after About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include location, job type, education in a short paragraph maybe under About the role or separate

  without heading. But we must only output sections when there is real specific content; we can have a

  for metadata. Better: After About the role

  About the role

  ... job summary ...

  Location: Jersey City, New Jersey; Job type: Contract; Education: Bachelors

  but we should avoid adding extra markup like strong? Not prohibited. But we should keep simple. Alternatively we could incorporate location etc into About the role paragraph. Let's craft About the role paragraph: combine job summary plus location, job type, education? Might be too long but okay. But we need to avoid duplication: The job summary already includes responsibilities; we can keep that as About the role. Then we can have a separate

  for location, job type, education. Now Responsibilities: list items. Qualifications: list items. Skills: list items. Benefits: list items. Pay:

  Pay

  $57.78 - 67.78 per hour

  Schedule:

  Schedule

  8am to 5pm

  Now ensure we don't include empty sections. Let's extract responsibilities items: - Degrees in any of the following: Computer Science, Computational Finance, Financial Mathematics, Applied Mathematics / Statistics, Financial Engineering - Responsible for designing and building scalable, low-latency Python-based systems supporting front-office Short End Trading front to back systems - Ensures robust handling of trade lifecycle, validation, and downstream system integration (Risk, Finance, Ops) - Implements strong engineering practices to prevent data inconsistencies, trade capture errors, and lifecycle breaks - Addresses scalability challenges through well-architected services, efficient data models, and event-driven design - Acts as a key engineering link across Trading, Risk, Finance, and technology teams ensuring seamless data flow and system integration - Enables high-quality, predictable delivery supporting GFF growth, faster product onboarding, and reduced execution risk Note the first item about degrees may be more of a qualification but it's under Responsibilities; we keep as is. Now Qualifications items: split sentences. Let's list: - Python / ReactJS / Functional Programming - Strong domain expertise in Global Markets, with deep understanding of trade lifecycle including capture, margining, collateral management, lifecycle events, and settlement flows - Proven hands-on experience in end-to-end development using Python, covering design, development, testing, deployment, and production support - Strong application of object-oriented programming (OOPS) principles with focus on modular, scalable, and maintainable architecture - Experience designing and implementing object-based data models and working with object-oriented / NoSQL / distributed databases for trade, position, pricing, and risk data - Hands-on experience building front-office trade capture systems (Repo, TRS, SFT), including real-time trade ingestion, validation, enrichment, and processing - Strong understanding of system integration patterns including APIs, messaging, and event-driven architectures across FO, Risk, Finance, and Ops systems - Experience implementing data quality controls, reconciliation frameworks, auditability, and lineage for downstream Risk, PL, and Finance accuracy - Prior experience within GFF / FICC environments, with understanding of products, workflows, and operating models - Experience building high-performance, low-latency systems with focus on scalability, concurrency, caching, and distributed processing - Strong architectural and design skills with ability to build extensible, reusable, and loosely coupled systems - Ability to translate business requirements from Trading, Risk, and Operations into scalable technical solutions - Strong focus on automated testing (unit, integration, regression) and CI/CD pipeline implementation - Experience with large-scale platform build