Repository: posquit0/Awesome-CV
Branch: master
Commit: 36075ed034f7
Files: 36
Total size: 128.9 KB
Directory structure:
gitextract_si4y015o/
├── .github/
│ ├── CODEOWNERS
│ ├── dependabot.yml
│ ├── labeler.yaml
│ ├── labels.yaml
│ └── workflows/
│ ├── integration.yaml
│ ├── main.yml
│ ├── pull-request-labeler.yaml
│ ├── sync-labels.yaml
│ └── welcome.yaml
├── .gitignore
├── .yamllint.yaml
├── LICENCE
├── Makefile
├── README.md
├── awesome-cv.cls
└── examples/
├── coverletter.tex
├── cv/
│ ├── certificates.tex
│ ├── committees.tex
│ ├── education.tex
│ ├── experience.tex
│ ├── extracurricular.tex
│ ├── honors.tex
│ ├── presentation.tex
│ ├── skills.tex
│ └── writing.tex
├── cv.tex
├── resume/
│ ├── certificates.tex
│ ├── committees.tex
│ ├── education.tex
│ ├── experience.tex
│ ├── extracurricular.tex
│ ├── honors.tex
│ ├── presentation.tex
│ ├── summary.tex
│ └── writing.tex
└── resume.tex
================================================
FILE CONTENTS
================================================
================================================
FILE: .github/CODEOWNERS
================================================
* @posquit0 @OJFord
================================================
FILE: .github/dependabot.yml
================================================
version: 2
updates:
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "daily"
================================================
FILE: .github/labeler.yaml
================================================
================================================
FILE: .github/labels.yaml
================================================
# Warning
- color: "ee0701"
description: "Categorize bug reports."
name: ":warning: bug"
- color: "ee0701"
description: "Categorize vulnerability reports."
name: ":warning: vulnerability"
# Highlight
- color: "0e8a16"
description: "Good for newcomers."
name: ":fire: good first issue"
- color: "0e8a16"
description: "Extra attention is needed."
name: ":fire: help wanted"
# Cancel
- color: "b60205"
description: "This issue or pull request already exists."
name: ":pray: duplicate"
- color: "b60205"
description: "This will not be worked on."
name: ":pray: wontfix"
# Size
- color: "cfd3d7"
description: "Extra Small size issue or PR."
name: "size/XS"
- color: "cfd3d7"
description: "Small size issue or PR."
name: "size/S"
- color: "cfd3d7"
description: "Medium size issue or PR."
name: "size/M"
- color: "cfd3d7"
description: "Large size issue or PR."
name: "size/L"
- color: "cfd3d7"
description: "Extra Large size issue or PR."
name: "size/XL"
================================================
FILE: .github/workflows/integration.yaml
================================================
name: Integration
on:
push:
branches:
- master
pull_request: {}
concurrency:
group: integration-${{ github.ref }}
cancel-in-progress: true
jobs:
changed:
runs-on: ubuntu-latest
outputs:
yaml_changed: ${{ steps.filter-yaml.outputs.changed }}
yaml_files: ${{ steps.filter-yaml.outputs.files }}
steps:
- name: Checkout
uses: actions/checkout@v6
with:
fetch-depth: 0
- name: Get Changed Files
id: changed-files
uses: dorny/paths-filter@v3
with:
list-files: json
filters: |
yaml:
- '**/*.yaml'
- '**/*.yml'
- name: Filter changed YAML files to outputs
id: filter-yaml
run: |
echo ::set-output name=changed::${{ steps.changed-files.outputs.yaml }}
echo ::set-output name=files::${{ steps.changed-files.outputs.yaml_files }}
yaml:
needs:
- changed
if: ${{ needs.changed.outputs.yaml_changed != 'false' }}
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v6
- name: Lint YAML Files
id: yaml-lint
run: |
yamllint .
================================================
FILE: .github/workflows/main.yml
================================================
name: Compile PDFs
on:
push: {}
pull_request: {}
jobs:
build:
runs-on: ubuntu-latest
container: texlive/texlive:latest
steps:
- name: Checkout repo
uses: actions/checkout@v6
- name: Install fonts
run: |
apt update
apt install --yes \
fonts-roboto \
fonts-adobe-sourcesans3 \
;
- name: Compile
run: make
- uses: actions/upload-artifact@v6
with:
name: examples
path: examples/*.pdf
================================================
FILE: .github/workflows/pull-request-labeler.yaml
================================================
name: Label Pull Requests
on:
- pull_request_target
jobs:
label-pr:
runs-on: ubuntu-latest
steps:
- name: Add Labels for PR
uses: actions/labeler@v6
with:
repo-token: "${{ secrets.GITHUB_TOKEN }}"
configuration-path: .github/labeler.yaml
sync-labels: true
- name: Add PR Size Labels for PR
uses: codelytv/pr-size-labeler@v1
with:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
xs_label: 'size/XS'
xs_max_size: '20'
s_label: 'size/S'
s_max_size: '100'
m_label: 'size/M'
m_max_size: '500'
l_label: 'size/L'
l_max_size: '1000'
xl_label: 'size/XL'
fail_if_xl: 'false'
message_if_xl: >
'This PR has too many changes.
Please make sure you are NOT addressing multiple issues with one PR.'
files_to_ignore: |
"examples/*"
"*.otf"
"*.pdf"
"*.png"
"*.sty"
"*.ttf"
================================================
FILE: .github/workflows/sync-labels.yaml
================================================
name: Sync labels
on:
push:
branches:
- master
paths:
- .github/labels.yaml
jobs:
sync-labels:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v6
- name: Sync labels
uses: crazy-max/ghaction-github-labeler@v5
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
yaml-file: .github/labels.yaml
skip-delete: false
dry-run: false
# exclude: |
================================================
FILE: .github/workflows/welcome.yaml
================================================
name: Welcome for First Issue or Pull Request
on:
pull_request_target:
types:
- opened
issues:
types:
- opened
jobs:
welcome:
runs-on: ubuntu-latest
steps:
- name: Welcome for First Issue or Pull Request
uses: actions/first-interaction@v1
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
issue-message: |
### :wave: Welcome! Looks like this is your first issue.
Hey, thanks for your contribution! Please give us a bit of time to review it. 😄
pr-message: |
### :wave: Welcome! Looks like this is your first pull request.
Hey, thanks for your contribution! Please give us a bit of time to review it. 😄
================================================
FILE: .gitignore
================================================
### TeX ###
## Core latex/pdflatex auxiliary files:
*.aux
*.lof
*.log
*.lot
*.fls
*.out
*.toc
## Intermediate documents:
*.dvi
*-converted-to.*
### Editor ###
## Vim & Emacs temp files:
.*sw[op]
*~
### Mac OS X ###
## Mac OS X metadata files:
*.DS_Store
================================================
FILE: .yamllint.yaml
================================================
yaml-files:
- '*.yaml'
- '*.yml'
rules:
braces:
min-spaces-inside: 0
max-spaces-inside: 1
min-spaces-inside-empty: 0
max-spaces-inside-empty: 0
brackets:
min-spaces-inside: 0
max-spaces-inside: 1
min-spaces-inside-empty: 0
max-spaces-inside-empty: 0
colons:
max-spaces-before: 0
max-spaces-after: 1
commas:
max-spaces-before: 0
comments:
level: warning
require-starting-space: true
min-spaces-from-content: 1
comments-indentation: disable
document-end: disable
document-start: disable
empty-lines:
level: warning
max: 2
max-start: 0
max-end: 1
empty-values:
forbid-in-block-mappings: true
forbid-in-flow-mappings: true
hyphens:
max-spaces-after: 1
indentation:
spaces: consistent
indent-sequences: false
key-duplicates: enable
key-ordering: disable
line-length: disable
new-line-at-end-of-file: enable
# Use UNIX new line characters `\n` instead of DOS new line characters `\r\n`
new-lines:
type: unix
octal-values: disable
quoted-strings:
quote-type: any
required: false
trailing-spaces: enable
truthy: disable
================================================
FILE: LICENCE
================================================
The LaTeX Project Public License
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
LPPL Version 1.3c 2008-05-04
Copyright 1999 2002-2008 LaTeX3 Project
Everyone is allowed to distribute verbatim copies of this
license document, but modification of it is not allowed.
PREAMBLE
========
The LaTeX Project Public License (LPPL) is the primary license under
which the LaTeX kernel and the base LaTeX packages are distributed.
You may use this license for any work of which you hold the copyright
and which you wish to distribute. This license may be particularly
suitable if your work is TeX-related (such as a LaTeX package), but
it is written in such a way that you can use it even if your work is
unrelated to TeX.
The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
below, gives instructions, examples, and recommendations for authors
who are considering distributing their works under this license.
This license gives conditions under which a work may be distributed
and modified, as well as conditions under which modified versions of
that work may be distributed.
We, the LaTeX3 Project, believe that the conditions below give you
the freedom to make and distribute modified versions of your work
that conform with whatever technical specifications you wish while
maintaining the availability, integrity, and reliability of
that work. If you do not see how to achieve your goal while
meeting these conditions, then read the document `cfgguide.tex'
and `modguide.tex' in the base LaTeX distribution for suggestions.
DEFINITIONS
===========
In this license document the following terms are used:
`Work'
Any work being distributed under this License.
`Derived Work'
Any work that under any applicable law is derived from the Work.
`Modification'
Any procedure that produces a Derived Work under any applicable
law -- for example, the production of a file containing an
original file associated with the Work or a significant portion of
such a file, either verbatim or with modifications and/or
translated into another language.
`Modify'
To apply any procedure that produces a Derived Work under any
applicable law.
`Distribution'
Making copies of the Work available from one person to another, in
whole or in part. Distribution includes (but is not limited to)
making any electronic components of the Work accessible by
file transfer protocols such as FTP or HTTP or by shared file
systems such as Sun's Network File System (NFS).
`Compiled Work'
A version of the Work that has been processed into a form where it
is directly usable on a computer system. This processing may
include using installation facilities provided by the Work,
transformations of the Work, copying of components of the Work, or
other activities. Note that modification of any installation
facilities provided by the Work constitutes modification of the Work.
`Current Maintainer'
A person or persons nominated as such within the Work. If there is
no such explicit nomination then it is the `Copyright Holder' under
any applicable law.
`Base Interpreter'
A program or process that is normally needed for running or
interpreting a part or the whole of the Work.
A Base Interpreter may depend on external components but these
are not considered part of the Base Interpreter provided that each
external component clearly identifies itself whenever it is used
interactively. Unless explicitly specified when applying the
license to the Work, the only applicable Base Interpreter is a
`LaTeX-Format' or in the case of files belonging to the
`LaTeX-format' a program implementing the `TeX language'.
CONDITIONS ON DISTRIBUTION AND MODIFICATION
===========================================
1. Activities other than distribution and/or modification of the Work
are not covered by this license; they are outside its scope. In
particular, the act of running the Work is not restricted and no
requirements are made concerning any offers of support for the Work.
2. You may distribute a complete, unmodified copy of the Work as you
received it. Distribution of only part of the Work is considered
modification of the Work, and no right to distribute such a Derived
Work may be assumed under the terms of this clause.
3. You may distribute a Compiled Work that has been generated from a
complete, unmodified copy of the Work as distributed under Clause 2
above, as long as that Compiled Work is distributed in such a way that
the recipients may install the Compiled Work on their system exactly
as it would have been installed if they generated a Compiled Work
directly from the Work.
4. If you are the Current Maintainer of the Work, you may, without
restriction, modify the Work, thus creating a Derived Work. You may
also distribute the Derived Work without restriction, including
Compiled Works generated from the Derived Work. Derived Works
distributed in this manner by the Current Maintainer are considered to
be updated versions of the Work.
5. If you are not the Current Maintainer of the Work, you may modify
your copy of the Work, thus creating a Derived Work based on the Work,
and compile this Derived Work, thus creating a Compiled Work based on
the Derived Work.
6. If you are not the Current Maintainer of the Work, you may
distribute a Derived Work provided the following conditions are met
for every component of the Work unless that component clearly states
in the copyright notice that it is exempt from that condition. Only
the Current Maintainer is allowed to add such statements of exemption
to a component of the Work.
a. If a component of this Derived Work can be a direct replacement
for a component of the Work when that component is used with the
Base Interpreter, then, wherever this component of the Work
identifies itself to the user when used interactively with that
Base Interpreter, the replacement component of this Derived Work
clearly and unambiguously identifies itself as a modified version
of this component to the user when used interactively with that
Base Interpreter.
b. Every component of the Derived Work contains prominent notices
detailing the nature of the changes to that component, or a
prominent reference to another file that is distributed as part
of the Derived Work and that contains a complete and accurate log
of the changes.
c. No information in the Derived Work implies that any persons,
including (but not limited to) the authors of the original version
of the Work, provide any support, including (but not limited to)
the reporting and handling of errors, to recipients of the
Derived Work unless those persons have stated explicitly that
they do provide such support for the Derived Work.
d. You distribute at least one of the following with the Derived Work:
1. A complete, unmodified copy of the Work;
if your distribution of a modified component is made by
offering access to copy the modified component from a
designated place, then offering equivalent access to copy
the Work from the same or some similar place meets this
condition, even though third parties are not compelled to
copy the Work along with the modified component;
2. Information that is sufficient to obtain a complete,
unmodified copy of the Work.
7. If you are not the Current Maintainer of the Work, you may
distribute a Compiled Work generated from a Derived Work, as long as
the Derived Work is distributed to all recipients of the Compiled
Work, and as long as the conditions of Clause 6, above, are met with
regard to the Derived Work.
8. The conditions above are not intended to prohibit, and hence do not
apply to, the modification, by any method, of any component so that it
becomes identical to an updated version of that component of the Work as
it is distributed by the Current Maintainer under Clause 4, above.
9. Distribution of the Work or any Derived Work in an alternative
format, where the Work or that Derived Work (in whole or in part) is
then produced by applying some process to that format, does not relax or
nullify any sections of this license as they pertain to the results of
applying that process.
10. a. A Derived Work may be distributed under a different license
provided that license itself honors the conditions listed in
Clause 6 above, in regard to the Work, though it does not have
to honor the rest of the conditions in this license.
b. If a Derived Work is distributed under a different license, that
Derived Work must provide sufficient documentation as part of
itself to allow each recipient of that Derived Work to honor the
restrictions in Clause 6 above, concerning changes from the Work.
11. This license places no restrictions on works that are unrelated to
the Work, nor does this license place any restrictions on aggregating
such works with the Work by any means.
12. Nothing in this license is intended to, or may be used to, prevent
complete compliance by all parties with all applicable laws.
NO WARRANTY
===========
There is no warranty for the Work. Except when otherwise stated in
writing, the Copyright Holder provides the Work `as is', without
warranty of any kind, either expressed or implied, including, but not
limited to, the implied warranties of merchantability and fitness for a
particular purpose. The entire risk as to the quality and performance
of the Work is with you. Should the Work prove defective, you assume
the cost of all necessary servicing, repair, or correction.
In no event unless required by applicable law or agreed to in writing
will The Copyright Holder, or any author named in the components of the
Work, or any other party who may distribute and/or modify the Work as
permitted above, be liable to you for damages, including any general,
special, incidental or consequential damages arising out of any use of
the Work or out of inability to use the Work (including, but not limited
to, loss of data, data being rendered inaccurate, or losses sustained by
anyone as a result of any failure of the Work to operate with any other
programs), even if the Copyright Holder or said author or said other
party has been advised of the possibility of such damages.
MAINTENANCE OF THE WORK
=======================
The Work has the status `author-maintained' if the Copyright Holder
explicitly and prominently states near the primary copyright notice in
the Work that the Work can only be maintained by the Copyright Holder
or simply that it is `author-maintained'.
The Work has the status `maintained' if there is a Current Maintainer
who has indicated in the Work that they are willing to receive error
reports for the Work (for example, by supplying a valid e-mail
address). It is not required for the Current Maintainer to acknowledge
or act upon these error reports.
The Work changes from status `maintained' to `unmaintained' if there
is no Current Maintainer, or the person stated to be Current
Maintainer of the work cannot be reached through the indicated means
of communication for a period of six months, and there are no other
significant signs of active maintenance.
You can become the Current Maintainer of the Work by agreement with
any existing Current Maintainer to take over this role.
If the Work is unmaintained, you can become the Current Maintainer of
the Work through the following steps:
1. Make a reasonable attempt to trace the Current Maintainer (and
the Copyright Holder, if the two differ) through the means of
an Internet or similar search.
2. If this search is successful, then enquire whether the Work
is still maintained.
a. If it is being maintained, then ask the Current Maintainer
to update their communication data within one month.
b. If the search is unsuccessful or no action to resume active
maintenance is taken by the Current Maintainer, then announce
within the pertinent community your intention to take over
maintenance. (If the Work is a LaTeX work, this could be
done, for example, by posting to comp.text.tex.)
3a. If the Current Maintainer is reachable and agrees to pass
maintenance of the Work to you, then this takes effect
immediately upon announcement.
b. If the Current Maintainer is not reachable and the Copyright
Holder agrees that maintenance of the Work be passed to you,
then this takes effect immediately upon announcement.
4. If you make an `intention announcement' as described in 2b. above
and after three months your intention is challenged neither by
the Current Maintainer nor by the Copyright Holder nor by other
people, then you may arrange for the Work to be changed so as
to name you as the (new) Current Maintainer.
5. If the previously unreachable Current Maintainer becomes
reachable once more within three months of a change completed
under the terms of 3b) or 4), then that Current Maintainer must
become or remain the Current Maintainer upon request provided
they then update their communication data within one month.
A change in the Current Maintainer does not, of itself, alter the fact
that the Work is distributed under the LPPL license.
If you become the Current Maintainer of the Work, you should
immediately provide, within the Work, a prominent and unambiguous
statement of your status as Current Maintainer. You should also
announce your new status to the same pertinent community as
in 2b) above.
WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
======================================================
This section contains important instructions, examples, and
recommendations for authors who are considering distributing their
works under this license. These authors are addressed as `you' in
this section.
Choosing This License or Another License
----------------------------------------
If for any part of your work you want or need to use *distribution*
conditions that differ significantly from those in this license, then
do not refer to this license anywhere in your work but, instead,
distribute your work under a different license. You may use the text
of this license as a model for your own license, but your license
should not refer to the LPPL or otherwise give the impression that
your work is distributed under the LPPL.
The document `modguide.tex' in the base LaTeX distribution explains
the motivation behind the conditions of this license. It explains,
for example, why distributing LaTeX under the GNU General Public
License (GPL) was considered inappropriate. Even if your work is
unrelated to LaTeX, the discussion in `modguide.tex' may still be
relevant, and authors intending to distribute their works under any
license are encouraged to read it.
A Recommendation on Modification Without Distribution
-----------------------------------------------------
It is wise never to modify a component of the Work, even for your own
personal use, without also meeting the above conditions for
distributing the modified component. While you might intend that such
modifications will never be distributed, often this will happen by
accident -- you may forget that you have modified that component; or
it may not occur to you when allowing others to access the modified
version that you are thus distributing it and violating the conditions
of this license in ways that could have legal implications and, worse,
cause problems for the community. It is therefore usually in your
best interest to keep your copy of the Work identical with the public
one. Many works provide ways to control the behavior of that work
without altering any of its licensed components.
How to Use This License
-----------------------
To use this license, place in each of the components of your work both
an explicit copyright notice including your name and the year the work
was authored and/or last substantially modified. Include also a
statement that the distribution and/or modification of that
component is constrained by the conditions in this license.
Here is an example of such a notice and statement:
%% pig.dtx
%% Copyright 2005 M. Y. Name
%
% This work may be distributed and/or modified under the
% conditions of the LaTeX Project Public License, either version 1.3
% of this license or (at your option) any later version.
% The latest version of this license is in
% http://www.latex-project.org/lppl.txt
% and version 1.3 or later is part of all distributions of LaTeX
% version 2005/12/01 or later.
%
% This work has the LPPL maintenance status `maintained'.
%
% The Current Maintainer of this work is M. Y. Name.
%
% This work consists of the files pig.dtx and pig.ins
% and the derived file pig.sty.
Given such a notice and statement in a file, the conditions
given in this license document would apply, with the `Work' referring
to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
referring to any `LaTeX-Format', and both `Copyright Holder' and
`Current Maintainer' referring to the person `M. Y. Name'.
If you do not want the Maintenance section of LPPL to apply to your
Work, change `maintained' above into `author-maintained'.
However, we recommend that you use `maintained', as the Maintenance
section was added in order to ensure that your Work remains useful to
the community even when you can no longer maintain and support it
yourself.
Derived Works That Are Not Replacements
---------------------------------------
Several clauses of the LPPL specify means to provide reliability and
stability for the user community. They therefore concern themselves
with the case that a Derived Work is intended to be used as a
(compatible or incompatible) replacement of the original Work. If
this is not the case (e.g., if a few lines of code are reused for a
completely different task), then clauses 6b and 6d shall not apply.
Important Recommendations
-------------------------
Defining What Constitutes the Work
The LPPL requires that distributions of the Work contain all the
files of the Work. It is therefore important that you provide a
way for the licensee to determine which files constitute the Work.
This could, for example, be achieved by explicitly listing all the
files of the Work near the copyright notice of each file or by
using a line such as:
% This work consists of all files listed in manifest.txt.
in that place. In the absence of an unequivocal list it might be
impossible for the licensee to determine what is considered by you
to comprise the Work and, in such a case, the licensee would be
entitled to make reasonable conjectures as to which files comprise
the Work.
================================================
FILE: Makefile
================================================
.PHONY: examples
CC = lualatex
EXAMPLES_DIR = examples
RESUME_DIR = examples/resume
CV_DIR = examples/cv
RESUME_SRCS = $(shell find $(RESUME_DIR) -name '*.tex')
CV_SRCS = $(shell find $(CV_DIR) -name '*.tex')
examples: $(foreach x, coverletter cv resume, $x.pdf)
resume.pdf: $(EXAMPLES_DIR)/resume.tex $(RESUME_SRCS)
$(CC) -output-directory=$(EXAMPLES_DIR) $<
cv.pdf: $(EXAMPLES_DIR)/cv.tex $(CV_SRCS)
$(CC) -output-directory=$(EXAMPLES_DIR) $<
coverletter.pdf: $(EXAMPLES_DIR)/coverletter.tex
$(CC) -output-directory=$(EXAMPLES_DIR) $<
clean:
rm -rf $(EXAMPLES_DIR)/*.pdf
================================================
FILE: README.md
================================================
<h1 align="center">
<a href="https://github.com/posquit0/Awesome-CV" title="AwesomeCV Documentation">
<img alt="AwesomeCV" src="https://github.com/posquit0/Awesome-CV/raw/master/icon.png" width="200px" height="200px" />
</a>
<br />
Awesome CV
</h1>
<p align="center">
LaTeX template for your outstanding job application
</p>
<div align="center">
<a href="https://www.paypal.me/posquit0">
<img alt="Donate" src="https://img.shields.io/badge/Donate-PayPal-blue.svg" />
</a>
<a href="https://github.com/posquit0/Awesome-CV/actions/workflows/main.yml">
<img alt="GitHub Actions" src="https://github.com/posquit0/Awesome-CV/actions/workflows/main.yml/badge.svg" />
</a>
<a href="https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/resume.pdf">
<img alt="Example Resume" src="https://img.shields.io/badge/resume-pdf-green.svg" />
</a>
<a href="https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/cv.pdf">
<img alt="Example CV" src="https://img.shields.io/badge/cv-pdf-green.svg" />
</a>
<a href="https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/coverletter.pdf">
<img alt="Example Coverletter" src="https://img.shields.io/badge/coverletter-pdf-green.svg" />
</a>
</div>
<br />
## What is Awesome CV?
**Awesome CV** is LaTeX template for a **CV(Curriculum Vitae)**, **Résumé** or **Cover Letter** inspired by [Fancy CV](https://www.sharelatex.com/templates/cv-or-resume/fancy-cv). It is easy to customize your own template, especially since it is really written by a clean, semantic markup.
## Donate
Please help keep this project alive! Donations are welcome and will go towards further development of this project.
PayPal: paypal.me/posquit0
*Thank you for your support!*
## Preview
#### Résumé
You can see [PDF](https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/resume.pdf)
| Page. 1 | Page. 2 |
|:---:|:---:|
| [](https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/resume.pdf) | [](https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/resume.pdf) |
#### Cover Letter
You can see [PDF](https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/coverletter.pdf)
| Without Sections | With Sections |
|:---:|:---:|
| [](https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/coverletter.pdf) | [](https://raw.githubusercontent.com/posquit0/Awesome-CV/master/examples/coverletter.pdf) |
## Quick Start
* [**Edit Résumé on OverLeaf.com**](https://www.overleaf.com/latex/templates/awesome-cv/tvmzpvdjfqxp)
* [**Edit Cover Letter on OverLeaf.com**](https://www.overleaf.com/latex/templates/awesome-cv-cover-letter/pfzzjspkthbk)
**_Note:_ Above services do not guarantee up-to-date source code of Awesome CV**
## How to Use
#### Requirements
A full TeX distribution is assumed. [Various distributions for different operating systems (Windows, Mac, \*nix) are available](http://tex.stackexchange.com/q/55437) but TeX Live is recommended.
You can [install TeX from upstream](https://tex.stackexchange.com/q/1092) (recommended; most up-to-date) or use `sudo apt-get install texlive-full` if you really want that. (It's generally a few years behind.)
If you don't want to install the dependencies on your system, this can also be obtained via [Docker](https://docker.com).
#### Usage
At a command prompt, run
```bash
xelatex {your-cv}.tex
```
Or using docker:
```bash
docker run --rm --user $(id -u):$(id -g) -i -w "/doc" -v "$PWD":/doc texlive/texlive:latest make
```
In either case, this should result in the creation of ``{your-cv}.pdf``
## Credit
[**LaTeX**](https://www.latex-project.org) is a fantastic typesetting program that a lot of people use these days, especially the math and computer science people in academia.
[**FontAwesome6 LaTeX Package**](https://github.com/braniii/fontawesome) is a LaTeX package that provides access to the [Font Awesome 6](https://fontawesome.com/v6/icons) icon set.
[**Roboto**](https://github.com/google/roboto) is the default font on Android and ChromeOS, and the recommended font for Google’s visual language, Material Design.
[**Source Sans Pro**](https://github.com/adobe-fonts/source-sans-pro) is a set of OpenType fonts that have been designed to work well in user interface (UI) environments.
## Contact
You are free to take my `.tex` file and modify it to create your own resume. Please don't use my resume for anything else without my permission, though!
If you have any questions, feel free to join me at [`#posquit0` on Freenode](irc://irc.freenode.net/posquit0) and ask away. Click [here](https://kiwiirc.com/client/irc.freenode.net/posquit0) to connect.
Good luck!
## Maintainers
- [posquit0](https://github.com/posquit0)
- [OJFord](https://github.com/OJFord)
## See Also
* [Awesome Identity](https://github.com/posquit0/hugo-awesome-identity) - A single-page Hugo theme to introduce yourself.
================================================
FILE: awesome-cv.cls
================================================
%% Start of file `awesome-cv.cls'.
% Awesome CV Class File
%
% This class has been downloaded from:
% https://github.com/posquit0/Awesome-CV
%
% Author:
% Claud D. Park <posquit0.bj@gmail.com>
% http://www.posquit0.com
%
% Notes:
% 1) This class file defines the structure and layout of the template file (cv.tex, resume.tex).
% 2) It has been written in such a way that under most circumstances you
% should not need to edit it.
%
% Class license:
% LPPL v1.3c (http://www.latex-project.org/lppl)
%
%-------------------------------------------------------------------------------
% Identification
%-------------------------------------------------------------------------------
\ProvidesClass{awesome-cv}[2017/02/05 v1.6.1 Awesome Curriculum Vitae Class]
\NeedsTeXFormat{LaTeX2e}
%-------------------------------------------------------------------------------
% Class options
%
% (need to be done before the external package loading, for example because
% we need \paperwidth, \paperheight and \@ptsize to be defined before loading
% geometry and fancyhdr)
%-------------------------------------------------------------------------------
% Options for draft or final
\DeclareOption{draft}{\setlength\overfullrule{5pt}}
\DeclareOption{final}{\setlength\overfullrule{0pt}}
% Inherit options of article
\DeclareOption*{%
\PassOptionsToClass{\CurrentOption}{article}
}
\ProcessOptions\relax
\LoadClass{article}
%-------------------------------------------------------------------------------
% 3rd party packages
%-------------------------------------------------------------------------------
% Needed to make fixed length table
\RequirePackage{array}
\RequirePackage{tabularx}
% Needed to handle list environment
\RequirePackage{enumitem}
% Needed to handle text alignment
\RequirePackage{ragged2e}
% Needed to configure page layout
\RequirePackage{geometry}
% Needed to make header & footer efficiently
\RequirePackage{fancyhdr}
% Needed to manage colors
\RequirePackage{xcolor}
% Needed to use \ifxetex-\else-\fi statement
\RequirePackage{ifxetex}
% Needed to use \if-\then-\else statement
\RequirePackage{xifthen}
% Needed to strip chars from telephone number
\RequirePackage{xstring}
% Needed to use a toolbox of programming tools
\RequirePackage{etoolbox}
% Needed to change line spacing in specific environment
\RequirePackage{setspace}
% Needed to manage fonts
\RequirePackage[quiet]{fontspec}
% To support LaTeX quoting style
\defaultfontfeatures{Ligatures=TeX}
% Needed to manage math fonts
\RequirePackage{unicode-math}
% Needed to use icons from font-awesome
\RequirePackage{fontawesome6}
\RequirePackage{accsupp}
\defaultfontfeatures{
Renderer=HarfBuzz,
}
\setmainfont{Source Sans 3}[
UprightFont=*,
ItalicFont=* Italic,
BoldFont=* Bold,
BoldItalicFont=* Bold Italic,
FontFace={l}{n}{Font=* Light},
FontFace={l}{it}{Font=* Light Italic},
]
\setsansfont{Source Sans 3}[
UprightFont=*,
ItalicFont=* Italic,
BoldFont=* Bold,
BoldItalicFont=* Bold Italic,
FontFace={l}{n}{Font=* Light},
FontFace={l}{it}{Font=* Light Italic},
]
\newfontfamily\roboto{Roboto}[
UprightFont=*,
ItalicFont=* Italic,
BoldFont=* Bold,
BoldItalicFont=* Bold Italic,
FontFace={l}{n}{Font=* Light},
FontFace={l}{it}{Font=* Light Italic},
]
% Needed for the photo ID
\RequirePackage[skins]{tcolorbox}
% Needed to deal a paragraphs
\RequirePackage{parskip}
% Needed to deal hyperlink
\RequirePackage[hidelinks,unicode,pdfpagelabels=false]{hyperref}
\hypersetup{%
pdftitle={},
pdfauthor={},
pdfsubject={},
pdfkeywords={}
}
% Solves issues Warning: File `cv.out' has changed
\RequirePackage{bookmark}
%-------------------------------------------------------------------------------
% Configuration for directory locations
%-------------------------------------------------------------------------------
% Configure an optional directory location for fonts(default: 'fonts/')
% Not required anymore but left in place for backward compatability.
\newcommand*{\fontdir}[1][fonts/]{\def\@fontdir{#1}}
%-------------------------------------------------------------------------------
% Configuration for layout
%-------------------------------------------------------------------------------
%% Page Layout
% Configure page margins with geometry
\geometry{left=2.0cm, top=1.5cm, right=2.0cm, bottom=2.0cm, footskip=.5cm}
%% Header & Footer
% Set offset to each header and footer
\fancyhfoffset{0em}
% Remove head rule
\renewcommand{\headrulewidth}{0pt}
% Clear all header & footer fields
\fancyhf{}
% Enable if you want to make header or footer using fancyhdr
\pagestyle{fancy}
%-------------------------------------------------------------------------------
% Configuration for colors
%-------------------------------------------------------------------------------
% Gray-scale colors
\definecolor{white}{HTML}{FFFFFF}
\definecolor{black}{HTML}{000000}
\definecolor{darkgray}{HTML}{333333}
\definecolor{gray}{HTML}{5D5D5D}
\definecolor{lightgray}{HTML}{999999}
% Basic colors
\definecolor{green}{HTML}{C2E15F}
\definecolor{orange}{HTML}{FDA333}
\definecolor{purple}{HTML}{D3A4F9}
\definecolor{red}{HTML}{FB4485}
\definecolor{blue}{HTML}{6CE0F1}
% Text colors
\definecolor{darktext}{HTML}{414141}
\colorlet{text}{darkgray}
\colorlet{graytext}{gray}
\colorlet{lighttext}{lightgray}
\colorlet{sectiondivider}{gray}
% Awesome colors
\definecolor{awesome-emerald}{HTML}{00A388}
\definecolor{awesome-skyblue}{HTML}{0395DE}
\definecolor{awesome-red}{HTML}{DC3522}
\definecolor{awesome-pink}{HTML}{EF4089}
\definecolor{awesome-orange}{HTML}{FF6138}
\definecolor{awesome-nephritis}{HTML}{27AE60}
\definecolor{awesome-concrete}{HTML}{95A5A6}
\definecolor{awesome-darknight}{HTML}{131A28}
\colorlet{awesome}{awesome-red}
% Boolean value to switch section color highlighting
\newbool{acvSectionColorHighlight}
\setbool{acvSectionColorHighlight}{true}
%-------------------------------------------------------------------------------
% Configuration for fonts
%-------------------------------------------------------------------------------
\newcommand*{\headerfont}{\roboto\selectfont}
\newcommand*{\headerfontlight}{\roboto\fontseries{l}\selectfont}
\newcommand*{\footerfont}{\sffamily}
\newcommand*{\bodyfont}{\sffamily}
\newcommand*{\bodyfontlight}{\sffamily\fontseries{l}\selectfont}
%-------------------------------------------------------------------------------
% Configuration for styles
%-------------------------------------------------------------------------------
% Configure styles for each CV elements
% For fundamental structures
\newcommand*{\headerfirstnamestyle}[1]{{\fontsize{32pt}{1em}\headerfontlight\color{graytext} #1}}
\newcommand*{\headerlastnamestyle}[1]{{\fontsize{32pt}{1em}\headerfont\bfseries\color{text} #1}}
\newcommand*{\headerpositionstyle}[1]{{\fontsize{7.6pt}{1em}\bodyfont\scshape\color{awesome} #1}}
\newcommand*{\headeraddressstyle}[1]{{\fontsize{8pt}{1em}\headerfont\itshape\color{lighttext} #1}}
\newcommand*{\headersocialstyle}[1]{{\fontsize{6.8pt}{1em}\headerfont\color{text} #1}}
\newcommand*{\headerquotestyle}[1]{{\fontsize{9pt}{1em}\bodyfont\itshape\color{darktext} #1}}
\newcommand*{\footerstyle}[1]{{\fontsize{8pt}{1em}\footerfont\scshape\color{lighttext} #1}}
\newcommand*{\sectionstyleface}[1]{{\fontsize{16pt}{1em}\bodyfont\bfseries #1}}
\newcommand*{\sectionstyle}[1]{%
\def\@acvSectionTmp{#1}
\ifthenelse{\boolean{acvSectionColorHighlight}}{%
\StrSplit{\@acvSectionTmp}{3}{\acvSectionStringAwesome}{\acvSectionStringPlain}%
\color{awesome}\sectionstyleface{\acvSectionStringAwesome%
\color{text}{\acvSectionStringPlain}}}%
{\color{text}\sectionstyleface{\@acvSectionTmp}}}
\newcommand*{\subsectionstyle}[1]{{\fontsize{12pt}{1em}\bodyfont\scshape\textcolor{text}{#1}}}
\newcommand*{\paragraphstyle}{\fontsize{9pt}{1em}\bodyfontlight\upshape\color{text}}
% For elements of entry
\newcommand*{\entrytitlestyle}[1]{{\fontsize{10pt}{1em}\bodyfont\bfseries\color{darktext} #1}}
\newcommand*{\entrypositionstyle}[1]{{\fontsize{8pt}{1em}\bodyfont\scshape\color{graytext} #1}}
\newcommand*{\entrydatestyle}[1]{{\fontsize{8pt}{1em}\bodyfontlight\slshape\color{graytext} #1}}
\newcommand*{\entrylocationstyle}[1]{{\fontsize{9pt}{1em}\bodyfontlight\slshape\color{awesome} #1}}
\newcommand*{\descriptionstyle}[1]{{\fontsize{9pt}{1em}\bodyfontlight\upshape\color{text} #1}}
% For elements of subentry
\newcommand*{\subentrytitlestyle}[1]{{\fontsize{8pt}{1em}\bodyfont\mdseries\color{graytext} #1}}
\newcommand*{\subentrypositionstyle}[1]{{\fontsize{7pt}{1em}\bodyfont\scshape\color{graytext} #1}}
\newcommand*{\subentrydatestyle}[1]{{\fontsize{7pt}{1em}\bodyfontlight\slshape\color{graytext} #1}}
\newcommand*{\subentrylocationstyle}[1]{{\fontsize{7pt}{1em}\bodyfontlight\slshape\color{awesome} #1}}
\newcommand*{\subdescriptionstyle}[1]{{\fontsize{8pt}{1em}\bodyfontlight\upshape\color{text} #1}}
% For elements of honor
\newcommand*{\honortitlestyle}[1]{{\fontsize{9pt}{1em}\bodyfont\color{graytext} #1}}
\newcommand*{\honorpositionstyle}[1]{{\fontsize{9pt}{1em}\bodyfont\bfseries\color{darktext} #1}}
\newcommand*{\honordatestyle}[1]{{\fontsize{9pt}{1em}\bodyfont\color{graytext} #1}}
\newcommand*{\honorlocationstyle}[1]{{\fontsize{9pt}{1em}\bodyfontlight\slshape\color{awesome} #1}}
% For elements of skill
\newcommand*{\skilltypestyle}[1]{{\fontsize{10pt}{1em}\bodyfont\bfseries\color{darktext} #1}}
\newcommand*{\skillsetstyle}[1]{{\fontsize{9pt}{1em}\bodyfontlight\color{text} #1}}
% For elements of the cover letter
\newcommand*{\lettersectionstyleface}[1]{{\fontsize{14pt}{1em}\bodyfont\bfseries #1}}
\newcommand*{\lettersectionstyle}[1]{%
\def\@acvLetterSectionTmp{#1}
\ifthenelse{\boolean{acvSectionColorHighlight}}{%
\StrSplit{\@acvLetterSectionTmp}{3}{\acvLetterSectionStringAwesome}{\acvLetterSectionStringPlain}%
\color{awesome}\sectionstyleface{\acvLetterSectionStringAwesome%
\color{text}{\acvLetterSectionStringPlain}}}%
{\color{text}\lettersectionstyleface{\@acvLetterSectionTmp}}}
\newcommand*{\recipientaddressstyle}[1]{{\fontsize{9pt}{1em}\bodyfont\scshape\color{graytext} #1}}
\newcommand*{\recipienttitlestyle}[1]{{\fontsize{11pt}{1em}\bodyfont\bfseries\color{darktext} #1}}
\newcommand*{\lettertitlestyle}[1]{{\fontsize{10pt}{1em}\bodyfontlight\bfseries\color{darktext} \underline{#1}}}
\newcommand*{\letterdatestyle}[1]{{\fontsize{9pt}{1em}\bodyfontlight\slshape\color{graytext} #1}}
\newcommand*{\lettertextstyle}{\fontsize{10pt}{1.4em}\bodyfontlight\upshape\color{graytext}}
\newcommand*{\letternamestyle}[1]{{\fontsize{10pt}{1em}\bodyfont\bfseries\color{darktext} #1}}
\newcommand*{\letterenclosurestyle}[1]{{\fontsize{10pt}{1em}\bodyfontlight\slshape\color{lighttext} #1}}
%-------------------------------------------------------------------------------
% Commands for personal information
%-------------------------------------------------------------------------------
% Define photo ID
% Usage: \photo[circle|rectangle,edge|noedge,left|right]{<path-to-image>}
\newcommand{\photo}[2][circle,edge,left]{%
\def\@photo{#2}
\@for\tmp:=#1\do{%
\ifthenelse{\equal{\tmp}{circle} \or \equal{\tmp}{rectangle}}%
{\let\@photoshape\tmp}{}%
\ifthenelse{\equal{\tmp}{edge} \or \equal{\tmp}{noedge}}%
{\let\@photoedge\tmp}{}%
\ifthenelse{\equal{\tmp}{left} \or \equal{\tmp}{right}}%
{\let\@photoalign\tmp}{}%
}%
}
\def\@photoshape{circle}
\def\@photoedge{edge}
\def\@photoalign{left}
% Define writer's name
% Usage: \name{<firstname>}{<lastname>}
% Usage: \firstname{<firstname>}
% Usage: \lastname{<lastname>}
% Usage: \familyname{<familyname>}
\newcommand*{\name}[2]{\def\@firstname{#1}\def\@lastname{#2}}
\newcommand*{\firstname}[1]{\def\@firstname{#1}}
\newcommand*{\lastname}[1]{\def\@lastname{#1}}
\newcommand*{\familyname}[1]{\def\@lastname{#1}}
\def\@familyname{\@lastname}
% Define writer's address
% Usage: \address{<address>}
\newcommand*{\address}[1]{\def\@address{#1}}
% Define writer's position
% Usage: \position{<position>}
\newcommand*{\position}[1]{\def\@position{#1}}
% Defines writer's mobile (optional)
% Usage: \mobile{<mobile number>}
\newcommand*{\mobile}[1]
{
\def\@mobile{#1}
\def\@teluri{tel:\@mobile}
% Strip unwanted characters
\StrDel{\@teluri}{ }[\@teluri]%
\StrDel{\@teluri}{-}[\@teluri]%
\StrDel{\@teluri}{(}[\@teluri]%
\StrDel{\@teluri}{)}[\@teluri]%
}
% Defines writer's WhatsApp (optional)
% Usage: \whatsapp{<mobile number>}
\newcommand*{\whatsapp}[1]
{
\def\@whatsapp{#1}
\def\@wameuri{https://wa.me/\@whatsapp}
% Strip unwanted characters
\StrDel{\@wameuri}{ }[\@wameuri]%
\StrDel{\@wameuri}{+}[\@wameuri]%
\StrDel{\@wameuri}{-}[\@wameuri]%
\StrDel{\@wameuri}{(}[\@wameuri]%
\StrDel{\@wameuri}{)}[\@wameuri]%
}
% Defines writer's email (optional)
% Usage: \email{<email address>}
\newcommand*{\email}[1]{\def\@email{#1}}
% Defines writer's date of birth (optional)
% Usage: \dateofbirth{<date>}
\newcommand*{\dateofbirth}[1]{\def\@dateofbirth{#1}}
% Defines writer's homepage (optional)
% Usage: \homepage{<url>}
\newcommand*{\homepage}[1]{\def\@homepage{#1}}
% Defines writer's github (optional)
% Usage: \github{<github-nick>}
\newcommand*{\github}[1]{\def\@github{#1}}
% Defines writer's gitlab (optional)
% Usage: \gitlab{<gitlab-nick>}
\newcommand*{\gitlab}[1]{\def\@gitlab{#1}}
% Defines writer's bitbucket (optional)
% Usage: \bitbucket{<bitbucket-nick>}
\newcommand*{\bitbucket}[1]{\def\@bitbucket{#1}}
% Defines writer's stackoverflow profile (optional)
% Usage: \stackoverflow{<so userid>}{<so username>}
% e.g.https://stackoverflow.com/users/123456/sam-smith
% would be \stackoverflow{123456}{sam-smith}
\newcommand*{\stackoverflow}[2]{\def\@stackoverflowid{#1}\def\@stackoverflowname{#2}}
% Defines writer's linked-in (optional)
% Usage: \linkedin{<linked-in-nick>}
\newcommand*{\linkedin}[1]{\def\@linkedin{#1}}
% Defines writer's orcid (optional)
% Usage: \orcid{<orcid-num>}
\newcommand*{\orcid}[1]{\def\@orcid{#1}}
% Defines writer's twitter (optional)
% Usage: \twitter{<twitter handle>}
\newcommand*{\twitter}[1]{\def\@twitter{#1}}
% Defines writer's x (formerly twitter) (optional)
% Usage: \x{<x account>}
\newcommand*{\x}[1]{\def\@x{#1}}
% Defines writer's Mastodon (optional)
% Usage: \mastodon{<instance>}{<mastodon-nick>}
\newcommand*{\mastodon}[2]{\def\@mastodoninstance{#1}\def\@mastodonname{#2}}
% Defines writer's resarchgate (optional)
% Usage: \researchgate{<researchgate-account>}
\newcommand*{\researchgate}[1]{\def\@researchgate{#1}}
% Defines writer's skype (optional)
% Usage: \skype{<skype account>}
\newcommand*{\skype}[1]{\def\@skype{#1}}
% Defines writer's reddit (optional)
% Usage: \reddit{<reddit account>}
\newcommand*{\reddit}[1]{\def\@reddit{#1}}
% Defines writer's xing (optional)
% Usage: \xing{<xing name>}
\newcommand*{\xing}[1]{\def\@xing{#1}}
% Defines writer's medium profile (optional)
% Usage: \medium{<medium account>}
\newcommand*{\medium}[1]{\def\@medium{#1}}
% Defines writer's kaggle (optional)
% Usage: \kaggle{<kaggle handle>}
\newcommand*{\kaggle}[1]{\def\@kaggle{#1}}
% Defines writer's Hackerrank (optional)
% Usage: \hackerrank{<Hackerrank profile name>}
\newcommand*{\hackerrank}[1]{\def\@hackerrank{#1}}
% Defines writer's Telegram (optional)
% Usage: \telegram{<Telegram username>}
\newcommand*{\telegram}[1]{\def\@telegram{#1}}
% Defines writer's google scholar profile (optional)
% Usage: \googlescholar{<googlescholar userid>}{<googlescholar username>}
% e.g.https://scholar.google.co.uk/citations?user=wpZDx1cAAAAJ
% would be \googlescholar{wpZDx1cAAAAJ}{Name-to-display-next-icon}
% If 'googlescholar-name' is not provided than it defaults to
% '\firstname \lastname'
\newcommand*{\googlescholar}[2]{%
\def\@googlescholarid{#1}%
\ifthenelse{\equal{#2}{}}{%
\def\@googlescholarname{\@firstname~\@lastname}%
}{%
\def\@googlescholarname{#2}%
}%
}
% Defines writer's extra information (optional)
% Usage: \extrainfo{<extra information>}
\newcommand*{\extrainfo}[1]{\def\@extrainfo{#1}}
% Defines writer's quote (optional)
% Usage: \quote{<quote>}
\renewcommand*{\quote}[1]{\def\@quote{#1}}
% Defines recipient's information (cover letter only)
% Usage: \recipient{<recipient name>}{<recipient address>}
% Usage: \recipientname{<recipient name>}
% Usage: \recipientaddress{<recipient address>}
\newcommand*{\recipient}[2]{\def\@recipientname{#1}\def\@recipientaddress{#2}}
\newcommand*{\recipientname}[1]{\def\@recipientname{#1}}
\newcommand*{\recipientaddress}[1]{\def\@recipientaddress{#1}}
% Defines the title for letter (cover letter only, optional)
% Usage: \lettertitle{<title>}
\newcommand*{\lettertitle}[1]{\def\@lettertitle{#1}}
% Defines the date for letter (cover letter only)
% Usage: \letterdate{<date>}
\newcommand*{\letterdate}[1]{\def\@letterdate{#1}}
% Defines a message of opening for letter (cover letter only)
% Usage: \letteropening{<message>}
\newcommand*{\letteropening}[1]{\def\@letteropening{#1}}
% Defines a message of closing for letter (cover letter only)
% Usage: \letterclosing{<message>}
\newcommand*{\letterclosing}[1]{\def\@letterclosing{#1}}
% Defines an enclosure for letter (cover letter only, optional)
% Usage: \letterenclosure[<enclosure name>]{<enclosure>}
\newcommand*{\letterenclname}[1][Enclosure]{\def\@letterenclname{#1}}
\newcommand*{\letterenclosure}[2][]{%
% if an optional argument is provided, use it to redefine \enclname
\ifthenelse{\equal{#1}{}}{}{\def\@letterenclname{#1}}
\def\@letterenclosure{#2}
}
%-------------------------------------------------------------------------------
% Commands for extra
%-------------------------------------------------------------------------------
%% Define helper macros a user can change easily
% Header
\newcommand{\acvHeaderNameDelim}{\space}
\newcommand{\acvHeaderAfterNameSkip}{.4mm}
\newcommand{\acvHeaderAfterPositionSkip}{.4mm}
\newcommand{\acvHeaderAfterAddressSkip}{-.5mm}
\newcommand{\acvHeaderIconSep}{\space}
\newcommand{\acvHeaderSocialSep}{\BeginAccSupp{ActualText={}}\quad\textbar\quad\EndAccSupp{}}
\newcommand{\acvHeaderAfterSocialSkip}{6mm}
\newcommand{\acvHeaderAfterQuoteSkip}{5mm}
% Others
\newcommand{\acvSectionTopSkip}{3mm}
\newcommand{\acvSectionContentTopSkip}{2.5mm}
%-------------------------------------------------------------------------------
% Commands for utilities
%-------------------------------------------------------------------------------
% Use to align an element of tabular table
\renewcommand{\tabularxcolumn}{p}
\newcolumntype{L}[1]{>{\raggedright\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
\newcolumntype{C}[1]{>{\centering\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
\newcolumntype{R}[1]{>{\raggedleft\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
% Use to draw horizontal line with specific thickness
\def\vhrulefill#1{\leavevmode\leaders\hrule\@height#1\hfill \kern\z@}
% Use to execute conditional statements by checking empty string
\newcommand*{\ifempty}[3]{\ifthenelse{\isempty{#1}}{#2}{#3}}
\newcommand{\faAlt}[3]{%
\BeginAccSupp{ActualText={#1}}%
\mbox{#2\acvHeaderIconSep#3}%
\EndAccSupp{}%
}
%-------------------------------------------------------------------------------
% Commands for elements of CV structure
%-------------------------------------------------------------------------------
% Define a header for CV
% Usage: \makecvheader
\newcommand*{\makecvheader}[1][C]{%
\newcommand*{\drawphoto}{%
\ifthenelse{\isundefined{\@photo}}{}{%
\newlength{\photodim}
\ifthenelse{\equal{\@photoshape}{circle}}%
{\setlength{\photodim}{1.3cm}}%
{\setlength{\photodim}{1.8cm}}%
\ifthenelse{\equal{\@photoedge}{edge}}%
{\def\@photoborder{darkgray}}%
{\def\@photoborder{none}}%
\begin{tikzpicture}%
\node[\@photoshape, draw=\@photoborder, line width=0.3mm, inner sep=\photodim, fill overzoom image=\@photo] () {};
\end{tikzpicture}
}%
}
\newlength{\headertextwidth}
\newlength{\headerphotowidth}
\ifthenelse{\isundefined{\@photo}}{
\setlength{\headertextwidth}{\textwidth}
\setlength{\headerphotowidth}{0cm}
}{%
\setlength{\headertextwidth}{0.76\textwidth}
\setlength{\headerphotowidth}{0.24\textwidth}
}%
\begin{minipage}[c]{\headerphotowidth}%
\ifthenelse{\equal{\@photoalign}{left}}{\raggedright\drawphoto}{}
\end{minipage}
\begin{minipage}[c]{\headertextwidth}
\ifthenelse{\equal{#1}{L}}{\raggedright}{\ifthenelse{\equal{#1}{R}}{\raggedleft}{\centering}}
\headerfirstnamestyle{\@firstname}\headerlastnamestyle{{}\acvHeaderNameDelim\@lastname}%
\\[\acvHeaderAfterNameSkip]%
\ifthenelse{\isundefined{\@position}}{}{\headerpositionstyle{\@position\\[\acvHeaderAfterPositionSkip]}}%
\ifthenelse{\isundefined{\@address}}{}{\headeraddressstyle{\@address\\[\acvHeaderAfterAddressSkip]}}%
\headersocialstyle{%
\newbool{isstart}%
\setbool{isstart}{true}%
\ifthenelse{\isundefined{\@mobile}}%
{}%
{%
\href{\@teluri}{\faAlt{tel:\@mobile}{\faMobile}{\@mobile}}%
\setbool{isstart}{false}%
}%
\ifthenelse{\isundefined{\@whatsapp}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{\@wameuri}{\faAlt{WhatsApp: \@whatsapp}{\faSquareWhatsapp}{\@whatsapp}}%
}%
\ifthenelse{\isundefined{\@email}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{mailto:\@email}{\faAlt{mailto:\@email}{\faEnvelope}{\@email}}%
}%
\ifthenelse{\isundefined{\@dateofbirth}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\faAlt{DoB: \@dateofbirth}{\faCakeCandles}{\@dateofbirth}%
}%
\ifthenelse{\isundefined{\@homepage}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{\@homepage}{\faAlt{homepage: \@homepage}{\faHouseChimney}{\@homepage}}%
}%
\ifthenelse{\isundefined{\@github}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://github.com/\@github}{\faAlt{GitHub: @\@github}{\faSquareGithub}{\@github}}%
}%
\ifthenelse{\isundefined{\@gitlab}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://gitlab.com/\@gitlab}{\faAlt{GitLab: @\@gitlab}{\faGitlab}{\@gitlab}}%
}%
\ifthenelse{\isundefined{\@bitbucket}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://bitbucket.com/\@bitbucket}{\faAlt{BitBucket: @\@bitbucket}{\faBitbucket}{\@bitbucket}}%
}%
\ifthenelse{\isundefined{\@stackoverflowid}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://stackoverflow.com/users/\@stackoverflowid}{\faAlt{StackOverflow: @\@stackoverflowname}{\faStackOverflow}{\@stackoverflowname}}%
}%
\ifthenelse{\isundefined{\@linkedin}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://www.linkedin.com/in/\@linkedin}{\faAlt{LinkedIn: /in/\@linkedin}{\faLinkedin}{\@linkedin}}%
}%
\ifthenelse{\isundefined{\@orcid}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://orcid.org/\@orcid}{\faAlt{OrcID: \@orcid}{\faOrcid}{\@orcid}}%
}%
\ifthenelse{\isundefined{\@twitter}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://twitter.com/\@twitter}{\faAlt{Twitter: @\@twitter}{\faTwitter}{\@twitter}}%
}%
\ifthenelse{\isundefined{\@x}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://x.com/\@x}{\faAlt{X: @\@x}{\faXTwitter}{\@x}}%
}%
\ifthenelse{\isundefined{\@mastodonname}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://\@mastodoninstance/@\@mastodonname}{\faAlt{Mastodon: \@mastodonname{}@\@mastodoninstance}{\faMastodon}{\@mastodonname}}%
}%
\ifthenelse{\isundefined{\@skype}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\faAlt{Skype: \@skype}{\faSkype}{\@skype}%
}%
\ifthenelse{\isundefined{\@reddit}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://www.reddit.com/user/\@reddit}{\faAlt{Reddit: /u/\@reddit}{\faReddit}{\@reddit}}%
}%
\ifthenelse{\isundefined{\@researchgate}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://www.researchgate.net/profile/\@researchgate}{\faAlt{ResearchGate: \@researchgate}{\faResearchgate}{\@researchgate}}%
}%
\ifthenelse{\isundefined{\@xing}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://www.xing.com/profile/\@xing}{\faAlt{Xing: \@xing}{\faSquareXing}{\@xing}}
}%
\ifthenelse{\isundefined{\@medium}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://medium.com/@\@medium}{\faAlt{Medium: @\@medium}{\faMedium}{\@medium}}%
}%
\ifthenelse{\isundefined{\@kaggle}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://kaggle.com/\@kaggle}{\faAlt{Kaggle: \@kaggle}{\faKaggle}{\@kaggle}}%
}%
\ifthenelse{\isundefined{\@hackerrank}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://www.hackerrank.com/\@hackerrank}{\faAlt{HackerRank: \@hackerrank}{\faHackerrank}{\@hackerrank}}%
}%
\ifthenelse{\isundefined{\@telegram}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://t.me/\@telegram}{\faAlt{Telegram: \@telegram}{\faTelegram}{\@telegram}}%
}%
\ifthenelse{\isundefined{\@googlescholarid}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\href{https://scholar.google.com/citations?user=\@googlescholarid}{\faAlt{Google Scholar: \@googlescholarid}{\faGraduationCap}{\@googlescholarname}}%
}%
\ifthenelse{\isundefined{\@extrainfo}}%
{}%
{%
\ifbool{isstart}{\setbool{isstart}{false}}{\acvHeaderSocialSep}%
\@extrainfo%
}%
} \\[\acvHeaderAfterSocialSkip]%
\ifthenelse{\isundefined{\@quote}}%
{}%
{\headerquotestyle{\@quote\\}\vspace{\acvHeaderAfterQuoteSkip}}%
\end{minipage}%
\begin{minipage}[c]{\headerphotowidth}%
\ifthenelse{\equal{\@photoalign}{right}}{\raggedleft\drawphoto}{}
\end{minipage}
}
% Define a footer for CV
% Usage: \makecvfooter{<left>}{<center>}{<right>}
\newcommand*{\makecvfooter}[3]{%
\fancyfoot{}
\fancyfoot[L]{\footerstyle{#1}}
\fancyfoot[C]{\footerstyle{#2}}
\fancyfoot[R]{\footerstyle{#3}}
}
% Define a section for CV
% Usage: \cvsection{<section-title>}
\newcommand{\cvsection}[1]{%
\vspace{\acvSectionTopSkip}
\sectionstyle{#1}
\phantomsection
\color{sectiondivider}\vhrulefill{0.9pt}
}
% Define a subsection for CV
% Usage: \cvsubsection{<subsection-title>}
\newcommand{\cvsubsection}[1]{%
\vspace{\acvSectionContentTopSkip}
\vspace{-3mm}
\subsectionstyle{#1}
\phantomsection
}
% Define a paragraph for CV
\newenvironment{cvparagraph}{%
\vspace{\acvSectionContentTopSkip}
\vspace{-3mm}
\paragraphstyle
}{%
\par
\vspace{2mm}
}
% Define an environment for cventry
\newenvironment{cventries}{%
\vspace{\acvSectionContentTopSkip}
\begin{center}
}{%
\end{center}
}
% Define an entry of cv information
% Usage: \cventry{<position>}{<title>}{<location>}{<date>}{<description>}
\newcommand*{\cventry}[5]{%
\vspace{-2.0mm}
\setlength\tabcolsep{0pt}
\setlength{\extrarowheight}{0pt}
\begin{tabular*}{\textwidth}{@{\extracolsep{\fill}} L{\textwidth - 4.5cm} R{4.5cm}}
\ifempty{#2#3}
{\entrypositionstyle{#1} & \entrydatestyle{#4} \\}
{\entrytitlestyle{#2} & \entrylocationstyle{#3} \\
\entrypositionstyle{#1} & \entrydatestyle{#4} \\}
\ifstrempty{#5}
{}
{\multicolumn{2}{L{\textwidth}}{\descriptionstyle{#5}} \\}
\end{tabular*}%
}
% Define an environment for cvsubentry
\newenvironment{cvsubentries}{%
\begin{center}
}{%
\end{center}
}
% Define a subentry of cv information
% Usage: \cvsubentry{<position>}{<title>}{<date>}{<description>}
\newcommand*{\cvsubentry}[4]{%
\setlength\tabcolsep{0pt}
\setlength{\extrarowheight}{0pt}
\begin{tabular*}{\textwidth}{@{\extracolsep{\fill}} L{\textwidth - 4.5cm} R{4.5cm}}
\setlength\leftskip{0.2cm}
\subentrytitlestyle{#2} & \ifthenelse{\equal{#1}{}}
{\subentrydatestyle{#3}}{}
\ifthenelse{\equal{#1}{}}
{}
{\subentrypositionstyle{#1} & \subentrydatestyle{#3} \\}
\ifthenelse{\equal{#4}{}}
{}
{\multicolumn{2}{L{17.0cm}}{\subdescriptionstyle{#4}} \\}
\end{tabular*}
}
% Define an environment for cvhonor
\newenvironment{cvhonors}{%
\vspace{\acvSectionContentTopSkip}
\vspace{-2mm}
\begin{center}
\setlength\tabcolsep{0pt}
\setlength{\extrarowheight}{0pt}
\begin{tabular*}{\textwidth}{@{\extracolsep{\fill}} C{1.5cm} L{\textwidth - 4.0cm} R{2.5cm}}
}{%
\end{tabular*}
\end{center}
}
% Define a line of cv information(honor, award or something else)
% Usage: \cvhonor{<position>}{<title>}{<location>}{<date>}
\newcommand*{\cvhonor}[4]{%
\honordatestyle{#4} & \honorpositionstyle{#1}\ifempty{#2}{}{,} \honortitlestyle{#2} & \honorlocationstyle{#3} \\
}
% Define an environment for cvskill
\newenvironment{cvskills}{%
\vspace{\acvSectionContentTopSkip}
\vspace{-2.0mm}
\setlength\tabcolsep{1ex}
\setlength{\extrarowheight}{0pt}
\tabularx{\textwidth}{r>{\raggedright\let\newline\\\arraybackslash\hspace{0pt}}X}
}{%
\endtabularx\par
}
% Define a line of cv information(skill)
% Usage: \cvskill{<type>}{<skillset>}
\newcommand*{\cvskill}[2]{%
\skilltypestyle{#1} & \leavevmode\skillsetstyle{#2} \\
}
% Define an environment for cvitems(for cventry)
\newenvironment{cvitems}{%
\vspace{-4.0mm}
\begin{justify}
\begin{itemize}[leftmargin=2ex, nosep, noitemsep]
\setlength{\parskip}{0pt}
\renewcommand{\labelitemi}{\bullet}
}{%
\end{itemize}
\end{justify}
\vspace{1.0mm}
}
%-------------------------------------------------------------------------------
% Commands for elements of Cover Letter
%-------------------------------------------------------------------------------
% Define an environment for cvletter
\newenvironment{cvletter}{%
\lettertextstyle
}{%
}
% Define a section for the cover letter
% Usage: \lettersection{<section-title>}
\newcommand{\lettersection}[1]{%
\par\addvspace{2.5ex}
\phantomsection{}
\lettersectionstyle{#1}
\color{sectiondivider}\vhrulefill{0.9pt}
\par\nobreak\addvspace{0.4ex}
\lettertextstyle
}
% Define a title of the cover letter
% Usage: \makelettertitle
\newcommand*{\makelettertitle}{%
\vspace{8.4mm}
\setlength\tabcolsep{0pt}
\setlength{\extrarowheight}{0pt}
\begin{tabular*}{\textwidth}{@{\extracolsep{\fill}} L{\textwidth - 4.5cm} R{4.5cm}}
\recipienttitlestyle{\@recipientname} & \letterdatestyle{\@letterdate}
\end{tabular*}
\begin{singlespace}
\recipientaddressstyle{\@recipientaddress} \\\\
\end{singlespace}
\ifthenelse{\isundefined{\@lettertitle}}
{}
{\lettertitlestyle{\@lettertitle} \\}
\lettertextstyle{\@letteropening}
}
% Define a closing of the cover letter
% Usage: \makeletterclosing
\newcommand*{\makeletterclosing}{%
\vspace{3.4mm}
\lettertextstyle{\@letterclosing} \\\\
\letternamestyle{\@firstname\ \@lastname}
\ifthenelse{\isundefined{\@letterenclosure}}
{\\}
{%
\\\\\\
\letterenclosurestyle{\@letterenclname: \@letterenclosure} \\
}
}
================================================
FILE: examples/coverletter.tex
================================================
%!TEX TS-program = xelatex
%!TEX encoding = UTF-8 Unicode
% Awesome CV LaTeX Template for Cover Letter
%
% This template has been downloaded from:
% https://github.com/posquit0/Awesome-CV
%
% Authors:
% Claud D. Park <posquit0.bj@gmail.com>
% Lars Richter <mail@ayeks.de>
%
% Template license:
% CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/)
%
%-------------------------------------------------------------------------------
% CONFIGURATIONS
%-------------------------------------------------------------------------------
% A4 paper size by default, use 'letterpaper' for US letter
\documentclass[11pt, a4paper]{awesome-cv}
% Configure page margins with geometry
\geometry{left=1.4cm, top=.8cm, right=1.4cm, bottom=1.8cm, footskip=.5cm}
% Color for highlights
% Awesome Colors: awesome-emerald, awesome-skyblue, awesome-red, awesome-pink, awesome-orange
% awesome-nephritis, awesome-concrete, awesome-darknight
\colorlet{awesome}{awesome-red}
% Uncomment if you would like to specify your own color
% \definecolor{awesome}{HTML}{CA63A8}
% Colors for text
% Uncomment if you would like to specify your own color
% \definecolor{darktext}{HTML}{414141}
% \definecolor{text}{HTML}{333333}
% \definecolor{graytext}{HTML}{5D5D5D}
% \definecolor{lighttext}{HTML}{999999}
% \definecolor{sectiondivider}{HTML}{5D5D5D}
% Set false if you don't want to highlight section with awesome color
\setbool{acvSectionColorHighlight}{true}
% If you would like to change the social information separator from a pipe (|) to something else
\renewcommand{\acvHeaderSocialSep}{\quad\textbar\quad}
%-------------------------------------------------------------------------------
% PERSONAL INFORMATION
% Comment any of the lines below if they are not required
%-------------------------------------------------------------------------------
% Available options: circle|rectangle,edge/noedge,left/right
\photo[circle,noedge,left]{./examples/profile}
\name{Claud D.}{Park}
\position{Site Reliability Engineer{\enskip\cdotp\enskip}Software Architect}
\address{235, World Cup buk-ro, Mapo-gu, Seoul, 03936, Republic of Korea}
\mobile{(+82) 10-9030-1843}
%\whatsapp{(+82) 10-9030-1843}
\email{posquit0.bj@gmail.com}
%\dateofbirth{January 1st, 1970}
\homepage{www.posquit0.com}
\github{posquit0}
\linkedin{posquit0}
% \gitlab{gitlab-id}
% \stackoverflow{SO-id}{SO-name}
% \twitter{@twit}
% \x{x-id}
% \skype{skype-id}
% \reddit{reddit-id}
% \medium{madium-id}
% \kaggle{kaggle-id}
% \hackerrank{hackerrank-id}
% \telegram{telegram-username}
% \googlescholar{googlescholar-id}{name-to-display}
%% \firstname and \lastname will be used
% \googlescholar{googlescholar-id}{}
% \extrainfo{extra information}
\quote{``Be the change that you want to see in the world."}
%-------------------------------------------------------------------------------
% LETTER INFORMATION
% All of the below lines must be filled out
%-------------------------------------------------------------------------------
% The company being applied to
\recipient
{Company Recruitment Team}
{Google Inc.\\1600 Amphitheatre Parkway\\Mountain View, CA 94043}
% The date on the letter, default is the date of compilation
\letterdate{\today}
% The title of the letter
\lettertitle{Job Application for Software Engineer}
% How the letter is opened
\letteropening{Dear Mr./Ms./Dr. LastName,}
% How the letter is closed
\letterclosing{Sincerely,}
% Any enclosures with the letter
\letterenclosure[Attached]{Curriculum Vitae}
%-------------------------------------------------------------------------------
\begin{document}
% Print the header with above personal information
% Give optional argument to change alignment(C: center, L: left, R: right)
\makecvheader[R]
% Print the footer with 3 arguments(<left>, <center>, <right>)
% Leave any of these blank if they are not needed
\makecvfooter
{\today}
{Claud D. Park~~~·~~~Cover Letter}
{}
% Print the title with above letter information
\makelettertitle
%-------------------------------------------------------------------------------
% LETTER CONTENT
%-------------------------------------------------------------------------------
\begin{cvletter}
\lettersection{About Me}
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis ullamcorper neque sit amet lectus facilisis sed luctus nisl iaculis. Vivamus at neque arcu, sed tempor quam. Curabitur pharetra tincidunt tincidunt. Morbi volutpat feugiat mauris, quis tempor neque vehicula volutpat. Duis tristique justo vel massa fermentum accumsan. Mauris ante elit, feugiat vestibulum tempor eget, eleifend ac ipsum. Donec scelerisque lobortis ipsum eu vestibulum. Pellentesque vel massa at felis accumsan rhoncus.
\lettersection{Why Google?}
Suspendisse commodo, massa eu congue tincidunt, elit mauris pellentesque orci, cursus tempor odio nisl euismod augue. Aliquam adipiscing nibh ut odio sodales et pulvinar tortor laoreet. Mauris a accumsan ligula. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Suspendisse vulputate sem vehicula ipsum varius nec tempus dui dapibus. Phasellus et est urna, ut auctor erat. Sed tincidunt odio id odio aliquam mattis. Donec sapien nulla, feugiat eget adipiscing sit amet, lacinia ut dolor. Phasellus tincidunt, leo a fringilla consectetur, felis diam aliquam urna, vitae aliquet lectus orci nec velit. Vivamus dapibus varius blandit.
\lettersection{Why Me?}
Duis sit amet magna ante, at sodales diam. Aenean consectetur porta risus et sagittis. Ut interdum, enim varius pellentesque tincidunt, magna libero sodales tortor, ut fermentum nunc metus a ante. Vivamus odio leo, tincidunt eu luctus ut, sollicitudin sit amet metus. Nunc sed orci lectus. Ut sodales magna sed velit volutpat sit amet pulvinar diam venenatis.
\end{cvletter}
%-------------------------------------------------------------------------------
% Print the signature and enclosures with above letter information
\makeletterclosing
\end{document}
================================================
FILE: examples/cv/certificates.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Certificates}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{AWS Certified Advanced Networking - Specialty} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2023} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified Developer – Associate} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2023} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified Cloud Practitioner} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2023} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified Security - Specialty} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2022} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified Solutions Architect – Professional} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2022} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified Solutions Architect – Associate} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2019} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified SysOps Administrator – Associate} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2021} % Date(s)
%---------------------------------------------------------
\cvhonor
{Certified Kubernetes Application Developer (CKAD)} % Name
{The Linux Foundation} % Issuer
{} % Credential ID
{2020} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Terraform Authoring and Operations Professional} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2024} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Terraform Associate (003)} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2023} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Terraform Associate (002)} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2020} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Consul Associate (003)} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2024} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Consul Associate (002)} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2023} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Vault Associate (003)} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2025} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
================================================
FILE: examples/cv/committees.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Program Committees}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{Problem Writer} % Position
{2016 CODEGATE Hacking Competition World Final} % Committee
{S.Korea} % Location
{2016} % Date(s)
%---------------------------------------------------------
\cvhonor
{Organizer \& Co-director} % Position
{1st POSTECH Hackathon} % Committee
{S.Korea} % Location
{2013} % Date(s)
%---------------------------------------------------------
\cvhonor
{Staff} % Position
{7th Hacking Camp} % Committee
{S.Korea} % Location
{2012} % Date(s)
%---------------------------------------------------------
\cvhonor
{Problem Writer} % Position
{1st Hoseo University Teenager Hacking Competition} % Committee
{S.Korea} % Location
{2012} % Date(s)
%---------------------------------------------------------
\cvhonor
{Staff \& Problem Writer} % Position
{JFF(Just for Fun) Hacking Competition} % Committee
{S.Korea} % Location
{2012} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
================================================
FILE: examples/cv/education.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Education}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{B.S. in Computer Science and Engineering} % Degree
{POSTECH(Pohang University of Science and Technology)} % Institution
{Pohang, S.Korea} % Location
{Mar. 2010 - Aug. 2017} % Date(s)
{
\begin{cvitems} % Description(s) bullet points
\item {Got a Chun Shin-Il Scholarship which is given to promising students in CSE Dept.}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/cv/experience.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Experience}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Founding Member \& Site Reliability Engineer \& Infrastructure Team Lead} % Job title
{Danggeun Pay Inc. (KarrotPay)} % Organization
{Seoul, S.Korea} % Location
{Mar. 2021 - Present} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Everything that matters.}
\item {Designed and provisioned the entire infrastructure on the AWS cloud to meet security compliance and acquire a business license for financial services in Korea.}
\item {Continuously improved the infrastructure architecture since launching the service. (currently 3.6 million users)}
\item {Established a standardized base for declarative management of infrastructures and service deployments, enabling operational efficiency and consistency. Over 90\% of AWS resources were all managed through standardized terraform modules. All add-ons and service workloads on the Kubernetes cluster were managed on a GitOps basis with Kustomize and ArgoCD.}
\item {Saved over 30\% of the overall AWS costs by establishing a quarterly purchasing strategiy for RI (Reserved Instance) and SP (Savings Plan) and by introducing Graviton instances.}
\item {Established a core architecture for regulating of outbound DNS traffic in multi-account and multi-VPC environments utilizing AWS Route53 DNS Firewall and FMS. This significantly increased the level of security confidence in the financial sector's segregated environment.}
\item {Introduced Okta employee identity solution in the company, establishing security policies and configuring SSO integration with over 20 enterprise systems including AWS, GitHub, Slack, Google Workspace. Set up a Hub and Spoke architecture, enabling a collaborative account structure with the parent company, Daangn Market.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Site Reliability Engineer} % Job title
{Danggeun Market Inc.} % Organization
{Seoul, S.Korea} % Location
{Feb. 2021 - Mar. 2021} % Date(s)
{
}
%---------------------------------------------------------
\cventry
{Founding Member \& Director of Infrastructure Division} % Job title
{Kasa} % Organization
{Seoul, S.Korea} % Location
{Jun. 2018 - Jan. 2021} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Designed on-boarding process to guide new engineers, help them to focus on the right tasks, and set expectations to help them be successful at Infrastructure team.}
\item {Migrated the orchestration system from DC/OS to Kubernetes which is based on AWS EKS. Managed 3 Kubernetes clusters and 300+ pods. Managed all Kubernetes manifests declaratively with Kustomize and ArgoCD.}
\item {Designed and managed complex network configurations on AWS with 4 VPC and 100+ subnets. Separated the development network and operation network according to financial regulations. Established dedicated network connections from AWS VPC to partners' on-premise network based on AWS Direct Connect with secure connection using IPsec VPN. Provisioned OpenVPN servers with LDAP integration.}
\item {Provisioned a observability system with Kafka, Elastic Stack(Filebeat, Heartbeat, APM Server, Logstash, Elasticsearch, Kibana). Collected log, uptime, tracing data from hosts, containers, pods and more. The ES cluster which has 9 nodes processed more than 1 billion documents per month. Wrote Terraform module to easily provision ES cluster on AWS EC2 instances.}
\item {Provisioned a monitoring system with Kafka, Telegraf, InfluxDB, Grafana. Collected metrics from hosts, containers, pods and more. Wrote Terraform module to easily provision InfluxDB with HA on AWS EC2 instances.}
\item {Introduced Kong API Gateway to easily connect all API microservices with a declarative management method based on Terraform and Atlantis to collaborate and audit change history.}
\item {Provisioned the Directory Service for employee identity management based on OpenLDAP which guarantees HA with multi-master replication.}
\item {Implemented Worker microservices consuming Kafka event topics for email, SMS, Kakaotalk and Slack notification. Developed in-house framework to easily build Kafka consumer microservice with common features including retry on failure, DLQ(Dead Letter Queue), event routing and more.}
\item {Introduced Elastic APM to help distributed tracing, trouble-shooting and performance testing in MSA.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Software Architect} % Job title
{Omnious. Co., Ltd.} % Organization
{Seoul, S.Korea} % Location
{Jun. 2017 - May 2018} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Provisioned an easily managable hybrid infrastructure(Amazon AWS + On-premise) utilizing IaC(Infrastructure as Code) tools like Ansible, Packer and Terraform.}
\item {Built fully automated CI/CD pipelines on CircleCI for containerized applications using Docker, AWS ECR and Rancher.}
\item {Designed an overall service architecture and pipelines of the Machine Learning based Fashion Tagging API SaaS product with the micro-services architecture.}
\item {Implemented several API microservices in Node.js Koa and in the serverless AWS Lambda functions.}
\item {Deployed a centralized logging environment(ELK, Filebeat, CloudWatch, S3) which gather log data from docker containers and AWS resources.}
\item {Deployed a centralized monitoring environment(Grafana, InfluxDB, CollectD) which gather system metrics as well as docker run-time metrics.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Co-founder \& Software Engineer} % Job title
{PLAT Corp.} % Organization
{Seoul, S.Korea} % Location
{Jan. 2016 - Jun. 2017} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Implemented RESTful API server for car rental booking application(CARPLAT in Google Play).}
\item {Built and deployed overall service infrastructure utilizing Docker container, CircleCI, and several AWS stack(Including EC2, ECS, Route 53, S3, CloudFront, RDS, ElastiCache, IAM), focusing on high-availability, fault tolerance, and auto-scaling.}
\item {Developed an easy-to-use Payment module which connects to major PG(Payment Gateway) companies in Korea.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Researcher} % Job title
{Undergraduate Research, Machine Learning Lab(Prof. Seungjin Choi)} % Organization
{Pohang, S.Korea} % Location
{Mar. 2016 - Exp. Jun. 2017} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Researched classification algorithms(SVM, CNN) to improve accuracy of human exercise recognition with wearable device.}
\item {Developed two TIZEN applications to collect sample data set and to recognize user exercise on SAMSUNG Gear S.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Software Engineer \& Security Researcher (Compulsory Military Service)} % Job title
{R.O.K Cyber Command, MND} % Organization
{Seoul, S.Korea} % Location
{Aug. 2014 - Apr. 2016} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Lead engineer on agent-less backtracking system that can discover client device's fingerprint(including public and private IP) independently of the Proxy, VPN and NAT.}
\item {Implemented a distributed web stress test tool with high anonymity.}
\item {Implemented a military cooperation system which is web based real time messenger in Scala on Lift.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Game Developer Intern at Global Internship Program} % Job title
{NEXON} % Organization
{Seoul, S.Korea \& LA, U.S.A} % Location
{Jan. 2013 - Feb. 2013} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Developed in Cocos2d-x an action puzzle game(Dragon Buster) targeting U.S. market.}
\item {Implemented API server which is communicating with game client and In-App Store, along with two other team members who wrote the game logic and designed game graphics.}
\item {Won the 2nd prize in final evaluation.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Researcher for <Detecting video’s torrents using image similarity algorithms>} % Job title
{Undergraduate Research, Computer Vision Lab(Prof. Bohyung Han)} % Organization
{Pohang, S.Korea} % Location
{Sep. 2012 - Feb. 2013} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Researched means of retrieving a corresponding video based on image contents using image similarity algorithm.}
\item {Implemented prototype that users can obtain torrent magnet links of corresponding video relevant to an image on web site.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Software Engineer Trainee} % Job title
{Software Maestro (funded by Korea Ministry of Knowledge and Economy)} % Organization
{Seoul, S.Korea} % Location
{Jul. 2012 - Jun. 2013} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Performed research memory management strategies of OS and implemented in Python an interactive simulator for Linux kernel memory management.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Software Engineer} % Job title
{ShitOne Corp.} % Organization
{Seoul, S.Korea} % Location
{Dec. 2011 - Feb. 2012} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Developed a proxy drive smartphone application which connects proxy driver and customer. Implemented overall Android application logic and wrote API server for community service, along with lead engineer who designed bidding protocol on raw socket and implemented API server for bidding.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Freelance Penetration Tester} % Job title
{SAMSUNG Electronics} % Organization
{S.Korea} % Location
{Sep. 2013, Mar. 2011 - Oct. 2011} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Conducted penetration testing on SAMSUNG KNOX, which is solution for enterprise mobile security.}
\item {Conducted penetration testing on SAMSUNG Smart TV.}
\end{cvitems}
%\begin{cvsubentries}
% \cvsubentry{}{KNOX(Solution for Enterprise Mobile Security) Penetration Testing}{Sep. 2013}{}
% \cvsubentry{}{Smart TV Penetration Testing}{Mar. 2011 - Oct. 2011}{}
%\end{cvsubentries}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/cv/extracurricular.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Extracurricular Activity}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Core Member} % Affiliation/role
{B10S (B1t 0n the Security, Underground hacker team)} % Organization/group
{S.Korea} % Location
{Nov. 2011 - PRESENT} % Date(s)
{
\begin{cvitems} % Description(s) of experience/contributions/knowledge
\item {Gained expertise in penetration testing areas, especially targeted on web application and software.}
\item {Participated on a lot of hacking competition and won a good award.}
\item {Held several hacking competitions non-profit, just for fun.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Member} % Affiliation/role
{WiseGuys (Hacking \& Security research group)} % Organization/group
{S.Korea} % Location
{Jun. 2012 - PRESENT} % Date(s)
{
\begin{cvitems} % Description(s) of experience/contributions/knowledge
\item {Gained expertise in hardware hacking areas from penetration testing on several devices including wireless router, smartphone, CCTV and set-top box.}
\item {Trained wannabe hacker about hacking technique from basic to advanced and ethics for white hackers by hosting annual Hacking Camp.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Core Member \& President at 2013} % Affiliation/role
{PoApper (Developers' Network of POSTECH)} % Organization/group
{Pohang, S.Korea} % Location
{Jun. 2010 - Jun. 2017} % Date(s)
{
\begin{cvitems} % Description(s) of experience/contributions/knowledge
\item {Reformed the society focusing on software engineering and building network on and off campus.}
\item {Proposed various marketing and network activities to raise awareness.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Member} % Affiliation/role
{PLUS (Laboratory for UNIX Security in POSTECH)} % Organization/group
{Pohang, S.Korea} % Location
{Sep. 2010 - Oct. 2011} % Date(s)
{
\begin{cvitems} % Description(s) of experience/contributions/knowledge
\item {Gained expertise in hacking \& security areas, especially about internal of operating system based on UNIX and several exploit techniques.}
\item {Participated on several hacking competition and won a good award.}
\item {Conducted periodic security checks on overall IT system as a member of POSTECH CERT.}
\item {Conducted penetration testing commissioned by national agency and corporation.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Member} % Affiliation/role
{MSSA (Management Strategy Club of POSTECH)} % Organization/group
{Pohang, S.Korea} % Location
{Sep. 2013 - Jun. 2017} % Date(s)
{
\begin{cvitems} % Description(s) of experience/contributions/knowledge
\item {Gained knowledge about several business field like Management, Strategy, Financial and marketing from group study.}
\item {Gained expertise in business strategy areas and inisght for various industry from weekly industry analysis session.}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/cv/honors.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Honors \& Awards}
%-------------------------------------------------------------------------------
% SUBSECTION TITLE
%-------------------------------------------------------------------------------
\cvsubsection{International Awards}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{2nd Place} % Award
{AWS ASEAN AI/ML GameDay} % Event
{Online} % Location
{2021} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 28th CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2020} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 26th CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2018} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 25th CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2017} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 22nd CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2014} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 21st CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2013} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 19th CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2011} % Date(s)
%---------------------------------------------------------
\cvhonor
{6th Place} % Award
{SECUINSIDE Hacking Competition World Final} % Event
{Seoul, S.Korea} % Location
{2012} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
%-------------------------------------------------------------------------------
% SUBSECTION TITLE
%-------------------------------------------------------------------------------
\cvsubsection{Domestic Awards}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{2nd Place} % Award
{AWS Korea GameDay} % Event
{Seoul, S.Korea} % Location
{2021} % Date(s)
%---------------------------------------------------------
\cvhonor
{3rd Place} % Award
{WITHCON Hacking Competition Final} % Event
{Seoul, S.Korea} % Location
{2015} % Date(s)
%---------------------------------------------------------
\cvhonor
{Silver Prize} % Award
{KISA HDCON Hacking Competition Final} % Event
{Seoul, S.Korea} % Location
{2017} % Date(s)
%---------------------------------------------------------
\cvhonor
{Silver Prize} % Award
{KISA HDCON Hacking Competition Final} % Event
{Seoul, S.Korea} % Location
{2013} % Date(s)
%---------------------------------------------------------
\cvhonor
{2nd Award} % Award
{HUST Hacking Festival} % Event
{S.Korea} % Location
{2013} % Date(s)
%---------------------------------------------------------
\cvhonor
{3rd Award} % Award
{HUST Hacking Festival} % Event
{S.Korea} % Location
{2010} % Date(s)
%---------------------------------------------------------
\cvhonor
{3rd Award} % Award
{Holyshield 3rd Hacking Festival} % Event
{S.Korea} % Location
{2012} % Date(s)
%---------------------------------------------------------
\cvhonor
{2nd Award} % Award
{Holyshield 3rd Hacking Festival} % Event
{S.Korea} % Location
{2011} % Date(s)
%---------------------------------------------------------
\cvhonor
{5th Place} % Award
{PADOCON Hacking Competition Final} % Event
{Seoul, S.Korea} % Location
{2011} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
%-------------------------------------------------------------------------------
% SUBSECTION TITLE
%-------------------------------------------------------------------------------
\cvsubsection{Community}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{AWS Community Builder (Container)} % Award
{Amazon Web Services (AWS)} % Event
{} % Location
{2022} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Ambassador} % Award
{HashiCorp} % Event
{} % Location
{2022} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
================================================
FILE: examples/cv/presentation.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Presentation}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Presenter for <Hosting Web Application for Free utilizing GitHub, Netlify and CloudFlare>} % Role
{DevFest Seoul by Google Developer Group Korea} % Event
{Seoul, S.Korea} % Location
{Nov. 2017} % Date(s)
{
\begin{cvitems} % Description(s)
\item {Introduced the history of web technology and the JAM stack which is for the modern web application development.}
\item {Introduced how to freely host the web application with high performance utilizing global CDN services.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Presenter for <DEFCON 20th : The way to go to Las Vegas>} % Role
{6th CodeEngn (Reverse Engineering Conference)} % Event
{Seoul, S.Korea} % Location
{Jul. 2012} % Date(s)
{
\begin{cvitems} % Description(s)
\item {Introduced CTF(Capture the Flag) hacking competition and advanced techniques and strategy for CTF}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Presenter for <Metasploit 101>} % Role
{6th Hacking Camp - S.Korea} % Event
{S.Korea} % Location
{Sep. 2012} % Date(s)
{
\begin{cvitems} % Description(s)
\item {Introduced basic procedure for penetration testing and how to use Metasploit}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/cv/skills.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Skills}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvskills}
%---------------------------------------------------------
\cvskill
{DevOps} % Category
{AWS, Docker, Kubernetes, Rancher, Vagrant, Packer, Terraform, Jenkins, CircleCI} % Skills
%---------------------------------------------------------
\cvskill
{Back-end} % Category
{Koa, Express, Django, REST API} % Skills
%---------------------------------------------------------
\cvskill
{Front-end} % Category
{Hugo, Redux, React, HTML5, LESS, SASS} % Skills
%---------------------------------------------------------
\cvskill
{Programming} % Category
{Node.js, Python, JAVA, OCaml, LaTeX} % Skills
%---------------------------------------------------------
\cvskill
{Languages} % Category
{Korean, English, Japanese} % Skills
%---------------------------------------------------------
\end{cvskills}
================================================
FILE: examples/cv/writing.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Writing}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Founder \& Writer} % Role
{A Guide for Developers in Start-up} % Title
{Facebook Page} % Location
{Jan. 2015 - PRESENT} % Date(s)
{
\begin{cvitems} % Description(s)
\item {Drafted daily news for developers in Korea about IT technologies, issues about start-up.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Undergraduate Student Reporter} % Role
{AhnLab} % Title
{S.Korea} % Location
{Oct. 2012 - Jul. 2013} % Date(s)
{
\begin{cvitems} % Description(s)
\item {Drafted reports about IT trends and Security issues on AhnLab Company magazine.}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/cv.tex
================================================
%!TEX TS-program = xelatex
%!TEX encoding = UTF-8 Unicode
% Awesome CV LaTeX Template for CV/Resume
%
% This template has been downloaded from:
% https://github.com/posquit0/Awesome-CV
%
% Author:
% Claud D. Park <posquit0.bj@gmail.com>
% http://www.posquit0.com
%
% Template license:
% CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/)
%
%-------------------------------------------------------------------------------
% CONFIGURATIONS
%-------------------------------------------------------------------------------
% A4 paper size by default, use 'letterpaper' for US letter
\documentclass[11pt, a4paper]{awesome-cv}
% Configure page margins with geometry
\geometry{left=1.4cm, top=.8cm, right=1.4cm, bottom=1.8cm, footskip=.5cm}
% Color for highlights
% Awesome Colors: awesome-emerald, awesome-skyblue, awesome-red, awesome-pink, awesome-orange
% awesome-nephritis, awesome-concrete, awesome-darknight
\colorlet{awesome}{awesome-red}
% Uncomment if you would like to specify your own color
% \definecolor{awesome}{HTML}{CA63A8}
% Colors for text
% Uncomment if you would like to specify your own color
% \definecolor{darktext}{HTML}{414141}
% \definecolor{text}{HTML}{333333}
% \definecolor{graytext}{HTML}{5D5D5D}
% \definecolor{lighttext}{HTML}{999999}
% \definecolor{sectiondivider}{HTML}{5D5D5D}
% Set false if you don't want to highlight section with awesome color
\setbool{acvSectionColorHighlight}{true}
% If you would like to change the social information separator from a pipe (|) to something else
\renewcommand{\acvHeaderSocialSep}{\quad\textbar\quad}
%-------------------------------------------------------------------------------
% PERSONAL INFORMATION
% Comment any of the lines below if they are not required
%-------------------------------------------------------------------------------
% Available options: circle|rectangle,edge/noedge,left/right
% \photo{./examples/profile.png}
\name{Claud D.}{Park}
\position{DevOps Engineer{\enskip\cdotp\enskip}Software Architect}
\address{Mapo-gu, Seoul, Republic of Korea}
\mobile{(+82) 10-9030-1843}
%\whatsapp{(+82) 10-9030-1843}
\email{posquit0.bj@gmail.com}
%\dateofbirth{January 1st, 1970}
\homepage{www.posquit0.com}
\github{posquit0}
\linkedin{posquit0}
% \gitlab{gitlab-id}
% \stackoverflow{SO-id}{SO-name}
% \twitter{@twit}
% \x{x-id}
% \skype{skype-id}
% \reddit{reddit-id}
% \medium{medium-id}
% \kaggle{kaggle-id}
% \hackerrank{hackerrank-id}
% \telegram{telegram-username}
% \googlescholar{googlescholar-id}{name-to-display}
%% \firstname and \lastname will be used
% \googlescholar{googlescholar-id}{}
% \extrainfo{extra information}
\quote{``Be the change that you want to see in the world."}
%-------------------------------------------------------------------------------
\begin{document}
% Print the header with above personal information
% Give optional argument to change alignment(C: center, L: left, R: right)
\makecvheader
% Print the footer with 3 arguments(<left>, <center>, <right>)
% Leave any of these blank if they are not needed
\makecvfooter
{\today}
{Claud D. Park~~~·~~~Curriculum Vitae}
{\thepage}
%-------------------------------------------------------------------------------
% CV/RESUME CONTENT
% Each section is imported separately, open each file in turn to modify content
%-------------------------------------------------------------------------------
\input{cv/education.tex}
\input{cv/skills.tex}
\input{cv/experience.tex}
\input{cv/extracurricular.tex}
\input{cv/honors.tex}
\input{cv/certificates.tex}
\input{cv/presentation.tex}
\input{cv/writing.tex}
\input{cv/committees.tex}
%-------------------------------------------------------------------------------
\end{document}
================================================
FILE: examples/resume/certificates.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Certificates}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{AWS Certified Advanced Networking - Specialty} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2023} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified Security - Specialty} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2022} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified Solutions Architect – Professional} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2022} % Date(s)
%---------------------------------------------------------
\cvhonor
{AWS Certified SysOps Administrator – Associate} % Name
{Amazon Web Services (AWS)} % Issuer
{} % Credential ID
{2021} % Date(s)
%---------------------------------------------------------
\cvhonor
{Certified Kubernetes Application Developer (CKAD)} % Name
{The Linux Foundation} % Issuer
{} % Credential ID
{2020} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Terraform Authoring and Operations Professional} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2024} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Terraform Associate (003)} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2023} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Consul Associate (003)} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2024} % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Certified: Vault Associate (003)} % Name
{HashiCorp} % Issuer
{} % Credential ID
{2025} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
================================================
FILE: examples/resume/committees.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Program Committees}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{Problem Writer} % Position
{2016 CODEGATE Hacking Competition World Final} % Committee
{S.Korea} % Location
{2016} % Date(s)
%---------------------------------------------------------
\cvhonor
{Organizer \& Co-director} % Position
{1st POSTECH Hackathon} % Committee
{S.Korea} % Location
{2013} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
================================================
FILE: examples/resume/education.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Education}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{B.S. in Computer Science and Engineering} % Degree
{POSTECH(Pohang University of Science and Technology)} % Institution
{Pohang, S.Korea} % Location
{Mar. 2010 - Aug. 2017} % Date(s)
{
\begin{cvitems} % Description(s) bullet points
\item {Got a Chun Shin-Il Scholarship which is given to promising students in CSE Dept.}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/resume/experience.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Work Experience}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{DevOps Engineer} % Job title
{Dunamu Inc.} % Organization
{Seoul, S.Korea} % Location
{Sep. 2023 - Mar. 2024} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Led service mesh technology research and implementation across enterprise cross-cluster environments, evaluating Istio, Cilium, Kuma, Consul, and AWS VPC Lattice for enhanced security and scalability.}
\item {Designed Terraform modules to efficiently manage and scale infrastructure across dozens of AWS accounts, enabling standardized, repeatable deployments.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Founding Member \& Site Reliability Engineer \& Infrastructure Team Lead} % Job title
{Danggeun Pay Inc. (KarrotPay)} % Organization
{Seoul, S.Korea} % Location
{Mar. 2021 - Jun. 2023} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Everything that matters.}
\item {Designed and provisioned the entire infrastructure on the AWS cloud to meet security compliance and acquire a business license for financial services in Korea.}
\item {Continuously improved the infrastructure architecture since launching the service. (currently 3.6 million users)}
\item {Established a standardized base for declarative management of infrastructures and service deployments, enabling operational efficiency and consistency. Over 90\% of AWS resources were all managed through standardized terraform modules. All add-ons and service workloads on the Kubernetes cluster were managed on a GitOps basis with Kustomize and ArgoCD.}
\item {Saved over 30\% of the overall AWS costs by establishing a quarterly purchasing strategiy for RI (Reserved Instance) and SP (Savings Plan) and by introducing Graviton instances.}
\item {Established a core architecture for regulating of outbound DNS traffic in multi-account and multi-VPC environments utilizing AWS Route53 DNS Firewall and FMS. This significantly increased the level of security confidence in the financial sector's segregated environment.}
\item {Introduced Okta employee identity solution in the company, establishing security policies and configuring SSO integration with over 20 enterprise systems including AWS, GitHub, Slack, Google Workspace. Set up a Hub and Spoke architecture, enabling a collaborative account structure with the parent company, Daangn Market.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Site Reliability Engineer} % Job title
{Danggeun Market Inc.} % Organization
{Seoul, S.Korea} % Location
{Feb. 2021 - Mar. 2021} % Date(s)
{
}
%---------------------------------------------------------
\cventry
{Founding Member \& Director of Infrastructure Division} % Job title
{Kasa} % Organization
{Seoul, S.Korea} % Location
{Jun. 2018 - Jan. 2021} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Designed on-boarding process to guide new engineers, help them to focus on the right tasks, and set expectations to help them be successful at Infrastructure team.}
\item {Migrated the orchestration system from DC/OS to Kubernetes which is based on AWS EKS. Managed 3 Kubernetes clusters and 300+ pods. Managed all Kubernetes manifests declaratively with Kustomize and ArgoCD.}
\item {Designed and managed complex network configurations on AWS with 4 VPC and 100+ subnets. Separated the development network and operation network according to financial regulations. Established dedicated network connections from AWS VPC to partners' on-premise network based on AWS Direct Connect with secure connection using IPsec VPN. Provisioned OpenVPN servers with LDAP integration.}
\item {Provisioned a observability system with Kafka, Elastic Stack(Filebeat, Heartbeat, APM Server, Logstash, Elasticsearch, Kibana). Collected log, uptime, tracing data from hosts, containers, pods and more. The ES cluster which has 9 nodes processed more than 1 billion documents per month. Wrote Terraform module to easily provision ES cluster on AWS EC2 instances.}
\item {Provisioned a monitoring system with Kafka, Telegraf, InfluxDB, Grafana. Collected metrics from hosts, containers, pods and more. Wrote Terraform module to easily provision InfluxDB with HA on AWS EC2 instances.}
\item {Introduced Kong API Gateway to easily connect all API microservices with a declarative management method based on Terraform and Atlantis to collaborate and audit change history.}
\item {Provisioned the Directory Service for employee identity management based on OpenLDAP which guarantees HA with multi-master replication.}
\item {Implemented Worker microservices consuming Kafka event topics for email, SMS, Kakaotalk and Slack notification. Developed in-house framework to easily build Kafka consumer microservice with common features including retry on failure, DLQ(Dead Letter Queue), event routing and more.}
\item {Introduced Elastic APM to help distributed tracing, trouble-shooting and performance testing in MSA.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Software Architect} % Job title
{Omnious. Co., Ltd.} % Organization
{Seoul, S.Korea} % Location
{Jun. 2017 - May. 2018} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Provisioned an easily managable hybrid infrastructure(Amazon AWS + On-premise) utilizing IaC(Infrastructure as Code) tools like Ansible, Packer and Terraform.}
\item {Built fully automated CI/CD pipelines on CircleCI for containerized applications using Docker, AWS ECR and Rancher.}
\item {Designed an overall service architecture and pipelines of the Machine Learning based Fashion Tagging API SaaS product with the micro-services architecture.}
\item {Implemented several API microservices in Node.js Koa and in the serverless AWS Lambda functions.}
\item {Deployed a centralized logging environment(ELK, Filebeat, CloudWatch, S3) which gather log data from docker containers and AWS resources.}
\item {Deployed a centralized monitoring environment(Grafana, InfluxDB, CollectD) which gather system metrics as well as docker run-time metrics.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Co-founder \& Software Engineer} % Job title
{PLAT Corp.} % Organization
{Seoul, S.Korea} % Location
{Jan. 2016 - Jun. 2017} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Implemented RESTful API server for car rental booking application(CARPLAT in Google Play).}
\item {Built and deployed overall service infrastructure utilizing Docker container, CircleCI, and several AWS stack(Including EC2, ECS, Route 53, S3, CloudFront, RDS, ElastiCache, IAM), focusing on high-availability, fault tolerance, and auto-scaling.}
\item {Developed an easy-to-use Payment module which connects to major PG(Payment Gateway) companies in Korea.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Software Engineer \& Security Researcher (Compulsory Military Service)} % Job title
{R.O.K Cyber Command, MND} % Organization
{Seoul, S.Korea} % Location
{Aug. 2014 - Apr. 2016} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Lead engineer on agent-less backtracking system that can discover client device's fingerprint(including public and private IP) independently of the Proxy, VPN and NAT.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Software Engineer} % Job title
{ShitOne Corp.} % Organization
{Seoul, S.Korea} % Location
{Dec. 2011 - Feb. 2012} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {Developed a proxy drive smartphone application which connects proxy driver and customer.}
\item {Implemented overall Android application logic and wrote API server for community service, along with lead engineer who designed bidding protocol on raw socket and implemented API server for bidding.}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/resume/extracurricular.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Extracurricular Activity}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Core Member \& President at 2013} % Affiliation/role
{PoApper (Developers' Network of POSTECH)} % Organization/group
{Pohang, S.Korea} % Location
{Jun. 2010 - Jun. 2017} % Date(s)
{
\begin{cvitems} % Description(s) of experience/contributions/knowledge
\item {Reformed the society focusing on software engineering and building network on and off campus.}
\item {Proposed various marketing and network activities to raise awareness.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Member} % Affiliation/role
{PLUS (Laboratory for UNIX Security in POSTECH)} % Organization/group
{Pohang, S.Korea} % Location
{Sep. 2010 - Oct. 2011} % Date(s)
{
\begin{cvitems} % Description(s) of experience/contributions/knowledge
\item {Gained expertise in hacking \& security areas, especially about internal of operating system based on UNIX and several exploit techniques.}
\item {Participated on several hacking competition and won a good award.}
\item {Conducted periodic security checks on overall IT system as a member of POSTECH CERT.}
\item {Conducted penetration testing commissioned by national agency and corporation.}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/resume/honors.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Honors \& Awards}
%-------------------------------------------------------------------------------
% SUBSECTION TITLE
%-------------------------------------------------------------------------------
\cvsubsection{International Awards}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{2nd Place} % Award
{AWS ASEAN AI/ML GameDay} % Event
{Online} % Location
{2021} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 28th CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2020} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 26th CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2018} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 25th CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2017} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 22nd CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2014} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 21st CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2013} % Date(s)
%---------------------------------------------------------
\cvhonor
{Finalist} % Award
{DEFCON 19th CTF Hacking Competition World Final} % Event
{Las Vegas, U.S.A} % Location
{2011} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
%-------------------------------------------------------------------------------
% SUBSECTION TITLE
%-------------------------------------------------------------------------------
\cvsubsection{Domestic Awards}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{2nd Place} % Award
{AWS Korea GameDay} % Event
{Seoul, S.Korea} % Location
{2021} % Date(s)
%---------------------------------------------------------
\cvhonor
{3rd Place} % Award
{WITHCON Hacking Competition Final} % Event
{Seoul, S.Korea} % Location
{2015} % Date(s)
%---------------------------------------------------------
\cvhonor
{Silver Prize} % Award
{KISA HDCON Hacking Competition Final} % Event
{Seoul, S.Korea} % Location
{2017} % Date(s)
%---------------------------------------------------------
\cvhonor
{Silver Prize} % Award
{KISA HDCON Hacking Competition Final} % Event
{Seoul, S.Korea} % Location
{2013} % Date(s)
%---------------------------------------------------------
\end{cvhonors}
%-------------------------------------------------------------------------------
% SUBSECTION TITLE
%-------------------------------------------------------------------------------
\cvsubsection{Community}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvhonors}
%---------------------------------------------------------
\cvhonor
{AWS Community Builder (Container)} % Award
{Amazon Web Services (AWS)} % Event
{} % Location
{2022 - } % Date(s)
%---------------------------------------------------------
\cvhonor
{HashiCorp Ambassador} % Award
{HashiCorp} % Event
{} % Location
{2022 - } % Date(s)
%---------------------------------------------------------
\cvhonor
{Organizer of HashiCorp Korea User Group} % Award
{HashiCorp} % Event
{} % Location
{2018 - } % Date(s)
%---------------------------------------------------------
\end{cvhonors}
================================================
FILE: examples/resume/presentation.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Presentation}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Presenter for <Hosting Web Application for Free utilizing GitHub, Netlify and CloudFlare>} % Role
{DevFest Seoul by Google Developer Group Korea} % Event
{Seoul, S.Korea} % Location
{Nov. 2017} % Date(s)
{
\begin{cvitems} % Description(s)
\item {Introduced the history of web technology and the JAM stack which is for the modern web application development.}
\item {Introduced how to freely host the web application with high performance utilizing global CDN services.}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Presenter for <DEFCON 20th : The way to go to Las Vegas>} % Role
{6th CodeEngn (Reverse Engineering Conference)} % Event
{Seoul, S.Korea} % Location
{Jul. 2012} % Date(s)
{
\begin{cvitems} % Description(s)
\item {Introduced CTF(Capture the Flag) hacking competition and advanced techniques and strategy for CTF}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/resume/summary.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Summary}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvparagraph}
%---------------------------------------------------------
Seasoned SRE/DevOps leader currently on a career sabbatical cherishing family moments, seeking high-impact opportunities in fast-growing start-up companies. With 15+ years of hands-on software engineering expertise — specializing in service architecture, DevOps \& SRE practices, infrastructure operations, and security engineering — proven in scaling infrastructure teams as lead engineer and founding member at two fintech companies. Delivered technical advisory and consulting for DeFi, AI, and B2B SaaS startups, optimizing cloud-native architectures (AWS multi-account, Kubernetes, Terraform) for reliability and scalability.
Passionate to contribute to open-source projects and tech communities through knowledge sharing knowledge and experience. Big fan of terminal-centric workflows on macOS with zsh, Tmux, NeoVim, and chezmoi; relentlessly optimizes personal setups and experiments with Claude Code-powered AI workflows to tackle complex challenges faster.
\end{cvparagraph}
================================================
FILE: examples/resume/writing.tex
================================================
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Writing}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Founder \& Writer} % Role
{A Guide for Developers in Start-up} % Title
{Facebook Page} % Location
{Jan. 2015 - PRESENT} % Date(s)
{
\begin{cvitems} % Description(s)
\item {Drafted daily news for developers in Korea about IT technologies, issues about start-up.}
\end{cvitems}
}
%---------------------------------------------------------
\end{cventries}
================================================
FILE: examples/resume.tex
================================================
%!TEX TS-program = xelatex
%!TEX encoding = UTF-8 Unicode
% Awesome CV LaTeX Template for CV/Resume
%
% This template has been downloaded from:
% https://github.com/posquit0/Awesome-CV
%
% Author:
% Claud D. Park <posquit0.bj@gmail.com>
% http://www.posquit0.com
%
% Template license:
% CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/)
%
%-------------------------------------------------------------------------------
% CONFIGURATIONS
%-------------------------------------------------------------------------------
% A4 paper size by default, use 'letterpaper' for US letter
\documentclass[11pt, a4paper]{awesome-cv}
% Configure page margins with geometry
\geometry{left=1.4cm, top=.8cm, right=1.4cm, bottom=1.8cm, footskip=.5cm}
% Color for highlights
% Awesome Colors: awesome-emerald, awesome-skyblue, awesome-red, awesome-pink, awesome-orange
% awesome-nephritis, awesome-concrete, awesome-darknight
\colorlet{awesome}{awesome-red}
% Uncomment if you would like to specify your own color
% \definecolor{awesome}{HTML}{3E6D9C}
% Colors for text
% Uncomment if you would like to specify your own color
% \definecolor{darktext}{HTML}{414141}
% \definecolor{text}{HTML}{333333}
% \definecolor{graytext}{HTML}{5D5D5D}
% \definecolor{lighttext}{HTML}{999999}
% \definecolor{sectiondivider}{HTML}{5D5D5D}
% Set false if you don't want to highlight section with awesome color
\setbool{acvSectionColorHighlight}{true}
% If you would like to change the social information separator from a pipe (|) to something else
\renewcommand{\acvHeaderSocialSep}{\quad\textbar\quad}
%-------------------------------------------------------------------------------
% PERSONAL INFORMATION
% Comment any of the lines below if they are not required
%-------------------------------------------------------------------------------
% Available options: circle|rectangle,edge/noedge,left/right
% \photo[rectangle,edge,right]{./examples/profile}
\name{Byungjin}{Park}
\position{DevOps Engineer{\enskip\cdotp\enskip}Software Architect}
\address{Mapo-gu, Seoul, Republic of Korea}
\mobile{(+82) 10-9030-1843}
%\whatsapp{(+82) 10-9030-1843}
\email{posquit0.bj@gmail.com}
%\dateofbirth{January 1st, 1970}
\homepage{www.posquit0.com}
\github{posquit0}
\linkedin{posquit0}
% \gitlab{gitlab-id}
% \stackoverflow{SO-id}{SO-name}
% \twitter{@twit}
% \x{x-id}
% \skype{skype-id}
% \reddit{reddit-id}
% \medium{madium-id}
% \kaggle{kaggle-id}
% \hackerrank{hackerrank-id}
% \telegram{telegram-username}
% \googlescholar{googlescholar-id}{name-to-display}
%% \firstname and \lastname will be used
% \googlescholar{googlescholar-id}{}
% \extrainfo{extra information}
\quote{``Be the change that you want to see in the world."}
%-------------------------------------------------------------------------------
\begin{document}
% Print the header with above personal information
% Give optional argument to change alignment(C: center, L: left, R: right)
\makecvheader[C]
% Print the footer with 3 arguments(<left>, <center>, <right>)
% Leave any of these blank if they are not needed
\makecvfooter
{\today}
{Byungjin Park~~~·~~~Résumé}
{\thepage}
%-------------------------------------------------------------------------------
% CV/RESUME CONTENT
% Each section is imported separately, open each file in turn to modify content
%-------------------------------------------------------------------------------
\input{resume/summary.tex}
\input{resume/experience.tex}
\input{resume/honors.tex}
\input{resume/certificates.tex}
% \input{resume/presentation.tex}
% \input{resume/writing.tex}
% \input{resume/committees.tex}
\input{resume/education.tex}
% \input{resume/extracurricular.tex}
%-------------------------------------------------------------------------------
\end{document}
gitextract_si4y015o/
├── .github/
│ ├── CODEOWNERS
│ ├── dependabot.yml
│ ├── labeler.yaml
│ ├── labels.yaml
│ └── workflows/
│ ├── integration.yaml
│ ├── main.yml
│ ├── pull-request-labeler.yaml
│ ├── sync-labels.yaml
│ └── welcome.yaml
├── .gitignore
├── .yamllint.yaml
├── LICENCE
├── Makefile
├── README.md
├── awesome-cv.cls
└── examples/
├── coverletter.tex
├── cv/
│ ├── certificates.tex
│ ├── committees.tex
│ ├── education.tex
│ ├── experience.tex
│ ├── extracurricular.tex
│ ├── honors.tex
│ ├── presentation.tex
│ ├── skills.tex
│ └── writing.tex
├── cv.tex
├── resume/
│ ├── certificates.tex
│ ├── committees.tex
│ ├── education.tex
│ ├── experience.tex
│ ├── extracurricular.tex
│ ├── honors.tex
│ ├── presentation.tex
│ ├── summary.tex
│ └── writing.tex
└── resume.tex
Condensed preview — 36 files, each showing path, character count, and a content snippet. Download the .json file or copy for the full structured content (139K chars).
[
{
"path": ".github/CODEOWNERS",
"chars": 25,
"preview": "* @posquit0 @OJFord\n"
},
{
"path": ".github/dependabot.yml",
"chars": 109,
"preview": "version: 2\nupdates:\n- package-ecosystem: \"github-actions\"\n directory: \"/\"\n schedule:\n interval: \"daily\"\n"
},
{
"path": ".github/labeler.yaml",
"chars": 0,
"preview": ""
},
{
"path": ".github/labels.yaml",
"chars": 995,
"preview": "# Warning\n- color: \"ee0701\"\n description: \"Categorize bug reports.\"\n name: \":warning: bug\"\n- color: \"ee0701\"\n descrip"
},
{
"path": ".github/workflows/integration.yaml",
"chars": 1160,
"preview": "name: Integration\n\non:\n push:\n branches:\n - master\n pull_request: {}\n\nconcurrency:\n group: integration-${{ gith"
},
{
"path": ".github/workflows/main.yml",
"chars": 506,
"preview": "name: Compile PDFs\n\non:\n push: {}\n pull_request: {}\n\njobs:\n build:\n runs-on: ubuntu-latest\n container: texlive/"
},
{
"path": ".github/workflows/pull-request-labeler.yaml",
"chars": 1003,
"preview": "name: Label Pull Requests\n\non:\n- pull_request_target\n\njobs:\n label-pr:\n runs-on: ubuntu-latest\n\n steps:\n - nam"
},
{
"path": ".github/workflows/sync-labels.yaml",
"chars": 455,
"preview": "name: Sync labels\n\non:\n push:\n branches:\n - master\n paths:\n - .github/labels.yaml\n\njobs:\n sync-labels:\n "
},
{
"path": ".github/workflows/welcome.yaml",
"chars": 712,
"preview": "name: Welcome for First Issue or Pull Request\n\non:\n pull_request_target:\n types:\n - opened\n issues:\n types:\n "
},
{
"path": ".gitignore",
"chars": 258,
"preview": "### TeX ###\n## Core latex/pdflatex auxiliary files:\n*.aux\n*.lof\n*.log\n*.lot\n*.fls\n*.out\n*.toc\n\n## Intermediate documents"
},
{
"path": ".yamllint.yaml",
"chars": 1161,
"preview": "yaml-files:\n- '*.yaml'\n- '*.yml'\n\nrules:\n braces:\n min-spaces-inside: 0\n max-spaces-inside: 1\n min-spaces-insi"
},
{
"path": "LICENCE",
"chars": 19107,
"preview": "The LaTeX Project Public License\n=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-\n\nLPPL Version 1.3c 2008-05-04\n\nCopyright 1999 2002-20"
},
{
"path": "Makefile",
"chars": 583,
"preview": ".PHONY: examples\n\nCC = lualatex\nEXAMPLES_DIR = examples\nRESUME_DIR = examples/resume\nCV_DIR = examples/cv\nRESUME_SRCS = "
},
{
"path": "README.md",
"chars": 5400,
"preview": "<h1 align=\"center\">\n <a href=\"https://github.com/posquit0/Awesome-CV\" title=\"AwesomeCV Documentation\">\n <img alt=\"Aw"
},
{
"path": "awesome-cv.cls",
"chars": 32619,
"preview": "%% Start of file `awesome-cv.cls'.\n% Awesome CV Class File\n%\n% This class has been downloaded from:\n% https://github.com"
},
{
"path": "examples/coverletter.tex",
"chars": 6005,
"preview": "%!TEX TS-program = xelatex\n%!TEX encoding = UTF-8 Unicode\n% Awesome CV LaTeX Template for Cover Letter\n%\n% This template"
},
{
"path": "examples/cv/certificates.tex",
"chars": 3370,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv/committees.tex",
"chars": 1493,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv/education.tex",
"chars": 921,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv/experience.tex",
"chars": 11786,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv/extracurricular.tex",
"chars": 3751,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv/honors.tex",
"chars": 5365,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv/presentation.tex",
"chars": 1896,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv/skills.tex",
"chars": 1237,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv/writing.tex",
"chars": 1226,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/cv.tex",
"chars": 3740,
"preview": "%!TEX TS-program = xelatex\n%!TEX encoding = UTF-8 Unicode\n% Awesome CV LaTeX Template for CV/Resume\n%\n% This template ha"
},
{
"path": "examples/resume/certificates.tex",
"chars": 2351,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume/committees.tex",
"chars": 887,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume/education.tex",
"chars": 921,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume/experience.tex",
"chars": 9037,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume/extracurricular.tex",
"chars": 1846,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume/honors.tex",
"chars": 4433,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume/presentation.tex",
"chars": 1525,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume/summary.tex",
"chars": 1438,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume/writing.tex",
"chars": 860,
"preview": "%-------------------------------------------------------------------------------\n%\tSECTION TITLE\n%----------------------"
},
{
"path": "examples/resume.tex",
"chars": 3796,
"preview": "%!TEX TS-program = xelatex\n%!TEX encoding = UTF-8 Unicode\n% Awesome CV LaTeX Template for CV/Resume\n%\n% This template ha"
}
]
About this extraction
This page contains the full source code of the posquit0/Awesome-CV GitHub repository, extracted and formatted as plain text for AI agents and large language models (LLMs). The extraction includes 36 files (128.9 KB), approximately 33.2k tokens. Use this with OpenClaw, Claude, ChatGPT, Cursor, Windsurf, or any other AI tool that accepts text input. You can copy the full output to your clipboard or download it as a .txt file.
Extracted by GitExtract — free GitHub repo to text converter for AI. Built by Nikandr Surkov.