When the competition is fierce and there are dozens (if not hundreds) of people applying for the same jobs, how do you stand out and catch a recruiter’s eye?

The key is a strong portfolio. A strong portfolio gives hiring managers a sense of who you are and what you can do, with tangible examples of your skills and expertise. Ahead, we’ll go over what you’ll want to include in a Machine Learning Engineer portfolio and how to build projects that’ll help you land a job.

What to include in a Machine Learning Engineer portfolio

A Machine Learning Engineer’s portfolio is similar to any other technical portfolio. You’ll want to include some information about you and your history in the machine learning field. Here are the basics:

Bio

This section allows you to tell recruiters more about who you are — the type of information that may not fit in a technical resume. Consider highlighting your passion for machine learning and explain why you got into the field. You can also include details about your current projects, your tech stack, and where you see yourself in the future.

Contact information

You’ll also want to let hiring managers know how to reach you, so don’t forget to add your name, email address, and phone number at the top of your portfolio. You can also add links to your professional social media accounts — including your LinkedIn, which is one of the primary tools for tech recruiters.

Adding a GitHub link is another good choice. As far as other social media accounts go, that depends. If your Twitter or other social media accounts are machine-learning related, then include them. If they’re more about your personal life, don’t.

Your skills

When it comes to your skills, emphasize those that apply to the type of job you want, but don’t go overboard and make it a huge list. The focus of your portfolio is the projects you include, but listing your skills provides added context.

Some of the top skills for Machine Learning Engineers include:

• Data visualization
• Algorithms and data structures
• Statistical modeling
• Quantitative analysis
• Cloud computing

The type of machine learning projects to include in your portfolio

The type of projects you should include in your portfolio depends on the companies and industries you’re applying for. Try looking through Machine Learning Engineer postings on sites like LinkedIn and Glassdoor. Make a list of a few companies you’d like to work for, and read through their job descriptions to see which skills and technologies they’re looking for in potential candidates.

Then, you can use these insights to create projects that will stand out. It helps to pick a few diverse ones so you can add more variety to your portfolio. You don’t want every project to use the same type of data set or make your skillset look more narrow than it actually is.

Use the job descriptions and your interests to build projects you’re curious about. Then, when you’re designing your projects, keep in mind the following tips:

• Keep it relatively small. Your portfolio should include several projects, so try not to spend too much time on a single one.
• Make it a complete project. You want recruiters to know that you can finish what you start. Don’t include any unfinished projects in your portfolio.
• Choose an interesting topic. Remember, your portfolio also helps show hiring teams who you are as a person, so you’ll want to include projects that exemplify the types of problems you like to solve.
• Use publicly available data sets. Using publicly available data sets is also great for coming up with project ideas. They give people a point of reference for your work, and it’s always better to use real data over toy data when showcasing your skills.

You can also build your portfolio as you learn. Many of our machine learning and data science courses teach you the skills you need while you build projects suitable for a Machine Learning Engineer portfolio. For example:

Where to host your machine learning portfolio

If you already have some web development skills, your own domain, and a hosting provider, then building and hosting your own portfolio site is a great option. But if you don’t, no worries. Most Machine Learning Engineer roles don’t require web dev knowledge.

The next best place to host your machine learning portfolio is GitHub. You can host all the code from your projects there. If you use Jupyter notebooks in your project, Github will automatically render the results of your notebooks, including charts and graphs. And for your bio and other details, you can create a simple ReadMe file in markdown and use Github Pages to turn it into a beautiful web page.

Build your portfolio with us

So now you know you need a portfolio if you plan to have a career in data science, and you know how to build a portfolio that’ll catch a recruiter’s eye. If you’re just getting started in machine learning and haven’t yet finished enough projects to flesh out your portfolio, we can help you out.

Our Data Scientist: Machine Learning Specialist career path will teach you all the skills you’ll need to kick off your career in machine learning. You’ll learn how to use Python and SQL to build machine learning models and manipulate data, and as you complete the course, you’ll build unique projects that you can include in your portfolio.

We can also help you prepare for the hiring process with advice from technical recruiters, interview prep courses, and other helpful resources you can find in our Career Center.

Machine Learning Courses & Tutorials | Codecademy

Machine Learning is an increasingly hot field of data science dedicated to enabling computers to learn from data. From spam filtering in social networks to computer vision for self-driving cars, the potential applications of Machine Learning are vast.

The tech job market is growing, and there are no signs of slowing down. According to the Bureau of Labor Statistics, tech jobs are expected to grow 13% between 2020 and 2030, and over 667,000 new jobs will be created in tech in the next few years. And since Computer Information System Manager roles touch on so many parts of the tech world, there will likely be plenty of opportunities within this field as the industry continues to expand.

A Computer Information Systems Manager is an IT professional who oversees, coordinates, and manages an organization’s computer systems. They understand what type of technology a company needs and implement systems to meet these needs. As is the case for most jobs, your salary in this role will depend on several factors, like your location, the company you work for, and the amount of experience you have.

