2

Remote Smalltalk Jobs in Oregon (NOW HIRING)

Remote Smalltalk information

What is the difference between Remote Smalltalk vs Remote Python Developer?

AspectRemote SmalltalkRemote Python Developer
Required CredentialsExperience with Smalltalk, programming skills, possibly certifications in specific Smalltalk environmentsProficiency in Python, relevant certifications (e.g., Python Institute), coding experience
Work EnvironmentRemote development teams, Smalltalk IDEs, collaborative toolsRemote teams, Python IDEs, cloud-based development platforms
Industry UsageLegacy systems, specialized software, research projectsWeb development, data analysis, automation, AI applications
Common Search & ComparisonYesYes

Remote Smalltalk developers focus on maintaining and developing legacy or specialized systems using Smalltalk, often in niche industries. In contrast, Remote Python Developers work across a broader range of applications like web development and data science. While both roles require programming skills and remote work experience, the specific language expertise and industry focus differ significantly.

What are some unique challenges of working remotely as a Smalltalk developer, and how can they be addressed?

Working remotely as a Smalltalk developer often means collaborating with teams that may not be familiar with the language, as Smalltalk is less commonly used than other programming languages. Communication and thorough documentation become essential when explaining design decisions or integrating with other systems. Additionally, remote Smalltalk developers may need to set up specialized development environments and find ways to participate in code reviews and pair programming sessions virtually. Leveraging collaboration tools and proactively engaging with your team can help bridge these gaps and ensure smooth project workflows.

What is a remote Smalltalk developer?

A Remote Smalltalk Developer is a software engineer who specializes in programming with the Smalltalk language and works remotely, often from home or another location outside of a traditional office. Smalltalk is an object-oriented, dynamically typed programming language known for its simplicity and powerful development environment. Remote Smalltalk Developers typically build and maintain applications, fix bugs, and collaborate with teams using online tools. They may work for companies that use legacy Smalltalk systems or on modern projects that leverage Smalltalk's unique capabilities. Remote work allows for flexibility in location and work hours while delivering the same technical expertise.

What are the key skills and qualifications needed to thrive as a remote Smalltalk developer?

To thrive as a Remote Smalltalk Developer, you need strong proficiency in Smalltalk programming, object-oriented design, and experience with relevant frameworks, typically supported by a degree in computer science or equivalent experience. Familiarity with version control systems (like Git), remote collaboration tools, and Smalltalk environments such as Pharo or Cincom VisualWorks is highly valuable. Excellent problem-solving, self-motivation, and clear written communication are crucial soft skills for succeeding in a distributed team setting. These competencies ensure high-quality code, effective collaboration, and productivity in a remote work context.
What cities in Oregon are hiring for Remote Smalltalk jobs? Cities in Oregon with the most Remote Smalltalk job openings:
Infographic showing various Remote Smalltalk job openings in Oregon as of August 2026, with employment types broken down into 100% Full Time. Highlights an 100% Remote job distribution.

Full-time

Re-posted 19 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.