close
Skip to content
View angelpixel-core's full-sized avatar

Block or report angelpixel-core

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
angelpixel-core/README.md

Angel — Backend Systems Engineer

I build systems that operate under real-world constraints: failures, retries, external APIs, and distributed workflows.

Senior Software Engineer with experience in fintech and high-scale environments, focused on designing reliable backend systems and integration-heavy architectures.

→ Open to backend / platform roles (Remote · US / EU)


What I do

I work on systems where things can (and will) break:

  • External APIs that fail or respond inconsistently
  • Async workflows that require retries and guarantees
  • Payment flows that need reconciliation and traceability
  • Event-driven Order processing systems with eventual consistency

My focus is building systems that are:

  • Reliable under failure
  • Observable in production
  • Safe to evolve over time

Selected Work

🧾 Financial Core Simulator

Deterministic accounting engine to model financial flows.

  • Ledger-based architecture
  • Replayable execution runs
  • CLI interface + admin visualization
  • Focus on correctness and traceability

→ View Repository


🔁 Event-driven Systems & Integrations

Asynchronous workflows and webhook-based integrations.

  • Idempotent operations
  • Retry-safe external integrations
  • Failure handling strategies
  • Observability-first design

→ Related Work


How I think about systems

  • Design for failure first, not just success paths
  • Prefer explicit domain modeling over implicit logic
  • Build idempotent and retry-safe workflows by default
  • Separate orchestration from execution (async / Saga patterns)
  • Keep systems simple, but not simplistic

Stack

Backend: Ruby on Rails · TypeScript + React · Node + Nest + Next Infra: AWS · Docker · CI/CD
Data: PostgreSQL · Redis · Kafka Architecture: Event-driven · Async workflows · Distributed systems


Current Focus

  • Designing systems for real-world constraints (latency, cost, operability)
  • Infrastructure as code & multi-environment setups
  • Shipping production-ready systems end-to-end

Contact

If you're building systems where reliability matters:

Popular repositories Loading

  1. qmk_firmware qmk_firmware Public

    Forked from dailycraftkeyboard/qmk_firmware

    Open-source keyboard firmware for Atmel AVR and Arm USB families

    C

  2. user-authentication user-authentication Public

    Ruby

  3. instaclone instaclone Public

    Ruby

  4. nvim nvim Public

    Modular Neovim configuration for multi-language development (Ruby, Python, JavaScript/TypeScript, Rust) with LSP, DAP, testing, and Git integration. Built on lazy.nvim with focus on developer exper…

    Lua

  5. n8n-langchain-ci-cd n8n-langchain-ci-cd Public

    Proof of concept for orchestrating AI-assisted workflows with strict architectural governance and decision separation.

  6. dashboard-backend-streamlit-py dashboard-backend-streamlit-py Public

    Production-grade Streamlit dashboard backend in Python, structured with DDD + Hexagonal Architecture (ports & adapters), strict typing, and quality gates (ruff, mypy, pytest) using uv.

    Python