2

Remote Bug Fixing Jobs in Oregon (NOW HIRING)

Salem, OR - Remote Only local Candidates Preferred Only W2 - No C2C USC/GC/H4 EAD 8 to 10 hours a ... bug fixes and system stability. Offer technical support and assistance for JJIS users as needed.

New

Engineering Project and QA Manager

OR · Remote

$140K - $178K/yr

Remote (United States, Europe, Canada, or LATAM) Role Type: Full-Time Reporting to: VP of ... a bug, read a stack trace, and write a test case to automate fixing it * Hands-on QA experience ...

Senior Software Engineer -GCP

OR · On-site +1

$122K - $161K/yr

Design and implement features, bug fixes, and infrastructure automation for the GCP HCP platform ... For positions with Remote-US locations, the actual salary range for the position may differ based ...

Senior Software Engineer -GCP

Salem, OR · On-site +1

$123K - $162K/yr

Design and implement features, bug fixes, and infrastructure automation for the GCP HCP platform ... For positions with Remote-US locations, the actual salary range for the position may differ based ...

Strong background in orchestrating large codebases or mono-repos and fixing dependency and build ... Excellent communication in a remote, distributed setup. Comfortable working across product, infra ...

This is a remote position. ESSENTIAL FUNCTIONS & RESPONSIBILITIES: * Create, automate, execute and ... Quickly respond to and test fixed defects; proactively identify problems/edge cases rooted in ...

Remote Bug Fixing information

What are the key skills and qualifications needed to thrive as a Remote Bug Fixing specialist, and why are they important?

To thrive in Remote Bug Fixing, you need strong problem-solving abilities, proficiency in programming languages relevant to your projects, and experience with debugging and troubleshooting software issues. Familiarity with version control systems like Git, issue tracking tools such as Jira, and remote collaboration platforms is essential, along with a background in computer science or software engineering. Excellent communication, attention to detail, and self-motivation are crucial soft skills for effectively diagnosing issues and collaborating with distributed teams. These skills ensure timely resolution of bugs, maintain software quality, and support efficient teamwork in a remote environment.

What is remote bug fixing?

Remote bug fixing is the process of identifying, diagnosing, and resolving software bugs or issues from a location outside of the physical office, often through remote access tools or collaboration platforms. This approach allows software developers or support engineers to address problems in software applications without being on-site, increasing flexibility and reducing downtime. Remote bug fixing is common in distributed teams and is essential for maintaining and improving software quality, especially in today's global and digital work environment.

What is the difference between Remote Bug Fixing vs Remote Software Developer?

AspectRemote Bug FixingRemote Software Developer
Primary RoleIdentify and fix bugs in software applicationsDesign, develop, and maintain software applications
Required SkillsDebugging, problem-solving, knowledge of programming languagesProgramming, system design, coding, testing
Work EnvironmentTypically part of a QA or development team, often in agile settingsFull development lifecycle, collaborative teams, project management tools
CredentialsKnowledge of programming languages, debugging tools, sometimes certificationsComputer science degree or equivalent, coding certifications often preferred

Remote Bug Fixing focuses on troubleshooting and resolving software issues, while Remote Software Development involves creating and building software from scratch. Both roles require technical skills, but bug fixers specialize in problem resolution, whereas developers handle the entire development process.

What are some common challenges faced when working in a remote bug fixing role, and how can they be managed?

Remote bug fixing professionals often encounter challenges such as coordinating with distributed teams across different time zones, limited direct access to development environments, and communication delays. These can be managed by leveraging collaboration tools (like Slack or Jira), maintaining clear documentation, and scheduling regular check-ins with team members. Proactively seeking clarifications and following structured debugging processes also help ensure efficient problem resolution in a virtual setting.
What are popular job titles related to Remote Bug Fixing jobs in Oregon? For Remote Bug Fixing jobs in Oregon, the most frequently searched job titles are:
Infographic showing various Remote Bug Fixing job openings in Oregon as of June 2026, with employment types broken down into 93% Full Time, 3% Part Time, 3% Contract, and 1% Nights. Highlights an 85% Physical, 4% Hybrid, and 11% Remote job distribution.

Full-time

Posted 2 days ago


Job description

Role : JJIS Small Talk Developer
Location : Salem, OR - Remote
Only local Candidates Preferred
Only W2 - No C2C
USC/GC/H4 EAD
8 to 10 hours a week
Job Decsription:
Key Responsibilities:
Serve as a Smalltalk developer on the application development team.
Interpret and document legacy system logic to facilitate the modernization process.
Support and maintain the existing JJIS Smalltalk application.
Work within a complex technical environment that includes multiple desktop operating systems, client/server technology, relational databases, and integrations with other state information systems.
Communicate technical concepts effectively to IT staff, business users, and management.
Required Qualifications:
Extensive experience in developing with the Smalltalk programming language.
Strong understanding and experience in Object-Oriented Analysis and Design (OOAD).
Excellent communication skills for effectively conveying technical details to diverse stakeholders
Experience working in a diverse technical environment with multiple system integrations.
Participation in all phases of the software development lifecycle.
DESCRIPTION OF DUTIES
Modernization of the Legacy JJIS Application:
Support the JJIS modernization project by translating Smalltalk code from the existing application.
Analyze and interpret the legacy JJIS Smalltalk application to document business logic and functionality.
Participate in Agile process, including reviewing user stories and technical reviews of the user stories and acceptance criterias.
Collaborate with cross-functional teams, including business analysts, quality assurance analysts, developers, and stakeholders.
Facilitate, document, and actively participate in Agile development meetings and work sessions.
Support testing efforts such as QA and UAT testing on modernized JJIS application.
Support for the Existing Legacy JJIS Smalltalk Application:
Provide ongoing support and maintenance for the legacy JJIS Smalltalk application as needed.
Develop use cases and user stories to support future development efforts.
Assist the Service Desk in diagnosing and resolving production issues, analyzing user problems, and determining the best approach to bug fixes and system stability.
Offer technical support and assistance for JJIS users as needed.
Conduct design walkthroughs with peers, supervisors, and stakeholders to validate and refine proposed solutions.
Support testing efforts such as unit testing on legacy JJIS application.