Refactor CV content for clarity and impact; update PDF version
This commit is contained in:
parent
f640c90b5f
commit
1fc99ca403
@ -8,16 +8,18 @@ nik@nik4nao.com | github.com/nikafiq | nik4nao.com
|
|||||||
|
|
||||||
## PROFESSIONAL SUMMARY
|
## PROFESSIONAL SUMMARY
|
||||||
|
|
||||||
Backend engineer with 3 years of professional experience designing,
|
Backend engineer with 3 years of professional experience building and
|
||||||
building, and operating distributed backend systems on GCP and AWS.
|
operating Go-based distributed backend systems on GCP and AWS. Strong
|
||||||
Strong in Go and Python, with hands-on production experience in
|
ownership mindset with end-to-end responsibility across architecture,
|
||||||
high-throughput event-driven services, Kafka-based pipelines,
|
implementation, deployment, production reliability, and continuous
|
||||||
Kubernetes, and cloud-native data platforms. Experienced in designing
|
improvement. Known for mechanism-driven problem solving, clear
|
||||||
systems with strict reliability, ordering, idempotency, retry safety,
|
technical documentation, and open knowledge sharing across teams.
|
||||||
and production-safe migration requirements. Applies AI/LLM tools with
|
Hands-on production experience with high-throughput event-driven
|
||||||
deliberate guardrails in daily workflows. Trilingual in English,
|
microservices, Kafka-based pipelines, Kubernetes, and cloud-native data
|
||||||
Japanese (JLPT N1), and Malay. Strong typed-language foundation and
|
platforms. Experienced in designing systems with strict reliability,
|
||||||
able to ramp quickly into Java backend development.
|
ordering, idempotency, retry safety, security, and production-safe
|
||||||
|
migration requirements. Applies AI/LLM tools with deliberate guardrails
|
||||||
|
in daily workflows. Trilingual in English, Japanese (JLPT N1), and Malay.
|
||||||
|
|
||||||
|
|
||||||
---
|
---
|
||||||
@ -41,7 +43,7 @@ able to ramp quickly into Java backend development.
|
|||||||
- Built cloud-native platforms across GCP, AWS, and Azure using
|
- Built cloud-native platforms across GCP, AWS, and Azure using
|
||||||
Kubernetes, ECS/Fargate, Lambda, Aurora, DynamoDB, and Kafka.
|
Kubernetes, ECS/Fargate, Lambda, Aurora, DynamoDB, and Kafka.
|
||||||
|
|
||||||
- Bilingual/trilingual engineer (EN/JA/Malay) with daily
|
- Trilingual engineer (English/Japanese/Malay) with daily
|
||||||
cross-functional communication across Japanese and overseas teams.
|
cross-functional communication across Japanese and overseas teams.
|
||||||
|
|
||||||
|
|
||||||
@ -57,28 +59,29 @@ next-generation carrier messaging platform initiative. Designing and
|
|||||||
operating a distributed GCP/GKE backend pipeline bridging high-volume
|
operating a distributed GCP/GKE backend pipeline bridging high-volume
|
||||||
upstream message delivery with a downstream consent fulfillment API.
|
upstream message delivery with a downstream consent fulfillment API.
|
||||||
|
|
||||||
- Proposed and led adoption of a Kafka-based queuing architecture;
|
- Designed system architecture and selected Kafka as the messaging
|
||||||
designed the end-to-end pipeline with GKE, Managed Kafka
|
backbone based on ordering, reliability, and scalability requirements
|
||||||
(8 partitions keyed by account_id), and Cloud Spanner under a
|
under a 1500 TPS downstream global cap
|
||||||
1500 TPS downstream global cap with strict per-account_id ordering
|
|
||||||
- Designed request coalescing with singleflight, reliable offset commit
|
- Designed request coalescing with singleflight, reliable offset commit
|
||||||
ordering (offsets committed only after durable Spanner writes),
|
ordering (offsets committed only after durable Spanner writes),
|
||||||
graceful shutdown, and a cronjob-based retry pipeline — achieving
|
graceful shutdown, and a cronjob-based retry pipeline — achieving
|
||||||
at-least-once delivery with no data loss on crash
|
at-least-once delivery with no data loss on crash
|
||||||
- Refactored the user-info-fetch API (a separate Spanner read service
|
- Proposed and implemented hashed phone number lookup in Spanner to
|
||||||
accessed by the Gateway aggregator team at 1500 TPS): guided a junior
|
avoid access hotspots, eliminate non-indexed searches, and improve
|
||||||
engineer through initial implementation, then led a full refactor
|
CPU efficiency under sustained load
|
||||||
introducing hashed phone number lookup, removing non-indexed searches,
|
- Improved team development efficiency by optimizing GitHub Actions
|
||||||
and tuning indexes — cutting CPU usage by ~30% under sustained load
|
CI/CD workflows, scoping full test runs to pull requests, improving
|
||||||
- Led Locust performance testing at 120 TPS steady and 600 TPS burst;
|
build cache usage, and reducing unnecessary image builds to shorten
|
||||||
used results to right-size GKE CPU and memory for stable production
|
feedback cycles
|
||||||
behavior
|
- Designed observability for distributed services using OpenTelemetry,
|
||||||
- Designed OpenTelemetry + Datadog + Wiz observability stack; built CI
|
Datadog, and tracing to improve production visibility and incident
|
||||||
controls with semantic version tag enforcement and least-privilege
|
response
|
||||||
Workload Identity
|
- Authored architecture and design documents, including Kafka adoption
|
||||||
- Led TDD adoption, authored team dev guidelines, identified and
|
rationale and request coalescing design, to align teams through clear
|
||||||
escalated a 1-month deadline slip, and stepped up as informal tech
|
written mechanisms
|
||||||
lead during a leadership gap
|
- Strengthened security and compliance posture by designing logs to mask
|
||||||
|
PII, implementing secure service-to-service authentication with
|
||||||
|
Workload Identity, and enforcing least-privilege access controls
|
||||||
- Applied AI tools (Copilot, Claude, Gemini, ChatGPT) in daily
|
- Applied AI tools (Copilot, Claude, Gemini, ChatGPT) in daily
|
||||||
workflows with deliberate guardrails: output validated through testing
|
workflows with deliberate guardrails: output validated through testing
|
||||||
and review, AI excluded from security-sensitive logic
|
and review, AI excluded from security-sensitive logic
|
||||||
@ -115,11 +118,11 @@ Azure-based delivery.
|
|||||||
|
|
||||||
| Category | Details |
|
| Category | Details |
|
||||||
|---|---|
|
|---|---|
|
||||||
| **Languages** | Go, Python, TypeScript/JavaScript, Java (learning; strong typed-language foundation) |
|
| **Languages** | Go, Python, TypeScript/JavaScript |
|
||||||
| **Backend** | Distributed systems, event-driven architecture, REST APIs, pub/sub, concurrency, retry design, idempotency, fault tolerance |
|
| **Backend** | Distributed systems, event-driven architecture, microservices, REST APIs, pub/sub, concurrency, retry design, idempotency, fault tolerance, familiarity with Protocol Buffers and gRPC through personal projects |
|
||||||
| **Cloud — AWS** | ECS/Fargate, Lambda, Aurora/RDS, DynamoDB, Glue, CDK, CodePipeline, Bedrock, Secrets Manager |
|
|
||||||
| **Cloud — GCP** | GKE, Cloud Spanner, Managed Kafka, BigQuery, Cloud Trace |
|
| **Cloud — GCP** | GKE, Cloud Spanner, Managed Kafka, BigQuery, Cloud Trace |
|
||||||
| **Cloud — Azure** | Web Apps, ADB2C, Azure Pipelines |
|
| **Cloud — AWS** | ECS/Fargate, Lambda, Aurora/RDS, DynamoDB, Glue, CDK, CodePipeline, Bedrock, Secrets Manager |
|
||||||
|
| **Cloud — Azure** | Web Apps, Azure AD B2C, Azure Pipelines |
|
||||||
| **Data** | MySQL, Aurora, PostgreSQL, DynamoDB, Cloud Spanner, Kafka, Redis |
|
| **Data** | MySQL, Aurora, PostgreSQL, DynamoDB, Cloud Spanner, Kafka, Redis |
|
||||||
| **DevOps** | Docker, Kubernetes, ArgoCD, CI/CD, IaC (Terraform, AWS CDK, Ansible) |
|
| **DevOps** | Docker, Kubernetes, ArgoCD, CI/CD, IaC (Terraform, AWS CDK, Ansible) |
|
||||||
| **Observability** | OpenTelemetry, Datadog, distributed tracing |
|
| **Observability** | OpenTelemetry, Datadog, distributed tracing |
|
||||||
@ -139,8 +142,7 @@ Azure-based delivery.
|
|||||||
| 基本情報技術者試験 (FE) — IPA Fundamental IT Engineer | Aug 2024 |
|
| 基本情報技術者試験 (FE) — IPA Fundamental IT Engineer | Aug 2024 |
|
||||||
| JLPT N1 — Japanese Language Proficiency | Dec 2022 |
|
| JLPT N1 — Japanese Language Proficiency | Dec 2022 |
|
||||||
|
|
||||||
*In progress: AWS Solutions Architect – Professional (SAP),
|
*In progress: Applied Information Technology Engineer (AP)*
|
||||||
Applied Information Technology Engineer (AP)*
|
|
||||||
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|||||||
Binary file not shown.
Loading…
x
Reference in New Issue
Block a user