How much do Computer Information Systems Managers make on average?

According to Indeed, Computer Information Systems Managers in the United States make an average salary of $92,291 a year. But since that number is an average, it’s only a rough idea of what your individual salary might be. Let’s take a look at some factors that will give you a better idea of the range you can expect to make as a Computer Information Systems Manager.

What factors affect the salary of a Computer Information Systems Manager?

Location

Where you live can have a big impact on your salary, even if you’re working remotely. Generally, the cost of living is higher in bigger cities and on the west and east coasts, where managers tend to get paid the most. Sometimes, salaries are higher because there is a significant demand for managers locally. Here are some cities where the pay for Computer Information Systems Managers is currently the highest, according to Indeed:

• Washington, D.C.: $106,907
• San Diego, CA: $98,922
• Alexandria, VA: $98,311
• Philadelphia, PA: $97,454
• Atlanta, GA: $97,076
• Tampa, FL: $91,691
• Fort Worth, TX: $90,864
• Huntsville, AL: $86,794
• San Antonia, TX: $89,749

Experience

Experience is always a factor in your salary, perhaps especially in tech jobs where employers will consider how many years you’ve been working with a specific technology or program. For a job as a Computer Information Systems Manager, the amount of broad experience you have in different facets of computer systems matters as well. After all, depending on the role, a Systems Manager could oversee the work of many technical divisions of a company, only a handful of those divisions, or just one division.

Experience in managing others is definitely crucial, since this is a leadership role. Many Computer Information Systems Managers get the role through a promotion from another management role, like Lead Developer, IT Project Manager, or IT team lead.

As a Computer Information Systems Manager, knowing both how to write software and manage networks — tasks usually handled by separate roles — means that you have the in-depth knowledge to manage people working in separate divisions of a company, thereby maximizing your salary potential.

Job description

The job description can also affect salary, as can the job title. There are many job titles that fit under the umbrella of Computer Information Systems Manager, including:

• Computer and Information Systems Manager
• Information Systems Manager
• Systems Manager
• IT Manager
• IS Director
• IT Security Manager

These jobs are similar. The only difference is the title and the scope of responsibilities. CTOs are also essentially Computer Information Systems Managers — they do the same type of work as the others, just at a higher level where they monitor the newest innovative technologies and create a vision for the entire company’s systems.

In that sense, CTOs occupy the higher range in terms of experience and pay (according to Salary.com, they make an average of $258,676 per year in the U.S.), while a more early or mid-career position like an Information Systems Manager will naturally have a lower salary (an average of $115,477 per year).

Company

Your salary may also depend on the company you work for. For example, some established companies may pay more for developers who they want to retain. Here are some companies currently offering above-average salaries for Computer Information Systems Managers, according to Indeed:

• EY: $298,064
• Accenture: $225,776
• Citi: $214,289
• Apple: $205,029
• Intuitive: $184,688

Becoming a Computer Information Systems Manager

The duties and responsibilities of a Computer Information Systems Manager can vary widely depending on the job title and the size of the company. Some companies may have more than one systems management role, with each manager overseeing a unique part of the company’s technologies. Smaller companies may have only one role.

As we mentioned earlier, a CTO is a Computer Information Systems Manager who has reached the highest level. CTOs direct the technological vision of an entire company. They have to have knowledge of every part of IT, including network management, IT support, software development, cybersecurity, database development, and more.

In a very small company or startup, a CTO may interact with IT support staff, software engineers, and network admins and oversee the work they do directly. As a company gets larger, each IT division will have its own Computer Information Systems Manager who will report to the CTO.

The manager who oversees software engineers may have a title like Software Development Manager or Engineering Manager and have in-depth programming knowledge. The manager who oversees network admins and cybersecurity professions may simply be called the IT Manager and have in-depth knowledge of networking.

But whatever the title or responsibilities, the job consists of two parts — managing people and knowing technology. So to get this job, you need some experience in business administration and some hands-on experience with the tools of the trade.

Want to get started today? Here are some of the courses we recommend:

Learning a selection of the technologies above will give any future Computer Information Systems Manager a step up on the competition in the job market. And you can get started for free by signing up here.

When you’re trying to land your dream job in tech, getting your “foot in the door” at an organization is half the battle. One common way that aspiring developers break into tech and land entry-level positions is through apprenticeships and internships.

These programs allow people from non-traditional backgrounds to work (and get paid!) as an engineer at an organization for a period of time, with the goal of ultimately getting hired at the end. An internship or apprenticeship is a great opportunity to demonstrate your coding skills through hands-on engineering projects, forge relationships with devs who could become your colleagues, and experience what it’s really like to work at an organization. However, depending upon the specific program, a job offer is not 100% guaranteed for all apprentices and interns.

Here’s some advice from Codecademy Software Engineers who made the leap from apprentice to full-time employee. Whether you’re wrapping up a summer internship or just want some advice for an entry-level position, these tips will help you stand out and boost your chances of getting hired.

Ask questions

