Jobs · New Jersey

Java Full Stack Developer-Software Engineer III

Deloitte · Jersey City, NJ · 3 wk ago
HybridFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "Are you an experienced, passionate pioneer in technology who wants to work in a collaborative environment? As an experienced Software Engineer III - Java Full Stack Developer you will have the ability to share new ideas and collaborate on projects as a consultant without the extensive demands of travel. If so, consider an opportunity with Deloitte under our Project Delivery Talent Model. Project Delivery Model (PDM) is a talent model that is tailored specifically for long-term, onsite client service delivery." That's about the role. So we can have

About the role

with

containing that text. - Responsibilities: The "Work You'll Do/Responsibilities" section: list of duties. We'll extract bullet points. Let's list them: "Join our AI and Systems Co-Design team, pioneering high-performance software and hardware technologies for AI and next-generation consumer devices. As a Consultant, you'll help design, build, and optimize foundational tools and applications that power cutting-edge AI platforms and smart devices. You'll collaborate cross-functionally, tackle large-scale technical challenges, and deliver innovative solutions with global impact. Design, build, and maintain backend services using Java, Spring Boot, Kafka, MongoDB, and MSSQL. Develop scalable, high-performance APIs and event-driven components for market technology applications. Write efficient multithreaded Java code and troubleshoot performance, concurrency, and reliability issues. Create and optimize database queries, stored procedures, and data access patterns in MSSQL and MongoDB. Support integration and message-driven workflows using Kafka and related event-processing patterns. Collaborate with product, architecture, QA, and DevOps teams to deliver secure, stable, and production-ready solutions. Participate in code reviews, technical design discussions, sprint ceremonies, and production support as needed. Identify root causes of defects, implement fixes, and improve application stability and maintainability. Follow engineering best practices for coding standards, testing, deployment, and documentation. Communicate regularly with Engagement Managers (Directors), project team members, and representatives from various functional and / or technical teams, including escalating any matters that require additional attention and consideration from engagement management Independently and collaboratively lead client engagement workstreams focused on improvement, optimization, and transformation of processes including implementing leading practice workflows, addressing deficits in quality, and driving operational outcomes" We need to put these as

  • items. - Requirements: The posting says "The successful candidate would possess these skills:" then a list of abilities. That could be considered Skills or Requirements. But we have separate sections for Requirements, Qualifications, Skills. The posting also has "Qualifications Required" list. Thus we need to separate: Qualifications Required: list of required qualifications (experience years etc). That's a list. Skills: The list after "The successful candidate would possess these skills:" includes abilities like ability to work independently, communication, attention to detail, etc. Requirements: Might be the same as Qualifications? Usually Requirements are like mandatory qualifications. But we have both sections; we can put the "Qualifications Required" under Qualifications, and the skill list under Skills. For Requirements maybe we can include something like "Ability to travel 10%"? That's a requirement but it's minor metadata; we could fold into a short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Travel 10% is minor metadata; we could include in a short p under About the role or maybe not include a separate section. We need to decide: include Requirements section only if there is real specific content not covered elsewhere. The posting includes "Limited immigration sponsorship may be available" and "Ability to travel 10%, on average". Those could be considered requirements but they are minor. We could include them in a short p under About the role or maybe under a "Requirements" section if we want. But we need to avoid thin sections. Better to fold them into About the role paragraph. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills. Possibly Benefits, Pay, Schedule: none provided, so omit. Now we need to preserve all substantive information. Let's extract qualifications list: "Qualifications Required 6+ years of experience in software, systems, or embedded engineering. 6+ years of experience working Java/J2EE, Core Java, and multithreading 6+ years of experience developing or deploying AI solutions, custom hardware, or high-performance platforms. 6+ years of experience with Springboot Strong expertise in MSSQL, including complex queries and stored procedures. Intermediate experience with Kafka or other event-driven messaging platforms. Experience building backend services in a scalable enterprise environmen Experience with Git, CI/CD pipelines, and modern DevOps practices. Experience working within Agile/Scrum development teams, participating in sprint planning, code reviews, and collaborative solutioning. Bachelor's degree, preferably in Computer Science, Information Technology, Computer Engineering, or related IT discipline; or equivalent experience Limited immigration sponsorship may be available Ability to travel 10%, on average, based on the work you do and the clients and industries/sectors you serve" We need to keep all. Note there is a typo: "environmen" missing 't' but we keep as is. Now Skills list: after "The successful candidate would possess these skills:" we have bullet-like sentences separated by line breaks? Let's extract: Ability to work independently and collaborate as part of a team Effective written and verbal communication skills Meticulous attention to detail and quality of work product Ability to build and sustain professional relationships Ability to lead projects or workstreams Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment Strong interpersonal skills and professional demeanor Ability to meet deadlines Ability to provide clear guidance to others Also later under "Preferred Experience" there are more: "Experience developing or deploying AI solutions, custom hardware, or high-performance platforms." (but that's already in qualifications). "Proven ability to communicate complex technical concepts clearly and effectively." "Analytical ability to manage multiple projects and prioritize tasks into manageable work products" "Can operate independently or with minimum supervision" "Excellent Written and Communication Skills" "Ability to deliver technical demonstrations" We need to preserve all substantive info; we can include these under Skills as well (maybe combine). The "Preferred Experience" could be considered Skills or Qualifications but we can add to Skills. Thus Skills section will contain all ability statements. Now About the role paragraph: we need to include the initial sentences plus maybe the description of PDM. Also maybe include the team description? The "The Team AI & Engineering leverages..." paragraph could be part of About the role or maybe a separate section like "About the team". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put team description under About the role as well. Thus About the role paragraph will combine: - Opening sentence about experienced pioneer. - Description of role as Software Engineer III - Java Full Stack Developer, consultant, etc. - Opportunity with Deloitte under Project Delivery Talent Model, PDM description. - Team description: "The Team AI & Engineering leverages cutting-edge engineering capabilities..." etc. We need to ensure we don't lose any substantive info. Let's craft About the role paragraph:

    Are you an experienced, passionate pioneer in technology who wants to work in a collaborative environment? As an experienced Software Engineer III - Java Full Stack Developer you will have the ability to share new ideas and collaborate on projects as a consultant without the extensive demands of travel. If so, consider an opportunity with Deloitte under our Project Delivery Talent Model. Project Delivery Model (PDM) is a talent model that is tailored specifically for long-term, onsite client service delivery. Join our AI and Systems Co-Design team, pioneering high-performance software and hardware technologies for AI and next-generation consumer devices. As a Consultant, you'll help design, build, and optimize foundational tools and applications that power cutting-edge AI platforms and smart devices. You'll collaborate cross-functionally, tackle large-scale technical challenges, and deliver innovative solutions with global impact. The Team AI & Engineering leverages cutting-edge engineering capabilities to build, deploy, and operate integrated/verticalized sector solutions in software, data, AI, network, and hybrid cloud infrastructure. These solutions are powered by engineering for business advantage, transforming mission-critical operations. We enable clients to stay ahead with the latest advancements by transforming engineering teams and modernizing technology & data platforms. Our delivery models are tailored to meet each client's unique requirements.

    But note some of that text is actually from Responsibilities and Team sections; we might be duplicating. We need to preserve all info but not duplicate unnecessarily? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should avoid repeating same content in multiple sections if possible. However, we need to ensure each piece appears at least once. We can allocate each piece to appropriate section. Better to keep About the role short: just the introductory paragraph about role and PDM. Then Responsibilities includes the detailed duties. Then Team description could be part of About the role or maybe a separate section like "About the team" but not allowed. Could fold into About the role as well. Thus we need to decide where each sentence goes. Let's list all substantive sentences from the posting: 1. Are you an experienced, passionate pioneer in technology who wants to work in a collaborative environment? 2. As an experienced Software Engineer III - Java Full Stack Developer you will have the ability to share new ideas and collaborate on projects as a consultant without the extensive demands of travel. 3. If so, consider an opportunity with Deloitte under our Project Delivery Talent Model. 4. Project Delivery Model (PDM) is a talent model that is tailored specifically for long-term, onsite client service delivery. 5. Join our AI and Systems Co-Design team, pioneering high-performance software and hardware technologies for AI and next-generation consumer devices. 6. As a Consultant, you'll help design, build, and optimize foundational tools and applications that power cutting-edge AI platforms and smart devices. 7. You'll collaborate cross-functionally, tackle large-scale technical challenges, and deliver innovative solutions with global impact. 8. Design, build, and maintain backend services using Java, Spring Boot, Kafka, MongoDB, and MSSQL. 9. Develop scalable, high-performance APIs and event-driven components for market technology applications. 10. Write efficient multithreaded Java code and troubleshoot performance, concurrency, and reliability issues. 11. Create and optimize database queries, stored procedures, and data access patterns in MSSQL and MongoDB. 12. Support integration and message-driven workflows using Kafka and related event-processing patterns. 13. Collaborate with product, architecture, QA, and DevOps teams to deliver secure, stable, and production-ready solutions. 14. Participate in code reviews, technical design discussions, sprint ceremonies, and production support as needed. 15. Identify root causes of defects, implement fixes, and improve application stability and maintainability. 16. Follow engineering best practices for coding standards, testing, deployment, and documentation. 17. Communicate regularly with Engagement Managers (Directors), project team members, and representatives from various functional and / or technical teams, including escalating any matters that require additional attention and consideration from engagement management 18. Independently and collaboratively lead client engagement workstreams focused on improvement, optimization, and transformation of processes including implementing leading practice workflows, addressing deficits in quality, and driving operational outcomes 19. The successful candidate would possess these skills: 20. Ability to work independently and collaborate as part of a team 21. Effective written and verbal communication skills 22. Meticulous attention to detail and quality of work product 23. Ability

Similar jobs