How to Write a CV for a Tech Job in Armenia

A CV for a tech job in Armenia should make your fit easy to assess. Start with the work you want to do, then support it with relevant skills and evidence. Browse current vacancies to understand what employers are asking for before deciding what to include.

What a recruiter needs to find quickly

A recruiter should quickly find your target role, relevant experience, strongest skills, and contact details. Put this information where it is easy to scan, using clear headings and consistent formatting.

Use a working email address and phone number. Add your location and relevant portfolio or repository links. Your headline should identify the role you are seeking. If you are changing direction, make the connection between your previous work and your target role clear.

Choose the language of the posting

English is the default for applications through ttjob.am. In the site's mid-November 2026 snapshot, 225 of 230 Armenia vacancies have an English text.

Prepare an Armenian or Russian CV when the posting is in that language. If the employer gives explicit language instructions, follow them. Keep technical terms consistent and proofread carefully: the reader should understand your experience without having to interpret awkward translations or unexplained abbreviations.

Build a clear structure

Use a predictable structure so the reader can find evidence without searching:

• Contacts and target role: your name, contact details, location, relevant links, and a clear professional headline.
• Short summary: your relevant background, main strengths, and the kind of work you can contribute to. Avoid generic claims about motivation.
• Skills grouped by area: organize programming languages, frameworks, databases, testing tools, or other relevant skills into readable groups.
• Experience: list roles from most recent to earlier work. Describe your responsibilities, personal contribution, and results.
• Projects: include relevant independent, academic, volunteer, or other work that demonstrates practical ability.
• Education: include qualifications and relevant coursework when they help explain your preparation.
• Languages: state your working proficiency honestly, particularly when the role involves communication across teams.

For each experience entry, explain what you worked on, what you did, and what changed. Use measured results when available; otherwise, describe a concrete, verifiable outcome.

Describe your technology stack honestly

A technology list should reflect what you can discuss and demonstrate. Distinguish tools you use independently from those you have only encountered in coursework or tutorials.

Connect important technologies to experience or projects. For example, “Used Python to validate imported records and SQL to prepare reporting queries” gives the reader more context than an isolated list of keywords.

Avoid rating yourself with progress bars or unexplained labels such as “expert.” Describe the work you completed, how independently you worked, and where your knowledge is still developing. Do not imply ownership of an entire system when you contributed to a limited part.

Use projects when experience is limited

If you have little professional experience, give projects enough space to show how you work. Relevant coursework, a useful personal tool, or a contribution to a shared project can provide evidence.

Explain the problem, your contribution, the technologies used, and the outcome. For group work, identify what you personally handled.

Repositories should have clear setup instructions, an explanation of the project, and enough context to understand its limitations. Remove credentials and private information, and share only material you are allowed to publish.

Explore internships and vacancies without an experience requirement, then choose projects that demonstrate the skills those postings request.

Tailor the CV to the vacancy

Read the responsibilities and requirements before editing. Identify the skills that matter most, then make your matching evidence easy to find.

Use the posting's terminology where it accurately describes your experience. Do not add a keyword simply because it appears in the requirements.

Adjust the order of sections and bullets. An experienced applicant may lead with employment history; a newcomer may put relevant projects before unrelated work. Keep your underlying facts consistent across applications, while changing the emphasis to match the role.

Show evidence that fits your role

Different roles need different kinds of detail:

• Developers: describe the component or feature you built, your technical decisions, testing, and contribution to delivery or maintenance.
• QA: explain test planning, manual or automated testing, bug investigation, and how your work improved coverage or release confidence. Match examples to the QA vacancy.
• Data: show how you prepared data, used queries or analysis, checked quality, and communicated findings. For data roles, distinguish reporting, analytics, and model development where relevant.
• Chip design: identify your design or verification discipline, tools, deliverables, and validation work. Connect your evidence to the requirements in chip design and hardware vacancies.
• Non-engineering roles in tech companies: show decisions, deliverables, collaboration, and outcomes relevant to marketing, design, product, project management, or another function. Technical familiarity should support evidence of your core work.

Across roles, describe your contribution precisely and make results understandable to someone outside your immediate team.

Avoid common mistakes

Long lists of technologies without context make it difficult to judge practical experience. Support your strongest skills with examples.

Task descriptions without outcomes leave the reader guessing about your contribution. Explain what your work enabled, improved, delivered, or clarified.

Sending an unchanged CV for every role can bury the most relevant evidence. Remove distracting detail and bring the experience that matches the vacancy closer to the top.

Add a focused cover note

If the application allows a cover note, use it to connect your background to this particular role. Name the position, mention a relevant contribution or project, and explain your interest in the work described.

Keep it short and specific. Avoid repeating the entire CV or making claims you cannot support.

Applications are made on the employer's own page, linked from each vacancy. ttjob.am does not collect CVs, so follow the employer's instructions for submitting your documents and note.

Check before sending

Before submitting, confirm that:

• Your target role and contact details are correct.
• The CV language matches the posting or application instructions.
• Relevant requirements have supporting evidence.
• Technology claims reflect your actual experience.
• Experience and project descriptions identify your contribution and results.
• Dates, role titles, spelling, and formatting are consistent.
• Portfolio and repository links work and contain no private material.
• The exported document opens correctly and its text is readable.
• You have used the requested file format and attached the intended version.

Check any unclear working arrangements or employment terms directly with the employer.