If you find yourself apologizing for asking “dumb questions,” we totally get it — but there’s nothing wrong with having questions and being curious. Learning and asking questions is a hugely important part of being a Software Engineer, so “you should get comfortable doing it,” says Ana Harris, a Software Engineer at Codecademy.

As an apprentice or intern, you might worry that your questions will reveal your inexperience, explains Sylvana Santos, a Software Engineer at Codecademy. Don’t let that fear keep you from asking important questions: The sooner you ask, the sooner you’ll get unstuck. “Always ask questions and don’t be afraid to feel silly,” Sylvana says. “Most of the time, you don’t sound silly at all. You just think you do.”

Act like it’s the “real deal”

Your workload as an apprentice or intern probably won’t change majorly after going full-time, says Jenesh Napit, a Software Engineer at Codecademy. Even though you’re “just an apprentice,” you should approach your work as though you’re already hired, Jenesh says.

“As an intern or apprentice we can often think that we are not capable of doing the work of other full-time engineers and that we are getting easy tasks, but don’t be fooled — you’re getting the real deal,” Jenesh says. “So just do your best and don’t think of yourself as ‘just’ an intern or apprentice. You are fully capable and ready for the next step in your career.”

Set goals based on competencies

Apprenticeship programs are often structured so that participants have a clear understanding of the competencies they need to reach in order to be considered for a full-time offer at the end. (A “competency” is another word for the measurable knowledge, skills, abilities, and behaviors that define success in a role.)

Ana recalls working with her mentor and manager from day one to establish those competencies and create goals that aligned with them. “We had a 30- 60- and 90-day plan, and we checked in on my progress every week,” she says.

Work with as many people as you can

Sylvana made a goal at the start of her apprenticeship to meet with as many engineers as possible, even ones who weren’t on her direct team, so she could learn about the different roles in the organization. She also mentioned this goal to her manager, who was able to keep an eye out for opportunities to work across different departments and could help facilitate introductions.

A good ice breaker if you want to get to know people outside of your department is to ask someone what they’re working on that they’re excited about. “I was very curious about what other people were working on,” Sylvana says. “I would be like, ‘Hey, I noticed you’re working on this thing. Would you mind if I shadow you and see what you’re up to?’”

Support your peers

The high-stakes nature of today’s job market can make you feel like you’re competing against your fellow interns and apprentices. While there may not be a guaranteed job offer for everyone at the end of the program, it’s important to foster a supportive environment with the other apprentices and interns, Sylvana says.

“We would help each other out if we got stuck, share tips, and give each other opportunities,” she recalls. “I think that was a big part of what makes this program successful and helped me to get the offer at the end.” Plus, you never know who you may end up working with down the line.

Get feedback from your mentor

It’s pretty standard for an intern or apprentice to get paired with a mentor who manages and guides them. Your mentor is there to help you, so “try to get their feedback and support from the very start and work with them towards a full-time position,” Ana suggests.

Mentors can also help with the less technical aspects of your career development. For example, Jenesh wishes he would have focused more on his soft skills, like communication, during his apprenticeship. “It’s hard to practice soft skills,” he says.

Keep in mind: Your mentor is also getting practice managing you, so everyone wins, Sylvana says. “A big part of being a Senior Engineer is enabling engineers who are more junior than you,” she says. “Helping people get unstuck and advising on projects is integral to them being able to move up [in their careers] as well.”

Voice your opinions

People experience impostor syndrome at every stage of their career — but it’s especially relevant when you’re first starting out. Looking back, Ana says she struggled to confidently express her opinions as an apprentice because she was so afraid of being wrong.

“I never in the past had issues with confidence or voicing my opinions, but in this particular situation — as a bootcamp grad, immigrant, non-native English speaker — I thought that I didn’t have enough knowledge and experience to be listened to,” Ana says. “Now I can tell that that approach was wrong, and that my way of thinking and understanding of engineering was most of the time correct.”

Integrating with the company where you’re interning or apprenticing can feel awkward at first (especially if you’re working remotely), but you should take advantage of any opportunities to connect with other people within your organization. Are there non-work activities that you could participate in, or clubs and ERGs that are open to apprentices?

For example, Sylvana recalls joining a book club and attending brown bag talks as an apprentice, which helped her get face time with engineers outside her team. “That was a really great way for me to show, like: Not only am I invested on the technical side and helping us get work done from an engineering perspective, but I also really like engaging in community, asking questions in those spaces, and sharing knowledge,” she says.

Hopefully this advice from people who successfully navigated the apprentice-to-engineer pipeline will help you feel confident going into an apprenticeship or internship. Remember: There’s no single path to finding a more fulfilling work life.

Ready to start applying to entry-level jobs? Check out this guide to making a Junior Developer portfolio (because, yes, you need one), plus our guide for writing a resume and some sample interview questions to practice. For even more job-search resources like portfolio projects and interview prep, head to our Career Center.

Catalog Home | Codecademy

If you’re not sure where to begin or what to learn next, this is a great place to start. Check out our top coding courses, Skill Paths, and Career Paths.