DEV Community: Ahmed

GİVE ME FEEDBACK

Ahmed — Thu, 06 Aug 2026 09:40:12 +0000

Building software is easy.

Building something people actually want to use is the hard part.

For the last few months, I've been working on CV Mimarı, a resume builder designed to make creating ATS-friendly resumes simple, fast, and accessible.

👉 https://cvimarı.xyz

My goal wasn't to build "another resume builder."

I wanted to remove the usual pain:

confusing editors
unnecessary account creation
complicated formatting
resumes that look good but fail ATS screening

The idea was simple:

Spend your time improving your experience, not fighting with Word formatting.

What it currently does

Today the project includes:

Resume templates
AI-powered resume improvements
ATS score checking
Resume optimization
Cover letter generation
Resume examples and guides
PDF export
Modern responsive interface

I tried to keep everything clean and straightforward instead of adding dozens of unnecessary options.

Sometimes software tries so hard to become "professional" that it forgets people just want to click a button and move on with their lives.

Why I'm posting here

I'm not looking for compliments.

I'm looking for problems.

Imagine you were using this to apply for your next job.

I want brutally honest feedback.

Things like:

Is something confusing?
Does the UI feel slow?
What would make you leave the site?
Which feature feels unnecessary?
What's missing?
Would you actually trust this with your resume?

If something is bad...

Tell me.

If something is ugly...

Tell me.

If something makes you want to close the tab...

Definitely tell me.

The biggest challenge

One thing I've learned is that building features is much easier than understanding users.

I can spend a weekend implementing a new AI feature.

But discovering why someone leaves after 20 seconds?

That takes dozens of real users.

That's why I'm asking for feedback before continuing to add more features.

The roadmap

Some ideas I'm considering:

More resume templates
Better AI suggestions
Portfolio integration
LinkedIn import
Resume version history
More ATS analysis
International templates

But maybe I'm solving the wrong problems.

I'd rather hear what you think should come next.

Be brutally honest

Here's the project:

LİNK

Please don't hold back.

Good feedback saves weeks of building the wrong thing.

I'd really appreciate any thoughts, criticism, or feature requests.

Thanks!

Software Engineer Resume Example and Writing Guide

Ahmed — Tue, 04 Aug 2026 08:58:50 +0000

Software engineer resumes get read a bit differently than resumes in other fields: as important as the list of technical skills is whether that skill was actually used to solve a real problem. This article covers how to structure a software engineer's resume section by section, with a concrete example.

If you haven't read the general resume-writing rules yet, we recommend checking out How to Write a Resume: A Complete Step-by-Step Guide first — here we focus specifically on what's unique to software engineering.

What Do Technical Interviewers Look for on a Resume?
What you built, not just which technology you used. Instead of "I know React," saying "built a dashboard from scratch in React with 10K+ monthly active users" sends a far stronger signal.
Measurable technical impact. Being able to point to a concrete improvement in metrics like performance, scalability, error rate, or development time.
Real code/project evidence. A link to GitHub, a personal project, or an open-source contribution.
A tech list that isn't inflated. Listing 40 technologies on a resume reinforces the impression that you're not truly proficient in any of them.
Section Structure

1. Contact Information + Links

Next to your name, email, phone, and city, add your GitHub and a personal portfolio/blog link if you have one. In technical positions, these links can be even more persuasive than a reference letter.

2. Professional Summary

In two or three sentences: how many years of experience you have, which layer you work in (frontend/backend/full-stack/mobile/data, etc.), and your strongest area.

Example: "Backend Developer with 4 years of experience, specialized in microservice architectures and API performance optimization. I build scalable systems in the Node.js and PostgreSQL ecosystem."

3. Technical Skills

Grouping these into categories instead of one flat list both improves readability and helps relevant keywords show up in the right groups during ATS scanning:

Category Example Content
Languages TypeScript, Python, Go
Frontend React, Next.js, Tailwind CSS
Backend Node.js, Express, PostgreSQL, Redis
Tools / DevOps Docker, GitHub Actions, AWS
When filling out this table, only list technologies you've genuinely used and can answer questions about in an interview.

4. Experience

For each position, write 3-5 bullet points using this pattern: [Action verb] + [what was built/solved] + [measurable/observable result].

Sample bullets:

