Comment by legothief

Comment by legothief

VP of Engineering | REMOTE (EUROPEAN TIME ZONES) | STARTUP | FULL-TIME

If you have a soft spot for bootstrapped, profitable companies with a meaningful product, and you would like to develop a small, super-capable technical team in a refreshing work environment, you might quite like this extremely rare executive position at Drops.

WHOM WE'RE AFTER:

You’ll be responsible for the tech team’s effectiveness, well-being and development, and that its working aligns well to the business’ and our users’ needs.

You’ll be making sure that the technical aspects of the projects are getting done on schedule, that we’re making the right trade-offs.

You’ll be leading, mentoring, managing the people who are part of the tech team.

You’ll be recruiting, onboarding top talent, sometimes. We’re a small team, and we’re not expecting to grow the headcount a lot (but we do expect to grow the impact each of us have!).

You’ll be working closely together with the leadership team, to lay down the tracks for future product and infrastructural expansion.

You’ll be in charge of flourishing our engineering culture - organise information sharing, hackathons, processes, developing new, helpful routines.

We value clear and honest communication and transparency, it’s the linchpin of our culture and current success and independency.

You will be involved in both high and low level decision making and will be available during European working hours (9AM - 6PM GMT).

We are looking for a missionary rather than a mercenary.

WHAT'D BE DIFFERENT HERE:

We’re a small team. We’re optimising for impact, not for headcount. You’ll be carefully considering any tradeoff that would lead to increased complexity.

We’re using a single programming language - TypeScript. We have strict linter rules. Every pull request needs to be approved before it lands in master. We use the rebase workflow.

We’re using React to develop UI, on both mobile and the web.

We’re doing things in a functional way, concentrating state, minimising side effects and making dependencies explicit.

We’re sharing 98%+ of the code between Android, iOS and Web.

We’re writing software with a web developer’s mindset.

We automate where it has positive ROI. Our biggest challenge is (and will remain): managing the complexity of sharing a lot of code between different apps.

We’re not building a hierarchy. We’re encouraging everyone to be autonomous. You’ll _not_ be an arbitrator between business and engineering. You’ll be helping both project owners and the tech team to work more closely together.

Your average day will be about helping with team members make technical decision, adjusting processes as needed, doing research and automation, actually developing software and also, recruiting.

REQUIREMENTS

Can see a problem from the product, business’ and the team’s perspective.

You have excellent technical and people skills. (yes, we know, it’s rare!)

You are more of a frontend than a backend engineer. (we’re frontend heavy)

You held senior software engineering management position such as CTO, Head of Development, or VP of Engineering positions in the past and enjoyed it.

You have introspective tendencies, and you’re looking for a position where you can grow fast.

You can represent the technology, infrastructure, and the engineering team at the executive level.

Replies legothief · 2019-09-04
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. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

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

Privacy policy · Terms of use

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 story above or below in the list, in the same article reader. Back returns to the story you came from.
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 Previous and Next buttons read up and 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, Previous and 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.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

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 is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. 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 anonymously and is included in retained applet state when signed in.

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. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

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