Skip to content
Full-stack software engineer

I build full-stack software that has to work in the real world.

I build full-stack software with auth, billing, real-time behavior, and AI features that fit a real workflow. The proof is public: 2 live products, public repos, and 8 merged PRs in external codebases.

Open to full-stack, product, and AI application engineering roles
Based in Alberta · open to remote work and relocation
Proof snapshot

At a glance

This section stays quantitative. The detailed proof lives in the project and open-source sections below.

2
Live Products
Auth, billing, sync, and persistence in public apps
8
Merged External PRs
Maintainer-reviewed merges across OpenAI, Astro, MSW, Google, and commaai
8
PRs In Review
Current OSS work still moving through maintainer review
3+
Years Building Publicly
Products, repositories, and OSS work visible in the open rather than hidden in resume bullets
Featured work

Selected work

Start with the strongest shipped work. Each case study is compressed for fast review and points straight to live proof or source.

Flagship Product
Flagship proof
TypeJung
Result

Shipped publicly at typejung.com with tiered monetization, public source code, and inspectable product behavior.

System

React and TypeScript on the frontend, Express on the backend, Supabase for auth and persistence, Stripe for billing, and Gemini-powered report generation.

TypeJung

Live full-stack assessment product with paid tiers and AI-generated reports.

Built a complete assessment product with a multi-step questionnaire, gated reports, account handling, and AI-generated insights that sit inside a paid product flow instead of a demo.

Why it exists

A personality assessment can get attention, but turning it into a product requires more than questions. It needs authentication, payments, report generation, and a flow that makes the value obvious.

Constraint

The system had to keep the experience readable while handling monetization, report generation, and account state without making the product feel fragile.

Inspectable proof
Live product at typejung.com
40-question assessment engine
Supabase auth, persistence, and Stripe billing
Stack
ReactTypeScriptExpressSupabaseStripeGemini
Real-Time Web App
Flagship proof
Collab Editor
Result

Published as a live app with public source code and clear proof of real-time systems work.

System

Next.js and TypeScript on the client, Tiptap for editing, Socket.io for sync, PostgreSQL for persistence, and Prisma for data access.

Collab Editor

Real-time collaborative editing with sync, autosave, and persistence.

Built a collaborative document editor with live synchronization, rich-text editing, autosave behavior, and a persistent backend instead of a local-only prototype.

Why it exists

Collaborative editing looks simple at the surface, but the real work is keeping shared state, autosave, and persistence coherent when multiple users are editing at once.

Constraint

The main challenge was balancing responsive editing, real-time collaboration, and durable persistence without turning the UX into lag or inconsistency.

Inspectable proof
Live app plus public repository
Socket.io synchronization with autosave
PostgreSQL persistence through Prisma
Stack
Next.jsTypeScriptSocket.ioTiptapPostgreSQLPrisma
Accepted Upstream PR
Flagship proof
commaai/opendbc PR
Result

Merged upstream on January 27, 2026, giving public proof of reviewable engineering work outside my own repositories.

System

Python testing and verification work inside an established open-source repository with maintainer review and existing project standards.

commaai/opendbc PR

Merged upstream testing contribution in a public open-source codebase.

Authored a focused upstream pull request improving cache hypothesis strategies in commaai/opendbc with test-backed changes and a narrow, reviewable scope.

Why it exists

Public proof is stronger when it includes reviewed code in somebody else’s codebase, not just self-published projects. That means finding a concrete issue and making a change that can survive review.

Constraint

The contribution had to be technically correct, easy to review, and precise enough to fit an existing upstream codebase without overclaiming impact.

Inspectable proof
Merged January 27, 2026
Public maintainer review and accepted diff
Test-backed cache hypothesis change
Stack
TestingOSSVerification
Public work

Open source

Reviewed upstream code is the strongest external proof here. This section separates merged work from PRs still in review, then shows the repositories behind both.

View all on GitHub
Contribution map

Where the upstream proof comes from

Logos anchor the organizations. The copy focuses on what the change proved, not just the PR title.

8
Merged upstream PRs
8
PRs in review
26
Public repositories
6
OSS ecosystems
OpenAI logo
OpenAI
2 merged · 1 open
Astro logo
Astro
2 merged · 3 open
MSW logo
MSW
2 merged · 1 open
Google logo
Google
1 merged
comma.ai logo
comma.ai
1 merged · 2 open
Community OSS
0 merged · 1 open
OpenAI logo
OpenAI

SDK reliability work across agents, memory, and realtime client flows.

Maintainer-accepted fixes in production-facing AI SDKs.

3
tracked PRs
Astro logo
Astro

Language-server correctness fixes and framework DX improvements.

Strong fit for debugging editor, typing, and framework edge cases.

5
tracked PRs
comma.ai logo
comma.ai

Validation and test reliability work in autonomous driving infrastructure.

Signals comfort with safety-critical testing and systems-level debugging.

3
tracked PRs
Felmon Fekadu portrait
LocationAlberta, Canada
EducationB.S. Computer Science
FocusFull-stack products, real-time systems, AI features
SeekingFull-stack / product / AI application engineering roles
About

What I build and how I work

I like product work that has real moving parts: backend logic, auth, payments, collaboration, state, and integrations.

