Link in bio for developers: projects, writing and how to hire you
A developer's bio link page that answers what you build, what you have shipped and how to work with you, with casas shaped like little computers and switchboard houses.
Developers collect links like other people collect mugs: a code profile, a blog, a talk recording, an app in the store, a side project with eleven users. The link in your bio, on a social profile or a conference badge, needs to turn that collection into a quick answer: what do you build, and should someone talk to you about it?
These ideas suit freelance developers, open source maintainers, indie app makers and engineers looking for their next role. The casas are computer-shaped workshops with keyboard porches and switchboard houses full of looping cables.
1. Write one line about what you build
"I build accessible web apps for small charities" tells a reader more than a list of languages. Put the kind of problem you solve and who for in your hello, then let your projects show the stack. Recruiters and clients both read the first line first.
2. Pin three projects with outcomes
Choose three projects and add each as a portfolio piece with one sentence about the result: the speed you improved, the people it helps, the problem it fixed. Link to the live project and to the code if it is public. Outcomes are what people remember.
3. Say what work you are looking for
A clear line such as "Open to contract work from spring, remote or nearby" or "Not looking, happy to chat about open source" saves everyone time. Update it the day your status changes.
4. Link your code profile, but do not lead with it
A code profile full of forks and experiments is useful context, but rarely the best first impression. Link it lower on the page with a label like "Code and experiments", and let your pinned projects do the introducing.
5. Collect talks and writing in one place
Conference talks, blog posts and podcast appearances show how you think and explain. Link to a short list of the best two or three, with the event or publication name. Organisers looking for speakers often start there.
6. Offer a simple way to get in touch
A work email or a contact form is enough. Say what helps: "A few lines about the project and your timeline." Keep your personal phone number off the page and away from scrapers.
7. Show the indie app or tool you maintain
If you make an app, a library or a small tool, give it its own link with a sentence on what it does and who it is for. Users, contributors and potential sponsors all find it more easily when it is not buried in a list.
8. Point sponsors to one place
Open source maintainers often rely on sponsorship. One clear link to your sponsorship page, with a line about what support pays for, works better than a scattering of donate buttons.
9. Note the languages you speak, human ones included
Teams working across time zones care about language and overlap. A small line such as "English and Portuguese, working hours in Lisbon time" helps clients and teams picture working with you.
10. Keep a changelog of your career lightly
A short post with the last few roles or contracts, a line each, gives context without a full CV. Link a full CV for those who need it, and keep the page itself light.
11. Choose a workshop with your kind of glow
A computer-shaped workshop with a terminal suits backend and tools developers. One with an open laptop and a circuit board suits full stack makers. A switchboard house with cables and a friendly robot suits hardware tinkerers and integration specialists.
Casitas that fit
Side Quest Software
Side Quest Software is a computer-shaped workshop with a glowing screen and a keyboard porch, with a little terminal, a keyboard and a steaming cup.
A glowing terminal and an optimistic debugger, for indie developers and side project builders.
Patchwork Code
Patchwork Code is a computer-shaped workshop with a glowing screen and a keyboard porch, with an open laptop, a circuit board and a little manuscript.
An open laptop and a circuit board, for full stack freelancers who stitch useful things together.
Connected Corner
Connected Corner is a switchboard house with visible sockets, looping cables and its own front door, with a curled cable, a pocket device and a portable radio.
A switchboard house with looping cables, for integration, API and networking specialists.
Circuit House
Circuit House is a switchboard house with visible sockets, looping cables and its own front door, with a circuit board, a friendly robot and a carefully cut gear.
A circuit board and a friendly robot, for hardware tinkerers and embedded developers.
App Cabin
App Cabin is a computer-shaped workshop with a glowing screen and a keyboard porch, with a pocket device, a pencil and a bright bulb.
A pocket device and a bright bulb, for mobile app makers. Premium: browse it now; premium casas cannot be published yet.
Premium casitas can be previewed and customized today; publishing them comes with paid plans, which are not open yet.
Before you share it
- Your hello says what you build and for whom
- Three projects show outcomes, not only stacks
- Your work status is current
- Contact is a work email or form
- Talks and writing are in one short list
- No personal phone number on the page
A developer's link page is a readme for you: what this is, what it does, how to get in touch. Keep it short, current and honest about your availability. If you work with AI agents, Mini Casa also has an agent API for managing casas. See how portfolio pieces work, or visit Mini Casa for freelancers.
Questions people ask
Is a link page enough for a developer, or do I need a portfolio site?
For many developers a link page with three good projects is enough. A fuller site helps if you write often or sell your own products. You can start small and add posts as you go.
Should I link to my code profile at all?
Yes, but lower on the page. It gives depth to people who want it, while your pinned projects make the first impression.