Prajwal Amatya
Software Developer
12+ years exp
PHP
Python
JavaScript
C#
SQL
Ruby
Active 13 days ago
+8084397244 Invite to interview
Message
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.
Technical skills
PHP
Python
JavaScript
C#• Middle • 12y+
SQL• Middle • 7y+
Ruby• Junior
C#
.NET• 12y+
Ruby
Factory Bot• 7y+
RSpec• 7y+
Ruby on Rails• 7y+
Capybara• 3y+
Databases
Oracle
MS SQL• 12y+
MySQL• 7y+
PostgreSQL• 7y+
DevOps
Docker
Jenkins
Kubernetes
Rest API
WebSockets
AWS• 7y+
AWS Lambda• 7y+
Git• 7y+
CI/CD• 3y+
GitHub Actions• 3y+
AI/ML
AI Agents
CrewAI
Model Context Protocol
Prompt Engineering
RAG
Copilot• 3y+
LLM• 3y+
Frontend
Redux
Material UI• 7y+
PrimeReact• 7y+
React.js• 5y+
Mobile
State Management
Analytics
Power BI• 12y+
QA
Jest• 7y+
Timeline
IT Sr. Software Developer
•
Senior
Take 2
•
Full-Time
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
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 Railssince 2019
React.jssince 2019
PostgreSQLsince 2019
MySQL
SQL
AWS Lambda
AWSsince 2019
RSpecsince 2019
Factory Bot
Jestsince 2019
Material UI
PrimeReact
Git
System Analyst
•
Middle
Pioneer Solutions LLC
•
Full-Time
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
C#
MS SQL
Power BI
Kathmandu University (KU)
Master's Degree •
Information Technology
Nepal Engineering College
Bachelor's Degree •
Electronics and Communication
Junior Backend Developer
Confidence: Low API Engineer
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.
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• Middle • 7y+
Ruby• Junior
C#• Middle • 12y+
MySQL• 7y+
PostgreSQL• 7y+
Rest API
.NET• 12y+
Oracle
GitHub Actions• 3y+
WebSockets
Ruby on Rails• 7y+
MS SQL• 12y+
CI/CD• 3y+
Jenkins
Git• 7y+
AWS• 7y+
Docker
Kubernetes
RSpec• 7y+
Capybara• 3y+
Factory Bot• 7y+
AWS Lambda• 7y+
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: