1

Haskell Jobs in Oregon (NOW HIRING)

Fluent in using semi-formal methods such as Haskell or other functional programming languages, including executable formal specifications. * Required General Skills: * Must work well with customers ...

Fluent in using semi-formal methods such as Haskell or other functional programming languages, including executable formal specifications. * Required General Skills: * Must work well with customers ...

Fluent in using semi-formal methods such as Haskell or other functional programming languages, including executable formal specifications. * Required General Skills: * Must work well with customers ...

Haskell information

See Oregon salary details

$9

$22

$38

How much do haskell jobs pay per hour?

As of Jul 15, 2026, the average hourly pay for haskell in Oregon is $22.00, according to ZipRecruiter salary data. Most workers in this role earn between $16.25 and $25.67 per hour, depending on experience, location, and employer.

What is a Haskell job?

A Haskell job involves developing software using the Haskell programming language, which is known for its strong type system and functional programming paradigm. Haskell developers work on applications ranging from financial systems and blockchain technologies to compiler development and distributed systems. These roles often require expertise in functional programming concepts, type theory, and performance optimization. Many Haskell jobs are found in research-driven industries, fintech, and startups leveraging functional programming for reliability and maintainability.

What kind of projects and team environments do Haskell Developers typically work in?

Haskell Developers often contribute to a wide range of software projects, including fintech applications, data processing pipelines, and large-scale distributed systems. Teams can vary in size, but Haskell developers frequently work in small, highly skilled groups where collaboration and code review are important parts of the workflow. Many companies hiring for Haskell roles offer flexible, remote-friendly environments and encourage participation in open-source communities. Collaborating closely with product managers, QA engineers, and other developers is common to ensure robust and maintainable solutions. This collaborative setting fosters both individual growth and collective technical excellence.

What are the key skills and qualifications needed to thrive in the Haskell position, and why are they important?

To thrive as a Haskell Developer, you need advanced proficiency in functional programming, Haskell language expertise, and a solid background in computer science or software engineering. Familiarity with version control systems like Git, build tools such as Stack or Cabal, and knowledge of software development best practices are commonly expected. Strong problem-solving skills, clear communication, and the ability to work independently or within a distributed team help set candidates apart. These skills ensure high-quality, reliable, and efficient code development in complex, collaborative software projects.

What are the most commonly searched types of Haskell jobs in Oregon? The most popular types of Haskell jobs in Oregon are:
Infographic showing various Haskell job openings in Oregon as of July 2026, with employment types broken down into 1% Internship, 2% As Needed, 83% Full Time, 8% Part Time, 1% Temporary, and 5% Contract. Highlights an 94% Physical, and 6% Remote job distribution, with an average salary of $45,767 per year, or $22 per hour.
Senior Software Engineer - Mercury Command

Senior Software Engineer - Mercury Command

Mercury

Portland, OR • On-site

$129K - $171K/yr

Full-time

Posted 19 days ago


Job description

Job Summary:
Mercury is a fintech company that is building technology to enhance financial interfaces for the long term. The Senior Software Engineer will be responsible for designing and shipping new capabilities for Command, maintaining the LLM layer, and ensuring the reliability and quality of the product.
Responsibilities:
• Design and ship new Command skills, the domain-specific instruction sets that teach the model how to handle workflows like sending money, managing invoices, and understanding cash flow
• Design and build agentic workflows in Command, defining the architecture for how multi-step agent interactions should work as we extend what the product can do on a customer's behalf
• Work with backend teams to define tool schemas for new capabilities, shaping the data contracts between Mercury's business logic and the model
• Own new capabilities end to end, from the system prompt to the frontend component that renders the response
• Maintain and evolve Command's prompt architecture: the system prompt, skill loading system, session context, and the policy and compliance layers underneath
• Tune model behavior: reasoning effort, prompt caching strategy, fallback chains, and the streaming patterns that make the product feel fast
• Stay current with how models are evolving and bring that knowledge back to how Command is built
• Write and expand Command's eval harness, adding cases that cover new capabilities and scoring rubrics that detect regressions before users do
• Partner with product and compliance teams to define what 'working correctly' means for each new capability, then build the tests that prove it
• Own the reliability and quality of what you ship, from initial design through post-launch monitoring
Qualifications:
Required:
• Has 7 or more years of software engineering experience, with deep technical expertise building and scaling LLM-powered applications in production
• Has gone beyond shipping a first version: you have scaled an LLM-powered product, dealt with the reliability and performance problems that come with real usage, and made it better over time
• Has experience designing agentic systems and has opinions about how to architect multi-step workflows that are reliable, explainable, and safe to run on behalf of real users
• Has built eval infrastructure and can write cases that actually measure whether the product works, not just whether the model outputs something plausible
• Understands the real tradeoffs in LLM deployments: latency, cost, compliance, and what breaks in production that doesn't show up in demos
• Has opinions about what makes an AI product trustworthy, not just impressive, and can build toward that bar
• Is comfortable with TypeScript and willing to learn Haskell for backend tool work, or already comfortable with both
• Can work across the full stack of an AI product, from the system prompt to the streaming frontend
• Has a track record of mentoring engineers and raising the technical bar of their team
Company:
Mercury provides digital banking and financial tools tailored for startups and modern businesses. Founded in 2017, the company is headquartered in San Francisco, USA, with a team of 1001-5000 employees. The company is currently Late Stage.