David Aplin Group, one of Canada's Best Managed Companies, has partnered with our client to recruit Junior Software Developers. New graduates or soon-to-graduate students are encouraged to apply! Our client is looking for Junior Software Developers to join their growing team. This position is responsible for the development, evaluation, implementation, and maintenance of new software solutions, including maintenance and development of existing applications. Applications involve data collection, data storage, machine learning, and data visualization. The Role: Designing, coding, and debugging software applications using front-end frameworks and enterprise applications - front-end, back-end, and full-stack development. Performing software analysis, code analysis, requirements analysis, software reviews, identification of code metrics, system risk analysis, software reliability analysis. Providing assistance with installations, system configuration, and third-party system integrations. Providing team members and clients with support and guidance. The Ideal Candidate: A Bachelor's degree or Diploma in Computer Science, Computer Engineering, Information Technology, or a similar field. Experience working with coding languages C#, JavaScript, Angular, React, Python, PHP jQuery, JSON, and Ajax. Solid understanding of web design and development principles. Good planning, analytical, and decision-making skills. A portfolio of web design, applications, and projects you have worked on including projects published on GitHub. Critical-thinking skills. In-depth knowledge of software prototyping and UX design tools. High personal code/development standards (peer testing, unit testing, documentation, etc). Team spirit and a sense of humour are always great. Goal-orientated and deadline-driven. COVID-19 considerations: All employees are currently working from home. Any equipment or materials required for work will be provided by the company via shipment to the employee's home. Company policy will continue to evolve through the COVID-19 pandemic and implement alternative working arrangements to ensure that all our people stay safe. If you are interested in this position and meet the above criteria, please send your resume in confidence directly to Jim Juacalla or Ron Cantiveros at Aplin Information Technology, A Division of David Aplin Group. We thank all applicants; however, only those selected for an interview will be contacted. Apply: https://jobs.aplin.com/job/409253/Junior-Software-Developers-New-Graduates

Portfolio | AI-first engineering: test automation, MCP/LLM validation, Playwright, TypeScript, Python

Personal portfolio showcasing automation projects, AI testing tools, and software engineering work.

# Unit 10 OOP Homework: Template Engine - Employee Summary One of the most important aspects of programming is writing code that is readable, reliable, and maintainable. Oftentimes, *how* we design our code is just as important as the code itself. In this homework assignment, your challenge is to build a Node CLI that takes in information about employees and generates an HTML webpage that displays summaries for each person. Since testing is a key piece in making code maintainable, you will also be ensuring that all unit tests pass. ## Instructions You will build a software engineering team generator command line application. The application will prompt the user for information about the team manager and then information about the team members. The user can input any number of team members, and they may be a mix of engineers and interns. This assignment must also pass all unit tests. When the user has completed building the team, the application will create an HTML file that displays a nicely formatted team roster based on the information provided by the user. Following the [common templates for user stories](https://en.wikipedia.org/wiki/User_story#Common_templates), we can frame this challenge as follows: ``` As a manager I want to generate a webpage that displays my team's basic info so that I have quick access to emails and GitHub profiles ``` How do you deliver this? Here are some guidelines: * Use the [Inquirer npm package](https://github.com/SBoudrias/Inquirer.js/) to prompt the user for their email, id, and specific information based on their role with the company. For instance, an intern may provide their school, whereas an engineer may provide their GitHub username. * Your app will run as a Node CLI to gather information about each employee. * Below is an example of what your application may look like. Remember, the styling is completely up to you so try to make it unique.   In the `Develop` folder, there is a `package.json`, so make sure to `npm install`. The dependencies are, [jest](https://jestjs.io/) for running the provided tests, and [inquirer](https://www.npmjs.com/package/inquirer) for collecting input from the user. There are also unit tests to help you build the classes necessary. It is recommended that you follow this workflow: 1. Run tests 2. Create or update classes to pass a single test case 3. Repeat 🎗 Remember, you can run the tests at any time with `npm run test` It is recommended that you start with a directory structure that looks like this: ``` lib/ // classes and helper code output/ // rendered output templates/ // HTML template(s) test/ // jest tests Employee.test.js Engineer.test.js Intern.test.js Manager.test.js app.js // Runs the application ``` ### Hints * Create multiple HTML templates for each type of user. For example, you could use the following templates: * `main.html` * `engineer.html` * `intern.html` * `manager.html` * You will want to make your methods as pure as possible. This means try to make your methods simple so that they are easier to test. * The different employee types should all inherit some methods and properties from a base class of `Employee`. * In your HTML template files, you may want to add a placeholder character that helps your program identify where the dynamic markup begins and ends. ## Minimum Requirements * Functional application. * GitHub repository with a unique name and a README describing the project. * User can use the CLI to generate an HTML page that displays information about their team. * All tests must pass. ### Classes The project must have the these classes: `Employee`, `Manager`, `Engineer`, `Intern`. The tests for these classes in the `tests` directory must all pass. The first class is an `Employee` parent class with the following properties and methods: * name * id * email * getName() * getId() * getEmail() * getRole() // Returns 'Employee' The other three classes will extend `Employee`. In addition to `Employee`'s properties and methods, `Manager` will also have: * officeNumber * getOfficeNumber() * getRole() // Overridden to return 'Manager' In addition to `Employee`'s properties and methods, `Engineer` will also have: * github // GitHub username * getGithub() * getRole() // Overridden to return 'Engineer' In addition to `Employee`'s properties and methods, `Intern` will also have: * school * getSchool() * getRole() // Overridden to return 'Intern' ### User input The project must prompt the user to build an engineering team. An engineering team consists of a manager, and any number of engineers and interns. ### Roster output The project must generate a `team.html` page in the `output` directory, that displays a nicely formatted team roster. Each team member should display the following in no particular order: * Name * Role * ID * Role-specific property (School, link to GitHub profile, or office number) ## Bonus * Use validation to ensure that the information provided is in the proper expected format. * Add the application to your portfolio. ## Commit Early and Often One of the most important skills to master as a web developer is version control. Building the habit of committing via Git is important for two reasons: * Your commit history is a signal to employers that you are actively working on projects and learning new skills. * Your commit history allows you to revert your codebase in the event that you need to return to a previous state. Follow these guidelines for committing: * Make single-purpose commits for related changes to ensure a clean, manageable history. If you are fixing two issues, make two commits. * Write descriptive, meaningful commit messages so that you and anyone else looking at your repository can easily understand its history. * Don't commit half-done work, for the sake of your collaborators (and your future self!). * Test your application before you commit to ensure functionality at every step in the development process. We would like you to have well over 200 commits by graduation, so commit early and often! ## Submission on BCS You are required to submit the following: * The URL of the GitHub repository * A video demonstrating the entirety of the app's functionality - - - © 2019 Trilogy Education Services, a 2U, Inc. brand. All Rights Reserved.

