HackerTrans
TopNewTrendsCommentsPastAskShowJobs

codeviking

no profile record

comments

codeviking
·上個月·discuss
Runway | Multiple Engineering & Research roles | Remote (global) | Full-time

Runway is building AI to simulate the world — merging art and science. We're a team of researchers, engineers, artists, and designers shipping the models and infrastructure behind a new generation of creative tools.

We're hiring across a lot of teams right now (engineering, research, product, design — see the full list below), but a few we'd especially love to talk to you about:

  - Engineering Manager, API — https://jobs.ashbyhq.com/runway-ml/b5d136bb-4143-400b-914a-0ae7377ad8ed
  - MTS, Backend Engineer, API — https://jobs.ashbyhq.com/runway-ml/8489a08a-f0cf-4418-968c-c7c803d538bc
  - MTS, Research Engineer — https://jobs.ashbyhq.com/runway-ml/98e4b160-3bbe-4acd-b106-ad75ccc49675
Remote-friendly globally, with offices in NYC, SF, Seattle, London, Tel Aviv, and Tokyo. Full benefits (100% medical/dental/vision for US employees, unlimited PTO, parental leave, learning stipend).

Full list of open roles: https://runwayml.com/careers
codeviking
·7 個月前·discuss
I'm a big fan of lightweight, automated tests. Despite that, I still default to manual verification. Usually I do both.

Automated tests omit a certain type of feedback that I think remains important to the development loop. Automation doesn't care about a poor UX; it only verifies what you tell it to.

For instance, I regularly contribute to a CLI that's widely used at $WORK. I can easily write tests to verify the I/O of a command I'm working on that assert correctness. Yet if I actually try to use the command I'm changing, usually as part of verifying my changes, I tend to discover usability issues that make the program more pleasant to use and the tests would happily ignore.

Also, there's certainly cases where automation isn't worth the cost. Maybe because the resulting tests are complex, or brittle. I've often found UI tests to lie in this category (but maybe I'm doing them wrong).

Because of these things I think manual testing is the right default. Automated tests should also exist; but manual tests should _always_ be part of the process.
codeviking
·2 年前·discuss
Ai2 | Senior Software Engineer | Seattle, WA | ONSITE / HYBRID |

Ai2 (https://allenai.org) is a Seattle based non-profit AI research institute founded in 2014 by the late Paul Allen. We pursue foundational AI research and innovation to deliver real-world impact through large-scale open models, data, robotics, conservation, and beyond.

My team is a group of software engineers redefining how researchers and engineers use state of the art GPU clusters. We own and actively develop Beaker, a GPU-first job orchestration system used by Ai2 researchers to manage and execute frontier research workloads, such as large-scale, distributed pre-training and online reinforcement learning. We’re also responsible for Ai2’s on-premise GPU servers from the bare-metal up, operating a high performance storage cluster and designing and developing critical systems that teams across the institute rely on for pushing forward cutting-edge, open science.

We're looking for a Senior Software Engineer to join our team. You should be proficient in Go and Python and have prior experience operating and configuring linux servers in a professional setting.

https://job-boards.greenhouse.io/thealleninstitute/jobs/6157...
codeviking
·2 年前·discuss
Ai2 | Senior Software Engineer | Seattle, WA | ONSITE / HYBRID |

Ai2 (https://allenai.org) is a Seattle based non-profit AI research institute founded in 2014 by the late Paul Allen. We develop foundational AI research and innovation to deliver real-world impact through large-scale open models, data, robotics, conservation, and beyond.

My team (ReOps) maintains the software and servers that allow research teams at Ai2 to execute machine learning workloads on high performance, SOTA GPU clusters.

Most of our time is spent contributing to Beaker (https://blog.allenai.org/beaker-ed617d5f4593), a GPU-first job orchestration system that was authored at the institute. We also spend a fair amount of time configuring and operating the underlying on-premise GPU servers.

We're looking for a Senior Software Engineer to join our team. You should be proficient in Go and Python and have prior experience operating and configuring linux servers in a professional setting.

https://job-boards.greenhouse.io/thealleninstitute/jobs/6157...