Or, how to be a good member of your professional community
In Spring 2025, I began serving as an Expert in Residence for BU Spark!, a program that matches Boston University students with non-profit and local government clients to work on data-for-good projects each semester. As an EiR, it’s also my role to serve as a mentor to these students - and I’ve been giving some thought to the career advice I’d like to give to the cohort after a busy spring semester, many of whom are now (or soon to be) on the job hunt. This is advice I’ve given many times in the past to students, recent graduates, colleagues, friends transitioning careers, and even strangers who have reached out via mutual connection (not strangers anymore!). And as they say, if you answer the same question or give the same advice over and over again, you should probably turn it into a blog post. So this is me formalizing my perspective and advice into a 12-step program for how to build a career.
But first, a spoiler: This is not, in fact, a blog post about how to get a job. This is a blog post about how to find and contribute to your professional community.
This particular post is also only part 1 of a series, which means we’ll only be covering the first 3 steps out of the 12. However, I think you’ll find there are plenty of actionable steps to keep you occupied until the next part is published.
Traditionally, we call the process of finding connections in your professional community “networking”. However, I have found that most people have an extremely negative association with “networking”. We think of networking as transactional, full of tit-for-tat favors and unethical biases towards the already privileged. Students shy away from networking because they feel they have nothing to offer, and asking for something (like a job) when you have nothing to give (except your time and labor) feels gross. I say this because this is exactly what I thought when I was in undergrad being told to network in order to find a job. I hated it, and so naturally I was awful at it. When I hear the old adage “it’s not what you know, it’s who you know,” I think of old boys’ clubs and a world where your privilege predetermines your success. But most of us are not starting with a ready-made network to lean on, and I would like to convince you that it’s just as important to grow your network as it is to grow your skills. More than that, I’d like to flip the whole idea of networking on its head.
I didn’t learn how to “network” until I went to grad school for library & information science, and I was surrounded by librarians. Here’s the thing about librarians: we love to be helpful. We want to share that interesting book, informative link, or knowledgeable person. At library school, everyone wanted to help connect me to resources that I might find interesting or useful, simply because making a great connection gave them joy. They were not asking for anything from me, and I barely had to ask for anything from them - simply expressing interest was enough to kick-start a series of introductions. And sometimes I also knew something or someone that could help someone else - and I found joy in that. I didn’t realize that library school taught me how to network until later, but by then it had been completely reframed for me. Networking was not about exchanging favors, rather it was about being part of a professional community. And in a community, you help each other – not because you will get something in return – because it is good for the community as a whole and contributing to your community makes you feel good. It turns out it’s good for you too; a sense of belonging and inclusion can do wonders for your mental health.
I cannot completely transmit my changed perspective and lived experience to you via this blog post, but I hope I can at least partially start to reframe the act of getting to know your professional peers. So this is the last time you will see the word “networking” in this post, and I hope the next time you see that word in the wild you can mentally replace it with “community building”.
So how can you start building your professional community?
That’s it!
I know, I know, it is much easier said than done. You may have already figured it out, but I have a very important caveat to this approach: it’s slow. It’s organic. It’s not going to follow your timeline. It won’t be predictable, or guarantee desired results. And it’s going to require an investment of your time and attention over the span of years, not weeks or months. This is a strategy for your career as a whole, not for finding a job tomorrow. But if you start investing the time now, it will pay off years down the road (when you may need to find a new job rather urgently).
And as with any good investment strategy, you should start seeing some returns on your investment in the short-term, with greater gains over the long-term the sooner you start. That is to say - you don’t need to reach the end of the 12-step program before you reap any benefits. You should be gaining additional benefits with each additional step… and furthermore, they should be compounding. After all, there is a reason I’m breaking this series up into multiple parts!
One more caveat: not all communities are created equal. There are some really toxic communities out there, and it’s important to remember that you get to choose which to be a part of. Here’s something else nobody tells you when you are choosing between potential career paths: when you choose a career, you are in many ways choosing your professional community. And while jobs will come and go, your professional community will stay… and follow you from job to job. But every career path has potential communities based on tools, domain knowledge, skills, conferences, etc. A word to the wise: explore widely, but choose carefully, and choose how you show up even more carefully. This is how reputations are built – or ruined.
I hope I’ve convinced you to give this approach a try. And if not, I hope you find some of the more concrete suggestions I will be offering next useful. And maybe, in a few years (after some experience in the workplace) you’ll revisit this post with a new perspective.
Now that we’ve established goals (building professional community) and set expectations (this is not a blog post about how to find a job in 10 days), let’s get down to the nitty-gritty: how to build your career and grow your professional communities in 12 steps. The first 3 steps (the focus of this blog post) are all about laying the groundwork: this is the prep work you need to put in so that you are ready to introduce yourself to communities. The actual act of introducing yourself is relatively short and easy. But introducing yourself well – and having people discover you and reach out to you – requires a decent amount of upfront effort and thought.
The next three steps will focus on finding communities, both online and IRL. Guess what you should be doing once you find and join these communities? Introducing yourself! I know, once again, easier said than done. In a future blog post, I’ll talk through some of the strategies that have helped me, a die-hard introvert, with being more social. Don’t worry, though - after following the first three steps, you’ll be very well prepared for these self-intros!
Next, it will be time to start participating in your communities. Give your time, knowledge, resources, and support - first figure out in what capacity you are able to contribute, then figure out what gives you joy, and lean into that. You will probably stay in this phase for a long time, experimenting and iterating. You may find new communities, and start the whole process over. You may change mediums - maybe you decide to create video content instead of writing blog posts. It’s your journey, and you get to decide what direction to explore.
As you continue to explore, many years into your journey, you may find some uncharted lands. You may identify some gaps in the communities you belong to, and you may identify some opportunities for new communities. Maybe you’ve identified a unique group of people who could do amazing things together if they just had a place to connect. Finally, it’s time for you to build your own community. Even if it’s for a small friend group, bringing people together is a magical thing.
Here is your 12-step program for building a career (and community):
This is the most obvious, boring, and also necessary first step: if you’re going to apply for jobs, you need to have a resume. A slightly less common recommendation: you should also have a CV (Curriculum Vitae).
A resume is a highly curated document - it should be 1 page (maximum 2 pages for those further along in their career) that is formatted according to good design principles. Hiring managers spend 6-8 seconds on average looking at a given resume - and that means that all relevant information needs to jump out at them in those 6-8 seconds. Use of whitespace, fonts, font size and styling, color, order and placement of elements all matter for a resume. If everything needs to fit on one page, you have to be selective in what you include. What you choose not to include is just as important as what you do include. Your resume will change depending on what types of jobs you are applying for, perhaps even depending on individual jobs, and you should also have a standard resume that gets periodically updated - even if you’re not actively job searching. Struggling to fit everything in 1 page? Here are some tricks that may help.
In contrast, a CV is where you list everything. Every degree, certification, paper, presentation, award, professional organization, internship, job… a CV is a document you always only add to. Formatting is also less important for your CV. Your resume, therefore, is a carefully selected, curated, and formatted version of your CV. While CVs are only required when applying to certain types of jobs (government, academic), you should still always maintain your CV. You never know when having that full documented history can come in handy!
So if you have neither, start with the CV. List out everything, and leave formatting to the bare minimum
Here are some of my tips for resumes, presented in no particular order:
Remember how the whole point of this post is to help you find and join your professional community? Well in this day and age, that mostly happens online, on a variety of social media platforms. And that means that you need to create accounts on said social media platforms. Our first stop: LinkedIn. But before we get there, we need to cover a few necessary preliminary steps.
The first pre-req: a professional-sounding personal email. At every university and job, you will get an email address. And when you inevitably leave that organization, you will also lose access to that email. Also, your organization has access to everything in that email account. You need an email that you will use throughout your career, and one that is private to just you. This email should be as close as you can make it to your name. Every social account is going to require an email to sign up, so if you don’t have one yet, do this first.
The next pre-req: a professional headshot. This should be a high quality photo of only you, shoulders and up, in at least semi-professional attire. Most universities offer the opportunity to get a professional headshot taken against a standard backdrop, but if you can I recommend hiring a professional photographer (or a very skilled friend) to take photos in a meaningful location and to try to inject some personality into your headshot. This headshot may be the only visual your online connections have of you, so make it good. You will use the same headshot across all of your social accounts
Final (optional but highly recommended) pre-req: a password manager. Ideally, you should choose a platform-agnostic password manager that you can use across any web browser or device. Personally, I use and like Bitwarden (it’s free). The most popular (paid) option is 1Password. These happen to be the two recommended options from Wirecutter. Other options include Keeper, Dashlane, and LastPass. Anyone who has accounts online (so, everyone) should be using a password manager, with generated passwords unique to each account. Using the same password for everything is a security hazard, plus more and more organizations are transitioning to passkeys. If you don’t already use a password manager, do yourself a favor and make that transition now.
Ok, time to walk through the process of creating your social media accounts! This section is going to be a bit hand-hold-y, so feel free to skim or skip as needed. But if LinkedIn or GitHub is a mystery for you - don’t worry, we got this.
If you do not already have a LinkedIn account, go create one. Once that is done, head to your profile page - we’re going to walk through every element you need to fill out.
Let’s start at the top: the most important elements here are your name and your profile photo. Next is your headline (aka tagline): this is the text that will appear next to or under your name and profile photo when you post. This should be short and to the point - your current/aspiring title/role/profession. Everything else in the intro is optional, and you can fill it out later.
Next: your cover image. If you belong to an organization (university or employer), they probably have a standard set of cover images you can choose from in their Brand Guidelines. This is the safest option - just remember to keep it up to date with your current organization. Alternatively, you can design a cover image for yourself. Think about what you want to communicate with it. When someone visits your profile page, this will be one of the first things they see. Some people will use another photo of themselves speaking at an event or engaged in some professional activity. If none of these appeal to you, another safe option is to use a landscape photo. If you like to travel, use a favorite scenic photo you took (this can be a great conversation starter too!).
Final bit of the intro: the about section. Many people skip over this section because writing bios is hard, or they don’t keep it up to date. This is a mistake. The about section is the first and best opportunity you have to tell someone about yourself. Consider this an elevator pitch for any future employers. You should introduce yourself, highlight key accomplishments, and state what you are currently looking for. While you can include more details in a longer bio, your first paragraph should be 2-4 sentences and include all of the most necessary information you want to convey. Edit this section carefully and get friends/family to review it for you as well.
Okay, introductions complete! Are we done? Definitely not. Remember the previous step, creating a resume and CV? We’re now going to transfer all of that information over to your LinkedIn profile. Your LinkedIn can be functionally identical to your CV, or you can exclude any irrelevant experiences. Take the time to go through and fill out all of the sections in your profile - and don’t forget to add skills!
Finally, one bonus step: trade recommendations with a peer or ask for one from a professor/supervisor. Are you working on a significant group project, for a class or a club? Identify someone who you worked with closely, who can speak to your contributions (and vice versa), and offer to write them a recommendation if they would be interested in writing one for you. If your professor recently wrote positive feedback for you on a major project, ask if they could put that same feedback in a LinkedIn recommendation. For strangers on the internet, knowing that someone else vouched for you can help a lot with establishing initial trust.
Your profile page is now complete: make sure to add a link to your LinkedIn profile on your resume. You are also now ready to start adding connections. We’ll cover more of this in a future step (Cultivating your social feeds), but you should go ahead and start making connection requests to anyone you personally know. Family, friends, professors, students from your classes or clubs, current and past employers - if you know them and they have a LinkedIn account, add them.
If you are reading this blog post, I’m assuming you probably write code. If you stumbled on this and you never write code and do not plan to, feel free to skip this section. But I’m guessing that this will be relevant for most people reading this.
If you do not have one already, go ahead and create a GitHub account. Fun fact: you can add as many email addresses as you want to your GitHub account. My advice is to only ever have 1 GitHub account. While some organizations may require you to create a specific GitHub account just for them, this is honestly rare. Instead, you should add your organization-specific email addresses, and route all notifications to the appropriate email based on the GitHub organization.
A GitHub account serves many purposes. Its primary function is for version control - you should be keeping all of your code in a git-tracked repository, and GitHub is (currently) the de-facto remote location. If you write code, and you have a GitHub account, I’m assuming that you know git (or are about to learn git, maybe even via this workshop I developed/adapted). If you don’t know git, this is something you need to learn pronto.
A secondary function of your GitHub account is to serve as a portfolio of your (coding) work. This means that you should have some public repositories with your work - personal projects, school projects, or work projects that can be safely made public. And guess what is just as important as having these projects in public repos? Documenting them. Every repo should have a well organized and thorough project README that introduces strangers on the internet to your work. (Note: READMEs should be markdown files. If you don’t know markdown syntax, invest 30 minutes in learning it). The audience may be other coders who want to build off your work, or prospective employers checking to see if your portfolio matches your resume. They are not just interested in if you can write good code - they want to know if you can write clean, documented, well-organized code. In other words - are you going to write PRs that they love or hate reviewing? So don’t just use a repo as a place to stash code that is functional enough to work - put effort into curating your repos and making them a joy to read.
However, we all have junk repos from that barely started personal project or that one-off workshop. I’m not saying you need to put a high level of care and attention into every repo - just those you want potential employers and community members to look at. And there are a few tricks you can use to direct their attention to the right repos.
First, put some effort into your GitHub profile. Go to your GitHub profile page, and edit your profile. Add your headshot, your (current or aspirational) role title, your LinkedIn and other socials, etc. Next, create a README for your profile. Remember your About section for LinkedIn? You can recycle and modify that bio for your GitHub profile. You can (and should) put links in your personal README - to your socials or other contact info, and to specific repositories that you want people to look at.
Right below your profile README will be your pinned repositories. You can choose up to 6 repos that you want to direct people to by pinning the repository. And if people go straight to your repositories (though it is far more likely they will look at your profile first if you’ve put any effort into it), they will see the repos in order of most recent activity by default. That means that if you put some extra effort into updating (documenting!) the repos you most want people to see, those will be the repos they see first.
Finally, consider making any repos you don’t want people to see private. While GitHub used to limit the number of private repositories for personal accounts, they no longer do, and you can freely switch between public and private in your repo settings.
One final tip: if you are a student, you should absolutely sign up for the GitHub Student Developer Pack. Among a myriad of other benefits, you can sign up for a .me domain name on Namecheap and get 1 year free. This is optional but highly recommended for the next step - building a personal website. Seriously, if you are a student, go sign up for the Student Pack right now - there are so many freebies and learning resources that are absolutely worth it.
While LinkedIn and GitHub are the only two I’m going to require (well, theoretically require, I can’t actually force you to do anything), I am going to highly suggest you create (professional) accounts on other popular social media sites as well. My top recommendation (at the moment) is Bluesky - think of it as the successor to Twitter. While X may still exist atop Twitter’s ashes, I’m not going to refer anyone to that raging dumpster fire of a site. There are also many thriving communities on Mastodon, especially among academia. Mastodon is a bit more complicated and less user-friendly than Bluesky, so you may want to research it a bit first. Speaking of academia - if you have ever published a paper, you should sign up for ORCiD. If you make (or want to make) professional video content, then create a professional YouTube (and Instagram, and TikTok, etc). Do not conflate these professional accounts with your personal accounts, though - that way danger lies. Reddit accounts are usually anonymous, and I’ll stick with that trend - create a dedicated professional reddit account (that can remain anonymous) and follow relevant subreddits. This can be a great way to learn new things and figure out what your communities are talking about right now.
There are so many social media sites out there… it is really up to you to figure out which sites and communities you want to invest time in. Typically on these sites you can be more of a whole person - keep it kind, but be a real person
Creating accounts on LinkedIn, GitHub, and other socials gives you an online presence where you can connect with people and present some information about yourself. It is also relatively easy to establish a presence on these sites. So you may be strongly inclined to skip this next step - after all, building a personal website is more difficult, time-intensive, and requires some technical skills. I’m going to first attempt to make the case for why you should absolutely build a personal website, and then I’m going to walk you through the process.
There are both ideological and practical reasons why you should have a personal website. Let’s get the manifesto out of the way, then we’ll discuss practicalities. A personal website is your home on the internet - your personal space that you have complete control over. You get to choose the design, the content, when and how you update it, and how people can engage with it. You own it - not some big corporation. As anyone who has been around on the internet for long enough can tell you, you don’t own anything on the social media sites. And eventually, they will die, or become so enshittified that they might as well be dead. The content that you put on social media sites is not really yours - it’s provided by you, to the site, just with your name attached. You are subject to their algorithm… for better or for worse (and believe me, it can get pretty bad).
Think of social media sites as places in your neighborhood that you go visit - the local coffee shop, the bar, the book shop, the cafe. But you don’t live there - you live in your house. Your house is the space that belongs just to you, and you get to furnish and decorate it as you choose. You get to decide who can visit and when. And when your favorite local coffee shop closes down, that’s very sad, but you aren’t suddenly homeless. You can convince your friends to meet up with you at the book shop instead.
If you aren’t convinced by the ideology of having a personal website as your home on the internet (and trust me, I’m far from the only one with this perspective), then let’s talk about the practical reasons. Your personal website is a one-stop-shop for someone to learn everything (you want them to) about you. Your website has your bio, resume, cv, portfolio, writings (blog posts!), socials, publications, projects, learnings, hobbies…. Everything and anything you want to put on it. It is a place for you to curate all of the information about you on the internet - and that content can either live on your website or you can point to it. With a personal website, you are making a potential employer’s job much easier - they don’t have to go look you up on all these different sites to try to see if you do good work and are a potential fit. On your personal website, it’s all there in one place, and you control how it is presented.
Convinced yet? Hopefully you are… and if not maybe you’ll trust me enough to follow along and reap the potential benefits later. Let’s move on to talking about how to actually accomplish this fantastic internet feat.
There are many, many ways to build a personal website. If you are in web development, you do not need my help or my convincing - your personal website is your portfolio, and it’s probably custom. If you have zero technical skills and do not aspire to gain them, you’re probably going with one of the classics like WordPress.
But if you know basic git, have a GitHub account, and are comfortable writing markdown and editing YAML files, then I’m going to suggest my personal favorite method: GitHub Pages and Jekyll. This website is built on GitHub Pages, uses a pre-made Jekyll theme (al-folio), and lives at a custom domain name (which I obtained via the GitHub student pack and have been paying NameCheap approx. $15/year for after the free first year ran out). You don’t need a custom domain name (though I personally think it is worth it), and you get to choose whatever theme or technology you want to build on.
I’m going to continue the “how-to” portion of this section with the assumption that you are following this recommendation, though if you prefer a different method you may still find some of the following content helpful.
Step 1: Brainstorming
What do you want out of your personal website? Before you start building, you need to plan, design, and prioritize. Come up with a list of features that are important to you. This is going to help enormously with the next step (picking a theme).
Here are some examples of features that you might want for your personal website:
What features do you absolutely want, and what features are nice-to-have?
Next, consider what you want your homepage to look like. Do you want your bio front and center? Or do you want people to see your blog posts first? Maybe you want a portfolio carousel to be near the top. Or maybe you just want visitors to see your resume. Even if your website has all of these capabilities, only one primary feature can be the first thing visitors see when they visit your website - everything else will require clicks (or scrolling) to navigate to the right spot. What you choose to feature on your homepage communicates something about your priorities. While many themes are flexible enough that you can alter what shows up as your homepage, it is usually easiest to go with the default.
By choosing what features you need, what features you want, and what you want your homepage to focus on, you are now ready to filter through the multitude of themes and select one to build your website with.
Step 2: Choose a Theme
Even if we restrict the options to Jekyll themes, there are many, many options out there. Browse through the many options at jekyllthemes.io, though you probably want to restrict the options to only the free ones. You can also find curated lists, like this one of awesome jekyll themes. I personally have used (and can highly recommend) two themes: minimal-mistakes and al-folio (I started out using minimal-mistakes, then a few years later switched to al-folio. This is part of the beauty of having a personal website - you can change the theme/design any time!)
If none of the Jekyll theme options are speaking to you, then go ahead and look at the Hugo options as well. Hugo is becoming more popular, and many folks are switching from Jekyll to Hugo. Check out some Hugo themes here. I’ve noticed that the blowfish theme is pretty popular, as well as the LoveIt theme. Or maybe you want to build your website with Quarto!
Based purely on available features and appearance (explore the examples!), pick out ~3 themes that you like. But before making your final choice, you should read the documentation. You should know how much work it is to first set up the website, and to maintain and extend the website. Different themes may have different setup steps, and before committing to a theme, you need to take this into consideration.
Step 3: Create & clone the repo
Before you go creating a repo called my-website, slow down and read some documentation first. Start with the Quickstart for Github Pages. You should notice something very important here - your repo name needs to follow the formula of <username>.github.io. You also need to read the setup documentation of your chosen theme. For example, al-folio recommends creating the repo by using the theme as a template. Any theme you choose should have well-documented setup instructions. Read the instructions first, then follow them - exactly.
After creating your repo on Github, you will need to clone the new repo to your local computer, and then set up your local development environment. Why do you need a local development environment? Because you are going to want to be able to preview changes to your website before publishing them. Again, this should be documented as part of the theme’s setup instructions. There are also generic Jekyll instructions in the Github pages documentation.
Step 4: Make your first updates
One of the most important files in your new website repo will be the _config.yml file. This is where all of the core settings for your site will live, including key information like your site’s name. Go through this file and make all the updates you want. After you are finished, save the file. Then, open a local preview of your website. If you are using Jekyll, you will want to type this in the command line: bundle exec jekyll serve. Either a localhost webpage will automatically open, or you should see a line like this in the terminal: Server address: http://127.0.0.1:4000. This is your localhost URL, and if you copy and paste http://127.0.0.1:4000 into your browser, you should see your website.
At this point, the version of your website you see on localhost should be different from the published version, because you haven’t yet pushed your changes. Let’s compare by looking at the currently published version at <username>.github.io. See steps 20-23 at this documentation page for further help.
After making the most important updates to your site (updating _config.yml and perhaps removing some of the example material), and previewing the changes on localhost, go ahead and push your changes to Github. This will kick off a Github Action to update your website (see step 24 of the aforementioned docs). Within a few minutes, you should see these updated changes on your published site (at <username>.github.io).
It is during steps 3 and 4 that you are most likely to encounter confusing issues. Whether you missed a step, something wasn’t documented, or something has changed since the documentation was updated, it is totally normal for you to encounter some bumps along the road. I highly encourage you to persist, and reach out for help if you need it.
Step 5: Use a custom URL (optional)
While you are welcome to use the github.io URL for free in perpetuity, there are some advantages to using a custom domain name. For one, custom domain names are pretty useful. They can help you establish your identity and brand online, and they also help communicate authenticity and credibility. It is also one further step in you owning your home on the internet (and again, don’t just listen to me!). You can do cool things like set up your own email hosting or switch your bluesky handle to your domain. In the long run, you are likely to find many uses for owning a domain name. If you have the Github student pack, this should be a very easy decision - register a .me domain name for free, and hopefully your name (or some variation of it) will be available.
After registering your domain name (and you may need to give it up to 24 hours after actually buying the domain name), you will then want to configure Github pages to use your new custom domain. As always, read the documentation, and follow the steps exactly. You will also need to update your _config.yml file with your new domain name.
This is the last tricky setup step. After you have completed all of the setup (following the documentation!), visit your new custom URL and verify that you can see your Github Pages website (debug as needed). You are now ready to start curating the content on your website!
Step 6: Update the bare bones basics
There is a lot of content that you can put on your website, and fully building out your website will take time. Blog posts, projects or portfolio items, and other such content are important, but they are not essential right now. Your first goal is to get your website into a shareable state - that is, you can put a link to it on your resume and not be embarrassed. So let’s go through the key items in roughly their order of importance.
Your home page. This is the first thing a visitor sees when they visit your website URL. Some websites only have a homepage, but most separate out the pages. If you choose a single-page theme, then consider your homepage the portion you view without scrolling. Look at all of the elements on your home page, and update them. Your website will have a title - I highly recommend using your name as the title. After all, this is your personal website, all about you. You’ll also likely want to include a profile photo, and some kind of “about me” blurb and/or tagline. Sound familiar? These are the same key elements you should have updated on your social media profiles. Be consistent, and re-use the same content for your personal website.
Your bio. The theme you chose may have a separate, longer “about me” page, or the about me may be simply part of the home page. Re-use the same “about me” content you wrote for your LinkedIn profile - you can tweak, add to, and improve it later!
Your socials. Most themes have a specific way to display your social media profiles - figure out which profiles you want to link to from your website, and make sure you have added the correct URLs in the correct place. At a minimum, include your LinkedIn and GitHub profiles. You should also include your professional email address.
Your CV. Most personal website themes include a dedicated page for displaying your CV. If not, there should at least be some way to link to your resume PDF file. When filling out your CV page, again, re-use content - copy exactly from the resume/CV you’ve already written, which you also should have already re-used on your LinkedIn profile.
The menu bar. Likely at the top of your website, there are a number of pages and menu options. There may be some pages you plan on filling out later, while others may not be relevant to you. You don’t need to delete the pages, necessarily - just remove the links to them in the menu. When you visit your website, you should only be able to navigate to pages that have actual content on them.
Optionally, a placemark blog post. You don’t need to actually write a blog post yet, but if your website has a blog section (which it should), make sure to remove any posts from the template and write a single blog post with the title of “Coming Soon!” or something similar. Include a brief blurb that this is a new website and you’ll be updating with your first blog post soon.
Throughout this process of updating the bare bones basics of your site, you will also be learning how to use your website. This is a learning process! So take it slow, forgive yourself for mistakes, and treat this as an exploratory exercise. You’ll need to learn how to add and reference images and files appropriately. You’ll need to learn how to update yaml files, and where the files that control certain elements of your website live. Throughout this entire process, you should have a local preview of the website in your browser, and you should preview each change after each file save. After you are finished, make sure you commit and push all of these changes, and then go check it over on the actual live website. You may find things not displaying as intended, and you will need to further learn how to debug these issues. While the destination (of having a personal website) is the goal, the (learning, skill-building) journey is just as important. Not only are you learning new technical skills, but you are also learning how to write about and market yourself. You are telling the world a story about who you are - exactly what you will need to do in interviews.
Step 7: Request a review
You now have a shareable website - congratulations! But before you go publicizing this fact to the world, ask a few trusted people to review it first. Whether it be family members, friends, colleagues, or other advisors, invite feedback from people who you know can give you an honest critique. At the end of the day, it is your choice on whether to take any of that feedback, but the process of getting an outside perspective is invaluable. Whether it be typos, phrasing, framing, or design, there is something that can be improved, and I promise you will benefit from a second (and third!) perspective. All you have to do is share the URL, what you are trying to accomplish with the website, and what type of feedback you are open to. Then, make sure to update your website with any of the feedback you agree with!
Step 8: Share & Publicize
Now, you are finally ready to share your website with the world. First, distribute the URL for your website - put the URL on your resume and in the bio of all of your socials (whether it be in an official spot for your personal website or just at the top of your bio). Then, share the news by posting about your new website on all of your socials. It’s official: you now have a personal website! The hard upfront work is done, and you can start to reap the rewards. But remember: what you just created was the foundation. It is now your responsibility to build on that foundation over time. After all, your website just has the bare bones basics right now. You have some content to add!
Step 9: Your first portfolio entry
Your portfolio is something that you will build over time. You may already have a number of projects you can write about for your portfolio, in which case you have a backlog to slowly work through. Or you may not have a lot of projects right now - but you will in the future, and you need a place to write about those projects. For right now, focus on getting just one entry into your portfolio. If you want to keep going and add more, go for it!
For your first portfolio entry, pick the project you’ve completed that you are most proud of (and also can be fully shared on the internet). Include all important materials about this project - all of the relevant files and links (including to the code!). If possible, include as many images as you can. Write a basic description of the project, and then write a longer narrative - what you learned, what the outcomes were, etc.
Step 10: Your first blog post
Most people are not quite sure what to write about in a blog. You will find that you probably have quite a bit to write about over time, but we will cover that later. I am a strong believer that your first blog post should essentially be a longer “about me” page. Your bio should be short and sweet - only the headlines, not the full story. This first blog post is your chance to tell your story in your real voice. You can talk about your accomplishments, important and formative experiences, your hobbies and interests, and even your ambitions and goals in life. Don’t worry as much about sounding “professional” - you want to let your voice and your personality shine through. After reading this post, I want to feel like I know you better - that you’re someone I could comfortably strike up a conversation with.
Again, go through a review process before you publish this post. And again, officially “publish” your first blog post by posting about it on your socials. These are good practices to follow with every new blog post or addition of content to your website - ask someone to review it first, and then share it with the world via your social media (this goes for new portfolio entries as well!)
Over time, keep adding your website. Continue to flesh out your portfolio, write new blog posts, and keep your website up to date. We’ll cover more about writing content in Step 6, “Start posting” (in part 2 of this blog post series). But you now have a solid foundation and are ready to introduce yourself to the world.
Thus concludes my advice on how to prepare to introduce yourself, and part 1 of this blog post series. There is a reason we are taking a pause here - completing these first 3 steps takes a lot of time and effort! I’d rather get this section into your hands sooner, and hope that some of you can get started and benefit from my advice now, than wait to publish until all 12 steps are written out. I hope you can also see how these 3 steps build on each other, and you can and should re-use the work you put into one step into the next
The next steps rely on you having followed these 3 steps first. For example, the very next step is “Cultivate your social feeds”, which boils down to following and connecting with people. Every time you click follow, there is a chance they will look at your profile and decide whether they want to follow you back. Your chances of being followed back are much greater if you are clearly a real person who is doing interesting work - as demonstrated in your bio and on your website!
There is one final piece of advice that I want to leave you with as you embark on this self-introduction journey. Please, please, do not use AI* (*LLMs, a.k.a ChatGPT, Claude, Gemini, etc) to write any of your content. Do not use AI to write your bio. Do not use AI to write your intro blog post. Do not use AI to edit/create your profile photo. Talking and writing about yourself is hard, but it is a muscle you must start exercising. Here’s another reason why: by having a social media presence and a personal website, you are giving potential employers a big signal that you are a real person. Right now, recruiters and hiring managers are drowning in a sea of AI-generated resumes and cover letters. They are painfully easy to spot, and while some may be attached to real people, it simply isn’t worth the effort to sort “real” AI-generated resumes from fake - so they all go in the trash. If your social media profile or personal website smells AI-generated, you end up accomplishing exactly the opposite of what you are intending - people may assume that you are not real. So, don’t. It doesn’t matter if your bio is a bit awkward, if you have the occasional typo, if your profile photo isn’t studio perfect. What matters is that you are genuine, and that your authenticity shines through.
I hope I have convinced you that establishing a presence online - through social media platforms and through a personal website - is worth the investment. And hopefully, I have also demystified what it takes to get started. Still, learning and doing new things can be scary - and it’s not going to stop being scary until you actually try. So if you’ve made it to the end of this blog post, I want you to make a deal with you: I’ll keep writing the next parts of this series, and you follow the 3 steps I’ve already laid out
Here are some more articles you might like to read next: