Parth Gupta
Software Developer
10+ years exp
8+ years ML exp
JavaScript
Dart
SQL
C#
System Architecture: 4/10
Active 7 days ago
+46 (76) 1963896 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend C#/.NET developer (Middle) specializing in building small, well-structured REST API services with unit tests. The strongest proven skill is implementing thin ASP.NET Core controllers and a service layer with file-backed persistence and unit tests, evidenced by ThesaurusController.cs, SynonymService.cs and SynonymServiceTests.cs. There is little evidence of database-backed schema evolution, distributed systems design, cloud deployment, or high-scale performance engineering in the public code.
Technical skills
JavaScript
Dart• Junior
SQL• Senior • 10y+
C#• Senior • 6y+
Dart
Riverpod
Go_router
Dio
C#
.NET
ASP.NET Core• 7y+
Moq• 7y+
Databases
Oracle
RabbitMQ
MS SQL• 10y+
Apache Kafka• 3y+
Mobile
Clean Architecture
Flutter
Firebase
Offline-First
Material Design
Core Location
DevOps
Jenkins
Azure• 6y+
CI/CD• 6y+
Docker• 6y+
Rest API• 6y+
Azure DevOps
Frontend
Bootstrap
JQuery• 3y+
React.js• 3y+
AI/ML
LLM
Tokenization• 8y+
Claude
Copilot
Prompt Engineering
Cybersecurity
Dependabot
SBOM
Timeline
Senior Software Engineer
•
Senior
Tobii Dynavox
•
Full-Time
Architected Azure DevOps YAML pipelines and modernized legacy services into Windows container-based deployments. Drove spec-driven development workflows using Claude and GitHub Copilot to keep AI-generated code aligned with enterprise architecture. Modernized a legacy .NET application for WCAG 2.1 Level AA compliance and improved supply-chain security via Dependabot plus SBOM generation. Re-engineered real-time notification flows using Azure Functions, Service Bus, and Logic Apps and integrated analytics dashboards and Zuora API for subscription and payment processing.
Azure
Azure DevOps
CI/CD
React.js
Copilot
Claude
Dependabot
SBOM
Prompt Engineering
Associate Consultant
•
Middle
Globallogic
•
Full-Time
Delivered enterprise solutions integrating 30+ vendor systems using .NET/.NET Core backend services with React frontends, C#, and SQL. Improved scalability and maintainability by introducing standardized design patterns and reducing duplication across codebases. Built end-to-end CI/CD workflows and supported customer deployments using GitHub, Docker, and Azure messaging and storage services. Strengthened delivery quality by adding NUnit with Moq for unit and integration testing and raising coverage to 95%.
C#
React.jssince 2020
SQL
Docker
Azuresince 2020
CI/CDsince 2020
Moq
Rest API
Software Engineer
•
Middle
Landis+Gyr
•
Full-Time
Built and streamlined a smart metering platform for high-volume, event-driven processing using SQL and ASP.NET. Designed a Kafka-based event streaming pipeline to handle device telemetry and distribute it with low-latency delivery for large concurrent usage. Improved reliability via comprehensive unit testing with NUnit and Moq and added technical documentation, increasing code coverage significantly. Optimized database performance by using SQL Profiler, execution plans, and Query Store to address long-running queries.
SQL
ASP.NET Core
Apache Kafka
Moqsince 2019
Full Stack Developer
•
Middle
Rosh Capital
•
Full-Time
Developed features on a P2P money lending platform using ASP.NET MVC. Guided implementation of a Stripe-based payment gateway module, covering secure online transactions with end-to-end flow design. Implemented tokenization, webhook handling, and transaction logging to support reliable payment processing. Coordinated integration details to ensure payment events were correctly captured by the system.
Tokenization
Software Engineer
•
Middle
Axon IT Services
•
Full-Time
Delivered inventory management and school management web applications using .NET and SQL Server. Implemented backend data handling and application features backed by relational database design. Supported maintenance and ongoing updates while working with an Agile team to ship sprint deliverables. Provided fixes and improvements based on user needs and defect reports.
SQLsince 2017
Trainee Application Developer
•
Junior
Trendsetterz
•
Full-Time
Maintained a web application with a .NET backend and an Angular/JQuery-based frontend. Built functionality to crawl news sources, aggregate articles, and render customizable news cards for end users. Performed large-scale data cleanup for a voter database by standardizing name records to reduce inconsistencies. Improved query performance by optimizing the updated dataset and related application logic.
Angular
JQuery
Junior Backend Developer
Confidence: Medium API Engineer
Backend C#/.NET developer (Middle) specializing in building small, well-structured REST API services with unit tests. The strongest proven skill is implementing thin ASP.NET Core controllers and a service layer with file-backed persistence and unit tests, evidenced by ThesaurusController.cs, SynonymService.cs and SynonymServiceTests.cs. There is little evidence of database-backed schema evolution, distributed systems design, cloud deployment, or high-scale performance engineering in the public code.
API Design
3/10
How well APIs are designed
Basic REST API surface with clear controller/service separation but minimal API design features (no versioning, pagination, or explicit error contract beyond ModelState).
Data Layer & Database
2/10
Working with databases
Simple file-backed cache usage rather than a relational database; no migration history, transaction boundaries, or advanced data-layer patterns are present.
Scalability & Performance
1/10
Handling load and speed
In-memory and file-based approaches with no scalability controls, eviction, batching, or caching invalidation strategy; not designed for high throughput or large datasets.
System Architecture
4/10
Overall system structure
Reasonable separation of concerns and DI-friendly structure (controllers, library services, interfaces). The architecture is small-scale but intentionally modular and testable.
Evidence
ProManXi/BeijerThesaurusProject/ThesaurusWebAPI/Controllers/ThesaurusController.cs: thin controller delegating to ISynonymService and IValidationService
ProManXi/BeijerThesaurusProject/ThesaurusLibrary/Services/SynonymService.cs: service implementation with injected ISupportService and ICacheService
Security & Auth
2/10
Protecting data and access
Minimal input validation and error handling are present but no auth/authorization, no rate limits, and no demonstrated defenses against larger web threats beyond basic checks.
Reliability & Observability
3/10
Stability and monitoring
Basic observability and reliability practices: custom logger usage and unit tests exist, but no structured tracing, metrics, timeouts, or retry/backoff patterns are shown.
Verified artifacts
Expertise
.NET• Junior
Industries
Education• Junior
Recommendations
- Build small to medium REST services and APIs in ASP.NET Core where clear controller-service separation and unit tests are required.
- Migrate file-backed caches to a proper database or durable store and implement schema migrations and transaction boundaries for multi-user scenarios.
- Harden API surfaces with auth/authorization, rate limiting, and input-sanitization rules when exposing services publicly.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Mobile Developer
Confidence: Medium Cross-platform
Cross-platform mobile engineer (Flutter) at a Middle level specializing in offline-first, location-based gameplay features. The strongest proven skill is building resilient offline synchronization and retention-critical pipelines using a disk-backed WAL, a deterministic batch-drain service, and user-bound caches (see mobile/lib/shared/services/step_claim_queue.dart, batch_drain_service.dart, notification_cache.dart). There is limited public evidence of release automation (store pipelines) and measured performance telemetry in the code artifacts provided.
Platform Native Mastery
5/10
Knowing the mobile platform
Solid platform/lifecycle handling and cancellation patterns are visible (permission checks, subscription cancelation, mounted guards, write-layer disposal), but there is limited evidence of deep OS-level hardening (process-death state restoration, advanced lifecycle edge-case frameworks).
Evidence
mobile/lib/shared/services/location_service.dart: requestPermission() and position APIs (permission gating)
mobile/lib/shared/services/step_claim_queue.dart: WAL-based enqueue semantics (persistent queue lifecycle)
mobile/ios/Runner/AppDelegate.swift: iOS app lifecycle integration (AppDelegate/SceneDelegate present)
Mobile UI/UX & Responsiveness
5/10
Smooth mobile experience
UI shows practical, production-minded patterns (shimmer placeholders, performance-minded list lazy-loading, modal/sheet patterns, animation control) and fixes for rebuild/time leaks, but there is no evidence of broad adaptive UI strategy for foldables/tablets or documented accessibility work.
Evidence
mobile/lib/shared/widgets/shimmer_loading.dart: shimmer placeholders used during initial load
mobile/lib/features/home/home_tab.dart: shimmer-to-content flow and UI components; mission countdown resource-leak fix (dispose cancels timer)
mobile/lib/shared/widgets/retry_button.dart and mobile/lib/shared/widgets/offline_notice.dart: in-place retry affordances and offline recovery controls
Performance & Battery
4/10
Speed and battery use
Shows concrete performance/battery attention (timer cancellation, removing unbounded caches, backoff on retry, bounded drains), but lacks measured profiling artifacts (p95/p99 numbers, baseline vs optimized traces) and device telemetry.
Evidence
mobile/lib/shared/services/batch_drain_service.dart: backoff window, drainNow loop and deterministic clock for tests
mobile/lib/shared/services/step_claim_queue.dart: write-ahead log with disk durability tests
api/MyLoop.Api/Services/HexGridService.cs (referenced in PRs): removed unbounded static cache to prevent memory growth (perf/memory work mentioned in PRs)
Offline & Data Sync
7/10
Working offline and syncing
Clear offline-first design: disk-backed WAL queue, drain service with deterministic tests, user-bound caches and clear-on-signout semantics, and durability tests prove disk==memory invariants; that is strong, production-worthy offline sync work.
Evidence
mobile/lib/shared/services/step_claim_queue.dart: persistent WAL enqueue and init() hooks
mobile/lib/shared/services/batch_drain_service.dart: drainNow, backoff windows, injectable clock for deterministic tests
mobile/lib/shared/services/notification_cache.dart: user-bound file-backed inbox with cross-user guard and encode/decode tests
Device Integration
6/10
Using device features
Good device integration: live GPS tracking, permission flows, SignalR/real-time subscription handling, and map tile layers; permission denial paths and retry UX are present. Some platform corner cases (background location runtime traps, detailed multi-permission flows) are documented in skills but not shown as implemented in release code.
Evidence
mobile/lib/shared/services/location_service.dart: location permission request and currentPosition APIs
mobile/lib/shared/services/territory_realtime_service.dart: SignalR connection and onHexChanges stream handling
mobile/ios/Runner/AppDelegate.swift and SceneDelegate.swift: iOS embedding points present
Release & App Lifecycle
3/10
Building and publishing apps
CI and verification practices are present (coverage gating, test isolation, Testcontainers for integration tests), but explicit mobile release tooling (fastlane/Play/App Store deploy pipelines, signed binary configs) and crash-report integration with triaged fixes are not evidenced.
Evidence
.github/workflows/ (coverage gating and CI changes described in PRs)
mobile/test/*: many unit/widget tests and specialized disk-concurrency tests (e.g. step_claim_queue_test.dart)
docs/ and .claude/skills: verification-loop and ci(coverage) descriptions used as process artifacts
Expertise
Flutter• Junior
Industries
Gaming• Junior
Technologies
C#• Senior • 6y+
Dart• Junior
Flutter
Firebase
Clean Architecture
Moq• 7y+
Riverpod
Dio
Go_router
Offline-First
Core Location
Material Design
Recommendations
- Lead implementation of offline-first mobile features that require a durable WAL, resumable drains, and idempotent server contracts (e.g. walk capture, queued uploads).
- Build and harden GPS/location-based features and anti-cheat integrations where client and server validation must agree (mock walk simulator, preview + server-side path validation).
- Own cross-stack contract work between Flutter client and backend APIs for user-bound caches, session correlation (walkSessionId), and privacy-sensitive fields.
- Develop robust mobile unit+integration test suites and CI gating for mobile (coverage gates, deterministic path tests, disk-stubbing patterns).
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior QA Engineer
Confidence: Medium Generalist
A C# backend engineer (middle-level) focused on small web API services and service-layer unit tests. The strongest proven skill is implementing testable service-layer logic with dependency injection and unit tests, as shown by ThesaurusLibrary.Services.SynonymService and ThesuarusTests/SynonymServiceTests.cs. There is no public evidence of CI integration, API contract or integration testing, performance/load testing, or advanced test infrastructure.
Test Automation Frameworks
2/10
Building automated tests
There are unit tests (NUnit-style) and use of Moq covering the service layer, but no evidence of a custom test fixture layer, testcontainers, mock servers with logic, parallelization/sharding, selector discipline, or advanced test-infra. This is basic unit-test automation rather than a dedicated QA/test-framework effort.
Test Coverage & Strategy
2/10
What and how to test
Tests exercise happy-paths and some negative cases at the unit level (e.g. missing word path), but there is no risk-based tagging (smoke/critical/regression), no explicit boundary/property tests, no mutation or invariants, and assertions are simple and example-driven rather than adversarial/failure-focused.
API & Integration Testing
1/10
Testing how parts work together
API controllers are present (ASP.NET Core controller) but there are no API-level integration or contract tests, no schema validation tests, and no idempotency/retry scenario coverage; evidence is server-side controller code with unit tests focused on services rather than end-to-end API contracts.
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
Finding and describing bugs
Not evidenced in public code
CI Test Integration
Running tests automatically
Not evidenced in public code
Expertise
Unit & Component Testing• Junior
Industries
Education• Junior
Technologies
.NET
ASP.NET Core• 7y+
Recommendations
- Develop RESTful ASP.NET Core endpoints and extend coverage with integration tests (controller-to-storage) using a reproducible test database or Testcontainers.
- Add CI test-integration (GitHub Actions/GitLab CI) that runs unit and integration suites and collects coverage to prevent regressions.
- Replace broad exception-swallowing with specific error handling and fail-fast assertions to avoid hiding production errors and to make tests more reliable.
- Introduce contract/schema validation for API responses and add negative-path API tests (malformed input, auth failures, 4xx/5xx scenarios) and a small set of property-based or boundary tests for graph traversal logic
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: