Engineering Trainee - US
BBI · Schaumburg, IL · 4 wk ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Blackbuck Insights (BBI) (company description), The Role, Eligibility Criteria, Requirements, Responsibilities, Good To Have, Why Join BBI? Also location, experience, qualification, employment type maybe as metadata.
We must use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
We must preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them.
We have no explicit Pay, Benefits, Schedule details. The posting mentions "Willingness to work 5 days a week from our Schaumburg office location." That's schedule info? It says 5 days work-from-office. That's schedule: 5 days a week in office. Could we create a Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state willingness to work 5 days a week from Schaumburg office location. That's schedule info. So we could include a Schedule section with that detail. However the rule says "Prefer a few substantive sections over many thin ones." Might combine location and schedule into a short paragraph.
We also have no explicit Benefits or Pay. So we should not create those sections.
We need sections: About the company? Could be "About Blackbuck Insights (BBI)" maybe as a section heading? The allowed headings list includes "About the role" but not "About the company". However we can still use
for any section heading; the examples are not exclusive. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples but we can use other headings as needed. Probably okay to use "About Blackbuck Insights (BBI)" as heading.
We also have "Eligibility Criteria" which could be Qualifications. Use "Qualifications" heading.
We have "Requirements" heading.
We have "Responsibilities" heading.
We have "Good To Have" maybe as "Skills" or "Preferred Qualifications". Could use "Skills" heading.
We have "Why Join BBI?" maybe as "Benefits"? But it's not benefits; it's reasons to join. Could be a section like "Why Join BBI?" but not in list. Might still be okay.
We need to avoid duplication: The eligibility criteria repeats requirements; we should preserve all info but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all info, but we can combine similar info if it's same? Might be okay to keep both but avoid duplicate lines. The eligibility criteria and requirements have overlapping content. We could merge them under Qualifications and Requirements sections, but ensure we don't lose any unique points.
Let's extract content:
Location: Schaumburg (5 days’ work-from-office)
Experience: Freshers (2025 - 2026 batch)
Qualification: UG/PG (CS/IT or related fields)
Employment Type: Full-time
About Blackbuck Insights (BBI): description.
The Role: description.
Eligibility Criteria:
- Qualification: UG/PG in Computer Science, IT, or related technical disciplines.
- Batch: 2025 & 2026 graduates.
- Academic Score: Minimum CGPA 3.0 (no backlogs).
- Candidates must be legally authorized to work in the United States
Requirements (list):
- 2025 and 2026 Undergraduates or Postgraduates in Computer Science, Information Technology, or related technical disciplines.
- Minimum aggregate of CGPA 3.0 in graduation/post-graduation.
- Sound programming skills in Python, Java, C/C++, or SQL, with hands-on coding experience.
- Solid understanding of core Computer Science fundamentals: object-oriented design and analysis (OOA/OOD), algorithm design, data structures, debugging, and analytical reasoning.
- Passion for software development best practices, clean code, and developing innovative ideas.
- Interest, curiosity, and openness to learning modern data stack tools and AI frameworks on the fly.
- Demonstrable track record of handling ambiguous or undefined problems, prioritizing tasks, thinking abstractly, and delivering results in a dynamic environment.
- Ability to work independently and multi-task effectively under performance-driven conditions.
- Excellent verbal, written, and interpersonal communication skills to effectively articulate technical challenges and solutions to both business and engineering stakeholders.
- Proficiency with MS Office tools and developer productivity suites.
- Willingness to work 5 days a week from our Schaumburg office location.
Responsibilities (list):
- Involvement across the full software and data development lifecycle - including requirements gathering, system architecture, coding, testing, documentation, deployment, ongoing optimization, and maintenance for both internal initiatives and global client engagements.
- Gain hands-on exposure to Large Language Models (LLMs), prompt engineering, fine-tuning concepts, and LLM orchestration tools.
- Assist in designing and deploying autonomous AI agents and multi-agent workflows to automate enterprise processes.
- Adhere to AI safety guidelines, ethical AI practices, data privacy controls, and token/compute cost optimization (FinOps).
- Execute full lifecycle application development, translating functional specifications into robust technical designs and well-architected code.
- Perform software analysis, requirements analysis, system risk evaluations, code metrics identification, and software reliability testing.
- Integrate software components, third-party APIs, and application modules into fully functional enterprise systems.
- Develop software verification plans, quality assurance procedures, system layouts, flowcharts, and technical documentation.
- Investigate, debug, and resolve issues in production and application environments.
- Participate in specification and peer code reviews to ensure alignment with architectural guidelines, security benchmarks, and quality standards.
- Collaborate in agile teams, provide project status updates, and continuously adapt to shifting project priorities in high-pressure scenarios.
- Help build and maintain scalable, fault-tolerant, low-cost distributed storage, indexing, and query structures across modern cloud lakehouse frameworks.
- Develop, test, and schedule automated data transformation pipelines and ETL/ELT workflows to process structured and unstructured data at scale.
- Maintain high engineering standards including clean, modular, and self-sustaining code, unit testing, continuous integration/continuous deployment (CI/CD), version control, and release management.
Good To Have (list):
- Previous technical internship experience in software development, data engineering, or AI/ML domains.
- Industry certifications in Python, Java, SQL, Database Management Systems Cloud Platforms or Data/AI Engineering.
Why Join BBI? (list):
- Mentor to guide your deliverables, provide feedback, and accelerate your growth.
- Work with modern Cloud, Data Analytics, and Agentic AI platforms.
- Collaborative, fast-paced, and innovation-driven environment with measurable business impact.
- Real-world project ownership and continuous learning opportunities from day one.
We also have location and schedule: "Willingness to work 5 days a week from our Schaumburg office location." Already in Requirements list. Could also note location separately.
We need to avoid duplication: The eligibility criteria and requirements have overlapping points (qualification, batch, CGPA, work authorization). We could keep both but maybe combine under Qualifications and Requirements sections, ensuring we don't repeat same sentences verbatim. However the instruction says preserve ALL substantive information; we could keep both sections but ensure we don't duplicate identical sentences. The eligibility criteria includes "Candidates must be legally authorized to work in the United States" which is not in requirements list. The requirements list includes "Willingness to work 5 days a week from our Schaumburg office location." Not in eligibility. So we can keep both sections but avoid repeating identical lines.
Eligibility Criteria list:
- Qualification: UG/PG in Computer Science, IT, or related technical disciplines.
- Batch: 2025 & 2026 graduates.
- Academic Score: Minimum CGPA 3.0 (no backlogs).
- Candidates must be legally authorized to work in the United States
Requirements list includes many items, some overlapping: first two items repeat qualification and batch and CGPA. We could keep them but maybe we should deduplicate: The requirement list includes "2025 and 2026 Undergraduates or Postgraduates in Computer Science, Information Technology, or related technical disciplines." and "Minimum aggregate of CGPA 3.0 in graduation/post-graduation." That's essentially same as eligibility. To avoid duplication, we could keep them but note they are same; but instruction says preserve ALL substantive information, not necessarily avoid duplication. However earlier they said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to eliminate duplicate lines that appear multiple times. So we should keep only one copy of each unique piece of information.
Thus we need to merge eligibility and requirements, removing duplicates.
Let's list unique items:
From eligibility:
- Qualification: UG/PG in Computer Science, IT, or related technical disciplines.
- Batch: 2025 & 2026 graduates.
- Academic Score: Minimum CGPA 3.0 (no backlogs).
- Candidates must be legally authorized to work in the United States.
From requirements (excluding duplicates):
- Sound programming skills in Python, Java, C/C++, or SQL, with hands-on coding experience.
- Solid understanding of core Computer Science fundamentals: object-oriented design and analysis (OOA/OOD), algorithm design, data structures, debugging, and analytical reasoning.
- Passion for software development best practices, clean code, and developing innovative ideas.
- Interest, curiosity, and openness to learning modern data stack tools and AI frameworks on the fly.
- Demonstrable track record of handling ambiguous or undefined problems, prioritizing tasks, thinking abstractly, and delivering results in a dynamic environment.
- Ability to work independently and multi-task effectively under performance-driven conditions.
- Excellent verbal, written, and interpersonal communication skills to effectively articulate technical challenges and solutions to both business and engineering stakeholders.
- Proficiency with MS Office tools and developer productivity suites.
- Willingness to work 5 days a week from our Schaumburg office location.
Also note that "Minimum aggregate of CGPA 3.0 in graduation/post-graduation." is duplicate of eligibility academic score; we already have that.
Now responsibilities list as given.
Good To Have list as given.
Why Join BBI list as given.
Now we need sections: maybe "About the Company", "About the Role", "Qualifications", "Responsibilities", "Preferred Skills" (Good To Have), "Why Join BBI?".
We also need to include location and schedule info; we already have willingness to work 5 days a week from Schaumburg office location under Qualifications (or Requirements). Could also add a short paragraph about location.
We must not create Pay/Benefits sections unless stated. Not present.
We must not create Schedule section unless stated; we have schedule info in the willingness line; but we could keep it within Qualifications.
Now produce HTML.
Structure:
About Blackbuck Insights (BBI)
Headquartered in Schaumburg, Illinois with offices across India and Canada, BBI is a technology consulting firm that helps enterprises modernize data ecosystems and accelerate digital transformation through Data Engineering,
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. We must preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. We have no explicit Pay, Benefits, Schedule details. The posting mentions "Willingness to work 5 days a week from our Schaumburg office location." That's schedule info? It says 5 days work-from-office. That's schedule: 5 days a week in office. Could we create a Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state willingness to work 5 days a week from Schaumburg office location. That's schedule info. So we could include a Schedule section with that detail. However the rule says "Prefer a few substantive sections over many thin ones." Might combine location and schedule into a short paragraph. We also have no explicit Benefits or Pay. So we should not create those sections. We need sections: About the company? Could be "About Blackbuck Insights (BBI)" maybe as a section heading? The allowed headings list includes "About the role" but not "About the company". However we can still use
for any section heading; the examples are not exclusive. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples but we can use other headings as needed. Probably okay to use "About Blackbuck Insights (BBI)" as heading.
We also have "Eligibility Criteria" which could be Qualifications. Use "Qualifications" heading.
We have "Requirements" heading.
We have "Responsibilities" heading.
We have "Good To Have" maybe as "Skills" or "Preferred Qualifications". Could use "Skills" heading.
We have "Why Join BBI?" maybe as "Benefits"? But it's not benefits; it's reasons to join. Could be a section like "Why Join BBI?" but not in list. Might still be okay.
We need to avoid duplication: The eligibility criteria repeats requirements; we should preserve all info but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all info, but we can combine similar info if it's same? Might be okay to keep both but avoid duplicate lines. The eligibility criteria and requirements have overlapping content. We could merge them under Qualifications and Requirements sections, but ensure we don't lose any unique points.
Let's extract content:
Location: Schaumburg (5 days’ work-from-office)
Experience: Freshers (2025 - 2026 batch)
Qualification: UG/PG (CS/IT or related fields)
Employment Type: Full-time
About Blackbuck Insights (BBI): description.
The Role: description.
Eligibility Criteria:
- Qualification: UG/PG in Computer Science, IT, or related technical disciplines.
- Batch: 2025 & 2026 graduates.
- Academic Score: Minimum CGPA 3.0 (no backlogs).
- Candidates must be legally authorized to work in the United States
Requirements (list):
- 2025 and 2026 Undergraduates or Postgraduates in Computer Science, Information Technology, or related technical disciplines.
- Minimum aggregate of CGPA 3.0 in graduation/post-graduation.
- Sound programming skills in Python, Java, C/C++, or SQL, with hands-on coding experience.
- Solid understanding of core Computer Science fundamentals: object-oriented design and analysis (OOA/OOD), algorithm design, data structures, debugging, and analytical reasoning.
- Passion for software development best practices, clean code, and developing innovative ideas.
- Interest, curiosity, and openness to learning modern data stack tools and AI frameworks on the fly.
- Demonstrable track record of handling ambiguous or undefined problems, prioritizing tasks, thinking abstractly, and delivering results in a dynamic environment.
- Ability to work independently and multi-task effectively under performance-driven conditions.
- Excellent verbal, written, and interpersonal communication skills to effectively articulate technical challenges and solutions to both business and engineering stakeholders.
- Proficiency with MS Office tools and developer productivity suites.
- Willingness to work 5 days a week from our Schaumburg office location.
Responsibilities (list):
- Involvement across the full software and data development lifecycle - including requirements gathering, system architecture, coding, testing, documentation, deployment, ongoing optimization, and maintenance for both internal initiatives and global client engagements.
- Gain hands-on exposure to Large Language Models (LLMs), prompt engineering, fine-tuning concepts, and LLM orchestration tools.
- Assist in designing and deploying autonomous AI agents and multi-agent workflows to automate enterprise processes.
- Adhere to AI safety guidelines, ethical AI practices, data privacy controls, and token/compute cost optimization (FinOps).
- Execute full lifecycle application development, translating functional specifications into robust technical designs and well-architected code.
- Perform software analysis, requirements analysis, system risk evaluations, code metrics identification, and software reliability testing.
- Integrate software components, third-party APIs, and application modules into fully functional enterprise systems.
- Develop software verification plans, quality assurance procedures, system layouts, flowcharts, and technical documentation.
- Investigate, debug, and resolve issues in production and application environments.
- Participate in specification and peer code reviews to ensure alignment with architectural guidelines, security benchmarks, and quality standards.
- Collaborate in agile teams, provide project status updates, and continuously adapt to shifting project priorities in high-pressure scenarios.
- Help build and maintain scalable, fault-tolerant, low-cost distributed storage, indexing, and query structures across modern cloud lakehouse frameworks.
- Develop, test, and schedule automated data transformation pipelines and ETL/ELT workflows to process structured and unstructured data at scale.
- Maintain high engineering standards including clean, modular, and self-sustaining code, unit testing, continuous integration/continuous deployment (CI/CD), version control, and release management.
Good To Have (list):
- Previous technical internship experience in software development, data engineering, or AI/ML domains.
- Industry certifications in Python, Java, SQL, Database Management Systems Cloud Platforms or Data/AI Engineering.
Why Join BBI? (list):
- Mentor to guide your deliverables, provide feedback, and accelerate your growth.
- Work with modern Cloud, Data Analytics, and Agentic AI platforms.
- Collaborative, fast-paced, and innovation-driven environment with measurable business impact.
- Real-world project ownership and continuous learning opportunities from day one.
We also have location and schedule: "Willingness to work 5 days a week from our Schaumburg office location." Already in Requirements list. Could also note location separately.
We need to avoid duplication: The eligibility criteria and requirements have overlapping points (qualification, batch, CGPA, work authorization). We could keep both but maybe combine under Qualifications and Requirements sections, ensuring we don't repeat same sentences verbatim. However the instruction says preserve ALL substantive information; we could keep both sections but ensure we don't duplicate identical sentences. The eligibility criteria includes "Candidates must be legally authorized to work in the United States" which is not in requirements list. The requirements list includes "Willingness to work 5 days a week from our Schaumburg office location." Not in eligibility. So we can keep both sections but avoid repeating identical lines.
Eligibility Criteria list:
- Qualification: UG/PG in Computer Science, IT, or related technical disciplines.
- Batch: 2025 & 2026 graduates.
- Academic Score: Minimum CGPA 3.0 (no backlogs).
- Candidates must be legally authorized to work in the United States
Requirements list includes many items, some overlapping: first two items repeat qualification and batch and CGPA. We could keep them but maybe we should deduplicate: The requirement list includes "2025 and 2026 Undergraduates or Postgraduates in Computer Science, Information Technology, or related technical disciplines." and "Minimum aggregate of CGPA 3.0 in graduation/post-graduation." That's essentially same as eligibility. To avoid duplication, we could keep them but note they are same; but instruction says preserve ALL substantive information, not necessarily avoid duplication. However earlier they said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to eliminate duplicate lines that appear multiple times. So we should keep only one copy of each unique piece of information.
Thus we need to merge eligibility and requirements, removing duplicates.
Let's list unique items:
From eligibility:
- Qualification: UG/PG in Computer Science, IT, or related technical disciplines.
- Batch: 2025 & 2026 graduates.
- Academic Score: Minimum CGPA 3.0 (no backlogs).
- Candidates must be legally authorized to work in the United States.
From requirements (excluding duplicates):
- Sound programming skills in Python, Java, C/C++, or SQL, with hands-on coding experience.
- Solid understanding of core Computer Science fundamentals: object-oriented design and analysis (OOA/OOD), algorithm design, data structures, debugging, and analytical reasoning.
- Passion for software development best practices, clean code, and developing innovative ideas.
- Interest, curiosity, and openness to learning modern data stack tools and AI frameworks on the fly.
- Demonstrable track record of handling ambiguous or undefined problems, prioritizing tasks, thinking abstractly, and delivering results in a dynamic environment.
- Ability to work independently and multi-task effectively under performance-driven conditions.
- Excellent verbal, written, and interpersonal communication skills to effectively articulate technical challenges and solutions to both business and engineering stakeholders.
- Proficiency with MS Office tools and developer productivity suites.
- Willingness to work 5 days a week from our Schaumburg office location.
Also note that "Minimum aggregate of CGPA 3.0 in graduation/post-graduation." is duplicate of eligibility academic score; we already have that.
Now responsibilities list as given.
Good To Have list as given.
Why Join BBI list as given.
Now we need sections: maybe "About the Company", "About the Role", "Qualifications", "Responsibilities", "Preferred Skills" (Good To Have), "Why Join BBI?".
We also need to include location and schedule info; we already have willingness to work 5 days a week from Schaumburg office location under Qualifications (or Requirements). Could also add a short paragraph about location.
We must not create Pay/Benefits sections unless stated. Not present.
We must not create Schedule section unless stated; we have schedule info in the willingness line; but we could keep it within Qualifications.
Now produce HTML.
Structure:
About Blackbuck Insights (BBI)
About Blackbuck Insights (BBI)
Headquartered in Schaumburg, Illinois with offices across India and Canada, BBI is a technology consulting firm that helps enterprises modernize data ecosystems and accelerate digital transformation through Data Engineering,