No sign-up needed to edit. Building, editing and previewing are free; you pay only for the clean PDF.
Download this sample as a PDF (watermarked, free)
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.
Full text of this sample
The sample above as plain text, section by section. Every name, employer and contact detail is fictional, and phone numbers are masked.
Arif Hossain
Software Engineer · Backend (Node.js, Go, PostgreSQL)
Dhaka, Bangladesh · Contact: email, phone, LinkedIn, GitHub, personal website in the header
Summary
Backend software engineer with 3+ years building payment and order services for e-commerce in Bangladesh. Designed APIs that handle 1.2M+ requests a day, led the move of a monolith checkout to services, and mentor two junior engineers. Strong in Node.js, Go and PostgreSQL, with a habit of measuring before optimising. Looking for a senior backend role on a product team.
Experience
Software Engineer (Backend), Nimbus Commerce Ltd.
Feb 2023 – Present · Dhaka
Marketplace serving 900+ sellers; payments and order platform team of 7.
- Split checkout out of a PHP monolith into 3 Node.js services, cutting failed orders during sale campaigns from 4.1% to 0.6%.
- Built a bKash and card payment reconciliation job that matches 40,000+ transactions a night and flags mismatches for finance.
- Reduced p95 latency of the order-status API from 900ms to 210ms with query tuning and a Redis read cache.
- Introduced contract tests between services, catching 20+ breaking changes before release in the first quarter.
- Mentor 2 junior engineers through weekly code reviews and pairing sessions.
Junior Software Engineer, Brightline Labs
Jan 2022 – Jan 2023 · Dhaka
Software agency building web platforms for local and overseas clients.
- Delivered REST APIs for 3 client projects in Go and Node.js, from specification to production.
- Automated deployments with GitHub Actions and Docker, cutting release time from 2 hours to 15 minutes.
- Wrote the monitoring runbook used by a 5-person on-call rotation.
Education
- BSc in Computer Science and Engineering, Khulna University of Engineering & Technology (KUET), Mar 2017 – Dec 2021. CGPA 3.52 / 4.00
Skills
- Languages: JavaScript, TypeScript, Go, SQL
- Backend: Node.js, Express, gRPC, REST API design
- Data: PostgreSQL, Redis, RabbitMQ
- DevOps: Docker, GitHub Actions, AWS (EC2, RDS, S3), Grafana
- Practices: Code review, Automated testing, System design
Projects
Open-source rate limiter for Express
Small middleware library for per-user rate limits backed by Redis. Tools: TypeScript, Redis
- Used in production by 2 local startups; 300+ stars on GitHub.
- Handles 10,000 requests per second on a single Redis instance in benchmarks.
Certifications and training
- AWS Certified Developer – Associate, Amazon Web Services, May 2024
Languages
- Bengali: Native
- English: Professional working proficiency
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.
Career objective and summary examples
Each one fits a different situation. Swap in your own employer, results and tools, and keep only numbers you can explain in an interview.
Backend engineer, about 3 years
Backend engineer with 3 years building payment and order services in Node.js and Go for an e-commerce marketplace in Dhaka. Cut failed checkout orders from 4.1% to 0.6% by splitting a monolith into services, and mentor two junior engineers. Looking for a senior backend role on a product team.
Applying to remote or international roles
Software engineer in Dhaka with 3 years of remote-ready experience: written design docs, async code review across time zones and a production on-call rotation. Built APIs serving 1.2 million requests a day in Node.js and Go. Available for full-time remote work with at least 3 hours of overlap with European working hours.
Senior engineer, 6 years or more
Senior software engineer with 6 years designing high-traffic backend systems for fintech in Bangladesh. Led a team of 5 through a move to event-driven services that halved production incidents in a year. Strong in system design, Go and PostgreSQL, and in hiring and mentoring engineers.
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.
সাধারণ প্রশ্ন
- Should a software engineer CV in Bangladesh have a photo?
- For software roles, usually not. Product companies and remote employers focus on your work, and many international employers prefer CVs without photos. Add one only if the job post asks for it.
- How long should a software engineer CV be?
- One page for up to about three years of experience, two pages beyond that. Cut older or less relevant work before you shrink the font.
- Do I need to list every technology I have touched?
- No. List the ones you could discuss confidently in an interview, with the ones the job asks for first. A long list of tools you used once weakens the rest.
- Should I include competitive programming ratings?
- If they are strong (a good Codeforces rating, an ICPC or IUPC placing), yes, especially early in your career. Otherwise leave them out.