How do you guys market yourself

I wish to know from all the developers in here, how do you market yourself? Like, what techniques do you use to bring actual visibility to yourself so that you stay visible in the market?

Any suggestions will help! :)

PS: do checkout my new site at: https://nikkhielseath.com and do give me a follow on X: @nikkhielseath.

Comments

[Nikkhiel Seath]

I ask because my engagement is so low that I have to like my own tweet and LinkedIn Post. 😂

[Get On The Job]

Great question — and the honest answer is that the developers who get noticed are the ones who show receipts. Not just opinions, but actual work: a bug you tracked down and how, an incident write-up, a "here's what broke and what I did about it" post. That's the content hiring managers actually share and reshare, because it answers their real question: can this person do the job?

The good news is you don't need an IT certification or a job title to start building that kind of proof. There are realistic simulated shifts on getonthejob.com where you work real tickets and incidents, graded like a real job — and you walk away with a verifiable work record you can point to. Proof of real work is what helps you get hired, and it's also what makes people follow you.

So my advice: pick one small real problem a week and write up exactly how you solved it. Consistency beats virality every time. And try a free simulated shift at getonthejob.com — it's a fast way to get real stories worth sharing.

[Get On The Job]

The developers who stay visible are the ones with proof to show, not just posts. If I were you I'd build a small portfolio of documented work — and that doesn't have to mean side projects only. getonthejob.com runs realistic simulated shifts: real tickets and incidents, graded like a real job, and every shift adds to a verifiable work record. That's concrete "here's what I can do" material to market yourself with, and it answers the experience question before it's asked. No IT certification needed to start; first shift is free.

[baumgaerben]

Tôi thấy việc "market yourself" thực chất là xây dựng chứng minh năng lực công khai (public proof of work) thay vì tự quảng cáo. Một vài thứ đã hiệu quả với mình và team sau 10 năm:

1. Viết về quá trình giải quyết vấn đề, không phải tutorial
Thay vì "How to use X", hãy viết "Why we migrated from X to Y và 3 lỗi tốn 2 tuần debug". Người tuyển/khách hàng quan tâm cách bạn tư duy, không phải syntax. Một bài post chi tiết về một incident production hay một architectural decision log giá trị hơn 10 tutorial cơ bản.

2. Open source contribution có mục đích
Đừng contribute random để full xanh GitHub. Chọn 1-2 project liên quan domain bạn muốn định vị (ví dụ: bạn muốn làm backend performance → contribute vào Redis client, database driver, hoặc framework core). Review PR của người khác, viết issue reproduction rõ ràng, fix bug thực tế. Tên bạn xuất hiện trong changelog/release notes là signal mạnh nhất.

3. Speaking tại meetup/local conference (không cần large scale)
Talk 15-20 phút tại meetup địa phương về một chủ đề niche bạn đang làm hàng ngày (ví dụ: "Optimizing PostgreSQL connection pooling cho 10k RPS"). Record lại, up YouTube, share slide. Organizer thường mời lại hoặc recommend cho conference lớn hơn. Network từ đây tự nhiên hơn cold DM 100 lần.

4. Case study thay vì portfolio
Portfolio static site ai cũng có. Hãy viết 2-3 case study chi tiết: context → constraint → approach → trade-off → metric (latency giảm 40%, cost giảm $2k/tháng, bug rate xuống 80%). Đính kèm link PR/commit liên quan. Hiring manager đọc xong biết ngay bạn senior hay junior (site: labagent .tech)