Prajwal Amatya

Backend • Junior • Denver, USA • UTC-07:00 • In office, Partially remote, Fully remote • Relocation • Work permits: United States • Available now • from $160k per year

Software Developer

12+ years exp

SQL

Ruby

Python

JavaScript

PHP

Invite to interview

Download CVCV

Overview

Technical skills

Timeline

Roles

Overview

Junior Ruby on Rails developer focused on small web applications with a practical, pragmatic approach to building features. The strongest proven skill is building a simple Rails web app with a service layer for weather lookups, evidenced by app/services/weather/forecast.rb and app/controllers/forecasts_controller.rb. There is little public evidence of production-grade concerns such as schema evolution/migration history, advanced reliability patterns, or multi-service architecture and deployment pipelines.

Phone

Technical skills

Languages

SQL

Ruby

Python

JavaScript

PHP

Ruby

RSpec

Ruby on Rails

Factory Bot

Capybara

Databases

PostgreSQL

MS SQL

MySQL

DevOps

AWS

AWS Lambda

Git

GitHub Actions

CI/CD

Frontend

React.js

Material UI

PrimeReact

Other

Power BI

Jest

.NET

LLM

Copilot

Oracle

Kubernetes

CrewAI

Redux

Rest API

Docker

Model Context Protocol

Jenkins

AI Agents

WebSockets

RAG

Prompt Engineering

State Management

Timeline

IT Sr. Software Developer • Senior

Take 2 • Full-Time

Jan 2023 to May 2025 2 Years 4 Months In office

Delivered full-stack development for mission-critical federal applications using Ruby on Rails, React, and PostgreSQL. Implemented and remediated Section 508 accessibility compliance aligned to WCAG. Built REST APIs and microservices, and automated secure releases with CI/CD using GitHub Actions and AWS CodePipeline. Improved quality with test-driven development using RSpec, Capybara, and Jest, and used AI-assisted tooling to accelerate development.

Ruby on Rails

React.js

PostgreSQL

RSpec

Capybara

Jest

GitHub Actions

CI/CD

AWS

Copilot

LLM

Sr. Full Stack Developer • Senior

Merge World • Full-Time

Mar 2019 to Dec 2023 4 Years 9 Months In office

Built SaaS products with a Ruby on Rails backend and React UI, integrating with REST APIs and OAuth and connecting data flows via Domo’s SDK. Implemented UI features using modular components and applied TDD practices with RSpec, FactoryBot, and Jest to maintain high test coverage. Developed AWS Lambda functions for S3-based data archiving and created Ruby scripts for SOAP-based ingestion workflows triggered by CloudWatch scheduling. Designed ETL pipelines and data warehouse models using relational databases such as PostgreSQL, MySQL, and SQL Server.

Ruby on Rails

React.js

PostgreSQL

MySQL

SQL

AWS Lambda

AWS

RSpec

Factory Bot

Jest

Material UI

PrimeReact

Git

System Analyst • Middle

Pioneer Solutions LLC • Full-Time

Jan 2014 to Feb 2019 5 Years 1 Month Denver In office

Worked across the full SDLC for enterprise data platforms, supporting client implementations and system upgrades in Agile environments. Built and maintained ETL workflows using C#/.NET components and automated data ingestion from FTP/SFTP, web services, and third-party sources. Developed and optimized T-SQL stored procedures, CLR functions, and reporting data logic for high-volume processing. Created and deployed business reporting assets including SSRS reports and Power BI dashboards, and provided technical support for deployments and debugging across environments.

.NET

MS SQL

Power BI

Kathmandu University (KU)

Master's Degree • Information Technology

Kathmandu, Nepal

Nepal Engineering College

Bachelor's Degree • Electronics and Communication

Kathmandu, Nepal

Junior Backend Developer Confidence: Low API Engineer

API Design

2/10

How well APIs are designed

Minimal API design evidence: a simple Rails controller with standard CRUD-style actions is present but there is no versioning, no idempotency keys, no pagination conventions, and no explicit error contract or backwards compatibility strategy.

Evidence

app/controllers/forecasts_controller.rb: methods index, new, create, forecast_params

app/services/weather/forecast.rb: service object used by controller to fetch remote weather data

Data Layer & Database

2/10

Working with databases

Basic ActiveRecord / Rails defaults are used; there is evidence of transactional test fixtures and migration checks but no migration history, no explicit transaction boundary handling, and no tuned SQL or index work.

Evidence

spec/rails_helper.rb: config.use_transactional_fixtures = true

config/environments/test.rb: config.active_record.migration_error = :page_load

Scalability & Performance

2/10

Handling load and speed

Some production-oriented settings appear (eager loading, force SSL, server timing), but there are no concrete caching strategies, queue-based decoupling, connection-pooling tuning, or measured performance optimizations.

Evidence

config/environments/production.rb: config.eager_load = true, config.force_ssl = true

config/environments/development.rb: config.server_timing = true

System Architecture

2/10

Overall system structure

A small separation of concerns exists (controllers, app/services/weather) indicating basic modularity, but overall the app appears to be a single Rails monolith without documented service decomposition, feature-flagging, or secret/config management beyond Rails defaults.

Evidence

app/services/weather/forecast.rb: Weather service object

app/services/weather/geolocation.rb: Geolocation helper/service

Security & Auth

3/10

Protecting data and access

Some security awareness is present via Rails production defaults and test hardening; force SSL and request_id log tagging are enabled, and tests disable external network calls, but there is no clear authn/authz lifecycle, input validation strategy, or secrets management beyond dotenv usage referenced in service code.

Evidence

config/environments/production.rb: config.force_ssl = true, config.log_tags = [:request_id]

spec/rails_helper.rb: WebMock.disable_net_connect!(allow_localhost: true)

Reliability & Observability

2/10

Stability and monitoring

Basic observability and reliability fallbacks are visible in environment configs and logging setup, but advanced reliability patterns (retries with backoff, circuit breakers, timeouts, structured correlation across services) are not present in the analyzed files.

Evidence

config/environments/production.rb: config.log_level and ActiveSupport::TaggedLogging setup

config/environments/test.rb: config.action_dispatch.show_exceptions = :rescuable

Expertise

Ruby• Junior

Technologies

Python

PHP

SQL• since 2019 • Middle

Ruby• since 2025 • Junior

C#• since 2014 • Middle

MySQL• since 2019

PostgreSQL• since 2019

Rest API

.NET• since 2014

Oracle

GitHub Actions• since 2023

WebSockets

Ruby on Rails• since 2019

MS SQL• since 2014

CI/CD• since 2023

Jenkins

Git• since 2019

AWS• since 2019

Docker

Kubernetes

RSpec• since 2019

Capybara• since 2023

Factory Bot• since 2019

AWS Lambda• since 2019

Recommendations

Develop REST endpoints with explicit API versioning, consistent error contracts, and idempotency handling for create/update flows.
Add a migration history and evolve schema examples; include tests that cover schema migrations and edge cases for transactional boundaries.
Introduce basic reliability patterns for external calls in service objects such as timeouts, retries with exponential backoff and jitter, and circuit-breaker guards.
Expand automated tests to include integration tests for the weather service (using recorded HTTP responses) and add simple monitoring/metrics for key flows.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

whats-the-weather