QA Engineering Portfolio | Test Automation | Exploratory Testing | API | Performance | Cypress | Playwright | Selenium

AI quality testing, bug discovery and prompt engineering portfolio - Julian Cutini

pavlok api testing... possibly going to be used in my engineering portfolio

Automated Sandbox Infrastructure Testing for AI Agent Workflows. Portfolio-grade cloud engineering project.

Independent mechanical & aerospace rocketry engineering portfolio featuring rocket design, CAD, flight testing, and applied physics.

A comprehensive portfolio showcasing cybersecurity projects, including penetration testing, malware analysis, SOC operations, and security engineering.

A massive consolidated portfolio of diverse software engineering projects and unit tests from the fourth-year curriculum.

test-orbit-ai is a personal portfolio repository that showcases my hands-on exploration of AI-driven testing, quality engineering, and automation.

A structured QA portfolio showcasing test plans, bug reports, automation scripts & projects. Built to pursue excellence in software quality engineering.

Portfolio of QA Engineering projects completed in the TripleTen Bootcamp, showcasing manual, API, database, mobile, and automated testing with Python + Selenium.

Cloud & DevOps CI pipeline project demonstrating GitHub Actions automation, Node.js testing, and production‑ready workflow design. Built as part of a multi‑cloud engineering portfolio

A professional portfolio built with React and Vite, showcasing my skills and projects from the Multiverse software engineering apprenticeship. Features a dynamic 3D starfield background using React Three Fiber and a full suite of tests with Vitest.

A curated portfolio of practical prompt engineering experiments focused on LLM evaluation, security testing, and advanced prompting techniques. Includes examples of jailbreak resistance, few‑shot prompting, chain‑of‑thought reasoning, and structured output refinement, documented with goals, prompts, outputs, and analysis

Official personal portfolio of Mujahid Hasan — Cyber Security Engineering student from Bangladesh. Includes projects, labs, CTF writeups, ethical hacking practice, Windows AD lab work, networking notes, and study resources. Designed to showcase my skills in cybersecurity, penetration testing, data science, and programming.

Retail Inventory is a full-stack portfolio project built with ASP.NET Core (.NET 10), PostgreSQL, and React + TypeScript. It focuses on practical backend engineering patterns: Clean Architecture, CQRS-style reads and writes, JWT auth, API versioning, transactional outbox messaging, Dockerized infrastructure, and automated testing.

Explore my professional journey through this portfolio showcasing past projects, skills, and current developments in software engineering. Initially built using the MERN stack for development/testing, it has been transitioned to utilize AWS services, including API Gateway and Lambda functions to fetch data from an S3 bucket.

A structured, master’s-level Computer Science playbook that combines deep concepts, tested implementations, real-world case studies, and flagship projects. This repository is designed to be both: a high-quality educational resource for students and professionals, and a proof-of-work portfolio demonstrating real engineering and AI capability.

"DoNotWaste" is a project developed for a Computer and Electronic Engineering degree. Using ASP.NET MVC, it compares energy benchmarking and optimization tools to aid users in selecting the best one. It integrates with ENERGY STAR Portfolio Manager Test Environment API for accurate data analysis, ensuring informed decision-making.

Welcome to my GitHub portfolio, showcasing the distinguished career of Mr. Ravi Prakash, a seasoned Performance Specialist and Engineer with over 7+ YOE. Explore my elite performance engineering work. 6.5+ years expertise in Performance Testing, DevOps, AWS. Proven track record, award-winning author. Elevate your projects with my contributions.

No description available

A curated QE/SDET toolkit: test agents, Playwright (Python) automation patterns, scaffolding, and case-study artifacts focused on reliability, observability, and testability.

Portfolio about Software Engineering Test

Production-style SDET portfolio showcasing UI, API, and CI test engineering

Practical QA portfolio for MLB Technology Internship: test design, automation and quality practices using MLB.com as a real-world web application.

Product & Test Engineering skills using Python for quality and yield analysis.

Test portfolio website for platform engineering