About this sample

This sample is for an engineer with a few years of experience. If you are still a student or a fresh graduate, the order changes: education and projects move above experience. See our guide for BUET, IUT and NSU CSE students for that version.

Notice what the sample leaves out: no objective statement, no photo, no personal details block. Product companies in Dhaka and remote employers abroad judge engineering CVs on what you built and how well, and they read a one-to-two page CV in under a minute.

What recruiters check first

• Impact, not duties. Engineering managers skim for what changed because of you: latency cut, failures reduced, time saved. "Worked on the payment module" says nothing; "cut failed orders from 4.1% to 0.6%" says a lot.
• A stack that matches the job. Recruiters and screening software both look for the languages and tools in the job post. List the ones you have really used in production first, grouped so they can be scanned in seconds.
• Proof you can own work. Mentoring, leading a migration, writing runbooks, being on call: signs that you can be trusted with a system, not just a ticket. One or two such bullets separate a mid-level CV from a junior one.
• Links that work. GitHub and LinkedIn in the header, and a link on any project you mention. Make sure the repositories are public and tidy before you send the CV.

Bullet points: weak vs strong

The same experience, written two ways. The strong version says what was done and what changed because of it. Only use numbers you can explain in an interview.

• Instead of: Responsible for backend development of the checkout system.
  Write: Split checkout out of a PHP monolith into 3 Node.js services, cutting failed orders during sale campaigns from 4.1% to 0.6%.
• Instead of: Worked on improving API performance.
  Write: Reduced p95 latency of the order-status API from 900ms to 210ms with query tuning and a Redis read cache.
• Instead of: Helped junior developers.
  Write: Mentor 2 junior engineers through weekly code reviews and pairing sessions.

Skills to include

List the skills the job circular asks for that you really have, in its own words, grouped so a recruiter can scan them in seconds:

• Languages: JavaScript / TypeScript, Go, Python, SQL
• Backend: Node.js, REST and gRPC API design, Message queues
• Data: PostgreSQL, MySQL, Redis
• DevOps: Docker, CI/CD (GitHub Actions), AWS basics, Monitoring

Format tips

• Keep it to one page if you have under 3 years of experience, two pages at most after that.
• Put your GitHub link in the header and next to each project; recruiters click them.
• Write technologies in plain text, not logos or icons, so screening software can read them.
• State your CGPA for your first two jobs; after that it matters much less and can move lower.
• Tailor the skills block to each job post: the first four items should match what they ask for.