Moved synchronous calls in the payment service to a queue-based architecture, noticeably reducing average response time.
Expanded end-to-end test coverage, reducing the number of regression bugs reaching production.
Built and drove adoption of a checklist that standardized the team's code review process.
If you have numbers (percentages, time saved, user counts), be sure to use them; if not, prefer observable but understated phrasing like "noticeably" or "significantly." A number you can't defend when asked about it in an interview is far less credible than an honest, concrete sentence.

5. Projects

If you have personal or open-source projects, list them in a separate section, each with a one-sentence description and a GitHub link. For interns/junior candidates, this section can go a long way toward making up for a lack of work experience.

6. Education and Certifications

Major, school, and graduation year are enough. If you have a relevant certification (like a cloud provider certification), note it on its own line.

The Difference Between a Junior and Senior Resume

Junior: Weighted toward projects and education; internships, capstone projects, and open-source contributions stand out. The skills list can be broader since there's been less opportunity to go deep yet.
Senior: Weighted toward impact and ownership; which technical decisions you made, which systems you designed, and how you mentored junior developers stand out. The tech list should be shorter but deeper.

Common Mistakes

Inflating the tech list. A "let me list everything I've ever touched" approach leads to a loss of credibility in the interview.
Not sharing a GitHub/project link. Not offering evidence in a technical position means not playing your strongest card.
Writing only a task description. "Developed APIs" is a task description; adding what problem you solved and its outcome turns it into an achievement.
A pile of jargon. Clear, plain language is more effective than unnecessarily heavy terminology.

Conclusion

What really makes a difference on a software engineer's resume isn't the number of technology names, but how you describe the real problems you solved with them. To make sure your resume gets past an ATS, also check out What Is an ATS? How Does Your Resume Get Past the Robots?

Body Language in Interviews: A Guide to Leaving the Right Impression

Ahmed — Tue, 04 Aug 2026 08:52:18 +0000

Before you start reading, if you enjoy this article, you can find more educational articles on my website.

How you say something leaves as much of an impression in an interview as what you say. Your body language conveys your confidence and sincerity independently of your verbal answers. This article covers how to use the right body language in an interview.

Posture

An upright but not tense posture conveys both confidence and ease. Pulling your shoulders back and finding a balanced position — not fully slumped in the chair, but not rigid either — is ideal.

Eye Contact

Constant eye contact isn't required (it can create unnatural tension), but maintaining regular eye contact while speaking and listening shows interest and confidence. In online interviews, this means looking at the camera (see How to Prepare for an Online Interview).

Hand Gestures

Natural hand gestures support your speech — staying completely still can look artificial. But avoid signs of tension like excessive movement or constantly fidgeting with your hands.

Smiling

A natural smile conveys sincerity and a positive attitude. Rather than a forced smile, smiling naturally at a point that genuinely interests you is more effective.

Avoid Signs of Tension

Shaking your foot or tapping your fingers
Constantly fidgeting with your hair or clothes
Crossing your arms over your chest (can read as a defensive posture)
Constantly checking the time
Body Language Should Be Natural
Rather than memorizing these tips, rehearsing a few times before the interview (with a friend or in front of a mirror) so you feel at ease brings out the most natural and convincing body language. A forced performance is less convincing than genuine ease.

Conclusion

Your body language is a silent layer of communication that either reinforces or undercuts your verbal answers. An upright posture, natural eye contact, and a relaxed manner are among the most effective ways to leave a confident impression in an interview.

Handshake (In In-Person Interviews)
A firm but not crushing handshake shows confidence in a first impression. A handshake that's too limp or too hard can unintentionally send a negative signal.

