Position: DevOps engineer
Category: DevOps
English level: upper
Years of experience: 9

Built a comprehensive CI/CD process from scratch that surpassed pre-existing one and became its successor
 the process was designed, taking into account multiple company-wide security restrictions and design flaws, integrating it with all mandatory in-house systems (mostly custom static code analysis tools), including common branching strategy, unified versioning system per every managed project, release management, generic approach per every single project, etc
Created a flexible and extensible Jenkins global library that adds custom DSL closures, allowing to build & deploy an arbitrary project with simple definitions as short as ~ 10 lines of code; the library also featured different build & deploy flows based on environment and other criterias (green-blue deployments with automated roll-back, health checks, pre-flight & post merge builds for pull requests and so forth)
Brought reproducible builds & automated configuration of Jenkins servers (due to corporate limitations, a server had its lifespan set to 60 days and then would get decommissioned)
I'm a seasoned System Adminstrator/Devops engineer (yea, this may seem silly, as 'DevOps' is more of a methodology to adopt rather than a position). 

Used to working with large American enterprise companies – facilitating their on-prem to cloud transition, helping to build complex & sophisticated CI/CD processes, thus streamlining software development processes.

Stack-wise – unix-like operating systems (different GNU/Linux flavors & FreeBSD), Netflix OSS,
Jenkins (including own shared libraries' development), AWS.
Neither a huge fan of Windows Server-based envs, nor have experience in dealing with it.