Comment by seebq2

Back to stories Open in a window

Comment by seebq2

DevOps Engineer - Robotics Atlanta, GA Full-Time Greenzie is hiring a DevOps Engineer on our Robotics team to further our mission to free humans from repetitive outdoor labor. We’re accepting applications on an on-going basis, with flexible start dates, but ideally we’d have someone tomorrow if we could.

JOB DESCRIPTION As a Robotics DevOps Engineer you will ensure building, testing, and deploying is a smooth and stable process, so that robotics engineers can focus on robotics development. You will:

* Collaborate with robotics engineers and customers to manage code releases and deployments * Manage, analyze, and toss out (and save a little bit) of the massive amount of data we collect * Develop software, build pipelines, scripts, and documentation to improve the way we build, deploy, and test * Code-review, pair-program, and problem solve with teammates

This position will also involve daily stand-up meetings, weekly team meetings, high level architecture meetings, retrospectives, and long term strategic road-map planning. And the best thing is, we’re a startup and we need your help in continuing to build a great company: if you want to be involved in other areas of the company, it's up to you. From customer discovery to sales and marketing, the field is wide open for you to participate and help us fulfill our mission.

Important: this position is focused on helping the robotics team test and deploy code to our fleet of robotic mowers, not assisting the web platform team on a traditional web application stack.

ABOUT YOU As a candidate you already:

* Have DevOps experience deploying things into production Have experience with Linux (Ubuntu LTS preferred), Docker, CircleCI, and more * Are familiar with debian package management and best practices * Have programmed in Python or similar Object Oriented languages * Know Git, Bash and your way around a terminal * Desire to free humans from hard, manual labor

As a bonus, you may already have experience:

* Working in the robotics industry or knowledge of ROS * Working with ARM-based systems and cross-compilation * Have working knowledge of VPNs, certificates, and other security tools * Building test infrastructure or automated test frameworks * Familiarity with AWS tools

You may have a Computer Science or direct engineering degree. You may not. That’s not necessarily top of mind for us: we value what you can do, not just how you learned to do it. Solid code and strong experience is just as valuable to us.

We have big goals, but try to zoom out on high-level initiatives when appropriate to get day to day work, week to week planning, and big quarterly projects done. You can expect an on-boarding process involving safety training (we’re big on safety), some mindful “brain dumps,” and space and time to learn and figure out how to work best. We seek to provide feedback quickly and often, we praise publicly, and deliver critical feedback privately. You can expect to be given meaningful work, to take ownership of features, processes, and to deliver working code and product. We are in this for the long haul. We need your help.

Direct at { cbq at greenzie dot com }

Replies seebq2 · 2024-02-13
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.