I created attention for myself (I'm pathetic)

Ahmed — Wed, 24 Jun 2026 00:02:11 +0000

I sent 47 CVs in one year and got exactly zero replies.

Not a single rejection email. Not even a "we decided to go in a different direction." Just pure, deafening silence. I was ghosted by every single company I applied to.

I rewrote my CV from scratch. Then rewrote it again. Changed the format, the font, the structure, the summary. I asked friends to review it. I watched YouTube tutorials at 2 AM. I tailored it to each role. I did everything "right."

Nothing.

For twelve months, I refreshed my inbox like it owed me money. I started questioning whether my applications were even going through. Whether I was invisible. Whether I just was not good enough.

Then something broke inside me. Not in a sad way. In a fed-up way.

I stopped asking "why can I not find an internship" and started asking a sharper question: "why am I being ghosted before a human even reads my CV?"

That question changed everything.

I discovered that most of my CVs were being filtered out by ATS systems before they ever reached a recruiter's desk. The problem was never my skills. It was the translation layer between my experience and what the algorithm wanted to see.

So I built the thing I wished existed during my darkest job-search days.

CV Architect is a SaaS tool that optimizes your CV based on the specific job posting you are targeting. It reads your resume the way an employer would. It checks ATS compatibility. It tells you what is missing before you hit send, so you stop screaming into the void.

I did not set out to build a product. I set out to find an internship. But sometimes the struggle itself becomes the solution if you pay close enough attention.

The site is live. You can try it with your own CV right now. And I genuinely want your feedback, the honest kind, the kind that makes the product better.

What is the longest you have ever been ghosted during a job search?

İş İlanına Uygun CV Nasıl Yazılır? AI ile Optimize Et (Türk İş Arayanlar İçin)

Ahmed — Thu, 18 Jun 2026 17:57:37 +0000

Geçen hafta 50 CV'yi analiz ettim.
Cevap buldum: İşe yarayanların hepsi bir şeyi yapıyor — işe yaramayan yüzde 95'i ise hiç yapmıyor.
O şey nedir? CV'lerini iş ilanına göre optimize etmek.

SORUN: GENEL CV YANLIŞ OYUN
Son 5 yıl halkta sık görülen hata:
❌ Bir CV, yüz iş başvurusu

❌ "Profesyonel", "Yaratıcı", "İletişim becerileri var"

❌ Hiç rakam yok — sadece güzel kelimeler

❌ İlan ne istiyor? "Bilmem, ben bu CV'yi çok seviyorum"
Sonuç? Takılan olmayan başvurular, reddedilen mail'ler.
İnsan kaynakları (HR) ortalama 7 saniye bir CV'ye bakıyor. 7 saniye. Onda ilk gözüne çarpan: CV'nin iş ilanı ile uyumunun olup olmadığı.
Eğer CV genel yazılmışsa, HR "Bu kişi bu rol için mi yazıyor, yoksa rasgele yolluyorsa mı?" düşüncesiyle geçiyor.

ÇÖZÜM: İŞ İLANINA ÖZEL CV
İyi haberle başlayalım:
Genel CV'den iş ilanına uygun CV'ye geçmek sadece 15-20 dakika alıyor.
Ama manuel olarak?

İş ilanını oku (5 dakika)
Önemli kelimeleri işaretle (3 dakika)
CV'ni düzenle (10 dakika)
PDF'i indir (2 dakika)

= 20 dakika per başvuru

Haftalık 20 başvuru yapıyorsan?

= 6-7 saat işi harcaman gerekiyor
Burada AI devreye giriyor.

AI İLE CV OPTİMİZASYONU: GERÇEK BİR ÖRNEK
Şunu hayal et:
İŞ İLANI:

Senior Frontend Developer — React + TypeScript

3+ yıl deneyim
Performance optimization
Team leadership preferred

SENIN CV'NDE (ŞU AN):

"Yazılım geliştirici olarak 4 yıl çalıştım.

Ekipte iyi iletişim kurabilirim.

React biliyorum."
AI OPTİMİZE ETTİ SONRA:

"Senior Frontend Developer — 4 yıl deneyim

React & TypeScript ile 50+ production components geliştirdim
Web sayfasında 45% performance improvement sağladım

(Lighthouse score: 38 → 92)
3 kişilik frontend ekibi lead ettim, code reviews yaptım"

Fark görüyor musun?
İlk hali genel, ikinci hali iş ilanına direkt cevap veriyor.
HR 7 saniye içinde: "Tamam, bu adam biliyordu ne yapıyor." deyip ilgisini çekiyor.

İŞ İLANINA UYGUN CV YAZMA ADIMLARI
ADIM 1: İŞ İLANINI DİKKATLİCE OKU
İlan'da şu kelimeleri bul:

Must-have skills: React, Python, SQL vb.
Nice-to-have: Leadership, Agile vb.
KPI'lar: "Haftalık 100+ request handle et" gibi
Problem çözmek: "Ödeme sistemi yavaşlığını fix ettim" gibi

ADIM 2: SENİN CV'NDEN İLGİLİ KISIMLAR ÇIKAR
Tüm CV'ni gönderme. Sadece iş ilanı ile ilgili olanları vurgula.
Örnek:

İlan React istiyor → JavaScript/Frontend section'ı highlight et
Leadership istiyor → Ekip yönetim tecrübeni ön plana çıkar

ADIM 3: SAYILAR EKLE
❌ YANLIŞ:

"Veritabanı performans iyileştirmesi yaptım"
✅ DOĞRU:

"Sorgu optimize ile veritabanı response time'ı 5 saniyeden 500ms'ye düşürdüm (10x improvement)"
Rakamlar = İspat.
ADIM 4: İŞ İLANINDAKİ DİLİ KULLAN
İlan şu kelimeleri kullanıyorsa senin CV'nde de kullan:

"Agile" sıkça geçiyor → senin CV'ne "Scrum" ekle
"Full-stack" istiyor → sen "Frontend" + "Backend" yaz
"Cloud infrastructure" istiyor → "AWS", "Docker" explicit yaz

HR elektronik tarama (Applicant Tracking System - ATS) yapıyor. CV'nde ilanın kelimeleri varsa sistem seni ön sıraya koyuyor.
ADIM 5: PDF İNDİR, GÖNDER
İş ilanına uygun CV'yi PDF'le indir, başvur.

3 SIK YAPILAN HATA
HATA 1: "DEĞERLER" YERİNE "BAŞARILAR"
❌ "İletişim becerileri var"

✅ "Müşteri problemi çözdüğümde 20% daha fazla positive feedback aldım"
HATA 2: GENEL CV HERKESE GÖNDERME
❌ Pazarlama ilanına Frontend CV gönder

✅ CV'deki pazarlama / business impact kısımlarını highlight et
HATA 3: TARİHİ ATLA
❌ "3 yıl deneyim"

✅ "2021-2024: Senior Developer (3 yıl)"
Tarih = Güvenilirlik.

SONUÇ: 7 SANİYE KURALI
HR'nin ilk 7 saniyesinde CV'nin şunları göstermesi lazım:

İLGİLİ SKİLL'LER — iş ilanında yazanlar
SAYILARLA KANIT — neyi başardığın
TARİH VE BAĞLAM — ne zaman, ne kadar süre
İŞ İLANINA CEVAP — sadece ilgili kısımlar

Eğer bu dört elemanı görebilirse HR 7 saniyede "Tamam, görüşmeye çağırmalıyız" diye karar verir.

İŞTE GERÇEK OYUN: AI KIŞAYETME
Ancak şunu biliyorsun: Manuel olarak her iş ilanı için CV optimize etmek saat harcıyor.
20 başvuru = 6-7 saat.
300 başvuru = 90-105 saat = 3 hafta tam zamanlı.
Kimde var 3 hafta?
Burada AI devreye giriyor. Bir AI tool'u (mesela CV Mimarı) kullanırsan:

İş ilanını yapıştır
"Optimize et" butonuna bas
30 saniye sonra: İlanına uygun CV'n hazır
PDF indir, gönder

Süresi? 2 dakika per başvuru. 20 başvuru = 40 dakika.
Fark hissettin mi?

TÜRKÇE İŞ PİYASASI'NDA GERÇEK SONUÇ
2024'te iş bulma oyunu değişti. Eski kurallar:

Bir CV, 100 başvuru
Umarız biri cevap verir
Kaç tane reddedildi? "Bilmem"

Yeni kural:

50 başvuru, 50 farklı CV (her birine optimize)
Cevap oranı 5x yükseliyor
Hatta iş bulduğun zaman daha iyi pozisyon

Neden? Çünkü HR senin CV'sinde "Bu rol için yazıldı" görüyor.

HAZIRSANİZ: İLK ADIM
CV'nizi optimize etmek 15 dakika alıyor. Hatta AI ile 2 dakika.
Şu an bunu yapan Türkçe tool yok — ben de yaptım. CV Mimarı deniyor.
Deneyimek istersen:

3 ücretsiz kredi ile başla
İş ilanına uygun CV'yi gör
Beğenirsen, paket satın al

Hedef: İş bulana kadar seni desteklemek.
Başvuru yağmuruna hazır mısın?

I created a website specifically for my laziness.

Ahmed — Mon, 08 Jun 2026 22:03:52 +0000

I built an AI tool to write LinkedIn posts.

And nobody cared.

Let me tell you the full story because I think it matters.

Three months ago I was sitting in my apartment at 2 AM, convinced I had found a gap in the market. I was spending hours every week trying to write LinkedIn content for my own brand. Staring at blank screens. Rewriting the same sentence fourteen times. Watching other founders post effortlessly while I struggled to string together three coherent paragraphs.

So I thought, what if I just build something to fix this. An AI-powered web app that helps people create LinkedIn posts faster. Smart templates. Tone selection. Hook generators. The whole package.

I went heads down for weeks. Designed the UI. Built the backend. Integrated the AI models. Tweaked the prompts until the output actually sounded human. I was proud of it. Genuinely proud.

Then I launched it.

Crickets.

Not the dramatic kind where you get hate or pushback. The worse kind. Silence. A few sign-ups from friends who never came back. A couple of polite messages saying it looked cool. Zero paying users in the first two weeks.

Here is what I got wrong and I am sharing this because I see other founders making the same mistakes right now.

First, I built in isolation. I never once asked my target audience what they actually needed. I assumed my own pain point was universal. It was not. Some people wanted help with ideas, not full posts. Some wanted editing, not generation. I built for a version of the customer that only existed in my head.

Second, I launched without distribution. I had no audience. No email list. No community. I just put it out there and expected the product to speak for itself. Products do not speak. People do. And I had nobody speaking for mine.

Third, I underestimated how crowded the space already was. There are dozens of LinkedIn content tools. Some backed by real teams with real budgets. I did not take five minutes to ask myself what makes mine genuinely different. The honest answer at launch was nothing.

So what did I do next.

I stopped building features and started having conversations. I reached out to fifty founders and content creators. I asked them to use the tool and tell me everything that was broken, confusing, or unnecessary. The feedback was brutal and exactly what I needed.

I started posting on LinkedIn myself, using my own tool, sharing the messy behind-the-scenes journey. That raw honesty attracted more users than any feature ever did.

Slowly things started shifting. Not overnight. Not dramatically. But the kind of slow traction that actually means something because it is built on real feedback from real people.

The tool is still early. I am still figuring it out. I am not writing this as a success story. I am writing this as a founder who made every classic mistake in the playbook and is trying to learn from each one in public.

If you are building something right now and you have not talked to a single potential customer this week, close your code editor and open a conversation instead.

That is the lesson I paid for with three months of my time.

What is the biggest mistake you made early in building your product? I would genuinely love to hear it.

I Built a Flutter Package for Turkish-Specific Form Validation

Ahmed — Sat, 06 Jun 2026 11:45:02 +0000

I Built a Flutter Package for Turkish-Specific Form Validation

If you've ever built a Flutter app targeting Turkish users, you know the pain.

You need to validate a TC Kimlik No — there's no package for that. You need to format a Turkish IBAN — you end up writing your own regex. You want a proper ₺1.250,50 currency format — good luck finding something ready-made.

So I built it myself: turkish_validators

What's inside

✅ TC Kimlik No Validation

TC Kimlik No has a real checksum algorithm behind it — it's not just "is it 11 digits." This package validates the full algorithm:

bool isValid = TcKimlik.validate('12345678901');

// Drop it straight into a TextFormField
TextFormField(
  validator: TcKimlik.formValidator,
)

✅ Turkish IBAN (MOD-97)

Validates TR IBANs using the MOD-97 standard and formats them for display:

bool isValid = TurkishIban.validate('TR330006100519786457841326');

String formatted = TurkishIban.format('TR330006100519786457841326');
// → TR33 0006 1005 1978 6457 8413 26

TextFormField(
  validator: TurkishIban.formValidator,
)

✅ Turkish Phone Number

Handles both 0532... and +9053... formats, plus clean formatting for display:

bool isValid = TurkishPhone.validate('05321234567');   // true
bool isValid2 = TurkishPhone.validate('+905321234567'); // true

String formatted = TurkishPhone.format('05321234567');
// → 0532 123 45 67

✅ Turkish Lira Formatting

Proper Turkish number format with dot-as-thousands and comma-as-decimal:

String price = TurkishLira.format(1250.5);
// → ₺1.250,50

String price2 = TurkishLira.format(1250.5, showSymbol: false);
// → 1.250,50

double? amount = TurkishLira.parse('₺1.250,50');
// → 1250.50

Installation

dependencies:
  turkish_validators: ^0.0.3

That's it. No extra dependencies — just Flutter.

Why I built this

I kept rewriting the same validators across different projects. TC Kimlik alone has a non-trivial algorithm that I was copy-pasting between apps. IBAN formatting was always a manual job. At some point it just made sense to package it properly.

The Turkish Flutter ecosystem has a lot of talented developers but not many locale-specific utilities. Hopefully this saves someone a few hours.