Most of the proof is public. TypeJung and Collab Editor are live, and I have merged external PRs across OpenAI, Astro, MSW, Google, and comma.ai.

I’m a strong fit for teams that want engineers to work across the stack, own details, and keep quality visible in the code.

Strong fit problems
Shipping full-stack product slices
Auth, billing, and backend workflows
Real-time sync and collaboration
AI features inside real products
Debugging, tests, and reviewable OSS fixes
How I work
Clear interfaces
Make the product understandable before making it clever.
Real systems
Build for persistence, auth, payments, sync, and failure paths.
Honest proof
Lead with shipped work and label upstream contributions precisely.
Fast iteration
Ship, inspect, and improve instead of polishing in isolation.
Product ownership
Own outcomes, not just isolated implementation tasks.
Learning in public
Use repositories and PRs as public proof of engineering growth.
Technical depth

Engineering decisions, not just polished screens

The UI matters, but the work underneath it matters more. These are the patterns I use to keep products stable and credible.

AI as a product capability

Model features are useful when they fit a clear workflow. I prefer bounded product use cases over AI ornamentation.

Example: TypeJung reports
Assessment flow, account state, and billing exist around the report generator.
AI output serves the product instead of replacing the product.
The proof is a live app, not just a prompt demo.
Use models where they improve the workflow, not where they add theater.

Real-time behavior needs discipline

Collaboration features create state problems quickly. The work is keeping sync, autosave, and persistence coherent under real edits.

Example: Collab Editor
Socket-driven updates for shared editing.
Autosave and persistence built alongside the editor experience.
Real-time UX balanced against backend consistency.
Fast interfaces only matter if the underlying state stays trustworthy.

Public review is part of the proof

Open-source contributions force precision. The claim only counts if the code can survive review in someone else’s codebase.

Example: external merged PRs
Merged fixes in OpenAI, MSW, Astro, and commaai instead of one-off contribution theater.
Public maintainer review and accepted outcomes across multiple external codebases.
Open and closed PRs elsewhere are labeled accurately when not merged.
Reviewed code in public repositories is stronger proof than self-description.
Journey

Experience

The current fit comes first. The timeline below explains how the range was built.

Open-Source PR Author

OpenAI + MSW + Astro + commaai + selected upstream repos
2026 - Present
Remote
Merged eight external PRs across OpenAI, MSW, Astro, Google, and commaai spanning concurrency, runtime behavior, typing compatibility, language tooling, documentation, and test performance.
Worked across Python and TypeScript codebases, adding regression tests, targeted fixes, and reviewable changes accepted by maintainers.
Additional public proposals remain open or closed in repositories including OpenAI Node, Astro, Prettier, commaai, and Minecraft Web Client.
TypeScriptPythonTestingOpen Source

Safety Watch / Fire Watch

United Safety
2022 - 2024
Fort McMurray / Northern Alberta
Monitored high-risk operations and executed emergency response procedures at industrial sites.
Tracked atmospheric readings and maintained compliance and incident logs.
Coordinated with operations and technical teams in rotational camp environments.
Safety OperationsIncident LoggingTeam Coordination

Mobile Security Patrol Officer

Security Services
2020 - 2022
Calgary, AB
Conducted facility patrols and documented incidents using digital reporting systems.
Responded to alarms and coordinated with dispatch and emergency services.
OperationsReportingResponse Procedures

B.S. Computer Science Student

University of the People
Expected 2026
Online
Focused on software engineering, algorithms, systems, and full-stack development.
Built portfolio projects spanning real-time systems, API design, and AI integrations.
Named to the UoPeople Honors List for Term 2, 2025-2026.
Computer ScienceSoftware EngineeringProject-Based Learning
Timeline context

How the public proof was built

This timeline adds context behind the current portfolio, open-source work, and nontraditional operating experience.

2026Milestone

Open to full-time engineering roles

Targeting full-time software engineering, full-stack, and AI product roles where product judgment and engineering standards both matter.

2026Project

Merged external PRs across OpenAI, Astro, MSW, Google, and comma.ai

Maintainer-reviewed merged fixes across SDK internals, runtime behavior, language tooling, documentation, and test performance.

2026Project

Shipped public portfolio products

TypeJung and Collab Editor provide public proof of product engineering, real-time systems work, and model-powered features.

2025-2026Education

Computer Science studies at University of the People

Focused on software engineering, systems, and full-stack development, with Honors List recognition in Term 2, 2025-2026.

2022-2024Work

Safety Watch / Fire Watch at United Safety

High-risk industrial monitoring, atmospheric readings, compliance logs, and coordination with operations teams in northern Alberta.

2020-2022Work

Mobile Security Patrol Officer

Facility patrols, alarm response, digital incident reporting, and dispatch coordination across mobile security operations.

Let's work together

If you’re hiring, email me.

I’m looking for full-time full-stack, product, and AI application engineering roles. Resume, GitHub, and LinkedIn are below.

GitHub
View repositories
LinkedIn
Professional profile
Availability
Full-time full-stack, product, and AI application engineering roles
Based in Alberta and open to remote work or relocation
Best contact path: email with role, team, and timing
© 2026 Felmon Fekadu. Built with care.
Alberta, CanadaOpen to remote work and relocation