Shivraj Malik
QA Engineer
Python
SQL
TypeScript
Node JS
JavaScript
Active 1 day ago
Invite to interview
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
A Python-focused automation engineer (middle level) specializing in end-to-end Selenium test frameworks and lightweight orchestration UIs. The strongest proven skill is building reliable test automation and orchestration tooling as shown by the subscription-billing-automation-framework pages (Search_customer.py), UI runners (flaskapp.py and Tkinter UIs), and test artifacts. There is little evidence of designing production backend systems such as transactional DB schema migrations, robust API versioning, or scalable distributed services.
Phone
Technical skills
Languages
5
Python
SQL
TypeScript
Node JS
JavaScript
QA
6
Playwright
Selenium
Pytest
Postman
BrowserStack
Appium
DevOps
7
GitHub
GitHub Actions
Docker
Git
Rest API
CI/CD
Jenkins
Frontend
4
React.js
Next.js
Tailwind CSS
Framer Motion
Other
11
MySQL
Flask
Axios
Tkinter
Vite
PostCSS
Copilot
JMeter
Locust
autoprefixer
TestRail
Timeline
QA Automation Engineer
•
Middle
Telgoo5
•
Full-Time
Built and maintained automated UI test suites for web-based telecom and billing applications using Python with Selenium WebDriver and Playwright, with tests organized through a modular framework and data-driven approach. Performed functional, regression, smoke, integration, and end-to-end testing across UI, API, and database layers. Implemented REST API automation with Postman/Python Requests and validated backend transaction and billing data using SQL/MySQL. Integrated test execution into CI/CD pipelines with Jenkins and tracked defects and root causes in JIRA.
Python
Selenium
Playwright
Pytest
Rest API
SQL
MySQL
Postman
CI/CD
Jenkins
Docker
Git
GitHub
GitHub Actions
BrowserStack
Agile
Scrum
Middle Backend Developer
Confidence: Medium Generalist
A Python-focused automation engineer (middle level) specializing in end-to-end Selenium test frameworks and lightweight orchestration UIs. The strongest proven skill is building reliable test automation and orchestration tooling as shown by the subscription-billing-automation-framework pages (Search_customer.py), UI runners (flaskapp.py and Tkinter UIs), and test artifacts. There is little evidence of designing production backend systems such as transactional DB schema migrations, robust API versioning, or scalable distributed services.
API Design
1/10
How well APIs are designed
Minimal API design evidence; a small Flask orchestration app exposes form routes but there is no versioning, idempotency, pagination contracts, or consistent error contract design.
Evidence
subscription-billing-automation-framework/UI/flaskapp.py: simple @app.route('/') POST handling and form-based orchestration
Data Layer & Database
1/10
Working with databases
Data handling is file-based (Excel) and in-memory state; there is no migration history, transactional DB logic, isolation-level awareness, or hand-tuned SQL in the human-authored code.
Evidence
subscription-billing-automation-framework/UI/plan_renew_change_ui_new.py: fetch_client_details uses openpyxl to read client credentials from Excel
subscription-billing-automation-framework/UI/flaskapp.py: get_url_for_client_and_instance reads Excel rows for instance URLs
Scalability & Performance
2/10
Handling load and speed
Some operational awareness in tests and scraping flows (use of WebDriverWait, pagination handling and sleeps) but no architecture-level scalability patterns such as queue-based decoupling, caching strategies, or connection pooling.
Evidence
subscription-billing-automation-framework/pages/Search_customer.py: loop that iterates customer pages and handles Next button with sleeps and defensive checks
subscription-billing-automation-framework/tests/test_plan_renew.py: WebDriverWait usage for stable element access
System Architecture
3/10
Overall system structure
Clear modular test-automation structure and Page-Object style patterns with a lightweight orchestration layer (Flask/Tkinter); this is deliberate tooling design but not a distributed/microservice architecture.
Evidence
subscription-billing-automation-framework/pages/Search_customer.py: page-level functions and navigation logic (POM-like organization)
subscription-billing-automation-framework/UI/flaskapp.py: Flask-based orchestration to trigger automation runs and coordinate shared state
Security & Auth
1/10
Protecting data and access
Minimal security engineering visible: basic input checks and URL normalization appear in places but there are hard-coded placeholders and no evidence of token lifecycle management, secrets handling, or systematic input sanitization for external APIs.
Evidence
subscription-billing-automation-framework/UI/flaskapp.py: app.secret_key set to placeholder 'your_secret_key'
subscription-billing-automation-framework/UI/plan_renew_change_ui_new.py: URL normalization (adds https) but credentials are read from plain Excel without encryption
Reliability & Observability
3/10
Stability and monitoring
Good test reliability practices for an automation project: try/except handling, debug/info logging, screenshot/report utilities and a test decorator for reporting; lacks structured logging, metrics, retries with backoff/jitter, and production-grade observability.
Evidence
subscription-billing-automation-framework/pages/Search_customer.py: defensive try/except blocks and debug/info prints around navigation and element access
subscription-billing-automation-framework/tests/test_plan_renew.py: uses @test_logger decorator and assertions to validate flows
subscription-billing-automation-framework/utils/logger.py: screenshot and HTML report utilities
Expertise
Python• Middle
Industries
Commerce• Middle
Financial Services• Middle
Technologies
Python• since 2023 • Middle
Rest API• since 2023
Flask
Tkinter
Recommendations
- Develop small, production REST endpoints (with versioning and clear error contracts) around current orchestration code to expose test-run control programmatically and to practice API design.
- Add proper secrets and config management (avoid Excel/plain credentials), and introduce secure credential storage or environment-based configuration for test credentials.
- Introduce DB-backed state or lightweight persistence with migrations and explicit transaction boundaries to replace ad-hoc Excel/state files and practice schema evolution.
- Add CI automation that runs the Selenium test suite in containers, and include structured logs, screenshots on failure, and basic metrics so runs are observable and repeatable
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Frontend Developer
Confidence: Medium UI Engineer
Frontend UI developer (Junior) focused on polished static and marketing websites with strong HTML/CSS and Tailwind skills. The strongest proven skill is crafting responsive, visually polished UI layouts as shown by portfolio/index.html, portfolio/style.css and the Tailwind globals and configuration. The public code does not show complex SPA state handling, server-state management, automated testing, or measured performance work.
UI Component Architecture
2/10
How interface parts are built
Mostly static HTML/CSS and project-level Tailwind globals rather than a deliberate component library or composable component architecture.
Responsive & Cross-browser
3/10
Works on all screens and browsers
Responsive layouts and mobile media queries are present with grid-based layouts, but there is no evidence of advanced responsiveness strategies like container queries or RTL/i18n readiness.
Performance Optimization
1/10
Speed of the interface
No measured performance work, bundle analysis, or code-splitting; only CSS animations and keyframes are declared without performance justification.
Accessibility & Semantics
1/10
Usable for everyone
Basic semantic HTML and some alt attributes exist, but there is no sign of ARIA on custom widgets, keyboard/focus management, or CI a11y tooling.
State Management & Data Flow
1/10
Managing data in the app
No server-state discipline or advanced async state handling; only minimal DOM scripting and a sitemap mapper are present.
UX & Visual Polish
3/10
Look and feel quality
Visual polish and layout consistency are clear (well organized CSS, glass utilities, animations), but UX edge cases like loading/error/empty states, undo, or progressive enhancement are not implemented.
Expertise
React• Junior
Modern Web Frameworks• Junior
HTML & CSS• Junior
Industries
Commerce• Middle
Technologies
TypeScript• Junior
Node JS• Junior
Tailwind CSS
Next.js
React.js
Vite
Axios
PostCSS
Framer Motion
autoprefixer
Recommendations
- Build and maintain static marketing sites and landing pages using Next.js and Tailwind to leverage existing strengths in HTML/CSS and design.
- Develop small React-based frontends (inventory dashboards, admin UIs) to gain experience with client state, server-state patterns and request cancellation.
- Add accessibility improvements (ARIA, keyboard focus management) and automated a11y checks to increase production readiness.
- Introduce testing and CI (unit/interaction tests and basic performance audits) to demonstrate robustness beyond visual polish.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Game Developer
Confidence: Medium Generalist
A junior-level generalist focused on small browser-based utility scripts with practical DOM and vanilla JavaScript usage. The strongest proven skill is building simple front-end utilities, demonstrated by the timer/stopwatch implementation (timer stopwatch.js) and a units mapping with conversion logic (unit converter.js). There is no evidence of game-engine work, rendering/graphics, physics simulation, testing, or performance engineering in the public code.
Gameplay Systems & Mechanics
How game logic works
Not evidenced in public code
Graphics & Rendering
Drawing game visuals
Not evidenced in public code
Physics & Math
Game physics and math
Not evidenced in public code
Engine Proficiency
Skill with the game engine
Not evidenced in public code
Performance & Frame Budget
Keeping the game smooth
Not evidenced in public code
Content Pipeline & Tooling
Tools for game content
Not evidenced in public code
Recommendations
- Develop small web utilities and tools or UI prototypes that require straightforward DOM manipulation and input parsing, such as calculators, timers, and unit converters.
- Improve code robustness by adding input validation, error handling, and unit tests for conversion logic and edge cases.
- Practice performance- and architecture-minded projects next, such as a small game mechanic with a fixed timestep loop, or a pooled object spawn demo to demonstrate frame-budget thinking.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: