Quality Engineering
quality layerStarted by ensuring software worked. Built automated test suites for web and API layers.
JavaSeleniumRestAssuredTestNGCucumber
SYSTEM ONLINE
Software Engineer
Rohit Tudu
I build reliable software systems — then automate, test, validate, and ship them. From automated testing and API validation to backend development, containerization, and cloud deployment — I approach software as an end-to-end engineering system.
- role
- Software Engineer
- focus
- Quality · Backend · Cloud
- status
- ONLINE
- location
- Remote · Worldwide
system status
- FrontendONLINE
- BackendONLINE
- APIONLINE
- AutomationACTIVE
- ContainersRUNNING
- CloudDEPLOYED
— representational, not live telemetry
Engineering Identity
One system, three layers
Quality engineering taught me how software behaves. Backend engineering taught me how to build it. System engineering taught me how to ship it.
01 02 Backend Engineering
service layerExpanded from testing APIs to building them. Designed and implemented REST services with Python.
PythonFastAPISQLAlchemyPostgreSQLREST APIs03 System Engineering
infra layerNow works across the complete software lifecycle — development, testing, containerization, and deployment.
DockerAWSCI/CDMicroservicesDeployment
Started from testing and automation. Expanded into software development and backend engineering. Now works across the complete software lifecycle — development, testing, deployment, and cloud infrastructure.
01B · trajectory
The engineering journey
Chronological evolution — each stage expands to show what was actually worked on. Not a résumé bullet dump: a technical path.
- Python / FastAPI service development
- SQLAlchemy models and PostgreSQL persistence
- Pydantic validation and typed contracts
- REST APIs and WebSocket real-time channels
- Docker images and multi-service compose setups
- CI/CD pipeline design
- AWS core concepts: compute, storage, networking
- Deployment and environment management
- Java + Selenium web automation
- RestAssured API test suites
- TestNG runners and Cucumber BDD scenarios
- Postman collections and GitLab CI/CD execution
Experience
Engineering log
Recorded like an incident log — what was built, automated, and shipped, with the systems involved.
EPAM Systems
Junior Software Test Automation Engineer2026Automated test coverage for enterprise web and API layers as part of a delivery team.
- Built REST API automation suites validating contracts, status codes, and payload schemas
- Automated critical web application flows with Selenium WebDriver
- Developed and maintained test frameworks, utilities, and BDD scenarios
- Integrated test execution into GitLab CI/CD pipelines
JavaSeleniumRestAssuredPostmanTestNGCucumberGitLab CI/CD
LOG END — more history available on LinkedIn.
Projects
Engineering case studies
Built, tested, and deployed — each project documented like a system: problem, architecture, implementation, and validation.
Desktop Application
MyWellbeing
A local-first desktop app with embedded data architecture and analytics.
ElectronReactTypeScriptSQLite+2
Web Application
ArtConnect
Artwork discovery and commerce on a modern web stack.
Next.jsReactTypeScriptTailwind CSS+1
est. 2025
Developer Tooling
Terminal Critic CLI
A feature-complete CLI for tracking media with persistence and authentication.
CLI ArchitectureJSON PersistenceAuthenticationCSV Import+1
est. 2024
Quality Engineering
I don't just build software. I build systems that can be tested, validated, and trusted.
The differentiator: every layer of the stack has an automated answer to 'how do we know it works?'
validation pipeline
APPLICATION
The system under test
API
Contracts and endpoints
AUTOMATION
Selenium · RestAssured · Cucumber
TEST EXECUTION
TestNG runners · parallel suites
REPORTING
Allure · Extent Reports
CI/CD
GitLab CI/CD · scheduled runs
SIMULATED RUN — ILLUSTRATIVE
RUN #4821
- API Tests0/42✓
- UI Tests0/32!
- Regression0/50!
Duration00m 00s
- ✓HTTP Assertions
- ✓Schema Validation
- ✓Authentication
- ✓UI Validation
build statusPASSED
toolchain
SeleniumRestAssuredTestNGCucumberPostmanGitLab CI/CDAllureExtent Reports
Backend Engineering
From testing APIs to building them
A year of reading responses, then validating them, then designing them. FastAPI became the centerpiece of the transition.
capability path
API CONSUMER
Calling services, reading responses
API TEST AUTOMATION
Validating contracts, schemas, status codes
API DESIGN
Typed contracts with Pydantic
BACKEND ENGINEERING
FastAPI services, persistence, real-time
api_playground
simulated
GET /api/projects
Authorization: Bearer ****
Content-Type: application/json
200 OK· response_time: 84ms
{
"status": 200,
"data": [
{
"name": "Nebula",
"stack": [
"FastAPI",
"PostgreSQL",
"WebSockets"
]
},
{
"name": "MyWellbeing",
"stack": [
"Electron",
"SQLite"
]
},
{
"name": "ArtConnect",
"stack": [
"Next.js",
"TypeScript"
]
},
{
"name": "Terminal Critic",
"stack": [
"CLI",
"JSON"
]
}
]
}simulated responses — request log: no requests yet
Containers
Reproducible by construction
Every environment is a build artifact: layered, immutable, and portable from development to production.
image layers
APPLICATIONYour code + runtime entrypoint
FASTAPIApplication framework layer
PYTHONRuntime layer
DEPENDENCIESOS packages and libraries
CONTAINERIsolated, reproducible environment
layer 0 = runtime entrypoint · image = immutable artifact
containersclick to toggle (simulated)
illustrative lifecycle — not live container orchestration
Cloud / DevOps
Infrastructure thinking
Containerized services, pipeline-driven delivery, and cloud concepts — the operating layer of everything I build. Hover a node to inspect its role.
aws / conceptual topology
COMPUTEworkloads
Application workloads — containerized services and backend deployment.
STORAGEobjects · files
Object storage for uploads, media, and static assets.
DATABASEmanaged data
Managed relational database for durable application state.
NETWORKrouting · dns
Routing, DNS, and ingress to the exposed services.
REGISTRYimages
Container image registry feeding the deployment pipeline.
conceptual architecture — hover to inspect each layer's purpose
delivery pipeline
CI/CD PIPELINE
IMAGE BUILD
REGISTRY
DEPLOY
HEALTH CHECK
- COMPUTEApplication workloads — containerized services and backend deployment.
- STORAGEObject storage for uploads, media, and static assets.
- DATABASEManaged relational database for durable application state.
- NETWORKRouting, DNS, and ingress to the exposed services.
- REGISTRYContainer image registry feeding the deployment pipeline.
Technology
An interconnected stack, not a logo grid
Select a technology to trace how it connects to the rest of the system — every tool sits inside a workflow.
select a technology to trace its dependency chain →
LANGUAGES
Languages
BACKEND
Backend Engineering
TEST AUTOMATION
Quality Engineering
DATABASE
Data Layer
DEVOPS / CLOUD
Infrastructure
FRONTEND
Web Development
System Design
How I think about software
Not a skills list — the engineering questions I ask before, during, and after building something.
contracts
API Design
APIs are contracts first. Define them clearly, validate them strictly, then implement against them.
- 01Contract
- 02Validation
- 03Business Logic
- 04Persistence
- 05Response
Engineering Principles
Operating rules
AUTOMATE REPETITIVE WORK
If a machine can do it twice, it should do it forever.
TEST AT MULTIPLE LEVELS
Unit, integration, API, UI — each layer earns its own coverage.
DESIGN CLEAR API CONTRACTS
Typed inputs and outputs make every consumer's life predictable.
KEEP SYSTEMS OBSERVABLE
Logs, metrics, and status that answer 'what happened' without guessing.
CONTAINERIZE EVERYTHING
Reproducible environments from development to production.
BUILD FOR MAINTAINABILITY
The next engineer (often me) will thank the current one.
GitHub
Public work
Live from the GitHub API — latest public repositories for reaganblade.
ENGINEERING PROFILE
Software Engineer
Quality Engineering & Test Automation
Backend Engineering (Python / FastAPI)
Cloud & Containerization (Docker / AWS)
Automation × Backend × Cloud2026
11 · contact
Let's build something reliable.
Interested in software engineering, backend systems, automation, or infrastructure? The channels are open.